public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@kernel.org>
To: David Heidelberg <david@ixit.cz>
Cc: 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: Tue, 5 May 2026 15:57:29 +0200	[thread overview]
Message-ID: <afnugiRnPPMCIxO6@arch.a226c7d-lcedt> (raw)
In-Reply-To: <6d26fbb6-3885-47b5-bfba-6c84bcc42f89@ixit.cz>

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

On Tue, May 05, 2026 at 11:47:10AM +0200, David Heidelberg wrote:
> Hello Thierry,
> 
> 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.

The idea is that you should pull in only as much as necessary to reduce
dependencies and complexity. If you need to pull in some other tree (to
satisfy a dependency, for example, always make sure to work with the
corresponding maintainer to ensure they keep the branch that you pull in
stable (i.e. don't rebase it), otherwise things will get ugly and we
start pulling multiple versions of the same commits, etc.

Thierry

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

      reply	other threads:[~2026-05-05 13:57 UTC|newest]

Thread overview: 3+ 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 [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=afnugiRnPPMCIxO6@arch.a226c7d-lcedt \
    --to=thierry.reding@kernel.org \
    --cc=david@ixit.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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