linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jay Kallickal <jayamohank@gmail.com>
Cc: jbottomley@parallels.com, linux-scsi@vger.kernel.org,
	michaelc@cs.wisc.edu,
	Jayamohan Kallickal <jayamohan.kallickal@emulex.com>,
	John Soni Jose <sony.john-n@emulex.com>
Subject: Re: [PATCH 1/5] be2iscsi: Fix the sparse warning introduced in previous submission
Date: Tue, 19 Aug 2014 12:27:18 -0500	[thread overview]
Message-ID: <20140819172718.GB15268@infradead.org> (raw)
In-Reply-To: <1407474003-26220-1-git-send-email-jkallickal@emulex.com>

Thanks,

applied the whole series to the drivers-for-3.18 tree.


  parent reply	other threads:[~2014-08-19 17:25 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
2014-08-19 17:27 ` Christoph Hellwig [this message]
2014-08-27 13:50 ` [PATCH 1/5] be2iscsi: Fix the sparse warning introduced in previous submission 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=20140819172718.GB15268@infradead.org \
    --to=hch@infradead.org \
    --cc=jayamohan.kallickal@emulex.com \
    --cc=jayamohank@gmail.com \
    --cc=jbottomley@parallels.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=sony.john-n@emulex.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).