From: Sumit Saxena <sumit.saxena@avagotech.com>
To: linux-scsi@vger.kernel.org, thenzl@redhat.com,
martin.petersen@oracle.com, hch@infradead.org,
jbottomley@parallels.com,
Kashyap Desai <kashyap.desai@avagotech.com>,
Kiran Kumar Kasturi <kiran-kumar.kasturi@avagotech.com>
Cc: Uday Lingala <uday.lingala@avagotech.com>
Subject: RE: [PATCH v3 0/10] megaraid_sas : Updates for scsi for-next
Date: Fri, 9 Oct 2015 10:40:07 +0530 [thread overview]
Message-ID: <8b3d1ba23ef04e1d71f1eb2c2e16cda9@mail.gmail.com> (raw)
In-Reply-To: <201508311158.t7VBwALp031354@palmhbs0.lsi.com>
> -----Original Message-----
> From: sumit.saxena@avagotech.com [mailto:sumit.saxena@avagotech.com]
> Sent: Monday, August 31, 2015 5:23 PM
> To: linux-scsi@vger.kernel.org; thenzl@redhat.com;
> martin.petersen@oracle.com; hch@infradead.org; jbottomley@parallels.com;
> kashyap.desai@avagotech.com; sumit.saxena@avagotech.com; kiran-
> kumar.kasturi@avagotech.com
> Cc: uday.lingala@avagotech.com
> Subject: [PATCH v3 0/10] megaraid_sas : Updates for scsi for-next
>
> MegaRaid driver changes. This patch set is rebased on top of below
commit-
>
> commit da0dc9fb4e6b0ad5a947c27a3c48985f6a2377eb
> Author: Bjorn Helgaas <bhelgaas@google.com>
> Date: Tue Jul 7 15:52:45 2015 -0500
>
> megaraid_sas: fix whitespace errors
>
>
> Please consider this patch set for next kernel release.
James,
Gentle reminder. Can you consider these patches?
Thanks,
Sumit
>
> Signed-off-by: Sumit Saxena <sumit.saxena@avagotech.com>
> Signed-off-by: Kashyap Desai <kashyap.desai@avagotech.com>
> ---
> [PATCH v3 00/10] megaraid_sas : Updates for scsi for-next.
> [PATCH v3 01/10] megaraid_sas : Synchronize driver headers with firmware
> APIs.
> [PATCH v3 02/10] megaraid_sas : Increase timeout to 60 secs for abort
frames
> during shutdown.
> [PATCH v3 03/10] megaraid_sas : Jbod sequence number support.
> [PATCH v3 04/10] megaraid_sas : Code cleanup-use local variable drv_ops
inside
> megasas_ioc_init_fusion.
> [PATCH v3 05/10] megaraid_sas : Support for max_io_size 1MB.
> [PATCH v3 06/10] megaraid_sas : Chip reset if driver fail to bring ioc
ready.
> [PATCH v3 07/10] megaraid_sas : Print critical fw event message.
> [PATCH v3 08/10] megaraid_sas : Fix validHandles check in io path.
> [PATCH v3 09/10] megaraid_sas : Code refactor for use of requestorId.
> [PATCH v3 10/10] megaraid_sas : Version upgrade.
>
prev parent reply other threads:[~2015-10-09 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 11:52 [PATCH v3 0/10] megaraid_sas : Updates for scsi for-next sumit.saxena
2015-10-09 5:10 ` Sumit Saxena [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=8b3d1ba23ef04e1d71f1eb2c2e16cda9@mail.gmail.com \
--to=sumit.saxena@avagotech.com \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=kashyap.desai@avagotech.com \
--cc=kiran-kumar.kasturi@avagotech.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=thenzl@redhat.com \
--cc=uday.lingala@avagotech.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).