From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg Ungerer <gerg@uclinux.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] m68k: improve m68knommu MAINTAINERS entry
Date: Fri, 19 Jun 2015 08:58:25 +0200 [thread overview]
Message-ID: <CAMuHMdWr8CDn0qO1_unnpthMePHQcbMa9Duxc0z40ZKk73sZ0g@mail.gmail.com> (raw)
In-Reply-To: <1434676392-12766-1-git-send-email-gerg@uclinux.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
next prev parent reply other threads:[~2015-06-19 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 1:13 [PATCH] m68k: improve m68knommu MAINTAINERS entry gerg
2015-06-19 6:58 ` Geert Uytterhoeven [this message]
2015-06-19 7:25 ` Greg Ungerer
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=CAMuHMdWr8CDn0qO1_unnpthMePHQcbMa9Duxc0z40ZKk73sZ0g@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@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).