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 11:04:25 +0000 [thread overview]
Message-ID: <56F126B9.3010903@synopsys.com> (raw)
In-Reply-To: <20160322105827.GB2566@sirena.org.uk>
Hi Mark,
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.
Thanks,
Joao
On 3/22/2016 10:58 AM, Mark Brown wrote:
> On Tue, Mar 22, 2016 at 10:31:28AM +0000, Joao Pinto wrote:
>
>> 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.
>
> I've no idea why you're sending me this stuff but please stop - you sent
> a similar mail yesterday and I see there were a bunch of similar mails
> before you started CCing me into the thread - but sending daily top
> posted content free pings is just going to annoy people (or at least
> it's annoying me) and sending them to random other maintainers isn't
> likely to improve things. This is especially the case when we're more
> than half way through the merge window and the code apparently isn't
> even in -next yet.
>
> Please stop this and follow Arnd's advice (which you quoted from the
> message you're replying to):
>
>>>> On 3/18/2016 2:49 PM, Arnd Bergmann wrote:
>
>>>>> 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.
>
> If there's some reason to break the process you need to articulate what
> it is and give people a chance to respond but that's *very* rare, unless
> there is an unusually strong reason people are going to use the normal
> development workflow.
>
next prev parent reply other threads:[~2016-03-22 11:04 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 [this message]
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=56F126B9.3010903@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