From: Kees Cook <keescook@chromium.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] timers-conversion updates for next (part 4)
Date: Mon, 6 Nov 2017 14:01:44 -0800 [thread overview]
Message-ID: <20171106220144.GA65833@beast> (raw)
Hi Thomas,
Please pull these timer conversions for tip/timers/core. These are a couple
fixes and more conversions that have either been reviewed or have been
pending on the list long enough.
I expect at least one more pull that will have the last scsi fix and one
netfilter conversion. After that, there are 10 patches that will all be
late rc1 since they depend on multiple trees.
Details of the conversion progress is here:
https://marc.info/?l=linux-next&m=151000446600975&w=2
Thanks!
-Kees
The following changes since commit c7c2f3d9e86c2f09a514247d1623f00850125636:
Merge tag 'timers-conversion-next3' of https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux into timers/core (2017-11-03 00:06:08 +0100)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/timers-conversion-next4
for you to fetch changes up to 5ea22086ed42bef8dde93f45a42a3ace486eb788:
block/aoe: discover_timer: Convert timers to use timer_setup() (2017-11-06 12:50:09 -0800)
----------------------------------------------------------------
- a couple fixes for less common build configurations
- more stragglers that have either been reviewed or gone long enough on list
----------------------------------------------------------------
Kees Cook (7):
ARM: footbridge: Fix typo in timer conversion
drivers/pcmcia: omap1: Fix error in automated timer conversion
crypto: Convert timers to use timer_setup()
mailbox: Convert timers to use timer_setup()
drbd: Convert timers to use timer_setup()
ide: Convert timers to use timer_setup()
block/aoe: discover_timer: Convert timers to use timer_setup()
arch/arm/mach-footbridge/dc21285.c | 2 +-
drivers/block/aoe/aoemain.c | 44 +++++++-----------------------------
drivers/block/drbd/drbd_int.h | 4 ++--
drivers/block/drbd/drbd_main.c | 18 ++++++---------
drivers/block/drbd/drbd_receiver.c | 2 +-
drivers/block/drbd/drbd_req.c | 4 ++--
drivers/block/drbd/drbd_req.h | 2 +-
drivers/block/drbd/drbd_worker.c | 8 +++----
drivers/crypto/axis/artpec6_crypto.c | 6 ++---
drivers/crypto/mv_cesa.c | 4 ++--
drivers/crypto/picoxcell_crypto.c | 7 +++---
drivers/ide/ide-io.c | 4 ++--
drivers/ide/ide-probe.c | 2 +-
drivers/mailbox/mailbox-altera.c | 12 +++++-----
drivers/pcmcia/omap_cf.c | 4 +++-
include/linux/ide.h | 2 +-
16 files changed, 47 insertions(+), 78 deletions(-)
--
Kees Cook
Pixel Security
reply other threads:[~2017-11-06 22:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171106220144.GA65833@beast \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).