From: Paul Mundt <lethal@linux-sh.org>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux@arm.linux.org.uk, linux-m68k@lists.linux-m68k.org,
uclinux-dist-devel@blackfin.uclinux.org,
Linux Embedded <linux-embedded@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Daniel Walker <dwalker@soe.ucsc.edu>
Subject: Re: [PATCH 13/14] Pramfs: Write Protection
Date: Thu, 18 Jun 2009 15:28:33 +0900 [thread overview]
Message-ID: <20090618062833.GB2258@linux-sh.org> (raw)
In-Reply-To: <2ea1731b0906172324g4654966eq22cf0bdbd3eafabf@mail.gmail.com>
On Thu, Jun 18, 2009 at 08:24:35AM +0200, Marco Stornelli wrote:
> 2009/6/18 Paul Mundt <lethal@linux-sh.org>:
> > H8300 is a nommu platform, so it has no TLB to flush. Yoshinori Sato is
> > the maintainer. Consult the MAINTAINERS file, that's what it is there for.
>
> I know the MAINTAINERS file but for h8300 there isn't an exactly
> indication (/arch/h8300 as for the other archs).
>
The file patterns are a new thing, I guess not all of the platforms were
updated. In any event:
UCLINUX FOR RENESAS H8/300 (H8300)
P: Yoshinori Sato
M: ysato@users.sourceforge.jp
W: http://uclinux-h8.sourceforge.jp/
S: Supported
Which is basically the first thing you find when looking for H8.
next prev parent reply other threads:[~2009-06-18 6:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 16:58 [PATCH 13/14] Pramfs: Write Protection Marco
2009-06-17 17:10 ` Mike Frysinger
2009-06-18 2:57 ` Paul Mundt
2009-06-18 6:24 ` Marco Stornelli
2009-06-18 6:28 ` Paul Mundt [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-13 13:23 [PATCH 13/14] Pramfs: Write protection Marco
2009-06-17 2:35 ` Jared Hulbert
2009-06-17 7:07 ` Paul Mundt
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=20090618062833.GB2258@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=dwalker@soe.ucsc.edu \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux@arm.linux.org.uk \
--cc=marco.stornelli@gmail.com \
--cc=uclinux-dist-devel@blackfin.uclinux.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).