public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Chen Gang F T <chen.gang.flying.transformer@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	netdev@vger.kernel.org, linux-watchdog@vger.kernel.org,
	Wim Van Sebroeck <wim@iguana.be>,
	"David S. Miller" <davem@davemloft.net>,
	Yoshinori Sato <ysato@users.sourceforge.jp>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Al Viro <viro@zeniv.linux.org.uk>, Eric Paris <eparis@redhat.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiang Liu <jiang.liu@huawei.com>,
	David Howells <dhowells@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH v2 0/8] Drop support for Renesas H8/300 architecture
Date: Mon, 02 Sep 2013 20:26:16 -0700	[thread overview]
Message-ID: <522556D8.803@roeck-us.net> (raw)
In-Reply-To: <52254F11.8070601@gmail.com>

On 09/02/2013 07:53 PM, Chen Gang F T wrote:
> Hello Guenter Roeck:
> 
> 
> I don't care about whether I am in cc mailing list, but at least,
> please help confirm 2 things:
> 
>    Is what I had done for h8300 just making wastes and noisy in kernel and related sub-system mailing list ?
> 
>    and is the disccusion about h8300 between us also wastes and noisy in kernel mailing list ?
> 

It raised my awareness of the status of h8300 maintenance,
so I would not see it as noise or waste. I might have suggested
a different target for your efforts, but that is your choice to make,
not mine.

On the code review side, I had suggested that you should not add new
ifdefs into code, much less unnecessary ones. Your counter-argument
was that you wanted to follow the existing coding style in the file
in question. To me, that argument is along the line of "the coding
style in this file is bad, let's do more of it".
That doesn't make much sense to me, so I did not bother to respond.
Setting that aside, it is not up to me to approve or reject your patches.
Whoever does that would be the one you have to convince.

Guenter


  reply	other threads:[~2013-09-03  3:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 23:51 [PATCH v2 0/8] Drop support for Renesas H8/300 architecture Guenter Roeck
2013-08-30 23:51 ` [PATCH v2 1/8] Drop support for Renesas H8/300 (h8300) architecture Guenter Roeck
2013-08-30 23:51 ` [PATCH v2 2/8] ide: Drop H8/300 driver Guenter Roeck
2013-08-30 23:51 ` [PATCH v2 3/8] net/ethernet: smsc9194: Drop conditional code for H8/300 Guenter Roeck
2013-08-30 23:51 ` [PATCH v2 4/8] net/ethernet: Drop H8/300 Ethernet driver Guenter Roeck
2013-08-30 23:51 ` [PATCH v2 5/8] watchdog: Drop references to H8300 architecture Guenter Roeck
2013-08-30 23:51 ` [PATCH v2 6/8] Drop MAINTAINERS entry for H8/300 Guenter Roeck
2013-08-30 23:51 ` [PATCH v2 7/8] Drop remaining references to H8/300 architecture Guenter Roeck
2013-08-30 23:51 ` [PATCH v2 8/8] fs/minix: Drop dependency on H8300 Guenter Roeck
2013-09-03  2:53 ` [PATCH v2 0/8] Drop support for Renesas H8/300 architecture Chen Gang F T
2013-09-03  3:26   ` Guenter Roeck [this message]
2013-09-03  3:52     ` Chen Gang F T
2013-09-03 19:39       ` Al Viro
2013-09-03 20:59         ` Guenter Roeck
2013-09-04  1:53           ` Chen Gang F T

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=522556D8.803@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=chen.gang.flying.transformer@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=eparis@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiang.liu@huawei.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wim@iguana.be \
    --cc=ysato@users.sourceforge.jp \
    /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