public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: Include Altera's SoCFPGA tree
Date: Wed, 25 Feb 2026 06:46:23 -0600	[thread overview]
Message-ID: <dc81bd41-3957-486a-8a8b-272798e49341@kernel.org> (raw)
In-Reply-To: <42b96da6-ffb3-4fd9-8821-9093a323507c@sirena.org.uk>



On 2/25/26 06:37, Mark Brown wrote:
> On Tue, Feb 24, 2026 at 10:25:58PM -0600, Dinh Nguyen wrote:
>> Hi linux-next maintainers,
>>
>> Could you please add the SoCFPGA tree to linux-next? The branch contains
>> patches intended for the next merge window for the SoCFPGA subsystem.
>>
>>
>> Git Repo: https://git.kernel.org/pub/scm/linux/kernel/git/dinguyen/linux.git
>>
>> Branch: for-next
> 
> I've added this, all being well it will appear in today's next.
> 
> Thanks for adding your subsystem tree as a participant of linux-next.  As
> you may know, this is not a judgement of your code.  The purpose of
> linux-next is for integration testing and to lower the impact of
> conflicts between subsystems in the next merge window.
> 
> You will need to ensure that the patches/commits in your tree/series have
> been:
>       * submitted under GPL v2 (or later) and include the Contributor's
>          Signed-off-by,
>       * posted to the relevant mailing list,
>       * reviewed by you (or another maintainer of your subsystem tree),
>       * successfully unit tested, and
>       * destined for the current or next Linux merge window.
> 
> Basically, this should be just what you would send to Linus (or ask him
> to fetch).  It is allowed to be rebased if you deem it necessary.

Thank you so much!

Dinh

      reply	other threads:[~2026-02-25 12:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25  4:25 Include Altera's SoCFPGA tree Dinh Nguyen
2026-02-25 12:37 ` Mark Brown
2026-02-25 12:46   ` 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=dc81bd41-3957-486a-8a8b-272798e49341@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=broonie@kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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