From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>, ak@suse.de
Subject: Re: [PATCH -mm] x86_64: kill 19000+ sparse warnings
Date: Wed, 25 Apr 2007 23:21:55 -0700 [thread overview]
Message-ID: <46304503.4060505@oracle.com> (raw)
In-Reply-To: <20070425231452.929acac0.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 25 Apr 2007 23:07:56 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
>> oh. there is already an include/asm-x86_64/const.h that will help
>> with that. I'll try it out.
>
> No there isn't ;) There's a sparc64 one which looks good. Worth promoting
> to include/linux?
Did you look in -mm? I did.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-04-26 6:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 5:45 [PATCH -mm] x86_64: kill 19000+ sparse warnings Randy Dunlap
2007-04-26 5:55 ` Andrew Morton
2007-04-26 6:07 ` Randy Dunlap
2007-04-26 6:14 ` Andrew Morton
2007-04-26 6:21 ` Randy Dunlap [this message]
2007-04-26 6:28 ` Andrew Morton
2007-04-26 6:33 ` Randy Dunlap
2007-04-26 7:15 ` [PATCH -mm, v2] " Randy Dunlap
2007-04-26 9:24 ` [PATCH -mm] " Andi Kleen
2007-04-27 6:49 ` Jan Engelhardt
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=46304503.4060505@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.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