From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Paolo Abeni <pabeni@redhat.com>, torvalds@linux-foundation.org
Cc: kuba@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Networking for Linux 7.0
Date: Wed, 11 Feb 2026 15:07:18 -0800 [thread overview]
Message-ID: <76e6b68c-393e-48d4-9ee5-9e8d511ab308@oss.qualcomm.com> (raw)
In-Reply-To: <20260211173015.327542-1-pabeni@redhat.com>
On 2/11/2026 9:30 AM, Paolo Abeni wrote:
> Hi Linus!
>
> I'm not aware of any conflicts with other trees, even if this includes some
> changes to printk for the sake of netconsole.
There is one conflict between the refactored ath12k driver and the char-misc
tree. This was correctly addressed in linux-next:
https://lore.kernel.org/linux-next/aXD6X23btw8s-RZP@sirena.org.uk/
/jeff
next prev parent reply other threads:[~2026-02-11 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 17:30 [GIT PULL] Networking for Linux 7.0 Paolo Abeni
2026-02-11 23:07 ` Jeff Johnson [this message]
2026-02-11 23:40 ` Jakub Kicinski
2026-02-12 15:51 ` Jeff Johnson
2026-02-12 3:58 ` 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=76e6b68c-393e-48d4-9ee5-9e8d511ab308@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--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