mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Lai Jiangshan <jiangshanlai@gmail.com>
Subject: [GIT PULL] wq fixes for v5.19-rc1
Date: Sat, 11 Jun 2022 14:29:04 -1000	[thread overview]
Message-ID: <YqUzUBjG4N9pKlsv@slm.duckdns.org> (raw)

Hello, Linus.

First signed pull. Please let me know if anything doesn't look right.
Thanks.

The following changes since commit e71e60cd74df9386c3f684c54888f2367050b831:

  Merge tag 'dma-mapping-5.19-2022-06-06' of git://git.infradead.org/users/hch/dma-mapping (2022-06-06 17:56:18 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git tags/wq-for-5.19-rc1-fixes

for you to fetch changes up to 8bee9dd953b69c634d1c9a3241a8b357469ad4aa:

  workqueue: Switch to new kerneldoc syntax for named variable macro argument (2022-06-11 14:16:42 -1000)

----------------------------------------------------------------
Workqueue fixes for v5.19-rc1

Tetsuo's patch to trigger build warnings if system-wide wq's are flushed
along with a TP type update and trivial comment update.

----------------------------------------------------------------
Jonathan Neuschäfer (1):
      workqueue: Switch to new kerneldoc syntax for named variable macro argument

Tetsuo Handa (1):
      workqueue: Wrap flush_workqueue() using a macro

Wonhyuk Yang (1):
      workqueue: Fix type of cpu in trace event

 include/linux/workqueue.h        | 66 ++++++++++++++++++++++++++++++++++------
 include/trace/events/workqueue.h |  8 ++---
 kernel/workqueue.c               | 16 +++++++---
 3 files changed, 73 insertions(+), 17 deletions(-)

--
tejun

             reply	other threads:[~2022-06-12  0:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12  0:29 Tejun Heo [this message]
2022-06-12 18:19 ` Linus Torvalds
2022-06-12 19:35   ` Tejun Heo
2022-06-12 18:40 ` pr-tracker-bot

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=YqUzUBjG4N9pKlsv@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®