From: Harry Wei <jiaweiwei.xiyou@gmail.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, arvino55@gmail.com
Subject: Re: [PATCH RESEND]Remove a warning for drivers/edac/i82975x_edac.c
Date: Fri, 10 Jun 2011 13:20:50 +0800 [thread overview]
Message-ID: <20110610052047.GB3643@gmail.com> (raw)
In-Reply-To: <20110609103747.59805668.randy.dunlap@oracle.com>
On Thu, Jun 09, 2011 at 10:37:47AM -0700, Randy Dunlap wrote:
> On Thu, 9 Jun 2011 11:04:13 +0800 Harry Wei wrote:
>
> > - page = (unsigned long) info->eap;
> > + page = (unsigned long long) info->eap;
>
> But page is still unsigned long, not unsigned long long...
Yup, but if we can define a 'unsigned long long' type?
>
> > if (info->xeap & 1)
> > - page |= 0x100000000ul;
> > + page |= 0x100000000ull;
>
> and just making this second change fixes the warning.
I will try my best. Can anyone give some other comments?
>
> I don't know what the right answer is, but this patch does not look
> complete to me.
I will try to give a v2.
>
> Back in April there was a discussion about this warning message and the
> conclusion was that this driver should be replaced. See
> https://lkml.org/lkml/2011/4/21/232 and its replies.
> But we seem to be having problems reaching the EDAC subsystem maintainer
> (again cc-ed).
You have not got a exact conclusion about this warning.
Maybe Arvind knows more about this warning.(cc'ed)
Thanks
Harry Wei
next prev parent reply other threads:[~2011-06-10 5:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 3:04 [PATCH RESEND]Remove a warning for drivers/edac/i82975x_edac.c Harry Wei
2011-06-09 4:26 ` Connor Hansen
2011-06-09 5:25 ` Harry Wei
2011-06-09 6:17 ` Connor Hansen
2011-06-10 5:07 ` Harry Wei
2011-06-09 16:35 ` Randy Dunlap
2011-06-09 17:37 ` Randy Dunlap
2011-06-10 5:20 ` Harry Wei [this message]
2011-06-10 6:42 ` Connor Hansen
2011-06-12 15:50 ` Arvind R
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=20110610052047.GB3643@gmail.com \
--to=jiaweiwei.xiyou@gmail.com \
--cc=arvino55@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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