From: Michael Ellerman <mpe@ellerman.id.au>
To: Finn Thain <fthain@linux-m68k.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Joshua Thompson <funaho@jurai.org>
Subject: Re: [PATCH] MAINTAINERS: Exclude m68k-only drivers from powerpc entry
Date: Thu, 01 Jun 2023 17:30:51 +1000 [thread overview]
Message-ID: <87mt1jhc5w.fsf@mail.lhotse> (raw)
In-Reply-To: <f020b46c-f291-ad2f-6c4c-6bc79955e6f2@linux-m68k.org>
Finn Thain <fthain@linux-m68k.org> writes:
> On Wed, 31 May 2023, Geert Uytterhoeven wrote:
>> On Wed, May 31, 2023 at 2:50 PM Michael Ellerman <mpe@ellerman.id.au> wrote:
>> > The powerpc section has a "F:" entry for drivers/macintosh, matching
>> > all files in or below drivers/macintosh. That is correct for the most
>> > part, but there are a couple of m68k-only drivers in the directory, so
>> > exclude those.
>> >
>> > Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
>>
>> Thanks for your patch!
>>
>> > --- a/MAINTAINERS
>> > +++ b/MAINTAINERS
>> > @@ -11916,6 +11916,8 @@ L: linuxppc-dev@lists.ozlabs.org
>> > S: Odd Fixes
>> > F: arch/powerpc/platforms/powermac/
>> > F: drivers/macintosh/
>> > +X: drivers/macintosh/adb-iop.c
>> > +X: drivers/macintosh/via-macii.c
>> >
>> > LINUX FOR POWERPC (32-BIT AND 64-BIT)
>> > M: Michael Ellerman <mpe@ellerman.id.au>
>>
>> LGTM, as there are already entries for these two files under
>> "M68K ON APPLE MACINTOSH".
>
> Right. I should have addded those "X files" in commit 2ae92e8b9b7.
Or I should have suggested it when I acked that commit :}
cheers
next prev parent reply other threads:[~2023-06-01 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 12:50 [PATCH] MAINTAINERS: Exclude m68k-only drivers from powerpc entry Michael Ellerman
2023-05-31 12:59 ` Geert Uytterhoeven
2023-06-01 0:22 ` Finn Thain
2023-06-01 7:30 ` Michael Ellerman [this message]
2023-06-01 7:30 ` Michael Ellerman
2023-07-03 5: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=87mt1jhc5w.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=fthain@linux-m68k.org \
--cc=funaho@jurai.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linuxppc-dev@lists.ozlabs.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).