From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH v6 00/16] Revert h8300 archtecture support
Date: Tue, 10 Mar 2015 17:09:49 +0900 [thread overview]
Message-ID: <87mw3lmfxu.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20150310055522.GA9699@roeck-us.net>
At Mon, 9 Mar 2015 22:55:22 -0700,
Guenter Roeck wrote:
Thanks comment.
>
> On Mon, Mar 09, 2015 at 05:46:54PM +0900, Yoshinori Sato wrote:
> > Hello.
> >
> > I rewriting h8300 support.
> >
> It might possibly be better to use the term "re-introduce" instead of
> rewrite or revert (as in the headline).
>
> Also,
> s/archtecture/architecture/
>
> in the headline.
OK.
It's corrected next.
> Given that the reason for dropping the architecture in the first place was
> the lack of an active maintainer, I am somewhat surprised that you don't
> add one to the MAINTAINERS file.
Oh.
I add next.
> Guenter
--
Yoshinori Sato
<ysato@users.sourceforge.jp>
prev parent reply other threads:[~2015-03-10 8:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 8:46 [PATCH v6 00/16] Revert h8300 archtecture support Yoshinori Sato
2015-03-09 8:46 ` Yoshinori Sato
2015-03-09 8:46 ` [PATCH v6 01/16] h8300: Assembly headers Yoshinori Sato
2015-03-09 8:46 ` Yoshinori Sato
2015-03-09 8:46 ` [PATCH v6 02/16] h8300: UAPI headers Yoshinori Sato
2015-03-09 8:46 ` [PATCH v6 03/16] h8300: Exception and Interrupt handling Yoshinori Sato
2015-03-09 8:46 ` [PATCH v6 04/16] h8300: kernel booting Yoshinori Sato
2015-03-09 8:46 ` [PATCH v6 05/16] h8300: Process and signal Yoshinori Sato
2015-03-09 8:46 ` Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 06/16] h8300: CPU depend helpers Yoshinori Sato
2015-03-09 8:47 ` Yoshinori Sato
2015-03-09 16:21 ` Joe Perches
2015-03-09 16:21 ` Joe Perches
2015-03-09 17:55 ` Geert Uytterhoeven
2015-03-09 8:47 ` [PATCH v6 07/16] h8300: miscellaneous functions Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 08/16] h8300: Memory management Yoshinori Sato
2015-03-09 8:47 ` Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 09/16] h8300: library functions Yoshinori Sato
2015-03-09 8:47 ` Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 10/16] h8300: Build scripts Yoshinori Sato
2015-03-09 8:47 ` Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 11/16] h8300: clock driver Yoshinori Sato
2015-03-09 9:13 ` Jeff Kirsher
2015-03-10 7:46 ` Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 12/16] h8300: clocksource Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 13/16] h8300: configs Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 14/16] serial: Add h8300 Yoshinori Sato
2015-03-09 8:47 ` Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 15/16] Add ELF machine Yoshinori Sato
2015-03-09 9:10 ` Jeff Kirsher
2015-03-10 7:43 ` Yoshinori Sato
2015-03-09 8:47 ` [PATCH v6 16/16] mksysmap: Add h8300 local symbol pattern Yoshinori Sato
2015-03-09 8:47 ` Yoshinori Sato
2015-03-10 5:55 ` [PATCH v6 00/16] Revert h8300 archtecture support Guenter Roeck
2015-03-10 8:09 ` Yoshinori Sato [this message]
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=87mw3lmfxu.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).