From: Drew Fustini <fustini@kernel.org>
To: Paul Walmsley <pjw@kernel.org>
Cc: soc@kernel.org, Alexandre Belloni <alexandre.belloni@bootlin.com>,
Arnd Bergmann <arnd@arndb.de>, Linus Walleij <linusw@kernel.org>,
Conor Dooley <conor@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [GIT PULL] RISC-V defconfig changes for v7.3
Date: Tue, 4 Aug 2026 20:40:07 -0700 [thread overview]
Message-ID: <anKwl/5re7CMFTXF@x1> (raw)
In-Reply-To: <55196187-178b-1f88-0947-1612410372e0@kernel.org>
On Tue, Aug 04, 2026 at 08:54:21PM -0600, Paul Walmsley wrote:
> Hi,
>
> On Tue, 21 Jul 2026, Drew Fustini wrote:
>
> > Hi, I created my riscv-confg branches to shepard defconfig patches
> > related to the riscv platforms that I maintain. The branches are in
> > linux-next. For 7.3, there is just a single patch for the WiFi driver on
> > the TH1520-based LPi4a.
>
> Looks like this one hasn't gone anywhere, so maybe I'll just take that
> patch into riscv for-next. Thanks Drew
>
>
> - Paul
Thank you for checking but this was already pulled by Arnd:
https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/commit/?id=6495ae297ceb
It seems the patchwork reply had a narrow scope compared to my post:
https://lore.kernel.org/all/178491121788.3229915.9040423834090729571.git-patchwork-notify@kernel.org/
Thanks,
Drew
next prev parent reply other threads:[~2026-08-05 3:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 16:20 [GIT PULL] RISC-V defconfig changes for v7.3 Drew Fustini
2026-08-05 2:54 ` Paul Walmsley
2026-08-05 3:40 ` Drew Fustini [this message]
2026-08-05 14:42 ` 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=anKwl/5re7CMFTXF@x1 \
--to=fustini@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=conor@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=pjw@kernel.org \
--cc=soc@kernel.org \
/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