From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH v2 8/9] hwmon: (it87) Manage device specific features with table
Date: Mon, 29 Oct 2012 15:30:00 +0000 [thread overview]
Message-ID: <20121029163000.1660d0e2@endymion.delvare> (raw)
In-Reply-To: <1351448401-13985-9-git-send-email-linux@roeck-us.net>
On Mon, 29 Oct 2012 06:53:47 -0700, Guenter Roeck wrote:
> On Mon, Oct 29, 2012 at 01:39:58PM +0100, Jean Delvare wrote:
> > On Sun, 28 Oct 2012 11:20:00 -0700, Guenter Roeck wrote:
> > > diff --git a/drivers/hwmon/it87.c b/drivers/hwmon/it87.c
> > > index 340c4ea..f3f3e79 100644
> > > --- a/drivers/hwmon/it87.c
> > > +++ b/drivers/hwmon/it87.c
> > > @@ -228,6 +228,59 @@ static const u8 IT87_REG_TEMP_OFFSET[] = { 0x56, 0x57, 0x59 };
> > > #define IT87_REG_AUTO_TEMP(nr, i) (0x60 + (nr) * 8 + (i))
> > > #define IT87_REG_AUTO_PWM(nr, i) (0x65 + (nr) * 8 + (i))
> > >
> > > +struct it87_devices {
> > > + const char * const name;
> >
> > What is the second const good for?
>
> const char (equivalent to char const) The content is const
> * const The pointer is const
I know that. My question was: what is the point of making "name" a
const pointer here? I don't think it adds any value.
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2012-10-29 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 18:20 [lm-sensors] [PATCH v2 8/9] hwmon: (it87) Manage device specific features with table Guenter Roeck
2012-10-29 12:39 ` Jean Delvare
2012-10-29 13:53 ` Guenter Roeck
2012-10-29 15:30 ` Jean Delvare [this message]
2012-10-29 15:43 ` Guenter Roeck
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=20121029163000.1660d0e2@endymion.delvare \
--to=khali@linux-fr.org \
--cc=lm-sensors@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.