From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Sumit Saxena <sumit.saxena@avagotech.com>
Cc: megaraidlinux@lsi.com, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: scsi: megaraid: Add "megaraid_sas_internal.h" for internal shared functions using
Date: Sun, 30 Nov 2014 11:07:21 +0800 [thread overview]
Message-ID: <547A89E9.6010804@gmail.com> (raw)
In-Reply-To: <1085092fd0c2eadae3a0f8de3ee09b95@mail.gmail.com>
On 11/17/14 19:51, Sumit Saxena wrote:
>> -----Original Message-----
>> From: Chen Gang [mailto:gang.chen.5i5j@gmail.com]
>> Sent: Monday, November 17, 2014 5:17 PM
>> To: Sumit Saxena
>> Cc: megaraidlinux@lsi.com; linux-scsi@vger.kernel.org; linux-
>> kernel@vger.kernel.org
>> Subject: RE: [PATCH] drivers: scsi: megaraid: Add "megaraid_sas_internal.h"
>> for internal shared functions using
>>
>>
>> OK, I will send patch v2 for it.
>>
>> I sent this patch based on Linux next tree, please tell me the tree
>> location (git
>> address) which I shall base on for sending patch v2.
>
> I posted the patch series today, once the patches make it to scsi-next tree,
> I will let you know.
>
Is it OK? or if possible, please help rebase and send the patch for it
based on the related branches and patches.
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2014-11-30 3:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 11:46 [PATCH] drivers: scsi: megaraid: Add "megaraid_sas_internal.h" for internal shared functions using Chen Gang
2014-11-17 11:51 ` Sumit Saxena
2014-11-30 3:07 ` Chen Gang [this message]
2014-12-10 8:47 ` Sumit Saxena
2014-12-10 8:59 ` Chen Gang
-- strict thread matches above, loose matches on Subject: below --
2014-11-09 10:17 Chen Gang
2014-11-17 10:56 ` Sumit Saxena
2014-11-09 10:16 Chen Gang
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=547A89E9.6010804@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=megaraidlinux@lsi.com \
--cc=sumit.saxena@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).