linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] MFD fixes for v4.17
Date: Wed, 23 May 2018 07:25:02 +0100	[thread overview]
Message-ID: <20180523062502.GS5130@dell> (raw)

Hi Linus,

This fix seemingly builds fine for me locally:

 [for-mfd-fixes]$ ls -l build-x86/drivers/mfd/cros_ec_spi.o 
  -rw-rw-r-- 1 lee lee 39880 May 23 06:59 build-x86/drivers/mfd/cros_ec_spi.o
 [for-mfd-fixes]$ ls -l build-multi-v7/drivers/mfd/cros_ec_spi.o 
  -rw-rw-r-- 1 lee lee 10032 May 23 06:59 build-multi-v7/drivers/mfd/cros_ec_spi.o

... but hasn't been soak tested in -next for any length of time.

The following changes since commit 771c577c23bac90597c685971d7297ea00f99d11:

  Linux 4.17-rc6 (2018-05-20 15:31:38 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/mfd-fixes-4.17

for you to fetch changes up to 11799564fc7eedff50801950090773928f867996:

  mfd: cros_ec: Retry commands when EC is known to be busy (2018-05-23 06:59:00 +0100)

----------------------------------------------------------------
Single fix correcting the handling for long-running commands; cros_ec_spi

----------------------------------------------------------------
Brian Norris (1):
      mfd: cros_ec: Retry commands when EC is known to be busy

 drivers/mfd/cros_ec_spi.c               | 24 ++++++++++++++++++++----
 drivers/platform/chrome/cros_ec_proto.c |  2 ++
 2 files changed, 22 insertions(+), 4 deletions(-)
 
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

                 reply	other threads:[~2018-05-23  6:25 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=20180523062502.GS5130@dell \
    --to=lee.jones@linaro.org \
    --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;
as well as URLs for NNTP newsgroup(s).