From: David Miller <davem@davemloft.net>
To: ebiederm@xmission.com
Cc: James.Bottomley@HansenPartnership.com, netdev@vger.kernel.org,
James.Smart@Emulex.Com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi_netlink: Remove dead and buggy code
Date: Tue, 11 Sep 2012 18:48:46 -0400 (EDT) [thread overview]
Message-ID: <20120911.184846.1973557158791638595.davem@davemloft.net> (raw)
In-Reply-To: <878vcggp4n.fsf@xmission.com>
From: ebiederm@xmission.com (Eric W. Biederman)
Date: Tue, 11 Sep 2012 15:40:08 -0700
> So just for curiosity I searched the entire git history for scsi_nl_add_
> and the only commit that I found was the addition of that code to the
> tree in August of 2008.
>
> Does anyone have any reason to keep scsi_nl_add_transport or
> scsi_nl_add_driver that have never been used in the 4 years since
> they have been added?
That's basically the question on the table right now :-)
next prev parent reply other threads:[~2012-09-11 22:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pq5xjw4m.fsf@xmission.com>
2012-09-10 19:07 ` [PATCH] scsi_netlink: Remove dead and buggy code David Miller
2012-09-10 22:07 ` James Bottomley
2012-09-11 22:40 ` Eric W. Biederman
2012-09-11 22:48 ` David Miller [this message]
2012-09-13 20:24 ` 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=20120911.184846.1973557158791638595.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=James.Smart@Emulex.Com \
--cc=ebiederm@xmission.com \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@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).