public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Jakub Kicinski <kuba@kernel.org>, mhi@lists.linux.dev
Cc: Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Networking for Linux 7.0
Date: Thu, 12 Feb 2026 07:51:51 -0800	[thread overview]
Message-ID: <5afc9deb-e6c8-4224-b96d-5e8a2ebf7de3@oss.qualcomm.com> (raw)
In-Reply-To: <20260211154008.24db40a7@kernel.org>

On 2/11/2026 3:40 PM, Jakub Kicinski wrote:
> On Wed, 11 Feb 2026 15:07:18 -0800 Jeff Johnson wrote:
>> 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/
> 
> Will there be an effort at some point to improve how the MHI "bus"
> is structured? Maybe this is not a great example but we keep seeing
> patches that touch a driver + the bus. Clearly indicating IMHO that
> there's no proper abstraction / separation between the bus and its
> users..

+ MHI list to comment on this

  reply	other threads:[~2026-02-12 15:51 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
2026-02-11 23:40   ` Jakub Kicinski
2026-02-12 15:51     ` Jeff Johnson [this message]
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=5afc9deb-e6c8-4224-b96d-5e8a2ebf7de3@oss.qualcomm.com \
    --to=jeff.johnson@oss.qualcomm.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhi@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox