From: Mike Christie <michaelc@cs.wisc.edu>
To: Jay Kallickal <jayamohank@gmail.com>
Cc: jbottomley@parallels.com, linux-scsi@vger.kernel.org,
Jayamohan Kallickal <jayamohan.kallickal@emulex.com>
Subject: Re: [PATCH 0/5] be2iscsi: Update to 10.4.74.0
Date: Fri, 08 Aug 2014 13:55:14 -0500 [thread overview]
Message-ID: <53E51D12.5030002@cs.wisc.edu> (raw)
In-Reply-To: <1407474003-26220-6-git-send-email-jkallickal@emulex.com>
On 08/08/2014 12:00 AM, Jay Kallickal wrote:
> From: Jayamohan Kallickal <jayamohan.kallickal@emulex.com>
>
> This patchset updates be2iscsi driver to 10.4.74.0
>
> These patches are based on for-next branch of scsi.git.
>
> 0001 - Fix the sparse warning
> 0002 - Update the copyright year
> 0003 - Fix updating the boot enteries in sysfs
> 0004 - Fix processing CQE before freeing connection resources
> 0005 - Bump the driver version
>
Patches look ok to me. I am still behind on working on another fix for
4/5 which is more invasive, so that is ok with me.
Reviewed-by: Mike Christie <michaelc@cs.wisc.edu>
next prev parent reply other threads:[~2014-08-08 18:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 4:59 [PATCH 1/5] be2iscsi: Fix the sparse warning introduced in previous submission Jay Kallickal
2014-08-08 4:59 ` [PATCH 2/5] be2iscsi: Fix the copyright year Jay Kallickal
2014-08-27 13:50 ` Hannes Reinecke
2014-08-08 5:00 ` [PATCH 3/5] be2iscsi: Fix updating the boot enteries in sysfs Jay Kallickal
2014-08-27 13:52 ` Hannes Reinecke
2014-08-08 5:00 ` [PATCH 4/5] be2iscsi: Fix processing CQE before connection resources are freed Jay Kallickal
2014-08-27 13:53 ` Hannes Reinecke
2014-08-08 5:00 ` [PATCH 5/5] be2iscsi: Bump the driver version Jay Kallickal
2014-08-27 13:53 ` Hannes Reinecke
2014-08-08 5:00 ` [PATCH 0/5] be2iscsi: Update to 10.4.74.0 Jay Kallickal
2014-08-08 18:55 ` Mike Christie [this message]
2014-08-19 17:27 ` [PATCH 1/5] be2iscsi: Fix the sparse warning introduced in previous submission Christoph Hellwig
2014-08-27 13:50 ` Hannes Reinecke
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=53E51D12.5030002@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=jayamohan.kallickal@emulex.com \
--cc=jayamohank@gmail.com \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@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 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.