From: Dinh Nguyen <dinguyen@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>, arm <arm@kernel.org>, soc@kernel.org
Cc: soc@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: socfpga: updates for v6.16
Date: Mon, 12 May 2025 21:28:11 -0500 [thread overview]
Message-ID: <d3615e4f-4107-4f76-9e8d-c19fcf43c816@kernel.org> (raw)
In-Reply-To: <b8257b35-04b7-400b-bc58-948dd5fdf799@app.fastmail.com>
On 5/10/25 15:18, Arnd Bergmann wrote:
> On Tue, May 6, 2025, at 02:48, Dinh Nguyen wrote:
>> The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:
>>
>> Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)
>>
>> are available in the Git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git
>> tags/socfpga_dts_updates_for_v6.16
>>
>> for you to fetch changes up to 8dbffe5f5dd531a3c3f9d603462e499085449277:
>>
>> dt-bindings: clock: socfpga: convert to yaml (2025-05-03 13:33:23 -0500)
>>
>> ----------------------------------------------------------------
>> SoCFPGA DTS updates for v6.16
>> - Updates to dt-bindings
>> - Document Agilex5 NAND daughter board
>> - Convert Stratix10 FPGA Manager to json-schema
>> - Convert Stratix10 Service Layer to json-schema
>> - Add document for Terasic's DE10-nano board
>> - Add support for Agilex5 NAND daughter board
>> - Add basic support for Terasic's DE10-nano board
>
> Hi Dinh,
>
> I'm not sure exactly what happened, but I see that this is
> almost the same as the previous pull request that you had sent
> for 6.15 in late march.
>
> I had already pulled in the previous version, and if I pull
> this one now it would result in duplicate commits. Would
> it work for you if I just cherry-pick the "dt-bindings:
> clock: socfpga: convert to yaml" patch on top, to avoid
> rebasing everything else?
I apologize, I just assumed that since I missed the 6.15 window, that it
would gone and I'd rebase for v6.16. They are the same patches. I'll
remember that next time. Yes, just the "dt-bindings: clock: socfpga:
convert to yaml" patch would be fine.
>
> Note: the list address has changed again, so please send
> future pull requests to soc@lists.linux.dev, cc:linux-arm-kernel.
> The arm@kernel.org and soc@kernel.org aliases still work
> for the moment, but the real address is the @lists.linux.dev
> one.
>
Noted.
Thanks,
Dinh
prev parent reply other threads:[~2025-05-13 2:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 0:48 [GIT PULL] ARM: socfpga: updates for v6.16 Dinh Nguyen
2025-05-10 20:18 ` Arnd Bergmann
2025-05-13 2:28 ` Dinh Nguyen [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=d3615e4f-4107-4f76-9e8d-c19fcf43c816@kernel.org \
--to=dinguyen@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@kernel.org \
--cc=soc@lists.linux.dev \
/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