From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Nicholas Krause <xerofoify@gmail.com>
Cc: jesse.brandeburg@intel.com, shannon.nelson@intel.com,
carolyn.wyborny@intel.com, donald.c.skidmore@intel.com,
matthew.vick@intel.com, john.ronciak@intel.com,
mitch.a.williams@intel.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] fm10k:Fix error handling in the function fm10k_resume
Date: Sat, 05 Dec 2015 23:35:07 -0800 [thread overview]
Message-ID: <1449387307.3198.22.camel@intel.com> (raw)
In-Reply-To: <1449369415-22303-1-git-send-email-xerofoify@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On Sat, 2015-12-05 at 21:36 -0500, Nicholas Krause wrote:
> This fixes error handling to proper check if the call to the function
> fm10k_mbx_request_irq has failed by returning a error code and if
> so return immediately to the caller of fm10k_resume to properly
> signal a failure has occurred when accepting to resume this network
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> Tested-by: Krishneil SIngh <krishneil.k.singh@intel.com
> ---
> drivers/net/ethernet/intel/fm10k/fm10k_pci.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Don't bother, David Miller has spoken and will not accept any patches
from you. So even though this was not properly sent to intel-wired-
lan@lists.osuosl.org, which all kernel patches need to be sent to, I am
dropping this patch since David Miller will not accept ANY patches from
you.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
parent reply other threads:[~2015-12-06 7:35 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1449369415-22303-1-git-send-email-xerofoify@gmail.com>]
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=1449387307.3198.22.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=donald.c.skidmore@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.vick@intel.com \
--cc=mitch.a.williams@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@intel.com \
--cc=xerofoify@gmail.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).