All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keller, Jacob E <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 1/6] fm10k: Avoid crashing the kernel
Date: Tue, 16 Feb 2016 18:20:31 +0000	[thread overview]
Message-ID: <1455646831.23620.11.camel@intel.com> (raw)
In-Reply-To: <1455595062.7797.1.camel@intel.com>

On Mon, 2016-02-15 at 19:57 -0800, Jeff Kirsher wrote:
> Guess you did not bother to compile test this, because it still
> causes
> the same compile errors it did the first time Bruce submitted it.
> ?Dropping this patch, like I did the first time it was submitted.

Woops sorry, I thought I ran it through a test. :(

I'll submit a v2 shortly.

Regards,
Jake

  reply	other threads:[~2016-02-16 18:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 22:45 [Intel-wired-lan] [PATCH 1/6] fm10k: Avoid crashing the kernel Jacob Keller
2016-02-10 22:45 ` [Intel-wired-lan] [PATCH 2/6] fm10k: prevent possibly uninitialized variable Jacob Keller
2016-02-25 20:27   ` Singh, Krishneil K
2016-02-10 22:45 ` [Intel-wired-lan] [PATCH 3/6] fm10k: use ethtool_rxfh_indir_default for default redirection table Jacob Keller
2016-02-16  4:41   ` Jeff Kirsher
2016-02-25 20:28   ` Singh, Krishneil K
2016-02-10 22:45 ` [Intel-wired-lan] [PATCH 4/6] fm10k: update driver summary and reduce code duplication Jacob Keller
2016-02-25 20:29   ` Singh, Krishneil K
2016-02-25 21:45     ` Allan, Bruce W
2016-03-09 23:51       ` Allan, Bruce W
2016-03-10  0:19         ` Keller, Jacob E
2016-02-10 22:45 ` [Intel-wired-lan] [PATCH 5/6] fm10k: correctly clean up when init_queueing_scheme fails Jacob Keller
2016-02-25 20:30   ` Singh, Krishneil K
2016-02-10 22:45 ` [Intel-wired-lan] [PATCH 6/6] fm10k: fix a minor typo in some comments Jacob Keller
2016-02-25 20:31   ` Singh, Krishneil K
2016-02-16  3:57 ` [Intel-wired-lan] [PATCH 1/6] fm10k: Avoid crashing the kernel Jeff Kirsher
2016-02-16 18:20   ` Keller, Jacob E [this message]
2016-02-25 20:27 ` Singh, Krishneil K

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=1455646831.23620.11.camel@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.