All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: Richard Yang <weiyang@linux.vnet.ibm.com>,
	Jiri Kosina <jkosina@suse.cz>,
	Stefani Seibold <stefani@seibold.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove untouched code in kfifo_in
Date: Tue, 23 Oct 2012 12:39:03 -0700	[thread overview]
Message-ID: <20121023123903.626f9a7d.akpm@linux-foundation.org> (raw)
In-Reply-To: <CAFLxGvyQxdfm9KUcaUSJV5g19zGa71w=a8ma0xxWVuGsrdkzMQ@mail.gmail.com>

On Tue, 23 Oct 2012 21:25:46 +0200
richard -rw- weinberger <richard.weinberger@gmail.com> wrote:

> > Subject: [PATCH] Replace the type check code with typecheck() in kfifo_in
> >
> > In kfifo_in marco, one piece of code which is arounded by if(0) will check the
> > type of __tmp->ptr_const and __buf. If they are different type, there will
> > output a warning during compiling. This piece of code is not self explaining
> > and a little bit hard to understand.
> >
> > Based on Andrew Morton's suggestion, this patch replace this with typecheck()
> > which will be easy to understand.
> > ---
> >  include/linux/kfifo.h |    5 +----
> >  1 files changed, 1 insertions(+), 4 deletions(-)
> >
> > diff --git a/include/linux/kfifo.h b/include/linux/kfifo.h
> > index 10308c6..b48fe71 100644
> > --- a/include/linux/kfifo.h
> > +++ b/include/linux/kfifo.h
> > @@ -512,10 +512,7 @@ __kfifo_uint_must_check_helper( \
> >         unsigned long __n = (n); \
> >         const size_t __recsize = sizeof(*__tmp->rectype); \
> >         struct __kfifo *__kfifo = &__tmp->kfifo; \
> > -       if (0) { \
> > -               typeof(__tmp->ptr_const) __dummy __attribute__ ((unused)); \
> > -               __dummy = (typeof(__buf))NULL; \
> > -       } \
> > +       typecheck(typeof(__tmp->ptr_const), __buf);\
> >         (__recsize) ?\
> >         __kfifo_in_r(__kfifo, __buf, __n, __recsize) : \
> >         __kfifo_in(__kfifo, __buf, __n); \
> 
> What about all the other open coded type checks in that file?

Yes, there are a lot.  Searching for "if (0)" finds them.

  reply	other threads:[~2012-10-23 19:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 13:59 [PATCH] remove untouched code in kfifo_in Wei Yang
2012-10-18 22:37 ` richard -rw- weinberger
2012-10-19  5:23   ` Stefani Seibold
2012-10-19  7:34     ` Jiri Kosina
2012-10-22 23:56       ` Andrew Morton
     [not found]         ` <508600ba.a7fe440a.4c19.fffff64bSMTPIN_ADDED@mx.google.com>
2012-10-23 19:25           ` richard -rw- weinberger
2012-10-23 19:39             ` Andrew Morton [this message]
     [not found]     ` <5080f0b3.85712b0a.0d0f.ffff9dd2SMTPIN_ADDED@mx.google.com>
2012-10-19  8:14       ` richard -rw- weinberger
     [not found]         ` <50810e61.688c320a.1baa.6cacSMTPIN_ADDED@mx.google.com>
2012-10-19  8:28           ` richard -rw- weinberger
     [not found] <1350463837-30244-1-git-send-email-weiyang@linux.vnet.ibm.com>
2012-10-17 12:37 ` Jiri Kosina
     [not found]   ` <20121017140136.GA7913@richard.(null)>
2012-10-17 14:05     ` Jiri Kosina
2012-10-17 19:51       ` Stefani Seibold
     [not found]         ` <20121018015959.GD4511@richard.(null)>
2012-10-18  5:34           ` Stefani Seibold
2012-10-18  7:00             ` Jiri Kosina

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=20121023123903.626f9a7d.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=stefani@seibold.net \
    --cc=weiyang@linux.vnet.ibm.com \
    /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.