From: Brian Norris <briannorris@chromium.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Wolfram Sang <wsa@the-dreams.de>
Cc: Lee Jones <lee.jones@linaro.org>,
Thierry Reding <thierry.reding@gmail.com>,
Olof Johansson <olof@lixom.net>,
Brian Norris <computersforpeace@gmail.com>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Enric Balletbo <enric.balletbo@collabora.co.uk>,
Shawn Nematbakhsh <shawnn@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Brian Norris <briannorris@chromium.org>
Subject: [RESEND PATCH 0/2] cros_ec: utilize cros_ec_cmd_xfer_status()
Date: Wed, 10 Aug 2016 13:37:17 -0700 [thread overview]
Message-ID: <1470861439-129201-1-git-send-email-briannorris@chromium.org> (raw)
Hi all,
This is a resend of some patches I sent previously:
https://lkml.org/lkml/2016/7/25/488
There are no changes to the patch content. Only some additional commit
description and tagging.
The cros_ec_cmd_xfer_status() helper (which helps us better handle some error
scenarios) is now present in v4.8-rc1.
These can be taken independently by their subsystem maintainers. (Wolfram and
Dmitry, who already acked them.)
Regards,
Brian
Brian Norris (2):
i2c: cros-ec-tunnel: Fix usage of cros_ec_cmd_xfer()
Input: cros_ec_keyb - Fix usage of cros_ec_cmd_xfer()
drivers/i2c/busses/i2c-cros-ec-tunnel.c | 2 +-
drivers/input/keyboard/cros_ec_keyb.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-08-10 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 20:37 Brian Norris [this message]
2016-08-10 20:37 ` [RESEND PATCH 1/2] i2c: cros-ec-tunnel: Fix usage of cros_ec_cmd_xfer() Brian Norris
2016-08-10 21:15 ` Guenter Roeck
2016-08-14 22:24 ` Wolfram Sang
2016-08-10 20:37 ` [RESEND PATCH 2/2] Input: cros_ec_keyb - " Brian Norris
2016-08-10 21:16 ` Guenter Roeck
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=1470861439-129201-1-git-send-email-briannorris@chromium.org \
--to=briannorris@chromium.org \
--cc=computersforpeace@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.co.uk \
--cc=gwendal@chromium.org \
--cc=javier@osg.samsung.com \
--cc=lee.jones@linaro.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=olof@lixom.net \
--cc=shawnn@chromium.org \
--cc=thierry.reding@gmail.com \
--cc=tomeu.vizoso@collabora.com \
--cc=wsa@the-dreams.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).