From: "David S. Miller" <davem@redhat.com>
To: hch@lst.de
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] switch iph5526_probe to initcalls
Date: Sun, 15 Jun 2003 11:03:58 -0700 (PDT) [thread overview]
Message-ID: <20030615.110358.10308169.davem@redhat.com> (raw)
In-Reply-To: <20030615180514.GA5006@lst.de>
From: Christoph Hellwig <hch@lst.de>
Date: Sun, 15 Jun 2003 20:05:14 +0200
On Sun, Jun 15, 2003 at 10:58:11AM -0700, David S. Miller wrote:
> p.s. it doesn't compile with or without the patch due to scsi issues..
>
> Can we put this patch on hold until that's resolved?
Well, we could. It's just that I doubt anyone will fix it anytime soon,
the hardware doesn't seem to be widely used and it's hard to touch the
driver without a barfbag nearby.
Ugh, ok.
At least it's impossible for you to break the tree
with this change. :)
next prev parent reply other threads:[~2003-06-15 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 18:00 [PATCH] switch iph5526_probe to initcalls Christoph Hellwig
2003-06-15 17:58 ` David S. Miller
2003-06-15 18:05 ` Christoph Hellwig
2003-06-15 18:03 ` David S. Miller [this message]
2003-06-15 18:10 ` Christoph Hellwig
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=20030615.110358.10308169.davem@redhat.com \
--to=davem@redhat.com \
--cc=hch@lst.de \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).