linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Corentin Chary <corentin.chary@gmail.com>,
	Darren Hart <dvhart@infradead.org>,
	"Andy Shevchenko" <andy@infradead.org>
Subject: Re: [PATCH v2 3/3] platform/x86: intel_oaktrail: Use pr_warn instead of pr_warning
Date: Thu, 26 Sep 2019 15:48:51 +0800	[thread overview]
Message-ID: <4669c5b0-8587-92b7-a9da-5fbbb5255ff4@huawei.com> (raw)
In-Reply-To: <CAHp75Vd4DNqY-m6cz0t2Bg6ZS=v3qQ1oagYgbUwfd4daxLTyFA@mail.gmail.com>



On 2019/9/26 15:32, Andy Shevchenko wrote:
> On Thu, Sep 26, 2019 at 9:09 AM Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
>> On 2019/9/26 13:48, Andy Shevchenko wrote:
>>> On Thu, Sep 26, 2019 at 4:29 AM Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
>>>> On 2019/9/25 23:04, Andy Shevchenko wrote:
>>>>> On Fri, Sep 20, 2019 at 1:55 PM Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
>>>>> You have to send to proper mailing lists and people.
>>>> Used get_maintainer.pl to find the people, and all already in the CC,  will add proper maillist into each patch.
>>>>
>>>>> Don't spam the rest!
>>>> Not so clearly, should I not CC other people not in the list below?
>>>>
>>>> [wkf@localhost linux]$ ./scripts/get_maintainer.pl pr_warning/v3/0018-platform-x86-eeepc-laptop-Use-pr_warn-instead-of-pr_.patch
>>>> Corentin Chary <corentin.chary@gmail.com> (maintainer:ASUS NOTEBOOKS AND EEEPC ACPI/WMI EXTRAS DRIVERS)
>>>> Darren Hart <dvhart@infradead.org> (odd fixer:X86 PLATFORM DRIVERS)
>>>> Andy Shevchenko <andy@infradead.org> (odd fixer:X86 PLATFORM DRIVERS)
>>> You put a lot more people in Cc, than above list contains.
>>
>> This is a treewide change, and finally kill pr_warning in the whole linux code, so I add more people into Cc list.
> 
> No _this_ is change for only one subsystem / driver.
> Since the set is of independent patches, you may add all people to
> cover letter which I happened not to see and to the patches that are
> core of the series (like one with pr_warning() kill).
> 
> For now I considered them as completely independent to push thru my tree.
> In any case you have to carefully choose the Cc list per each patch in
> a treewide changes.
> 
>> Here is a brief discussion about how this be picked up,  is this ok for you?
>>
>> https://lore.kernel.org/lkml/82fe3d04-2985-7844-31bb-269655c83873@huawei.com/
> 
> I haven't got this. Care to do what I said above about cover letter
> and tell all stakeholders what you are expecting from them to do.

Got it, will put all stakeholders into cover letter next time.
Thanks for your patient guidance.
> 


  reply	other threads:[~2019-09-26  7:48 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20  6:25 [PATCH 00/32] Kill pr_warning in the whole linux code Kefeng Wang
2019-09-20  6:25 ` [PATCH 01/32] alpha: Use pr_warn instead of pr_warning Kefeng Wang
2019-09-20  6:25 ` [PATCH 02/32] arm64: " Kefeng Wang
2019-09-20 15:57   ` Will Deacon
2019-09-20  6:25 ` [PATCH 03/32] ia64: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 04/32] riscv: " Kefeng Wang
2019-09-25 21:05   ` Palmer Dabbelt
2019-09-20  6:25 ` [PATCH 05/32] sh: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 06/32] sparc: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 07/32] x86: " Kefeng Wang
2019-09-20  9:28   ` Robert Richter
2019-09-20 11:57     ` Kefeng Wang
2019-09-20 15:28       ` Joe Perches
2019-09-26  1:30         ` Kefeng Wang
2019-09-20  6:25 ` [PATCH 08/32] acpi: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 09/32] drbd: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 10/32] gdrom: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 11/32] clocksource: samsung_pwm_timer: " Kefeng Wang
2019-09-20  8:25   ` Daniel Lezcano
2019-09-20  6:25 ` [PATCH 12/32] crypto: n2: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 13/32] ide: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 14/32] idsn: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 15/32] macintosh: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 16/32] of: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 17/32] oprofile: " Kefeng Wang
2019-09-20  9:18   ` Robert Richter
2019-09-20  6:25 ` [PATCH 18/32] platform/x86: " Kefeng Wang
2019-09-20  6:26   ` Andy Shevchenko
2019-09-20  6:31     ` Kefeng Wang
2019-09-20 11:12     ` [PATCH v2 1/3] platform/x86: eeepc-laptop: " Kefeng Wang
2019-09-20 11:12       ` [PATCH v2 2/3] platform/x86: asus-laptop: " Kefeng Wang
2019-09-20 11:12       ` [PATCH v2 3/3] platform/x86: intel_oaktrail: " Kefeng Wang
2019-09-25 15:04         ` Andy Shevchenko
2019-09-26  1:28           ` Kefeng Wang
2019-09-26  5:48             ` Andy Shevchenko
2019-09-26  6:09               ` Kefeng Wang
2019-09-26  7:32                 ` Andy Shevchenko
2019-09-26  7:48                   ` Kefeng Wang [this message]
2019-09-20  6:25 ` [PATCH 19/32] scsi: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 20/32] sh/intc: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 21/32] staging: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 22/32] fs: afs: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 23/32] vgacon: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 24/32] dma-debug: " Kefeng Wang
2019-09-25 17:13   ` Christoph Hellwig
2019-09-26  1:44     ` Kefeng Wang
2019-09-20  6:25 ` [PATCH 25/32] trace: " Kefeng Wang
2019-09-20 13:26   ` Steven Rostedt
2019-09-20  6:25 ` [PATCH 26/32] lib: cpu_rmap: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 27/32] ASoC: samsung: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 28/32] printk: Drop pr_warning Kefeng Wang
2019-09-20  6:25 ` [PATCH 29/32] tools lib api: Renaming pr_warning to pr_warn Kefeng Wang
2019-09-20  6:25 ` [PATCH 30/32] tools lib bpf: " Kefeng Wang
2019-09-22 21:07   ` Andrii Nakryiko
2019-09-23  8:20     ` Daniel Borkmann
2019-09-23 11:03       ` Petr Mladek
2019-09-23 13:35         ` Daniel Borkmann
2019-09-26  2:01           ` Kefeng Wang
2019-09-20  6:25 ` [PATCH 31/32] tools perf: " Kefeng Wang
2019-09-20  6:25 ` [PATCH 32/32] checkpatch: Drop pr_warning check Kefeng Wang
2019-09-20  9:29 ` [PATCH 00/32] Kill pr_warning in the whole linux code Sergey Senozhatsky
2019-10-02  8:55 ` Petr Mladek
2019-10-08  6:39   ` Kefeng Wang
2019-10-17 13:05     ` Petr Mladek
2019-10-17 13:29       ` Kefeng Wang
2019-10-17 13:52         ` Petr Mladek
2019-10-17 16:38         ` Joe Perches
2019-10-18  1:11           ` Kefeng Wang

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=4669c5b0-8587-92b7-a9da-5fbbb5255ff4@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=andy@infradead.org \
    --cc=corentin.chary@gmail.com \
    --cc=dvhart@infradead.org \
    --cc=linux-kernel@vger.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).