All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: David Heidelberg <david@ixit.cz>
Cc: Paolo Abeni <pabeni@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	oe-linux-nfc@lists.linux.dev
Subject: Re: [pull-request] NFC updates for next-next 2026-08-17
Date: Mon, 17 Aug 2026 11:53:25 -0700	[thread overview]
Message-ID: <20260817115325.4333587c@kernel.org> (raw)
In-Reply-To: <93a47987-885f-4e5f-8920-788fb281db67@ixit.cz>

On Mon, 17 Aug 2026 19:45:45 +0200 David Heidelberg wrote:
> The following changes since commit 8d3ae59288f1e7d58d76558a6ee96d533bc5019f:
> 
>    Linux 7.2 (2026-08-16 14:32:26 -0700)
> 
> are available in the Git repository at:
> 
>    https://codeberg.org/linux-nfc/linux.git tags/nfc-net-next-20260817

Please don't rebase your trees. The base of your tree should be at
whatever point net-next was after the previous PR to net-next.
Because:
 - we don't have the 7.2 tag in our trees yet, if I merge this it will
   look like I pulled a week worth of Linus's tree, not a small PR from
   you
 - the commit hashes in linux-next do not match what you have in this PR

Did you rebase this tree recently? Perhaps you still have the previous
version in git reflog that we could pull instead? Exceptionally, this
time you may need to rebase to go back to an older base..

BTW normally to get your own fixes into your own -next tree you should
stagger the PRs - first send the fixes, after net -> net-next merge on
Thu afternoon - send the -next PR.


  reply	other threads:[~2026-08-17 18:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 17:45 [pull-request] NFC updates for next-next 2026-08-17 David Heidelberg
2026-08-17 18:53 ` Jakub Kicinski [this message]
2026-08-17 20:03   ` David Heidelberg

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=20260817115325.4333587c@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 \
    --cc=pabeni@redhat.com \
    /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.