From: Jeff Kirsher <tarbal@gmail.com>
To: Stefan Assmann <sassmann@kpanic.de>
Cc: netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net,
alexander.h.duyck@intel.com, carolyn.wyborny@intel.com,
jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH net-next 0/2] igb: fixes and improvements for irq fallback
Date: Mon, 03 Dec 2012 11:51:09 -0800 [thread overview]
Message-ID: <50BD02AD.4060605@gmail.com> (raw)
In-Reply-To: <1354540501-18407-1-git-send-email-sassmann@kpanic.de>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
On 12/03/2012 05:14 AM, Stefan Assmann wrote:
> The interrupt fallback code should utilize the same code that's used for normal
> setup instead of duplicating it. It also has some shortcomings when it comes
> to situations where for some reason request_irq() fails to allocate vectors for
> MSI-X. Hoping to address these with this patchset.
>
> Would be nice for these patches to go through Intel testing before inclusion.
>
> Stefan Assmann (2):
> igb: remove duplicate code for fallback interrupt initialization
> igb: release already assigned MSI-X interrupts if setup fails
>
Thanks Stefan, I have added the patches to my queue.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
prev parent reply other threads:[~2012-12-03 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 13:14 [PATCH net-next 0/2] igb: fixes and improvements for irq fallback Stefan Assmann
2012-12-03 13:15 ` [PATCH net-next 1/2] igb: remove duplicate code for fallback interrupt initialization Stefan Assmann
2012-12-03 13:15 ` [PATCH net-next 2/2] igb: release already assigned MSI-X interrupts if setup fails Stefan Assmann
2012-12-03 19:51 ` Jeff Kirsher [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=50BD02AD.4060605@gmail.com \
--to=tarbal@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@kpanic.de \
/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).