* [PATCH] m68k: improve m68knommu MAINTAINERS entry
@ 2015-06-19 1:13 gerg
2015-06-19 6:58 ` Geert Uytterhoeven
0 siblings, 1 reply; 3+ messages in thread
From: gerg @ 2015-06-19 1:13 UTC (permalink / raw
To: linux-m68k, linux-kernel, geert; +Cc: Greg Ungerer
From: Greg Ungerer <gerg@uclinux.org>
Improve the information in the m68knommu maintainers entry. This
should aid in making it clearer what parts of the m68k architecture
code can go via the m68knommu git tree.
Specifically the entry now lists the relevant git tree where m68knommu
patches are promoted through. It also spells out that the coldfire
sub-architecture, and with it the directory of arch/m68k/coldfire, as
being supported via this tree.
Signed-off-by: Greg Ungerer <gerg@uclinux.org>
---
MAINTAINERS | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index d8afd29..bd0090d 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -10155,11 +10155,14 @@ S: Maintained
F: Documentation/filesystems/ubifs.txt
F: fs/ubifs/
-UCLINUX (AND M68KNOMMU)
+UCLINUX (M68KNOMMU AND COLDFIRE)
M: Greg Ungerer <gerg@uclinux.org>
W: http://www.uclinux.org/
+L: linux-m68k@lists.linux-m68k.org
L: uclinux-dev@uclinux.org (subscribers-only)
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git
S: Maintained
+F: arch/m68k/coldfire/
F: arch/m68k/*/*_no.*
F: arch/m68k/include/asm/*_no.*
--
1.9.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] m68k: improve m68knommu MAINTAINERS entry
2015-06-19 1:13 [PATCH] m68k: improve m68knommu MAINTAINERS entry gerg
@ 2015-06-19 6:58 ` Geert Uytterhoeven
2015-06-19 7:25 ` Greg Ungerer
0 siblings, 1 reply; 3+ messages in thread
From: Geert Uytterhoeven @ 2015-06-19 6:58 UTC (permalink / raw
To: Greg Ungerer; +Cc: Linux/m68k, linux-kernel@vger.kernel.org
Hi Greg,
On Fri, Jun 19, 2015 at 3:13 AM, <gerg@uclinux.org> wrote:
> From: Greg Ungerer <gerg@uclinux.org>
>
> Improve the information in the m68knommu maintainers entry. This
> should aid in making it clearer what parts of the m68k architecture
> code can go via the m68knommu git tree.
>
> Specifically the entry now lists the relevant git tree where m68knommu
> patches are promoted through. It also spells out that the coldfire
> sub-architecture, and with it the directory of arch/m68k/coldfire, as
> being supported via this tree.
>
> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
with minor nit below...
> ---
> MAINTAINERS | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d8afd29..bd0090d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -10155,11 +10155,14 @@ S: Maintained
> F: Documentation/filesystems/ubifs.txt
> F: fs/ubifs/
>
> -UCLINUX (AND M68KNOMMU)
> +UCLINUX (M68KNOMMU AND COLDFIRE)
> M: Greg Ungerer <gerg@uclinux.org>
> W: http://www.uclinux.org/
> +L: linux-m68k@lists.linux-m68k.org
> L: uclinux-dev@uclinux.org (subscribers-only)
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git
> S: Maintained
> +F: arch/m68k/coldfire/
And "arch/m68k/68*/", to catch 68000 and 68030?
> F: arch/m68k/*/*_no.*
> F: arch/m68k/include/asm/*_no.*
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] m68k: improve m68knommu MAINTAINERS entry
2015-06-19 6:58 ` Geert Uytterhoeven
@ 2015-06-19 7:25 ` Greg Ungerer
0 siblings, 0 replies; 3+ messages in thread
From: Greg Ungerer @ 2015-06-19 7:25 UTC (permalink / raw
To: Geert Uytterhoeven; +Cc: Linux/m68k, linux-kernel@vger.kernel.org
Hi Geert,
On 19/06/15 16:58, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Fri, Jun 19, 2015 at 3:13 AM, <gerg@uclinux.org> wrote:
>> From: Greg Ungerer <gerg@uclinux.org>
>>
>> Improve the information in the m68knommu maintainers entry. This
>> should aid in making it clearer what parts of the m68k architecture
>> code can go via the m68knommu git tree.
>>
>> Specifically the entry now lists the relevant git tree where m68knommu
>> patches are promoted through. It also spells out that the coldfire
>> sub-architecture, and with it the directory of arch/m68k/coldfire, as
>> being supported via this tree.
>>
>> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
>
> Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
> with minor nit below...
Thanks!
I'll add arch/m68k/68*/ to catch those too.
Regards
Greg
>> ---
>> MAINTAINERS | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index d8afd29..bd0090d 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -10155,11 +10155,14 @@ S: Maintained
>> F: Documentation/filesystems/ubifs.txt
>> F: fs/ubifs/
>>
>> -UCLINUX (AND M68KNOMMU)
>> +UCLINUX (M68KNOMMU AND COLDFIRE)
>> M: Greg Ungerer <gerg@uclinux.org>
>> W: http://www.uclinux.org/
>> +L: linux-m68k@lists.linux-m68k.org
>> L: uclinux-dev@uclinux.org (subscribers-only)
>> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/gerg/m68knommu.git
>> S: Maintained
>> +F: arch/m68k/coldfire/
>
> And "arch/m68k/68*/", to catch 68000 and 68030?
>
>> F: arch/m68k/*/*_no.*
>> F: arch/m68k/include/asm/*_no.*
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-06-19 7:24 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-06-19 1:13 [PATCH] m68k: improve m68knommu MAINTAINERS entry gerg
2015-06-19 6:58 ` Geert Uytterhoeven
2015-06-19 7:25 ` Greg Ungerer
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 read-only IMAP folder(s) and NNTP newsgroup(s).