From: Jakub Kicinski <kuba@kernel.org>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>, <linux-pci@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>, <netdev@vger.kernel.org>,
<intel-wired-lan@lists.osuosl.org>,
<linux-kernel@vger.kernel.org>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@linux.intel.com>
Subject: Re: [Intel-wired-lan] [PATCH 2/9] e1000e: Remove redundant pci_enable_pcie_error_reporting()
Date: Thu, 19 Jan 2023 21:35:57 -0800 [thread overview]
Message-ID: <20230119213557.57598e8f@kernel.org> (raw)
In-Reply-To: <2c722338-c113-14a1-040b-70326e2e2451@intel.com>
On Thu, 19 Jan 2023 13:31:39 -0800 Tony Nguyen wrote:
> > Thanks a million for taking a look at these, Tony!
> >
> > These driver patches are all independent and have no dependency on the
> > 1/9 PCI/AER patch. What's your opinion on merging these? Should they
> > go via netdev? Should they be squashed into a single patch that does
> > all the Intel drivers at once?
> >
> > I'm happy to squash them and/or merge them via the PCI tree, whatever
> > is easiest.
>
> Since there's no dependency, IMO, it'd make sense to go through
> Intel-wired-lan/netdev. Keeping them per driver is fine.
Ah, damn, I spammed Bjorn with the same question because email was
pooped most of the day :/ Reportedly not vger, email in general but
fool me once...
Tony, if you could take these via your tree that'd be best.
next prev parent reply other threads:[~2023-01-20 5:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230118234612.272916-1-helgaas@kernel.org>
2023-01-18 23:46 ` [PATCH 2/9] e1000e: Remove redundant pci_enable_pcie_error_reporting() Bjorn Helgaas
2023-01-19 18:28 ` Tony Nguyen
2023-01-19 18:40 ` [Intel-wired-lan] " Bjorn Helgaas
2023-01-19 21:31 ` Tony Nguyen
2023-01-20 5:35 ` Jakub Kicinski [this message]
2023-01-20 3:17 ` Jakub Kicinski
2023-01-20 13:14 ` [Intel-wired-lan] " Bjorn Helgaas
2023-01-18 23:46 ` [PATCH 3/9] fm10k: " Bjorn Helgaas
2023-01-19 18:28 ` Tony Nguyen
2023-01-18 23:46 ` [PATCH 4/9] i40e: " Bjorn Helgaas
2023-01-19 18:28 ` Tony Nguyen
2023-01-25 10:34 ` [Intel-wired-lan] " G, GurucharanX
2023-01-18 23:46 ` [PATCH 5/9] iavf: " Bjorn Helgaas
2023-01-19 18:28 ` Tony Nguyen
2023-01-18 23:46 ` [PATCH 6/9] ice: " Bjorn Helgaas
2023-01-19 18:28 ` Tony Nguyen
2023-01-25 9:08 ` [Intel-wired-lan] " G, GurucharanX
2023-01-18 23:46 ` [PATCH 7/9] igb: " Bjorn Helgaas
2023-01-19 18:28 ` Tony Nguyen
2023-01-25 9:09 ` [Intel-wired-lan] " G, GurucharanX
2023-01-18 23:46 ` [PATCH 8/9] igc: " Bjorn Helgaas
2023-01-19 18:28 ` Tony Nguyen
2023-01-24 11:33 ` [Intel-wired-lan] " naamax.meir
2023-01-18 23:46 ` [PATCH 9/9] ixgbe: " Bjorn Helgaas
2023-01-19 18:28 ` Tony Nguyen
2023-01-25 9:09 ` [Intel-wired-lan] " G, GurucharanX
2023-01-26 23:15 ` [PATCH 0/9] PCI/AER: Remove redundant Device Control Error Reporting Enable Bjorn Helgaas
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=20230119213557.57598e8f@kernel.org \
--to=kuba@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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).