From: David Miller <davem@davemloft.net>
To: gregkh@linuxfoundation.org
Cc: linux@roeck-us.net, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, netdev@vger.kernel.org,
linux-watchdog@vger.kernel.org, wim@iguana.be,
viro@zeniv.linux.org.uk, eparis@redhat.com, jiang.liu@huawei.com,
dhowells@redhat.com, tglx@linutronix.de, sfr@canb.auug.org.au,
torvalds@linux-foundation.org
Subject: Re: [PATCH 0/7] Drop support for Renesys H8/300 architecture
Date: Fri, 30 Aug 2013 14:30:20 -0400 (EDT) [thread overview]
Message-ID: <20130830.143020.1246803952303746167.davem@davemloft.net> (raw)
In-Reply-To: <20130830165550.GA8151@kroah.com>
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: Fri, 30 Aug 2013 09:55:50 -0700
> On Fri, Aug 30, 2013 at 09:40:35AM -0700, Guenter Roeck wrote:
>> H8/300 has been dead for several years, the kernel for it has
>> not compiled for ages, and recent versions of gcc for it are broken.
>> It is time to drop support for it.
>>
>> Yes, I understand it is not that simple to drop an architecture,
>> and it may need some discussion, but someone has to put a stake
>> into the ground. Keeping a virtually dead architecture on life support
>> takes resources which are better spent elsewhere.
>
> If this doesn't build, and no one is using it anymore, I agree, it
> should be removed. If someone wants to revive it, 'git revert' works
> just fine.
>
> You can put my:
>
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> on these patches, unless someone steps up to be the active maintainer of
> the arch and gets it building/working again.
I completely agree with Greg, and for the IDE and networking bits:
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2013-08-30 18:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 16:40 [PATCH 0/7] Drop support for Renesys H8/300 architecture Guenter Roeck
2013-08-30 16:40 ` [PATCH 1/7] Drop support for Renesys H8/300 (h8300) architecture Guenter Roeck
2013-08-30 23:01 ` Sergei Shtylyov
2013-08-30 23:47 ` Guenter Roeck
2013-08-30 16:40 ` [PATCH 2/7] ide: Drop H8/300 driver Guenter Roeck
2013-08-30 16:40 ` [PATCH 3/7] net/ethernet: smsc: Drop conditional code for H8/300 Guenter Roeck
2013-08-30 16:40 ` [PATCH 4/7] net/ethernet: Drop H8/300 Ethernet driver Guenter Roeck
2013-08-30 16:40 ` [PATCH 5/7] watchdog: Drop references to H8300 architecture Guenter Roeck
2013-08-30 16:40 ` [PATCH 6/7] Drop MAINTAINERS entry for H8/300 Guenter Roeck
2013-08-30 16:40 ` [PATCH 7/7] Drop remaining references to H8/300 architecture Guenter Roeck
2013-08-30 16:55 ` [PATCH 0/7] Drop support for Renesys " Greg Kroah-Hartman
2013-08-30 18:30 ` David Miller [this message]
2013-08-30 18:46 ` Wim Van Sebroeck
2013-08-30 19:11 ` Guenter Roeck
2013-08-30 19:14 ` Linus Torvalds
2013-08-30 19:37 ` Guenter Roeck
2013-08-31 6:44 ` Geert Uytterhoeven
2013-08-31 13:56 ` Guenter Roeck
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=20130830.143020.1246803952303746167.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=eparis@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiang.liu@huawei.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=netdev@vger.kernel.org \
--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 \
/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).