linux-kernel - Re: [PATCH V2 1/5] backlight: qcom-wled: Rename pm8941-wled.c to qcom-wled.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 8 May 2018 09:36:58 +0100
From:   Daniel Thompson <daniel.thompson@...aro.org>
To:     kgunda@...eaurora.org
Cc:     Jingoo Han <jingoohan1@...il.com>, bjorn.andersson@...aro.org,
        'Lee Jones' <lee.jones@...aro.org>,
        'Jacek Anaszewski' <jacek.anaszewski@...il.com>,
        'Pavel Machek' <pavel@....cz>,
        'Rob Herring' <robh+dt@...nel.org>,
        'Mark Rutland' <mark.rutland@....com>,
        'Bartlomiej Zolnierkiewicz' <b.zolnierkie@...sung.com>,
        linux-leds@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
        linux-fbdev@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH V2 1/5] backlight: qcom-wled: Rename pm8941-wled.c to
 qcom-wled.c

On Mon, May 07, 2018 at 11:26:59AM +0530, kgunda@...eaurora.org wrote:
> Hi Jingoo Han,
> Thanks for the response.
> 
> Thanks,
> Kiran
> On 2018-05-04 21:25, Jingoo Han wrote:
> > On Thursday, May 3, 2018 6:12 AM, Kiran Gunda wrote:
> > 
> > If you really want someone to review your patch, please add more
> > detailed
> > explanations.
> > 
> > 1. Please add 0th patch.
> I have already added the 0th patch (cover letter). Following is the subject
> for the same.
> forwarding the same to you.
> [PATCH V2 0/5] backlight: qcom-wled: Support for QCOM wled driver

Perhaps you should interpret Jingoo's comment as a request to improve
the To: and Cc: list on the 0th patch the next time you circulate it.

Many maintainers configure their mailers to give patches where they are
in the To: or Cc: list special treatment so it confusing when a series
arrives with a spartan set of recipients for the 0th patch (and doubly
confusing when every patch in the set targets the same driver).


Daniel.