public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Joao Pinto <Joao.Pinto@synopsys.com>,
	vinayak holikatti <vinholikatti@gmail.com>,
	<JBottomley@parallels.com>, <rafael.j.wysocki@intel.com>,
	<hch@lst.de>, <broonie@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Carlos Palminha <CARLOS.PALMINHA@synopsys.com>,
	<gregkh@linuxfoundation.org>,
	"robh@kernel.org >> Rob Herring" <robh@kernel.org>
Subject: Re: UFS V11 patch-set
Date: Tue, 22 Mar 2016 10:31:28 +0000	[thread overview]
Message-ID: <56F11F00.1060408@synopsys.com> (raw)
In-Reply-To: <56EFCCB3.3040108@synopsys.com>

Hi,

The following patch-set was approved by Arnd Bergmann and Rob Herring and I
would appreciate that someone from SCSI / UFS gave a final checkout in order to
evaluate the possibility of still merging it to v4.6 or putting it in a branch
in SCSI to be merged to v4.7.

[PATCH v11 0/6] add support for DWC UFS Controller
http://www.gossamer-threads.com/lists/linux/kernel/2396797?#2396797

[PATCH v11 1/6] fixed typo in ufshcd-pltfrm
http://www.gossamer-threads.com/lists/linux/kernel/2396790?#2396790

[PATCH v11 2/6] added UFS 2.0 capabilities
http://www.gossamer-threads.com/lists/linux/kernel/2396791?#2396791

[PATCH v11 3/6] added support for DesignWare Controller
http://www.gossamer-threads.com/lists/linux/kernel/2396795?#2396795

[PATCH v11 4/6] added support for Synopsys G210 Test Chip
http://www.gossamer-threads.com/lists/linux/kernel/2396792?#2396792

[PATCH v11 5/6] add TC G210 platform driver
http://www.gossamer-threads.com/lists/linux/kernel/2396794?#2396794

[PATCH v11 6/6] add-TC-G210-pci-driver
http://www.gossamer-threads.com/lists/linux/kernel/2396793?#2396793


On 3/21/2016 10:28 AM, Joao Pinto wrote:
>> 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.
>>
>>
>>>
>>> 	Arnd
>

Thanks,

Joao

  reply	other threads:[~2016-03-22 10:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 12:49 UFS V11 patch-set Joao Pinto
2016-03-18 12:52 ` Joao Pinto
2016-03-18 14:49   ` Arnd Bergmann
2016-03-18 14:53     ` Joao Pinto
2016-03-21 10:28       ` Joao Pinto
2016-03-22 10:31         ` Joao Pinto [this message]
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-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=56F11F00.1060408@synopsys.com \
    --to=joao.pinto@synopsys.com \
    --cc=CARLOS.PALMINHA@synopsys.com \
    --cc=JBottomley@parallels.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=robh@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox