From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Mark Brown <broonie@kernel.org>, Joao Pinto <Joao.Pinto@synopsys.com>
Cc: vinayak holikatti <vinholikatti@gmail.com>,
<JBottomley@parallels.com>, <rafael.j.wysocki@intel.com>,
<hch@lst.de>, 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 15:39:54 +0000 [thread overview]
Message-ID: <56F1674A.3090309@synopsys.com> (raw)
In-Reply-To: <20160322153125.GC2566@sirena.org.uk>
On 3/22/2016 3:31 PM, Mark Brown wrote:
> On Tue, Mar 22, 2016 at 11:04:25AM +0000, Joao Pinto wrote:
>
> Please don't top post, reply in line with needed context. This allows
> readers to readily follow the flow of conversation and understand what
> you are talking about and also helps ensure that everything in the
> discussion is being addressed.
>
>> I have no intend to break the rules. I am just trying to communicate with UFS
>> maintainers that so far gave me no response. Merging in v4.7 is fine, but I
>> would like that UFS maintainers give me some feedback about the next steps, but
>> so far didn't have luck.
>
> Like I say the next steps are those Arnd gave you: repost after -rc1.
> Then give people at least a week or so to respond, people do get busy
> and other people are also sending patches.
>
Understood, I will repost this patch set after -rc1.
I suggest that the UFS maintenance should be revised because the e-mail of
ufshcd.c authors are no longer valid and the current maintainer (Vinayak
Holikatti) is having a career shift (has you can check in LinkedIn) and probably
is not available at the moment to do patch reviews.
Thanks,
Joao
next prev parent reply other threads:[~2016-03-22 15:40 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
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 [this message]
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=56F1674A.3090309@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