public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Thierry Reding <thierry.reding@kernel•org>
To: David Heidelberg <david@ixit•cz>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: Adding NFC tree to -next
Date: Mon, 4 May 2026 21:21:56 +0200	[thread overview]
Message-ID: <afjxJyTag9YT1How@arch.a226c7d-lcedt> (raw)
In-Reply-To: <f50c0c1e-ad33-46d9-a9b5-ab56c82a17d6@ixit.cz>

[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]

On Sun, May 03, 2026 at 12:47:42PM +0200, David Heidelberg wrote:
> Hi Mark,
> 
> Could you please add
> 
>   https://codeberg.org/linux-nfc/linux.git for-linus
>   https://codeberg.org/linux-nfc/linux.git for-next
> 
> to -next?
>   for-linus will typically include fixes for NFC targeting the current
> development cycle.
>   for-next include things for the next merge window.
> 
> If there are any issues or questions, please let me know.

I've added this from today. I'm a bit behind on schedule because I've
been battling with a new setup, but this should be part of today's
release if I manage to finish it in time.

I've added you as contact for the tree. If you want anyone else (or a
mailing list) to be listed, please let me know.

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.

Thanks,
Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

     prev parent reply	other threads:[~2026-05-04 19:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03 10:47 Adding NFC tree to -next David Heidelberg
2026-05-03 18:19 ` Randy Dunlap
2026-05-04 19:21 ` Thierry Reding [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=afjxJyTag9YT1How@arch.a226c7d-lcedt \
    --to=thierry.reding@kernel$(echo .)org \
    --cc=david@ixit$(echo .)cz \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox