From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Arnd Bergmann <arnd@arndb.de>, Joao Pinto <Joao.Pinto@synopsys.com>
Cc: vinayak holikatti <vinholikatti@gmail.com>,
JBottomley@parallels.com, rafael.j.wysocki@intel.com, hch@lst.de,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Carlos Palminha <CARLOS.PALMINHA@synopsys.com>
Subject: Re: UFS V11 patch-set
Date: Fri, 18 Mar 2016 14:53:41 +0000 [thread overview]
Message-ID: <56EC1675.2050002@synopsys.com> (raw)
In-Reply-To: <4014649.ENvamPh3sb@wuerfel>
Hi!
On 3/18/2016 2:49 PM, Arnd Bergmann wrote:
> On Friday 18 March 2016 12:52:13 Joao Pinto wrote:
>> Hi!
>>
>> Could you please check the following patch-set in order to evaluate if it is
>> ready for v4.6?
>>
>
> I think the code is ok now, but the timing apparently didn't work for 4.6.
> I'd suggest you resend as soon as 4.6-rc1 is out so it can get merged into 4.7.
Isn't it possible to be merged into a ufs-dwc branch in the SCSI Git tree that
could be pulled later, like Bjorn did in the PCIe RC?
>
> Arnd
>
Joao
WARNING: multiple messages have this Message-ID (diff)
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Arnd Bergmann <arnd@arndb.de>, Joao Pinto <Joao.Pinto@synopsys.com>
Cc: vinayak holikatti <vinholikatti@gmail.com>,
<JBottomley@parallels.com>, <rafael.j.wysocki@intel.com>,
<hch@lst.de>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Carlos Palminha <CARLOS.PALMINHA@synopsys.com>
Subject: Re: UFS V11 patch-set
Date: Fri, 18 Mar 2016 14:53:41 +0000 [thread overview]
Message-ID: <56EC1675.2050002@synopsys.com> (raw)
In-Reply-To: <4014649.ENvamPh3sb@wuerfel>
Hi!
On 3/18/2016 2:49 PM, Arnd Bergmann wrote:
> On Friday 18 March 2016 12:52:13 Joao Pinto wrote:
>> Hi!
>>
>> Could you please check the following patch-set in order to evaluate if it is
>> ready for v4.6?
>>
>
> I think the code is ok now, but the timing apparently didn't work for 4.6.
> I'd suggest you resend as soon as 4.6-rc1 is out so it can get merged into 4.7.
Isn't it possible to be merged into a ufs-dwc branch in the SCSI Git tree that
could be pulled later, like Bjorn did in the PCIe RC?
>
> Arnd
>
Joao
next prev parent reply other threads:[~2016-03-18 14:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 12:49 UFS V11 patch-set Joao Pinto
2016-03-18 12:49 ` Joao Pinto
2016-03-18 12:52 ` Joao Pinto
2016-03-18 12:52 ` Joao Pinto
2016-03-18 14:49 ` Arnd Bergmann
2016-03-18 14:53 ` Joao Pinto [this message]
2016-03-18 14:53 ` Joao Pinto
2016-03-21 10:28 ` Joao Pinto
2016-03-22 10:31 ` Joao Pinto
2016-03-22 10:58 ` Mark Brown
2016-03-22 11:04 ` Joao Pinto
2016-03-22 15:31 ` Mark Brown
2016-03-22 15:39 ` Joao Pinto
2016-03-22 15:43 ` Mark Brown
2016-03-22 15:53 ` Joao Pinto
2016-03-23 21:16 ` Martin K. Petersen
2016-03-23 21:16 ` Martin K. Petersen
2016-03-24 10:16 ` Joao Pinto
2016-03-24 10:16 ` Joao Pinto
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=56EC1675.2050002@synopsys.com \
--to=joao.pinto@synopsys.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=JBottomley@parallels.com \
--cc=arnd@arndb.de \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=vinholikatti@gmail.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.