From: Andrea Parri <parri.andrea@gmail.com>
To: "Leonardo Brás" <leobras@redhat.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Guo Ren <guoren@kernel.org>,
Conor Dooley <conor.dooley@microchip.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v1 0/2] Deduplicating RISCV cmpxchg.h macros
Date: Thu, 3 Aug 2023 05:14:41 +0200 [thread overview]
Message-ID: <ZMsboVmlrWhjfNJd@andrea> (raw)
In-Reply-To: <2f301cd6c4009248c5eb6af00f12f36f3127ca10.camel@redhat.com>
> > LGTM. AFAICT, this would need to be rebased, cf. e.g.
> >
> > a8596dda1fbf7e ("arch: rename all internal names __xchg to __arch_xchg")
> >
> > from the tip tree.
> >
> > Andrea
>
> Thanks for the heads up!
> I will update this and re-send!
>
>
> And sorry about the delay :(
> For some weird reason neither the cover letter, nor your message reached my
> gmail, and just now looking at lore I could find your message.
All's well that ends well. ;-) Thanks,
Andrea
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-08-03 3:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 8:20 [RFC PATCH v1 0/2] Deduplicating RISCV cmpxchg.h macros Leonardo Bras
2023-04-06 8:20 ` [RFC PATCH v1 1/2] riscv/cmpxchg: Deduplicate cmpxchg() asm and macros Leonardo Bras
2023-04-07 8:29 ` Guo Ren
2023-04-18 19:10 ` Leonardo Bras Soares Passos
2023-04-06 8:20 ` [RFC PATCH v1 2/2] riscv/cmpxchg: Deduplicate xchg() asm functions Leonardo Bras
2023-04-07 8:31 ` Guo Ren
2023-04-06 17:19 ` [RFC PATCH v1 0/2] Deduplicating RISCV cmpxchg.h macros Andrea Parri
2023-08-02 21:51 ` Leonardo Brás
2023-08-03 3:14 ` Andrea Parri [this message]
2023-08-03 6:12 ` Leonardo Brás
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=ZMsboVmlrWhjfNJd@andrea \
--to=parri.andrea@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=guoren@kernel.org \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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