linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-next@vger.kernel.org
Subject: linux-next:  tree build warning
Date: Tue, 31 Mar 2009 16:22:34 +1100	[thread overview]
Message-ID: <20090331162234.1780e0a4.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 553 bytes --]

Hi Rusty,

Today's linux-next build (powerpc ppc64_defconfig) produced this warning:

mm/allocpercpu.c: In function 'free_percpu':
mm/allocpercpu.c:146: warning: passing argument 2 of '__percpu_depopulate_mask' discards qualifiers from pointer target type

Caused by commit c36dd4785de7e87979e0c27aa53dff116ddf37c5
("cpumask:core-use-new-functions").

The "cpumask_t *" argument to __percpu_depopulate_mask() could be marked
"const".
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-03-31  5:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31  5:22 Stephen Rothwell [this message]
2009-04-06  5:08 ` [PATCH] percpu: __percpu_depopulate_mask can take a const mask Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-04-23  6:17 linux-next: tree build warning Stephen Rothwell
2009-04-23  6:43 ` Ingo Molnar
2009-03-16  8:14 Stephen Rothwell
2009-03-20  0:22 ` Neil Brown
2009-03-12  5:48 Stephen Rothwell
2009-03-12  6:37 ` Nick Piggin
2009-03-12  6:42   ` Stephen Rothwell
2008-12-15 13:35 Stephen Rothwell
2008-12-15 13:56 ` Thomas Gleixner
2008-12-03 23:33 Stephen Rothwell
2008-10-28  7:13 Stephen Rothwell
2008-10-30 18:05 ` Christoph Lameter

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=20090331162234.1780e0a4.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-next@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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).