From: Simon Horman <horms@verge.net.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-sh@vger.kernel.org, Olof Johansson <olof@lixom.net>,
Paul Mundt <lethal@linux-sh.org>, Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bastian Hecht <hechtb@gmail.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: linux-next: manual merge of the sh tree with the tree
Date: Fri, 10 Jan 2014 11:19:54 +0900 [thread overview]
Message-ID: <20140110021954.GB14912@verge.net.au> (raw)
In-Reply-To: <20140110125529.9843f450bf79223164031b02@canb.auug.org.au>
[CC Magnus]
On Fri, Jan 10, 2014 at 12:55:29PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> On Fri, 10 Jan 2014 09:47:24 +0900 Simon Horman <horms@verge.net.au> wrote:
> >
> > On Wed, Jan 08, 2014 at 11:11:03PM -0800, Olof Johansson wrote:
> > >
> > > The request to merge the sh code came through Simon with claimed
> > > agreement from SH maintainers to do so -- I didn't verify this since
> > > they have in the past been well-coordinated. Simon?
> >
> > I spoke with Paul recently and my understanding is that
> > he hasn't been actively working in this area for over a year now.
> >
> > I guess there are some stale patches in his tree.
>
> That is certainly what it looks like. So, do I remove the sh{,.-current)
> trees (git://github.com/pmundt/linux-sh.git#sh-{latest,fixes-for-linus})
> from linux-next permanently? Will it be cleaned up any time soon?
I think that removing it would be a good choice.
> Is anyone maintaining/supporting sh now? Is it a candidate for pruning?
Its a topic of discussion at Renesas. And I hope that someone
will be doing some form of maintenance again soon.
next prev parent reply other threads:[~2014-01-10 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 1:13 Stephen Rothwell
2014-01-09 7:11 ` Olof Johansson
2014-01-10 0:47 ` Simon Horman
2014-01-10 1:55 ` Stephen Rothwell
2014-01-10 2:19 ` Simon Horman [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-16 3:00 Stephen Rothwell
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=20140110021954.GB14912@verge.net.au \
--to=horms@verge.net.au \
--cc=arnd@arndb.de \
--cc=hechtb@gmail.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=lethal@linux-sh.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®