From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: sparse cleanups for ia32 subsystem
Date: Thu, 07 Oct 2004 08:04:14 +0000 [thread overview]
Message-ID: <16740.63614.271870.57061@napali.hpl.hp.com> (raw)
In-Reply-To: <16738.33692.510681.306179@napali.hpl.hp.com>
>>>>> On Wed, 06 Oct 2004 15:39:58 -0700, Arun Sharma <arun.sharma@intel.com> said:
Arun> On 10/5/2004 4:21 AM, David Mosberger wrote: Hi David,
>> Hi Arun,
>> Below is a complete patch for the sparse-triggered changes to the
>> ia32 subsystem. I take it you may have done some of this already
>> but I hope the patch is still useful. Please feed the patches to
>> Tony as you see fit.
Arun> Thanks for doing this! I've taken care of the remaining sparse
Arun> warnings and fixed up a couple of issues you found. Details
Arun> inside the patch.
Looks great to me!
Arun> Tony, please apply.
Once this patch hits Tony's patch, there is no excuse anymore to not
run sparse. I'd highly recommend it to everyone hacking on the kernel
as it can find some nasty bugs.
--david
prev parent reply other threads:[~2004-10-07 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 11:21 sparse cleanups for ia32 subsystem David Mosberger
2004-10-06 22:39 ` Arun Sharma
2004-10-07 8:04 ` David Mosberger [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=16740.63614.271870.57061@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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