From: Harvey Harrison <harvey.harrison@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Eduard Munteanu <eduard.munteanu@linux360.ro>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH-ugly] kmemtrace: casting a gfp_t requires __force
Date: Fri, 07 Nov 2008 11:22:39 -0800 [thread overview]
Message-ID: <1226085759.11596.43.camel@brick> (raw)
In-Reply-To: <20081107192029.GA4001@x200.localdomain>
On Fri, 2008-11-07 at 22:20 +0300, Alexey Dobriyan wrote:
> On Fri, Nov 07, 2008 at 10:58:41AM -0800, Harvey Harrison wrote:
> > --- a/include/linux/kmemtrace.h
> > +++ b/include/linux/kmemtrace.h
> > @@ -34,7 +34,7 @@ static inline void kmemtrace_mark_alloc_node(enum kmemtrace_type_id type_id,
> > "bytes_req %lu bytes_alloc %lu gfp_flags %lu node %d",
> > type_id, call_site, (unsigned long) ptr,
> > (unsigned long) bytes_req, (unsigned long) bytes_alloc,
> > - (unsigned long) gfp_flags, node);
> > + (__force unsigned long)gfp_flags, node);
>
> gfp_t is "unsigned int" actually. These casts are bogus.
>
> Subject: How do I printk <type> correctly?
>
> If variable is of Type use printk format specifier.
> ---------------------------------------------------------
> int %d or %x
> unsigned int %u or %x
> long %ld ot %lx
> unsigned long %lu or %lx
> long long %lld or %llx
> unsigned long long %llu or %llx
> size_t %zu or %zx
> ssize_t %zd or %zx
>
Perhaps add gfp_t to the list ;-)
Thanks.
Harvey
next prev parent reply other threads:[~2008-11-07 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 18:58 [PATCH-ugly] kmemtrace: casting a gfp_t requires __force Harvey Harrison
2008-11-07 19:20 ` Alexey Dobriyan
2008-11-07 19:22 ` Harvey Harrison [this message]
2008-11-07 19:38 ` Mathieu Desnoyers
2008-11-07 19:50 ` Harvey Harrison
2008-11-07 20:41 ` Alexey Dobriyan
2008-11-07 22:50 ` Eduard - Gabriel Munteanu
2008-11-07 23:08 ` Mathieu Desnoyers
2008-11-07 23:25 ` Alexey Dobriyan
2008-11-07 23:05 ` Eduard - Gabriel Munteanu
2008-11-07 23:06 ` Eduard - Gabriel Munteanu
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=1226085759.11596.43.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=adobriyan@gmail.com \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.