From: Paul Walmsley <pjw@kernel.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Alexandre Ghiti <alexghiti@rivosinc.com>,
linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
atish.patra@linux.dev, anup@brainfault.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] riscv: Replace __ASSEMBLY__ with __ASSEMBLER__ in header files
Date: Fri, 12 Sep 2025 19:33:00 -0600 (MDT) [thread overview]
Message-ID: <d34c4b47-4acd-fd68-4cdf-b9cfaf022a32@kernel.org> (raw)
In-Reply-To: <d1fe7fdf-b3da-4c53-8a5a-a87acd38d525@redhat.com>
Hi Thomas,
On Mon, 18 Aug 2025, Thomas Huth wrote:
> On 06/08/2025 19.15, patchwork-bot+linux-riscv@kernel.org wrote:
> > Hello:
> >
> > This series was applied to riscv/linux.git (for-next)
> > by Alexandre Ghiti <alexghiti@rivosinc.com>:
>
> Hi Alexandre,
>
> I can't see the patches in the for-next branch ... have they been dropped
> again? Was there an issue with the patches?
No issues with your patches; we just had some trouble getting the
arch/riscv PR merged during the last merge window. I've queued both of
your patches for v6.18. They should show up in for-next in a few days.
Thanks,
- Paul
WARNING: multiple messages have this Message-ID (diff)
From: Paul Walmsley <pjw@kernel.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Alexandre Ghiti <alexghiti@rivosinc.com>,
linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
atish.patra@linux.dev, anup@brainfault.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] riscv: Replace __ASSEMBLY__ with __ASSEMBLER__ in header files
Date: Fri, 12 Sep 2025 19:33:00 -0600 (MDT) [thread overview]
Message-ID: <d34c4b47-4acd-fd68-4cdf-b9cfaf022a32@kernel.org> (raw)
In-Reply-To: <d1fe7fdf-b3da-4c53-8a5a-a87acd38d525@redhat.com>
Hi Thomas,
On Mon, 18 Aug 2025, Thomas Huth wrote:
> On 06/08/2025 19.15, patchwork-bot+linux-riscv@kernel.org wrote:
> > Hello:
> >
> > This series was applied to riscv/linux.git (for-next)
> > by Alexandre Ghiti <alexghiti@rivosinc.com>:
>
> Hi Alexandre,
>
> I can't see the patches in the for-next branch ... have they been dropped
> again? Was there an issue with the patches?
No issues with your patches; we just had some trouble getting the
arch/riscv PR merged during the last merge window. I've queued both of
your patches for v6.18. They should show up in for-next in a few days.
Thanks,
- Paul
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-09-13 1:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 7:09 [PATCH v2 0/2] riscv: Replace __ASSEMBLY__ with __ASSEMBLER__ in header files Thomas Huth
2025-06-06 7:09 ` Thomas Huth
2025-06-06 7:09 ` [PATCH v2 1/2] riscv: Replace __ASSEMBLY__ with __ASSEMBLER__ in uapi headers Thomas Huth
2025-06-06 7:09 ` Thomas Huth
2025-06-06 7:09 ` [PATCH v2 2/2] riscv: Replace __ASSEMBLY__ with __ASSEMBLER__ in non-uapi headers Thomas Huth
2025-06-06 7:09 ` Thomas Huth
2025-07-27 13:29 ` [PATCH v2 0/2] riscv: Replace __ASSEMBLY__ with __ASSEMBLER__ in header files Alexandre Ghiti
2025-07-27 13:29 ` Alexandre Ghiti
2025-08-06 17:15 ` patchwork-bot+linux-riscv
2025-08-06 17:15 ` patchwork-bot+linux-riscv
2025-08-18 6:08 ` Thomas Huth
2025-08-18 6:08 ` Thomas Huth
2025-08-19 20:17 ` Alexandre Ghiti
2025-08-19 20:17 ` Alexandre Ghiti
2025-09-13 1:33 ` Paul Walmsley [this message]
2025-09-13 1:33 ` Paul Walmsley
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=d34c4b47-4acd-fd68-4cdf-b9cfaf022a32@kernel.org \
--to=pjw@kernel.org \
--cc=alex@ghiti.fr \
--cc=alexghiti@rivosinc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.