netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yuval Mintz <Yuval.Mintz@qlogic.com>
To: <davem@davemloft.net>, <netdev@vger.kernel.org>
Cc: Yuval Mintz <Yuval.Mintz@qlogic.com>
Subject: [PATCH net-next 0/6] qed*: Driver updates
Date: Wed, 24 Feb 2016 16:52:44 +0200	[thread overview]
Message-ID: <1456325570-1514-1-git-send-email-Yuval.Mintz@qlogic.com> (raw)

Usually I try to provide a sensible description of the patch set even if
it lacks a general 'motif', but this simply contains several small,
unrelated and self-explenatory tweaks and additions.

Dave,

Please consider applying this series to `net-next'.

Thanks,
Yuval

Yuval Mintz (6):
  qede: Change pci DID for 10g device
  qede: Linearize SKBs when needed
  qede: Don't report link change needlessly
  qed: add MODULE_FIRMWARE()
  qed: Prevent probe on previous error
  qed, qede: rebrand module description

 drivers/net/ethernet/qlogic/qed/qed_main.c   | 19 +++++++--
 drivers/net/ethernet/qlogic/qede/qede_main.c | 62 +++++++++++++++++++++-------
 2 files changed, 63 insertions(+), 18 deletions(-)
-- 
1.8.3.1

             reply	other threads:[~2016-02-24 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 14:52 Yuval Mintz [this message]
2016-02-24 14:52 ` [PATCH net-next 1/6] qede: Change pci DID for 10g device Yuval Mintz
2016-02-24 14:52 ` [PATCH net-next 2/6] qede: Linearize SKBs when needed Yuval Mintz
2016-02-24 14:52 ` [PATCH net-next 3/6] qede: Don't report link change needlessly Yuval Mintz
2016-02-24 14:52 ` [PATCH net-next 4/6] qed: add MODULE_FIRMWARE() Yuval Mintz
2016-02-24 14:52 ` [PATCH net-next 5/6] qed: Prevent probe on previous error Yuval Mintz
2016-02-24 14:52 ` [PATCH net-next 6/6] qed, qede: rebrand module description Yuval Mintz
2016-02-25 21:55 ` [PATCH net-next 0/6] qed*: Driver updates David Miller
  -- strict thread matches above, loose matches on Subject: below --
2016-10-09 15:25 [PATCH net-next 0/6] qed*: driver updates Yuval Mintz

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=1456325570-1514-1-git-send-email-Yuval.Mintz@qlogic.com \
    --to=yuval.mintz@qlogic.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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 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).