The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, jiangshanlai@gmail.com
Subject: [GIT PULL] workqueue changes for v6.7
Date: Mon, 30 Oct 2023 14:44:57 -1000	[thread overview]
Message-ID: <ZUBOCeLPnmgrE1qn@slm.duckdns.org> (raw)

The following changes since commit 06dc10eae55b5ceabfef287a7e5f16ceea204aa0:

  Merge tag 'fbdev-for-6.6-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev (2023-10-17 17:14:22 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git/ tags/wq-for-6.7

for you to fetch changes up to 265f3ed077036f053981f5eea0b5b43e7c5b39ff:

  workqueue: Provide one lock class key per work_on_cpu() callsite (2023-10-17 23:49:19 -1000)

----------------------------------------------------------------
workqueue: Changes for v6.7

Just one commit to improve lockdep annotation for work_on_cpu() to avoid
spurious warnings. I'll send another pull request for workqueue rust
binding.

----------------------------------------------------------------
Frederic Weisbecker (1):
      workqueue: Provide one lock class key per work_on_cpu() callsite

 include/linux/workqueue.h | 46 +++++++++++++++++++++++++++++++++++++++-------
 kernel/workqueue.c        | 20 ++++++++++++--------
 2 files changed, 51 insertions(+), 15 deletions(-)

-- 
tejun

             reply	other threads:[~2023-10-31  0:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31  0:44 Tejun Heo [this message]
2023-10-31  7:02 ` [GIT PULL] workqueue changes for v6.7 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=ZUBOCeLPnmgrE1qn@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