public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Marc Zyngier <maz@wild-wind.fr.eu.org>,
	linux-kernel@vger.kernel.org,
	Andries Brouwer <Andries.Brouwer@cwi.nl>
Subject: Re: [PATCH] eisa.ids: Add Network Peripherals FDDI boards
Date: Mon, 1 Jun 2009 19:28:23 -0700	[thread overview]
Message-ID: <20090601192823.68befe31.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0905310041200.15490@ftp.linux-mips.org>

On Sun, 31 May 2009 00:54:26 +0100 (BST) "Maciej W. Rozycki" <macro@linux-mips.org> wrote:

>  Add EISA IDs for Network Peripherals FDDI boards.  Descriptions taken 
> from the respective EISA configuration files.
> 
> Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>
> ---
>  It's unlikely we'll ever support these cards, the problem being the lack 
> of documentation.  Assuming the policy for the EISA ID database is the 
> same as for PCI I'm sending these entries for the sake of completeness.
> 
>  Please apply.
> 
>   Maciej
> 
> patch-mips-2.6.27-rc8-20081004-npi-eisa-0
> Index: linux-mips-2.6.27-rc8-20081004-dolch/drivers/eisa/eisa.ids
> ===================================================================
> --- linux-mips-2.6.27-rc8-20081004-dolch.orig/drivers/eisa/eisa.ids
> +++ linux-mips-2.6.27-rc8-20081004-dolch/drivers/eisa/eisa.ids

Gee.  Nobody has altered that file in six years.  Then again, few new
EISA cards have been designed in that time...

  reply	other threads:[~2009-06-02  2:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-30 23:54 [PATCH] eisa.ids: Add Network Peripherals FDDI boards Maciej W. Rozycki
2009-06-02  2:28 ` Andrew Morton [this message]
2009-06-02  8:09   ` Marc Zyngier
2009-06-02 19:07     ` Maciej W. Rozycki

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=20090601192823.68befe31.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=maz@wild-wind.fr.eu.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