DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, "Stephen Hemminger" <stephen@networkplumber.org>,
	"Ruifeng Wang" <ruifeng.wang@arm.com>,
	"Jan Viktorin" <viktorin@rehivetech.com>,
	"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
	"Joyce Kong" <joyce.kong@arm.com>,
	"David Christensen" <drc@linux.vnet.ibm.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>,
	"Konstantin Ananyev" <konstantin.v.ananyev@yandex.ru>,
	"Stanisław Kardach" <kda@semihalf.com>
Subject: Re: [PATCH v2] eal: remove unused arch specific headers for locks
Date: Wed, 08 Jun 2022 15:46:13 +0200	[thread overview]
Message-ID: <10091158.nUPlyArG6x@thomas> (raw)
In-Reply-To: <CALVGJWJ4uL4_vb_JFm1ircuofsiw=PuL946jiQHzfL=wL2mKhg@mail.gmail.com>

08/06/2022 15:16, Stanisław Kardach:
> On Wed, Jun 8, 2022 at 1:57 PM David Marchand <david.marchand@redhat.com> wrote:
> >
> > MCS lock, PF lock and Ticket lock have no arch specific implementation,
> > there is no need for the extra redirection in headers.
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > Acked-by: Stephen Hemminger <stephen@networkplumber.org>
> > ---
> > Note: this was mentionned during the seqlock patch review, and I spotted
> > it again, while reviewing the RISC-V port, and I see the same for a next
> > architecture too. So better clean this up as we don't need the
> > redirection.
> >
> > Changes since v1:
> > - rebased following RISC-V merge,
> >
> Thanks, this works just fine for RISC-V.
> 
> Acked-by: Stanislaw Kardach <kda@semihalf.com>

Applied, thanks.




      reply	other threads:[~2022-06-08 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 19:03 [PATCH] " David Marchand
2022-06-07 20:34 ` Stephen Hemminger
2022-06-08 11:57 ` [PATCH v2] " David Marchand
2022-06-08 13:16   ` Stanisław Kardach
2022-06-08 13:46     ` Thomas Monjalon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=10091158.nUPlyArG6x@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=joyce.kong@arm.com \
    --cc=kda@semihalf.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=ruifeng.wang@arm.com \
    --cc=stephen@networkplumber.org \
    --cc=viktorin@rehivetech.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).