All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Duyck <alexander.h.duyck@linux.intel.com>
To: Bart Van Assche <bvanassche@acm.org>, Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] kernel/workqueue: Verify alloc_workqueue() argument list consistency
Date: Mon, 15 Apr 2019 13:46:46 -0700	[thread overview]
Message-ID: <6171ae280e2056cf21adc4481dd9b98e47cc6a30.camel@linux.intel.com> (raw)
In-Reply-To: <1555348186.161891.104.camel@acm.org>

On Mon, 2019-04-15 at 10:09 -0700, Bart Van Assche wrote:
> On Tue, 2019-03-19 at 10:40 -0700, Bart Van Assche wrote:
> > This patch avoids that gcc reports the following warning when building
> > with W=1:
> > 
> > kernel/workqueue.c:4250:2: warning: function alloc_workqueue might be a candidate for gnu_printf format attribute [-Wsuggest-attribute=format]
> >   vsnprintf(wq->name, sizeof(wq->name), fmt, args);
> > 
> > Cc: Lai Jiangshan <jiangshanlai@gmail.com>
> > Cc: Alexander Duyck <alexander.h.duyck@linux.intel.com>
> > Cc: Dan Williams <dan.j.williams@intel.com>
> > Fixes: 669de8bda87b ("kernel/workqueue: Use dynamic lockdep keys for workqueues")
> > Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> > ---
> >  include/linux/workqueue.h | 1 
> >  1 file changed, 1 insertion()
> > 
> > diff --git a/include/linux/workqueue.h b/include/linux/workqueue.h
> > index d59525fca4d3..30737b5183c0 100644
> > --- a/include/linux/workqueue.h
> > ﯦハ眥맗뾖⧮쟼⢮䪮竧ꇣ为 ,7 @@ extern struct workqueue_struct *system_freezable_power_efficient_wq;
> >   * RETURNS:
> >   * Pointer to the allocated workqueue on success, %NULL on failure.
> >   */
> > __printf(1, 4)
> >  struct workqueue_struct *alloc_workqueue(const char *fmt,
> >  					 unsigned int flags,
> >  					 int max_active, ...);
> 
> Ping?
> 
> Bart.

I'm not sure if your Cc list is really the right people to be reviewing
the patch. Wouldn't it make more sense to Cc the people who were on the
original patch that you are now fixing?


  reply	other threads:[~2019-04-15 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 17:40 [PATCH] kernel/workqueue: Verify alloc_workqueue() argument list consistency Bart Van Assche
2019-04-15 17:09 ` Bart Van Assche
2019-04-15 20:46   ` Alexander Duyck [this message]
2019-04-16 14:56 ` Tejun Heo

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=6171ae280e2056cf21adc4481dd9b98e47cc6a30.camel@linux.intel.com \
    --to=alexander.h.duyck@linux.intel.com \
    --cc=bvanassche@acm.org \
    --cc=dan.j.williams@intel.com \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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.