From: Randy Dunlap <randy.dunlap@oracle.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [patch fixup] memcg: remove direct page_cgroup-to-page pointer fix
Date: Sat, 05 Feb 2011 10:04:10 -0800 [thread overview]
Message-ID: <4D4D911A.5080001@oracle.com> (raw)
In-Reply-To: <20110205090451.GA2315@cmpxchg.org>
On 02/05/11 01:04, Johannes Weiner wrote:
> On Fri, Feb 04, 2011 at 06:38:10PM -0800, Randy Dunlap wrote:
>> On Fri, 04 Feb 2011 15:15:17 -0800 akpm@linux-foundation.org wrote:
>>
>>> The mm-of-the-moment snapshot 2011-02-04-15-15 has been uploaded to
>>>
>>> http://userweb.kernel.org/~akpm/mmotm/
>>>
>>> and will soon be available at
>>>
>>> git://zen-kernel.org/kernel/mmotm.git
>>>
>>> It contains the following patches against 2.6.38-rc3:
>>
>>
>> Lots of these warnings in some kernel configs:
>>
>> mmotm-2011-0204-1515/include/linux/page_cgroup.h:144: warning: left shift count >= width of type
>> mmotm-2011-0204-1515/include/linux/page_cgroup.h:145: warning: left shift count >= width of type
>> mmotm-2011-0204-1515/include/linux/page_cgroup.h:150: warning: right shift count >= width of type
>
> Thanks for the report, Randy, and sorry for the breakage. Here is the
> fixup:
>
> ---
> Since the non-flags field for pc array ids in pc->flags is offset from
> the end of the word, we end up with a shift count of BITS_PER_LONG in
> case the field width is zero.
>
> This results in a compiler warning as we shift in both directions a
> long int by BITS_PER_LONG.
>
> There is no real harm -- the mask is zero -- but fix up the compiler
> warning by also making the shift count zero for a non-existant field.
>
> Reported-by: Randy Dunlap <randy.dunlap@oracle.com>
> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
> ---
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Thanks.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-02-05 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 23:15 mmotm 2011-02-04-15-15 uploaded akpm
2011-02-05 2:31 ` mmotm 2011-02-04-15-15 uploaded (printk DEFAULT_MESSAGE_LOGLEVEL) Randy Dunlap
2011-02-05 2:34 ` mmotm 2011-02-04-15-15 uploaded Stephen Rothwell
2011-02-05 2:43 ` Andrew Morton
2011-02-05 10:44 ` Johannes Weiner
2011-02-05 11:40 ` Johannes Weiner
2011-02-05 2:38 ` mmotm 2011-02-04-15-15 uploaded (page_cgroup.h) Randy Dunlap
2011-02-05 9:04 ` [patch fixup] memcg: remove direct page_cgroup-to-page pointer fix Johannes Weiner
2011-02-05 18:04 ` Randy Dunlap [this message]
2011-02-05 17:36 ` [PATCH -mmotm] staging/easycap: fix build when SND is not enabled Randy Dunlap
2011-02-06 7:25 ` Tomas Winkler
2011-02-06 16:01 ` Randy Dunlap
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=4D4D911A.5080001@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).