From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] parport_pc: fix section mismatch warnings
Date: Fri, 14 Apr 2006 23:07:09 -0700 [thread overview]
Message-ID: <20060414230709.33b2f877.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060414225528.4ec40510.akpm@osdl.org>
On Fri, 14 Apr 2006 22:55:28 -0700 Andrew Morton wrote:
> "Randy.Dunlap" <rdunlap@xenotime.net> wrote:
> >
> > This still leaves 5 other PCI-related section mismatches, but I
> > don't think that they are a real problem unless there are some
> > hotplug-parport cards out there. If needed, I'll fix those too.
>
> It would be good to do so, please. Ideally we'll end up with zero such
> warnings, so any ones which newly appear will be obvious, so nobody will
> ever submit a patch which generates new warnings (hah).
OK, just drop this one, please, and I'll send a replacement
patch.
---
~Randy
prev parent reply other threads:[~2006-04-15 6:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 5:44 Randy.Dunlap
2006-04-15 5:55 ` Andrew Morton
2006-04-15 6:07 ` Randy.Dunlap [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=20060414230709.33b2f877.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®