From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Tim Gardner <tim.gardner@canonical.com>
Cc: <linux-kernel@vger.kernel.org>,
Ben Hutchings <ben@decadent.org.uk>,
James Bottomley <JBottomley@parallels.com>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] firmware: Remove obsolete Myricom firmware
Date: Wed, 25 Jul 2012 15:42:02 -0400 [thread overview]
Message-ID: <50104C0A.8050607@windriver.com> (raw)
In-Reply-To: <1343237441-102862-1-git-send-email-tim.gardner@canonical.com>
On 12-07-25 01:30 PM, Tim Gardner wrote:
> The Myricom GB driver firmware is no longer in use. Furthermore,
> CONFIG_MYRI_SBUS is no longer defined.
If there is going to be more of these, it is kind of nice to
have in the commit header a reference to the commit when the
original user(s) went away.
In this case, it was:
---
commit 1b9c4134c126aa8ae00a57672d4a4eaecc436b54
Author: Jon Mason <mason@myri.com>
Date: Mon Jun 20 12:51:22 2011 -0700
myri_sbus: remove driver
Remove the myri_sbus driver. Why?
* There is no possibility of ethernet mode on this adapter, so it's
Myrinet only.
* It won't inter-op with modern versions of Myrinet, and thus can only
work with legacy adapters.
* There are no in-kernel Linux drivers for the PCI version of this
adapter, so it only can work on ~15 year old Sun hardware.
It's long in the tooth, let's take it to the knackers.
Signed-off-by: Jon Mason <mason@myri.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
----
Thanks,
Paul.
>
> Cc: Paul Gortmaker <paul.gortmaker@windriver.com>
> Cc: Ben Hutchings <ben@decadent.org.uk>
> Cc: James Bottomley <JBottomley@Parallels.com>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
next prev parent reply other threads:[~2012-07-25 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 17:30 [PATCH] firmware: Remove obsolete Myricom firmware Tim Gardner
2012-07-25 19:42 ` Paul Gortmaker [this message]
2012-07-25 19:49 ` [PATCH v2] " Tim Gardner
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=50104C0A.8050607@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=JBottomley@parallels.com \
--cc=ben@decadent.org.uk \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.gardner@canonical.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