public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel•org>
To: Thierry Reding <thierry.reding@kernel•org>
Cc: David Heidelberg <david@ixit•cz>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: omission of the nfc tree
Date: Wed, 6 May 2026 11:21:47 +0900	[thread overview]
Message-ID: <afqlu-wFE7xEuN36@sirena.co.uk> (raw)
In-Reply-To: <afnugiRnPPMCIxO6@arch.a226c7d-lcedt>

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

On Tue, May 05, 2026 at 03:57:29PM +0200, Thierry Reding wrote:
> On Tue, May 05, 2026 at 11:47:10AM +0200, David Heidelberg wrote:

> > sorry about that, should be fixed (rebased against -rc2 now).

> > Is there strong insensitive to use -rc1? In case it causing additional work,
> > I can stick with rc1.

> -rc2 is fine, too. Anything from Linus' tree should be fine, really,
> since Linus' tree is the base for linux-next.

Linus tends to prefer that it's a tag rather than a random commit from
his tree, but otherwise as Thierry says anything from his tree should be
fine (and a random commit is almost certainly fine in practice anyway).

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

      reply	other threads:[~2026-05-06  2:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04 20:50 linux-next: omission of the nfc tree Thierry Reding
2026-05-05  9:47 ` David Heidelberg
2026-05-05 13:57   ` Thierry Reding
2026-05-06  2:21     ` Mark Brown [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=afqlu-wFE7xEuN36@sirena.co.uk \
    --to=broonie@kernel$(echo .)org \
    --cc=david@ixit$(echo .)cz \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=thierry.reding@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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