public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Tobias Ringstrom <tori@tellus.mine.nu>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tulip oops
Date: Mon, 13 Nov 2000 19:43:03 -0500	[thread overview]
Message-ID: <3A108A97.579DD607@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011140111480.20014-100000@svea.tellus>

Tobias Ringstrom wrote:
> 
> This patch makes tulip/eeprom.c more robust.
> 
> /Tobias
> 
> --- eeprom.c.orig       Mon Jun 19 22:42:39 2000
> +++ eeprom.c    Tue Nov 14 01:19:19 2000
> @@ -237,6 +237,7 @@
>                         printk(KERN_INFO "%s:  Index #%d - Media %s (#%d) described "
>                                    "by a %s (%d) block.\n",
>                                    dev->name, i, medianame[leaf->media], leaf->media,
> +                                  leaf->type >= ARRAY_SIZE(block_name) ? "UNKNOWN" :
>                                    block_name[leaf->type], leaf->type);
>                 }
>                 if (new_advertise)

Someone else already spotted that.

The patch is applied to the HEAD (a.k.a. devel a.k.a. unstable) branch
of the tulip CVS repository at:  http://sourceforge.net/projects/tulip/

It will be merged to the stable branch and 2.4.0-test11-preXX after some
testing of this and some other changes...

-- 
Jeff Garzik             |
Building 1024           | The chief enemy of creativity is "good" sense
MandrakeSoft            |          -- Picasso
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-14  1:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-14  0:16 [PATCH] tulip oops Tobias Ringstrom
2000-11-14  0:43 ` Jeff Garzik [this message]

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=3A108A97.579DD607@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tori@tellus.mine.nu \
    /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