From: Jakub Kicinski <kuba@kernel.org>
To: torvalds@linux-foundation.org
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PULL] Networking for v6.1-rc8 (part 1)
Date: Mon, 28 Nov 2022 19:39:29 -0800 [thread overview]
Message-ID: <20221128193929.3e7384d2@kernel.org> (raw)
In-Reply-To: <20221129025219.2374322-1-kuba@kernel.org>
On Mon, 28 Nov 2022 18:52:19 -0800 Jakub Kicinski wrote:
> Hi Linus!
>
> I disappeared for Thanksgiving without communicating properly
> which resulted in some confusion on our side and things not
> getting merged up correctly, so flushing the queue again.
> Probably for the best given some of the patches here.
There is a clang warning in one of the mlx5 fixes here, which got
flagged by our CI/build system but it wasn't noticed. So you may
want to toss this PR and we'll retry again. Apologies.
next prev parent reply other threads:[~2022-11-29 3:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 2:52 [PULL] Networking for v6.1-rc8 (part 1) Jakub Kicinski
2022-11-29 3:39 ` Jakub Kicinski [this message]
2022-11-29 20:15 ` pr-tracker-bot
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=20221128193929.3e7384d2@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).