linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Allen Pais <allen.lkml@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Kees Cook <keescook@chromium.org>,
	Romain Perier <romain.perier@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [GIT PULL] tasklets updates for v5.9-rc1
Date: Mon, 3 Aug 2020 12:05:55 -0700	[thread overview]
Message-ID: <202008031200.7A9BCE5C@keescook> (raw)

Hi Linus,

Please pull these tasklets updates for v5.9-rc1. These are the
infrastructure updates needed to support converting the tasklet API
to something more modern (and hopefully for removal further down the
road). There is a 300-patch series waiting in the wings to get set out
to subsystem maintainers, but these changes need to be present in the
kernel first. Since this has some treewide changes, I carried this series
for -next instead of paining Thomas with it in -tip, but it's got his Ack.
This is similar to the timer_struct modernization from a while back, but
not nearly as messy (I hope). :)

Thanks!

-Kees

The following changes since commit 11ba468877bb23f28956a35e896356252d63c983:

  Linux 5.8-rc5 (2020-07-12 16:34:50 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/tasklets-v5.9-rc1

for you to fetch changes up to 12cc923f1ccc1df467e046b02a72c2b3b321b6a2:

  tasklet: Introduce new initialization API (2020-07-30 11:16:01 -0700)

----------------------------------------------------------------
tasklets API update for v5.9-rc1

- Prepare for tasklet API modernization (Romain Perier, Allen Pais, Kees Cook)

----------------------------------------------------------------
Kees Cook (2):
      usb: gadget: udc: Avoid tasklet passing a global
      treewide: Replace DECLARE_TASKLET() with DECLARE_TASKLET_OLD()

Romain Perier (1):
      tasklet: Introduce new initialization API

 drivers/input/keyboard/omap-keypad.c   |  2 +-
 drivers/input/serio/hil_mlc.c          |  2 +-
 drivers/net/wan/farsync.c              |  4 ++--
 drivers/s390/crypto/ap_bus.c           |  2 +-
 drivers/staging/most/dim2/dim2.c       |  2 +-
 drivers/staging/octeon/ethernet-tx.c   |  2 +-
 drivers/tty/vt/keyboard.c              |  2 +-
 drivers/usb/gadget/udc/snps_udc_core.c |  6 ++---
 drivers/usb/host/fhci-sched.c          |  2 +-
 include/linux/interrupt.h              | 41 +++++++++++++++++++++++++++++-----
 kernel/backtracetest.c                 |  2 +-
 kernel/debug/debug_core.c              |  2 +-
 kernel/irq/resend.c                    |  2 +-
 kernel/softirq.c                       | 18 ++++++++++++++-
 net/atm/pppoatm.c                      |  2 +-
 net/iucv/iucv.c                        |  2 +-
 sound/drivers/pcsp/pcsp_lib.c          |  2 +-
 17 files changed, 70 insertions(+), 25 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2020-08-03 19:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 19:05 Kees Cook [this message]
2020-08-04 21:40 ` [GIT PULL] tasklets updates for v5.9-rc1 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=202008031200.7A9BCE5C@keescook \
    --to=keescook@chromium.org \
    --cc=allen.lkml@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romain.perier@gmail.com \
    --cc=tglx@linutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).