public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: [GIT PULL] timers-conversion updates for next
Date: Fri, 27 Oct 2017 02:36:08 -0700	[thread overview]
Message-ID: <20171027093608.GA15167@beast> (raw)

Hi Thomas,

Please pull these timer conversions for tip/timers/core. These are the
first batch that Martin asked us to carry in the timers tree.

Thanks!

-Kees

The following changes since commit 52f737c2da40259ac9962170ce608b6fb1b55ee4:

  timer: Provide wrappers safe for use with LOCKDEP (2017-10-20 11:07:46 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/timers-conversion-next

for you to fetch changes up to 74a0f5739292a636d337ad6f8d7cd0061636e0eb:

  scsi: smartpqi: Convert timers to use timer_setup() (2017-10-27 02:22:00 -0700)

----------------------------------------------------------------
First batch of scsi conversions that have been Reviewed or Acked.

----------------------------------------------------------------
Kees Cook (10):
      scsi: aic94xx: Convert timers to use timer_setup()
      scsi: be2iscsi: Convert timers to use timer_setup()
      scsi: bnx2i: Convert timers to use timer_setup()
      scsi: dc395x: Convert timers to use timer_setup()
      scsi: fcoe: Convert timers to use timer_setup()
      scsi: gdth: Convert timers to use timer_setup()
      scsi: isci: Convert timers to use timer_setup()
      scsi: libfc: Convert timers to use timer_setup()
      scsi: libiscsi: Convert timers to use timer_setup()
      scsi: smartpqi: Convert timers to use timer_setup()

 drivers/scsi/aic94xx/aic94xx_hwi.c    |  3 +--
 drivers/scsi/aic94xx/aic94xx_hwi.h    |  5 ++---
 drivers/scsi/aic94xx/aic94xx_scb.c    |  6 +++---
 drivers/scsi/aic94xx/aic94xx_tmf.c    | 13 ++++++-------
 drivers/scsi/be2iscsi/be_main.c       | 18 +++++++-----------
 drivers/scsi/bnx2fc/bnx2fc_fcoe.c     | 11 +++++------
 drivers/scsi/bnx2i/bnx2i.h            |  2 +-
 drivers/scsi/bnx2i/bnx2i_hwi.c        |  4 ++--
 drivers/scsi/bnx2i/bnx2i_iscsi.c      | 15 ++++-----------
 drivers/scsi/dc395x.c                 | 13 +++++--------
 drivers/scsi/fcoe/fcoe.c              |  2 +-
 drivers/scsi/fcoe/fcoe_transport.c    |  6 ++++--
 drivers/scsi/gdth.c                   |  6 ++----
 drivers/scsi/isci/host.c              | 12 ++++++------
 drivers/scsi/isci/isci.h              |  6 ++----
 drivers/scsi/isci/phy.c               |  4 ++--
 drivers/scsi/isci/port.c              |  4 ++--
 drivers/scsi/isci/port_config.c       |  8 ++++----
 drivers/scsi/libfc/fc_fcp.c           | 21 ++++++++++-----------
 drivers/scsi/libiscsi.c               | 16 ++++++----------
 drivers/scsi/smartpqi/smartpqi_init.c |  9 ++++-----
 include/scsi/libfcoe.h                |  2 +-
 22 files changed, 80 insertions(+), 106 deletions(-)

-- 
Kees Cook
Pixel Security

                 reply	other threads:[~2017-10-27  9:36 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=20171027093608.GA15167@beast \
    --to=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --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