linux-kernel - Re: [PATCH] net: s6gmac: remove driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 11 Nov 2014 09:32:22 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	David Miller <davem@...emloft.net>
Cc:	Valentin Rothberg <valentinrothberg@...il.com>, jcmvbkbc@...il.com,
	dg@...ix.com, netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: s6gmac: remove driver

On Sun, 2014-10-19 at 13:28 -0400, David Miller wrote:
> From: Max Filippov <jcmvbkbc@...il.com>
> Date: Sun, 19 Oct 2014 21:26:05 +0400
> 
> > On Sun, Oct 19, 2014 at 8:45 PM, David Miller <davem@...emloft.net> wrote:
> >> From: Daniel Glöckner <dg@...ix.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?


Paul Bolle


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/