From: Andrew Morton <akpm@linux-foundation.org>
To: Dmitry <dbaryshkov@gmail.com>
Cc: david-b@pacbell.net, linux-kernel@vger.kernel.org,
dbrownell@users.sourceforge.net
Subject: Re: [PATCH] Make gpiochip label const
Date: Tue, 19 Aug 2008 11:28:28 -0700 [thread overview]
Message-ID: <20080819112828.dcfed0eb.akpm@linux-foundation.org> (raw)
In-Reply-To: <bc64b4640808190413o151cfb8x7809f0e08d1f7aaa@mail.gmail.com>
On Tue, 19 Aug 2008 15:13:47 +0400
Dmitry <dbaryshkov@gmail.com> wrote:
> 2008/8/19 Andrew Morton <akpm@linux-foundation.org>:
> > On Sun, 17 Aug 2008 23:00:35 +0400 Dmitry Baryshkov <dbaryshkov@gmail.com> wrote:
> >
> >> On Tue, Aug 12, 2008 at 03:06:19PM -0700, David Brownell wrote:
> >> > > From dbaryshkov@gmail.com Tue Aug 12 13:54:29 2008
> >> > > From: Dmitry Baryshkov <dbaryshkov@gmail.com>
> >> > > To: linux-kernel@vger.kernel.org
> >> > > Cc: Dmitry Baryshkov <dbaryshkov@gmail.com>,
> >> > > David Brownell <dbrownell@users.sourceforge.net>
> >> > > Subject: [PATCH] Make gpiochip label const
> >> > > Date: Wed, 13 Aug 2008 00:39:48 +0400
> >> > >
> >> > > Mark gpiochip label as a const char pointer.
> >> > >
> >> > > Signed-off-by: Dmitry Baryshkov <dbaryshkov@gmail.com>
> >> > > Cc: David Brownell <dbrownell@users.sourceforge.net>
> >> >
> >> > Acked-By: David Brownell <dbrownell@users.sourceforge.net>
> >> >
> >>
> >> Sorry to disturb, but will this make into 2.6.27-rc? Thanks.
> >>
> >
> > Ordinarily it would not. Is there some reason why you think it should?
> >
>
> It fixes lots of warnings (one per each instance of code filling the gpio chip)
That should have been in the changelog!
When fixing warnings or compilations errors, the compiler output should
also be in the changelog.
I don't recall seeing such warnings and I cannot make them happen with
drivers/gpio/gpiolib.c or with drivers/gpio/max732x.c or with
drivers/gpio/pca953x.c. So we still don't know what this patch
does :(
> and is pretty much small to honour inclusion IMO
Well sure it's small. But converting things to `const' carries a
fairly high risk of adding new warnings or breaking the build.
next prev parent reply other threads:[~2008-08-19 18:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 20:39 [PATCH] Make gpiochip label const Dmitry Baryshkov
2008-08-12 22:06 ` David Brownell
2008-08-17 19:00 ` Dmitry Baryshkov
2008-08-19 8:43 ` Andrew Morton
2008-08-19 11:13 ` Dmitry
2008-08-19 18:28 ` Andrew Morton [this message]
2008-08-20 8:39 ` Dmitry Baryshkov
2008-08-20 15:50 ` David Brownell
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=20080819112828.dcfed0eb.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=dbaryshkov@gmail.com \
--cc=dbrownell@users.sourceforge.net \
--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