From: Dan Murphy <dmurphy@ti.com>
To: Pavel Machek <pavel@ucw.cz>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>
Cc: <linux-leds@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Cleanups in "next" tree
Date: Fri, 3 Apr 2020 07:49:47 -0500 [thread overview]
Message-ID: <7cce20f9-f665-2b96-2657-e489df87dd3f@ti.com> (raw)
In-Reply-To: <20200402225745.GA9830@amd>
Pavel
On 4/2/20 5:57 PM, Pavel Machek wrote:
> On Sun 2020-03-22 14:35:56, Jacek Anaszewski wrote:
>> Hi Pavel,
>>
>> On 3/22/20 12:59 PM, Pavel Machek wrote:
>>> Hi!
>>>
>>> I've commited some cleanups into LED tree ( git/pavel/linux-leds.git
>>> branch for-next ), if someone wants to review them.
>> You abused your maintainer power by bypassing the usual patch
>> submission procedure. Please remove the patches from linux-next
>> and submit them officially for discussion. I would have some objections
>> to them.
> I'm sorry I failed to meet your high expectations... But I don't
> believe I done anything completely outside of usual kernel procedures.
So I can push a public tree out and request reviewers to review that
tree and expect it to get merged once the review is complete without
ever posting the patches to linux-leds?
This would be the precedent you are setting here as maintainer.
And Jacek does not have high expectations he is just requesting that we
follow the process as defined in the Linux kernel document
Dan
next parent reply other threads:[~2020-04-03 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200322115906.GA10623@duo.ucw.cz>
[not found] ` <3a103317-b9fb-5d0f-6944-0114b9af1629@gmail.com>
[not found] ` <20200402225745.GA9830@amd>
2020-04-03 12:49 ` Dan Murphy [this message]
[not found] ` <a4802e70-106b-3476-536f-1d8798ce156f@gmail.com>
2020-04-03 19:07 ` Cleanups in "next" tree Dan Murphy
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=7cce20f9-f665-2b96-2657-e489df87dd3f@ti.com \
--to=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).