From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: vkolluri@cisco.com, netdev@vger.kernel.org, scofeldm@cisco.com,
roprabhu@cisco.com
Subject: Re: [PATCH net-next 1/2] enic: remove dead code
Date: Wed, 29 Sep 2010 19:57:20 -0700 (PDT) [thread overview]
Message-ID: <20100929.195720.241921649.davem@davemloft.net> (raw)
In-Reply-To: <20100930114958.59c438d7@s6510>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Thu, 30 Sep 2010 11:49:58 +0900
> Ok, but Linux tree is not the repository for "possible future enhancements".
> Do it or remove it.
Agreed, remove it now and add it back when you submit the patches that
use the code.
The code is in the repository history so it's not like it's lost.
next prev parent reply other threads:[~2010-09-30 2:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 6:29 [PATCH net-next 1/2] enic: remove dead code Stephen Hemminger
[not found] ` <212AA327A3557741A058E787E0618873042E0BC6@xmb-sjc-219.amer.cisco.com>
2010-09-30 2:49 ` Stephen Hemminger
2010-09-30 2:57 ` David Miller [this message]
2010-09-30 5:16 ` Vasanthy Kolluri (vkolluri)
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=20100929.195720.241921649.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=roprabhu@cisco.com \
--cc=scofeldm@cisco.com \
--cc=shemminger@vyatta.com \
--cc=vkolluri@cisco.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).