From: Guenter Roeck <linux@roeck-us.net>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
netdev@vger.kernel.org, linux-watchdog@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
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>
Subject: Re: [PATCH 0/7] Drop support for Renesys H8/300 architecture
Date: Fri, 30 Aug 2013 12:11:46 -0700 [thread overview]
Message-ID: <20130830191146.GA12090@roeck-us.net> (raw)
In-Reply-To: <20130830184611.GA27455@spo001.leaseweb.com>
On Fri, Aug 30, 2013 at 08:46:11PM +0200, Wim Van Sebroeck wrote:
> Hi Guenter,
>
> > 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.
>
> Agree. You may add my Acked-by.
> How do you plan to get this upstream? Do I need to take the watchdog in my tree or do you plan to keep the set of patches together in one tree?
>
My plan is create a branch on my repository on kernel.org, ask Stephen
to add it to linux-next, and then ask Linus to pull it after one
release cycle (ie for 3.13). This should give people enough time
to find out about it and complain, and give everyone else enough time
to find any missing pieces.
I would not mind if Linus would agree to pull it right away for 3.12,
but that seems to be a bit on the fast side.
Thanks,
Guenter
next prev parent reply other threads:[~2013-08-30 19:11 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
2013-08-30 18:46 ` Wim Van Sebroeck
2013-08-30 19:11 ` Guenter Roeck [this message]
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=20130830191146.GA12090@roeck-us.net \
--to=linux@roeck-us.net \
--cc=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=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).