From: David Miller <davem@davemloft.net>
To: pebolle@tiscali.nl
Cc: valentinrothberg@gmail.com, jcmvbkbc@gmail.com, dg@emlix.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: s6gmac: remove driver
Date: Tue, 11 Nov 2014 11:30:07 -0500 (EST) [thread overview]
Message-ID: <20141111.113007.194586174190893576.davem@davemloft.net> (raw)
In-Reply-To: <1415694742.16021.11.camel@x220>
From: Paul Bolle <pebolle@tiscali.nl>
Date: Tue, 11 Nov 2014 09:32:22 +0100
> On Sun, 2014-10-19 at 13:28 -0400, David Miller wrote:
>> From: Max Filippov <jcmvbkbc@gmail.com>
>> Date: Sun, 19 Oct 2014 21:26:05 +0400
>>
>> > On Sun, Oct 19, 2014 at 8:45 PM, David Miller <davem@davemloft.net> wrote:
>> >> From: Daniel Glöckner <dg@emlix.com>
>> >> Date: Sun, 19 Oct 2014 00:49:05 +0200
>> >>
>> >>> The s6000 Xtensa support is removed from the kernel. There are no
>> >>> other chips using this driver.
>> >>
>> >> That's not what I see in Linus's current tree:
>> >
>> > David, s6000 removal is queued for 3.18.
>>
>> Then there is zero reason for me to apply this to my networking
>> tree.
>
> Commit 4006e565e150 ("xtensa: remove s6000 variant and s6105 platform")
> is included in linux-next as of next-20141111. So now we see:
> $ git grep XTENSA_VARIANT_S6000 next-20141111
> next-20141111:drivers/net/ethernet/Kconfig: depends on XTENSA_VARIANT_S6000
>
> Should Daniel resubmit, for net-next, perhaps with a commit explanation
> that references this commit?
When the s6000 removal shows up in Linus's tree, submit it.
next prev parent reply other threads:[~2014-11-11 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1413672385-8492-1-git-send-email-dg@emlix.com>
2014-10-18 22:49 ` [PATCH] net: s6gmac: remove driver Daniel Glöckner
2014-10-19 16:45 ` David Miller
2014-10-19 17:26 ` Max Filippov
2014-10-19 17:28 ` David Miller
2014-11-11 8:32 ` Paul Bolle
2014-11-11 16:30 ` David Miller [this message]
2014-12-21 19:27 ` [RESEND PATCH] " Daniel Glöckner
2014-12-22 21:29 ` David Miller
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=20141111.113007.194586174190893576.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dg@emlix.com \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pebolle@tiscali.nl \
--cc=valentinrothberg@gmail.com \
/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).