Linux Power Management development
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Kees Cook <keescook@chromium.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Linux-Next <linux-next@vger.kernel.org>,
	Fengguang Wu <fengguang.wu@intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH] PowerCap: Error with option -Werror=format-security
Date: Tue, 05 Nov 2013 15:25:38 +0100	[thread overview]
Message-ID: <17745805.W16rbqgmuH@vostro.rjw.lan> (raw)
In-Reply-To: <CAGXu5jJeixN6bAJh6KJWExyKiyJHFsFWboL7Z0Xtn2F-71zg5w@mail.gmail.com>

On Monday, November 04, 2013 11:51:25 AM Kees Cook wrote:
> On Mon, Nov 4, 2013 at 8:53 AM, Srinivas Pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> > Fix compile error with gcc option: -Werror=format-security for
> > dev_set_name(&control_type->dev, name)
> > Changed to
> > dev_set_name(&control_type->dev, "%s", name);
> >
> > Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
> > ---
> >  drivers/powercap/powercap_sys.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/powercap/powercap_sys.c b/drivers/powercap/powercap_sys.c
> > index 21814f9..8d0fe43 100644
> > --- a/drivers/powercap/powercap_sys.c
> > +++ b/drivers/powercap/powercap_sys.c
> > @@ -625,7 +625,7 @@ struct powercap_control_type *powercap_register_control_type(
> >         control_type->ops = ops;
> >         INIT_LIST_HEAD(&control_type->node);
> >         control_type->dev.class = &powercap_class;
> > -       dev_set_name(&control_type->dev, name);
> > +       dev_set_name(&control_type->dev, "%s", name);
> >         result = device_register(&control_type->dev);
> >         if (result) {
> >                 if (control_type->allocated)
> > --
> > 1.7.11.7
> 
> Thanks for getting this fixed!
> 
> Acked-by: Kees Cook <keescook@chromium.org>

Queued up for 3.13, thanks!

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

      reply	other threads:[~2013-11-05 14:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 16:53 [PATCH] PowerCap: Error with option -Werror=format-security Srinivas Pandruvada
2013-11-04 19:51 ` Kees Cook
2013-11-05 14:25   ` Rafael J. Wysocki [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=17745805.W16rbqgmuH@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=fengguang.wu@intel.com \
    --cc=keescook@chromium.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=srinivas.pandruvada@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox