netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, Dan Carpenter <dan.carpenter@oracle.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH net-next 0/2] Delete obsolete wanrouter support
Date: Fri, 01 Feb 2013 16:35:12 -0800	[thread overview]
Message-ID: <1359765312.17807.19.camel@joe-AO722> (raw)
In-Reply-To: <1359761422-27629-1-git-send-email-paul.gortmaker@windriver.com>

On Fri, 2013-02-01 at 18:30 -0500, Paul Gortmaker wrote:
> The removal of wanrouter code was originally listed in the (now
> gone) feature removal file since May 2012, and an RFC of the
> deletion was posted[1] in late 2012.
[]
> In addition to resolving the build failures of the RFC by keeping
> stub headers, this also splits the change into two parts, just like
> the token ring removal did.  Part #1 decouples the mainline kernel
> from the expired subsystem, and part #2 does the large scale
> deletion of the subsystem content.

Thanks Paul.

  parent reply	other threads:[~2013-02-02  0:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 23:30 [PATCH net-next 0/2] Delete obsolete wanrouter support Paul Gortmaker
2013-02-01 23:30 ` [PATCH net-next 1/2] wanrouter: completely decouple obsolete code from kernel Paul Gortmaker
2013-02-01 23:30 ` [PATCH net-next 2/2] wanrouter: delete now orphaned header content, files/drivers Paul Gortmaker
2013-02-02  0:35 ` Joe Perches [this message]
2013-02-03  4:13 ` [PATCH net-next 0/2] Delete obsolete wanrouter support 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=1359765312.17807.19.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=acme@redhat.com \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=paul.gortmaker@windriver.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).