From: Alexey Dobriyan <adobriyan@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [PATCH 2.6.13-c1 2/17] fix sparse warnings (__nocast type)
Date: Tue, 05 Jul 2005 15:07:31 +0000 [thread overview]
Message-ID: <200507051907.31823.adobriyan@gmail.com> (raw)
In-Reply-To: <200507031848.19703.victor@cetuc.puc-rio.br>
On Tuesday 05 July 2005 18:06, Domen Puncer wrote:
> On 04/07/05 00:58 +0000, Victor Fusco wrote:
> > --- linux-2.6-git.orig/mm/slab.c 2005-07-03 15:00:06.000000000 +0000
> > +++ linux-2.6-git/mm/slab.c 2005-07-03 15:00:51.000000000 +0000
> > @@ -1425,7 +1426,7 @@
> > INIT_LIST_HEAD(&cachep->lists.slabs_free);
> >
> > if (flags & CFLGS_OFF_SLAB)
> > - cachep->slabp_cache = kmem_find_general_cachep(slab_size,0);
> > + cachep->slabp_cache = kmem_find_general_cachep(slab_size, 0u);
> > cachep->ctor = ctor;
> > cachep->dtor = dtor;
> > cachep->name = name;
> > @@ -2365,7 +2366,7 @@
> > * and can sleep. And it will allocate memory on the given node, which
> > * can improve the performance for cpu bound structures.
> > */
> > -void *kmem_cache_alloc_node(kmem_cache_t *cachep, int flags, int nodeid)
> > +void *kmem_cache_alloc_node(kmem_cache_t *cachep, unsigned int __nocast
> > flags, int nodeid)
>
> Line wrapped.
And doesn't change prototype.
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
prev parent reply other threads:[~2005-07-05 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 18:48 [KJ] [PATCH 2.6.13-c1 2/17] fix sparse warnings (__nocast type) Victor Fusco
2005-07-03 22:22 ` Alexey Dobriyan
2005-07-04 0:58 ` Victor Fusco
2005-07-05 14:06 ` Domen Puncer
2005-07-05 14:52 ` [KJ] [PATCH 2.6.13-c1 2/17] fix sparse warnings [UPDATE] Victor Fusco
2005-07-05 15:07 ` Alexey Dobriyan [this message]
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=200507051907.31823.adobriyan@gmail.com \
--to=adobriyan@gmail.com \
--cc=kernel-janitors@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 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.