public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Baoquan He <bhe@redhat.com>
Cc: linux-kernel@vger.kernel.org, jiangshanlai@gmail.com,
	peterz@infradead.org, akpm@linux-foundation.org
Subject: Re: [PATCH] kernel/workqueue.c: fix DEFINE_PER_CPU_SHARED_ALIGNED expansion
Date: Wed, 11 Sep 2024 08:11:44 -1000	[thread overview]
Message-ID: <ZuHdYEncUmDee46Z@slm.duckdns.org> (raw)
In-Reply-To: <20240911050728.258817-1-bhe@redhat.com>

On Wed, Sep 11, 2024 at 01:07:28PM +0800, Baoquan He wrote:
> Make tags always produces below annoying warnings:
> 
> ctags: Warning: kernel/workqueue.c:470: null expansion of name pattern "\1"
> ctags: Warning: kernel/workqueue.c:474: null expansion of name pattern "\1"
> ctags: Warning: kernel/workqueue.c:478: null expansion of name pattern "\1"
> 
> In commit 25528213fe9f ("tags: Fix DEFINE_PER_CPU expansions"), codes in
> places have been adjusted including cpu_worker_pools definition. I noticed
> in commit 4cb1ef64609f ("workqueue: Implement BH workqueues to eventually
> replace tasklets"), cpu_worker_pools definition was unfolded back. Not
> sure if it was intentionally done or ignored carelessly.
> 
> Makes change to mute them specifically. 
> 
> Signed-off-by: Baoquan He <bhe@redhat.com>

Applied to wq/for-6.12.

Thanks.

-- 
tejun

      reply	other threads:[~2024-09-11 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11  5:07 [PATCH] kernel/workqueue.c: fix DEFINE_PER_CPU_SHARED_ALIGNED expansion Baoquan He
2024-09-11 18:11 ` Tejun Heo [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=ZuHdYEncUmDee46Z@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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