From: Jakub Kicinski <kuba@kernel.org>
To: David Heidelberg <david@ixit.cz>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, oe-linux-nfc@lists.linux.dev
Subject: Re: NFC for next-20260609
Date: Wed, 10 Jun 2026 08:48:25 -0700 [thread overview]
Message-ID: <20260610084825.64763972@kernel.org> (raw)
In-Reply-To: <b3084b2a-f8fa-4bba-8a92-1a14fbacb622@ixit.cz>
On Tue, 9 Jun 2026 10:45:21 +0200 David Heidelberg wrote:
> The following changes since commit 4549871118cf616eecdd2d939f78e3b9e1dddc48:
>
> Linux 7.1-rc7 (2026-06-07 15:37:58 -0700)
This should be based on net-next if you're sending a PR to net-next.
Normal flow of history is something like:
net-next - x - x - ... - x - merge - x - ...
\ / \
`- x - x - x - x [PR] ` x - ...
Note that net and net-next do the same dance of periodic merges,
and net does a periodic dance with Linus's tree, which is how
we get changes propagate from the tree with fixes to -next trees.
Problem 2 - the subject says next but the tag says "nfc pull request
for net:", which one is it? :)
^^^
Could you rebase the patches on top of net-next if that's your intended
target or net if you meant net?
prev parent reply other threads:[~2026-06-10 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 8:45 NFC for next-20260609 David Heidelberg
2026-06-10 15:48 ` Jakub Kicinski [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=20260610084825.64763972@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=david@ixit.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-linux-nfc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.