All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Randy Dunlap <rdunlap@infradead.org>,
	Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] powerpc: delete duplicated words
Date: Mon, 27 Jul 2020 09:55:31 +1000	[thread overview]
Message-ID: <87wo2pg7bg.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <b796e912-e945-3cb1-03f8-0f38009634a4@infradead.org>

Randy Dunlap <rdunlap@infradead.org> writes:
> On 7/26/20 7:29 AM, Christophe Leroy wrote:
>> Randy Dunlap <rdunlap@infradead.org> a écrit :
>> 
>>> Drop duplicated words in arch/powerpc/ header files.
>> 
>> How did you detect them ? Do you have some script for tgat, or you just read all comments ?
>
> Yes, it's a script that finds lots of false positives, so I have to check
> each and every one of them for validity.
>
>>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>> 
>> You say you Cc Michael, but in fact you don't ... Allthough he is the powerpc maintainer
>
> Thanks for noticing that.
> [time passes]
> I checked all of my emails for this patch series and they say that Mike was Cc:ed
> on all of them.
>
> I am adding his email address back to this one.
> Mike, did you receive this patch series?

Yes.

There's a mailman option which drops me from being explicity on Cc,
because I'm subscribed to the list. Otherwise I get two copies of
everything.

So as long as it goes to linuxppc-dev I should see it, regardless of
whether I'm explicitly listed in Cc.

cheers

WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Randy Dunlap <rdunlap@infradead.org>,
	Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/9] powerpc: delete duplicated words
Date: Mon, 27 Jul 2020 09:55:31 +1000	[thread overview]
Message-ID: <87wo2pg7bg.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <b796e912-e945-3cb1-03f8-0f38009634a4@infradead.org>

Randy Dunlap <rdunlap@infradead.org> writes:
> On 7/26/20 7:29 AM, Christophe Leroy wrote:
>> Randy Dunlap <rdunlap@infradead.org> a écrit :
>> 
>>> Drop duplicated words in arch/powerpc/ header files.
>> 
>> How did you detect them ? Do you have some script for tgat, or you just read all comments ?
>
> Yes, it's a script that finds lots of false positives, so I have to check
> each and every one of them for validity.
>
>>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>> 
>> You say you Cc Michael, but in fact you don't ... Allthough he is the powerpc maintainer
>
> Thanks for noticing that.
> [time passes]
> I checked all of my emails for this patch series and they say that Mike was Cc:ed
> on all of them.
>
> I am adding his email address back to this one.
> Mike, did you receive this patch series?

Yes.

There's a mailman option which drops me from being explicity on Cc,
because I'm subscribed to the list. Otherwise I get two copies of
everything.

So as long as it goes to linuxppc-dev I should see it, regardless of
whether I'm explicitly listed in Cc.

cheers

  parent reply	other threads:[~2020-07-26 23:55 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26  0:38 [PATCH 0/9] powerpc: delete duplicated words Randy Dunlap
2020-07-26  0:38 ` Randy Dunlap
2020-07-26  0:38 ` [PATCH 1/9] powerpc: book3s: mmu-hash.h: delete duplicated word Randy Dunlap
2020-07-26  0:38   ` Randy Dunlap
2020-07-26  0:38 ` [PATCH 2/9] powerpc: book3s: radix-4k.h: " Randy Dunlap
2020-07-26  0:38   ` Randy Dunlap
2020-07-26  0:38 ` [PATCH 3/9] powerpc: cputime.h: " Randy Dunlap
2020-07-26  0:38   ` Randy Dunlap
2020-07-26  0:38 ` [PATCH 4/9] powerpc: epapr_hcalls.h: delete duplicated words Randy Dunlap
2020-07-26  0:38   ` Randy Dunlap
2020-07-26  0:38 ` [PATCH 5/9] powerpc: hw_breakpoint.h: delete duplicated word Randy Dunlap
2020-07-26  0:38   ` Randy Dunlap
2020-07-26  0:38 ` [PATCH 6/9] powerpc: ppc_asm.h: " Randy Dunlap
2020-07-26  0:38   ` Randy Dunlap
2020-07-26  0:38 ` [PATCH 7/9] powerpc: reg.h: " Randy Dunlap
2020-07-26  0:38   ` Randy Dunlap
2020-07-26  0:38 ` [PATCH 8/9] powerpc: smu.h: " Randy Dunlap
2020-07-26  0:38   ` Randy Dunlap
2020-07-26  0:38 ` [PATCH 9/9] powerpc: powernv: pci.h: " Randy Dunlap
2020-07-26  0:38   ` Randy Dunlap
2020-07-26 14:29 ` [PATCH 0/9] powerpc: delete duplicated words Christophe Leroy
2020-07-26 14:29   ` Christophe Leroy
2020-07-26 17:23   ` Randy Dunlap
2020-07-26 17:23     ` Randy Dunlap
2020-07-26 17:49     ` Joe Perches
2020-07-26 17:49       ` Joe Perches
2020-07-26 19:08       ` Randy Dunlap
2020-07-26 19:08         ` Randy Dunlap
2020-07-26 20:48         ` Joe Perches
2020-07-26 20:48           ` Joe Perches
2020-07-27  6:51         ` Joe Perches
2020-07-27  6:51           ` Joe Perches
2020-07-27  7:33           ` [PATCH] checkpatch: Add test for repeated words Joe Perches
2020-07-28  0:03             ` Randy Dunlap
2020-07-28  1:25               ` Joe Perches
2020-07-26 23:55     ` Michael Ellerman [this message]
2020-07-26 23:55       ` [PATCH 0/9] powerpc: delete duplicated words Michael Ellerman
2020-07-27  7:26 ` Michael Ellerman
2020-07-27  7:26   ` Michael Ellerman

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=87wo2pg7bg.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.