From: kgunda@codeaurora.org
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Jingoo Han <jingoohan1@gmail.com>,
bjorn.andersson@linaro.org, 'Lee Jones' <lee.jones@linaro.org>,
'Jacek Anaszewski' <jacek.anaszewski@gmail.com>,
'Pavel Machek' <pavel@ucw.cz>, 'Rob Herring' <robh+dt@kernel.org>,
'Mark Rutland' <mark.rutland@arm.com>,
'Bartlomiej Zolnierkiewicz' <b.zolnierkie@samsung.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V2 1/5] backlight: qcom-wled: Rename pm8941-wled.c to qcom-wled.c
Date: Tue, 08 May 2018 15:23:15 +0530 [thread overview]
Message-ID: <19e02b14f0b828b9470eb863ab9f3a11@codeaurora.org> (raw)
In-Reply-To: <20180508083658.mc7x7izthxjrv5ey@holly.lan>
On 2018-05-08 14:06, Daniel Thompson wrote:
> On Mon, May 07, 2018 at 11:26:59AM +0530, kgunda@codeaurora.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.
Ok. Got it. Not sure how the To: Cc: list on the 0th patch got shrink,
while I was
using the To: Cc: list same for all the patches. Anyways, will double
check of it while
circulating the next series.
next prev parent reply other threads:[~2018-05-08 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1525342352-25072-1-git-send-email-kgunda@codeaurora.org>
2018-05-03 10:12 ` [PATCH V2 1/5] backlight: qcom-wled: Rename pm8941-wled.c to qcom-wled.c Kiran Gunda
2018-05-04 15:55 ` Jingoo Han
2018-05-07 5:56 ` kgunda
2018-05-08 8:36 ` Daniel Thompson
2018-05-08 9:53 ` kgunda [this message]
2018-05-07 16:40 ` Rob Herring
2018-05-08 10:25 ` kgunda
2018-05-08 8:43 ` Daniel Thompson
2018-05-03 10:12 ` [PATCH V2 2/5] backlight: qcom-wled: Add support for WLED4 peripheral Kiran Gunda
2018-05-07 16:45 ` Rob Herring
2018-05-08 10:04 ` kgunda
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=19e02b14f0b828b9470eb863ab9f3a11@codeaurora.org \
--to=kgunda@codeaurora.org \
--cc=b.zolnierkie@samsung.com \
--cc=bjorn.andersson@linaro.org \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.anaszewski@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
/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).