From: David Miller <davem@davemloft.net>
To: shahed.shaikh@qlogic.com
Cc: netdev@vger.kernel.org, Dept-GELinuxNICDev@qlogic.com
Subject: Re: [PATCH net-next 0/6] qlcnic: enhancements
Date: Mon, 10 Aug 2015 13:34:50 -0700 (PDT) [thread overview]
Message-ID: <20150810.133450.366990134543320574.davem@davemloft.net> (raw)
In-Reply-To: <1438946227-11426-1-git-send-email-shahed.shaikh@qlogic.com>
From: Shahed Shaikh <shahed.shaikh@qlogic.com>
Date: Fri, 7 Aug 2015 07:17:01 -0400
> This series adds few enhancements.
>
> o Patch from Harish reorders the sequence of header files inclusion,
> keeping kernel's header files on top.
>
> o Firmware introduced a new feature which allows driver to increases
> the size of firmware dump of iSCSI function which is being collected
> by NIC driver.
>
> o Print buffer address which is holding a firmware dump.
>
> o Use vzalloc() instead kzalloc() for allocating large chunk of memory
> which will avoid potential memory allocation failure.
>
> o Add new device ID for 0x8C30 which is a 83xx series based VF function.
>
> Please apply this series to net-next.
Series applied, thanks.
prev parent reply other threads:[~2015-08-10 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 11:17 [PATCH net-next 0/6] qlcnic: enhancements Shahed Shaikh
2015-08-07 11:17 ` [PATCH net-next 1/6] qlcnic: Rearrange ordering of header files inclusion Shahed Shaikh
2015-08-07 11:17 ` [PATCH net-next 2/6] qlcnic: Add support to enable capability to extend minidump for iSCSI Shahed Shaikh
2015-08-07 11:17 ` [PATCH net-next 3/6] qlcnic: Print firmware minidump buffer and template header addresses Shahed Shaikh
2015-08-07 11:17 ` [PATCH net-next 4/6] qlcnic: Add new VF device ID 0x8C30 Shahed Shaikh
2015-08-07 11:17 ` [PATCH net-next 5/6] qlcnic: Don't use kzalloc unncecessarily for allocating large chunk of memory Shahed Shaikh
2015-08-07 11:17 ` [PATCH net-next 6/6] qlcnic: Update version to 5.3.63 Shahed Shaikh
2015-08-10 20:34 ` David Miller [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=20150810.133450.366990134543320574.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Dept-GELinuxNICDev@qlogic.com \
--cc=netdev@vger.kernel.org \
--cc=shahed.shaikh@qlogic.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).