From: Sumit Saxena <sumit.saxena@avagotech.com>
To: Christoph Hellwig <hch@infradead.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, thenzl@redhat.com,
jbottomley@parallels.com,
Kashyap Desai <kashyap.desai@avagotech.com>
Subject: RE: [PATCH 1/5] megaraid_sas : Code optimization and refactoring
Date: Mon, 20 Apr 2015 18:08:14 +0530 [thread overview]
Message-ID: <193cf54f2b73978a01698fb3fa756e21@mail.gmail.com> (raw)
In-Reply-To: <20150414055640.GA29338@infradead.org>
>-----Original Message-----
>From: Christoph Hellwig [mailto:hch@infradead.org]
>Sent: Tuesday, April 14, 2015 11:27 AM
>To: Martin K. Petersen
>Cc: Sumit Saxena; linux-scsi@vger.kernel.org; thenzl@redhat.com;
>hch@infradead.org; jbottomley@parallels.com; Kashyap Desai
>Subject: Re: [PATCH 1/5] megaraid_sas : Code optimization and refactoring
>
>On Mon, Apr 13, 2015 at 09:17:27PM -0400, Martin K. Petersen wrote:
>> >>>>> "Sumit" == Sumit Saxena <sumit.saxena@avagotech.com> writes:
>>
>> Sumit> Ok, I will spilt this patch in 7 patches. Do you have any
>> Sumit> feedback/comments for other patches of this series? IF you are
>> Sumit> ok with other patches, I will resend the series with patch#1
>> Sumit> splitted in 7 patches and rest of the patches(2,3,4 and 5) will
>> Sumit> remain unchanged.
>>
>> The other patches looked OK on their own. But it's probably best to
>> repost the whole series since you'll need a review from at least one
>> person other than me.
>
>Please also include the sparse fixes I sent you a while ago in the
repost.
I have resent this patch series with sparse fixes sent by you.
prev parent reply other threads:[~2015-04-20 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 11:55 [PATCH 1/5] megaraid_sas : Code optimization and refactoring Sumit.Saxena
2015-04-07 23:14 ` Martin K. Petersen
2015-04-13 10:08 ` Sumit Saxena
2015-04-14 1:17 ` Martin K. Petersen
2015-04-14 5:56 ` Christoph Hellwig
2015-04-20 12:38 ` 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=193cf54f2b73978a01698fb3fa756e21@mail.gmail.com \
--to=sumit.saxena@avagotech.com \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=kashyap.desai@avagotech.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=thenzl@redhat.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 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.