From: Dan Murphy <dmurphy@ti.com>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>
Cc: <linux-leds@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Cleanups in "next" tree
Date: Fri, 3 Apr 2020 14:07:57 -0500 [thread overview]
Message-ID: <82de0f5e-2382-e2ae-ec70-392cc95502fc@ti.com> (raw)
In-Reply-To: <a4802e70-106b-3476-536f-1d8798ce156f@gmail.com>
Pavel
On 4/3/20 1:45 PM, Jacek Anaszewski wrote:
> On 4/3/20 12:57 AM, 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.
> I believe code review is quite usual kernel procedure.
>
>> Could you list the patches and objections you have?
> I already expressed my concerns regarding Turris Omnia patch.
>
> My comments regarding remaining patches:
>
> - "Make label "white:power" to be consistent with"
>
> I disagree here. "system" was OK.
>
> - "Warn about old defines that probably should not be used."
>
> Obsolete is only LED_FULL, so the comment is in wrong line
I would prefer to have the commit sha that obsoleted the LED_FULL to be
referenced in the commit message so we have traceability.
Dan
prev parent reply other threads:[~2020-04-03 19:13 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
[not found] ` <a4802e70-106b-3476-536f-1d8798ce156f@gmail.com>
2020-04-03 19:07 ` Dan Murphy [this message]
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=82de0f5e-2382-e2ae-ec70-392cc95502fc@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
all inboxes | Powered by JetHome®