public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rasmus Andersen <rasmus@jaquet.dk>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: Pavel Machek <pavel@suse.cz>,
	perex@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove warning from drivers/net/hp100.c (240-test12-pre7)
Date: Tue, 12 Dec 2000 14:49:43 +0100	[thread overview]
Message-ID: <20001212144943.L3742@jaquet.dk> (raw)
In-Reply-To: <20001208211908.D599@jaquet.dk> <20001209101924.A126@bug.ucw.cz> <20001209163740.U6567@cadcamlab.org> <20001211213208.B600@jaquet.dk> <14901.27835.458672.526580@wire.cadcamlab.org>
In-Reply-To: <14901.27835.458672.526580@wire.cadcamlab.org>; from peter@cadcamlab.org on Mon, Dec 11, 2000 at 06:09:31PM -0600

On Mon, Dec 11, 2000 at 06:09:31PM -0600, Peter Samuelson wrote:
> 
> [Rasmus Andersen]
> > How about this patch? It moves the offending struct to the __init
> > function where it is used and inside an existing #ifdef CONFIG_PCI.
> 
> Hmmmm, if you're messing around with the pci device table, why not just
> convert it to use new-style PCI init?  This is fairly easy to do (I did
> one driver myself, and that *proves* it's easy).  The main points:

I was looking into that regarding another driver anyway, so I'll try
my hand at that. Expect some b0rken patches soon :)

Regards,
  Rasmus
-
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-12-12 14:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-08 20:19 [PATCH] remove warning from drivers/net/hp100.c (240-test12-pre7) Rasmus Andersen
2000-12-09  9:19 ` Pavel Machek
2000-12-09 22:37   ` Peter Samuelson
2000-12-11 20:32     ` Rasmus Andersen
2000-12-12  0:09       ` Peter Samuelson
2000-12-12 13:49         ` Rasmus Andersen [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=20001212144943.L3742@jaquet.dk \
    --to=rasmus@jaquet.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=perex@suse.cz \
    --cc=peter@cadcamlab.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