mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jakub Kicinski <kuba@kernel.org>,
	Tim Hostetler <thostet@google.com>,
	Richard Cochran <richardcochran@gmail.com>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Harshitha Ramamurthy <hramamurthy@google.com>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	Miri Korenblit <miriam.rachel.korenblit@intel.com>
Subject: Re: [GIT PULL] Networking for Linux 6.19
Date: Mon, 22 Dec 2025 11:09:21 +0100	[thread overview]
Message-ID: <e0410b3b-c831-4c9c-9ee9-351315759291@redhat.com> (raw)
In-Reply-To: <221ba5ce-8652-4bc4-8d4a-6fc379e32ef8@hartkopp.net>

On 12/22/25 8:48 AM, Oliver Hartkopp wrote:
> There's already a fix tested by many people which is not getting 
> upstream for some reason ... ¯\_(ツ)_/¯
> 
> https://lore.kernel.org/netdev/20251204123204.9316-1-ziyao@disroot.org/

Such patch has to travel 3 sub-trees (iwlwifi, wireless and net) before
reaching mainline. Also there is a relevant patch processing capacity
reduction due to conferences and EoY celebrations.

AFAICS such patch is in Johannes tree right now. I'll coordinate with
him to move it forward in a reasonable time.

Cheers,

Paolo


      reply	other threads:[~2025-12-22 10:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 23:49 Jakub Kicinski
2025-12-04  2:50 ` pr-tracker-bot
2025-12-22  0:17 ` Linus Torvalds
2025-12-22  7:48   ` Oliver Hartkopp
2025-12-22 10:09     ` Paolo Abeni [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=e0410b3b-c831-4c9c-9ee9-351315759291@redhat.com \
    --to=pabeni@redhat.com \
    --cc=davem@davemloft.net \
    --cc=hramamurthy@google.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miriam.rachel.korenblit@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=socketcan@hartkopp.net \
    --cc=thostet@google.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vadim.fedorenko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®