From: Andy Gospodarek <andrew.gospodarek@broadcom.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
bhelgaas@google.com, Wei Huang <wei.huang2@amd.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, asml.silence@gmail.com,
almasrymina@google.com, michael.chan@broadcom.com,
ajit.khaparde@broadcom.com, somnath.kotur@broadcom.com,
andrew.gospodarek@broadcom.com, manoj.panicker2@amd.com,
Eric.VanTassell@amd.com
Subject: Re: [PATCH V1 1/2] bnxt_en: Add TPH support in BNXT driver
Date: Fri, 15 Nov 2024 17:28:37 -0500 [thread overview]
Message-ID: <ZzfLFSvHCaPgVPzH@JRM7P7Q02P.dhcp.broadcom.net> (raw)
In-Reply-To: <20241115222038.GA2063216@bhelgaas>
On Fri, Nov 15, 2024 at 04:20:38PM -0600, Bjorn Helgaas wrote:
> On Fri, Nov 15, 2024 at 02:04:34PM -0800, Jakub Kicinski wrote:
> > ...
> > Bjorn, do you have a strong preference to have a user of the TPH code
> > merged as part of 6.13? We're very close to the merge window, I'm not
> > sure build bots etc. will have enough time to hammer this code.
> > My weak preference would be to punt these driver changes to 6.14
> > avoid all the conflicts and risks (unless Linus gives us another week.)
>
> I do not have a preference. The PCI core changes are queued for
> v6.13, so driver changes will be able to go the normal netdev route
> for v6.14.
>
> I agree it seems late to add significant things for v6.13.
>
Excellent. Thank you!
next prev parent reply other threads:[~2024-11-15 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 20:04 [PATCH V1 0/2] Enable TPH support in BNXT driver Wei Huang
2024-11-15 20:04 ` [PATCH V1 1/2] bnxt_en: Add " Wei Huang
2024-11-15 22:04 ` Jakub Kicinski
2024-11-15 22:19 ` Michael Chan
2024-11-15 22:20 ` Bjorn Helgaas
2024-11-15 22:28 ` Andy Gospodarek [this message]
2025-01-08 11:33 ` Jiri Slaby
2025-01-09 19:09 ` Wei Huang
2025-01-09 19:17 ` Michael Chan
2024-11-15 20:04 ` [PATCH V1 2/2] bnxt_en: Pass NQ ID to the FW when allocating RX/RX AGG rings Wei Huang
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=ZzfLFSvHCaPgVPzH@JRM7P7Q02P.dhcp.broadcom.net \
--to=andrew.gospodarek@broadcom.com \
--cc=Eric.VanTassell@amd.com \
--cc=ajit.khaparde@broadcom.com \
--cc=almasrymina@google.com \
--cc=asml.silence@gmail.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=helgaas@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=manoj.panicker2@amd.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=somnath.kotur@broadcom.com \
--cc=wei.huang2@amd.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;
as well as URLs for NNTP newsgroup(s).