From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chris Metcalf <cmetcalf@mellanox.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: remove the tile tree?
Date: Tue, 5 Dec 2017 14:20:31 +1100 [thread overview]
Message-ID: <20171205142031.6941097b@canb.auug.org.au> (raw)
In-Reply-To: <d7d86b08-0c9b-6261-5860-712db6eadcee@mellanox.com>
Hi Chris,
On Mon, 4 Dec 2017 20:33:59 -0500 Chris Metcalf <cmetcalf@mellanox.com> wrote:
>
> On 12/4/2017 3:25 PM, Stephen Rothwell wrote:
> > Hi Chris,
> >
> > Given commit
> >
> > 8ee5ad1d4c0b ("arch/tile: mark as orphaned")
> >
> > in Linus' tree, should I remove the tile tree from linux-next?
>
> Yes, that would make sense. Good catch!
Done, thanks
--
Cheers,
Stephen Rothwell
prev parent reply other threads:[~2017-12-05 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 20:25 linux-next: remove the tile tree? Stephen Rothwell
2017-12-05 1:33 ` Chris Metcalf
2017-12-05 3:20 ` Stephen Rothwell [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=20171205142031.6941097b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cmetcalf@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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).