public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Android Kernel Team <kernel-team@android.com>
Subject: Re: [PATCH 01/13] android: lowmemorykiller: Fix warning on 64bit
Date: Wed, 07 Mar 2012 14:24:46 -0800	[thread overview]
Message-ID: <1331159086.2191.190.camel@work-vm> (raw)
In-Reply-To: <20120307220454.GA16555@kroah.com>

On Wed, 2012-03-07 at 14:04 -0800, Greg KH wrote:
> On Wed, Mar 07, 2012 at 01:58:11PM -0800, John Stultz wrote:
> > Fixes the following warning on 64bit:
> > drivers/staging/android/lowmemorykiller.c: In function ‘__check_minfree’:
> > drivers/staging/android/lowmemorykiller.c:215: warning: return from incompatible pointer type
> > 
> > CC: Greg KH <gregkh@linuxfoundation.org>
> > CC: Android Kernel Team <kernel-team@android.com>
> > Signed-off-by: John Stultz <john.stultz@linaro.org>
> > ---
> >  drivers/staging/android/lowmemorykiller.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/drivers/staging/android/lowmemorykiller.c b/drivers/staging/android/lowmemorykiller.c
> > index 052b43e..15a59c1 100644
> > --- a/drivers/staging/android/lowmemorykiller.c
> > +++ b/drivers/staging/android/lowmemorykiller.c
> > @@ -212,7 +212,7 @@ static void __exit lowmem_exit(void)
> >  module_param_named(cost, lowmem_shrinker.seeks, int, S_IRUGO | S_IWUSR);
> >  module_param_array_named(adj, lowmem_adj, int, &lowmem_adj_size,
> >  			 S_IRUGO | S_IWUSR);
> > -module_param_array_named(minfree, lowmem_minfree, uint, &lowmem_minfree_size,
> > +module_param_array_named(minfree, lowmem_minfree, ulong, &lowmem_minfree_size,
> >  			 S_IRUGO | S_IWUSR);
> 
> No, the correct fix for this is to make lowmem_minfree an int, not
> size_t, right?  I made that fix an hour ago in my tree.

Looks ok to me. I'll go ahead and drop this then.

thanks
-john



  reply	other threads:[~2012-03-07 22:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 21:58 [PATCH 00/13] staging: Android updates John Stultz
2012-03-07 21:58 ` [PATCH 01/13] android: lowmemorykiller: Fix warning on 64bit John Stultz
2012-03-07 22:04   ` Greg KH
2012-03-07 22:24     ` John Stultz [this message]
2012-03-07 21:58 ` [PATCH 02/13] android: ram_console: set CON_ANYTIME console flag John Stultz
2012-03-07 22:07   ` Greg KH
2012-03-07 21:58 ` [PATCH 03/13] android: ram_console: move footer strings John Stultz
2012-03-07 21:58 ` [PATCH 04/13] android: ram_console: drop early buffer support John Stultz
2012-03-07 21:58 ` [PATCH 05/13] android: ram_console: drop verbose ram_console support John Stultz
2012-03-07 21:58 ` [PATCH 06/13] android: ram_console: split out persistent ram John Stultz
2012-03-07 21:58 ` [PATCH 07/13] android: persistent_ram: refactor ecc support John Stultz
2012-03-07 22:21   ` Daniel Walker
2012-03-07 21:58 ` [PATCH 08/13] android: persistent_ram: handle reserving and mapping memory John Stultz
2012-03-07 22:08   ` Greg KH
2012-03-07 22:16     ` John Stultz
2012-03-08  1:46       ` Greg KH
2012-03-07 21:58 ` [PATCH 09/13] android: persistent_ram: make persistent_ram_write atomic John Stultz
2012-03-07 21:58 ` [PATCH 10/13] android: persistent_ram: add notrace to persistent_ram_write John Stultz
2012-03-07 21:58 ` [PATCH 11/13] android: persistent_trace: ftrace into persistent_ram John Stultz
2012-03-07 22:10   ` Greg KH
2012-03-07 22:40     ` John Stultz
2012-03-07 21:58 ` [PATCH 12/13] android: staging: ram_console: fix crash in ram_console_late_init John Stultz
2012-03-07 21:58 ` [PATCH 13/13] android: ram_console: honor dmesg_restrict John Stultz
2012-03-07 22:10   ` Greg KH
2012-03-07 22:11 ` [PATCH 00/13] staging: Android updates Greg KH

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=1331159086.2191.190.camel@work-vm \
    --to=john.stultz@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-team@android.com \
    --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