From: Stephen Boyd <swboyd@chromium.org>
To: Benson Leung <bleung@chromium.org>, Tzung-Bi Shih <tzungbi@kernel.org>
Cc: linux-kernel@vger.kernel.org, patches@lists.linux.dev,
chrome-platform@lists.linux.dev
Subject: [PATCH 0/4] platform/chrome: Random driver cleanups
Date: Mon, 2 Oct 2023 17:34:24 -0700 [thread overview]
Message-ID: <20231003003429.1378109-1-swboyd@chromium.org> (raw)
Here's some random chromeos driver cleanups that have been sitting in my
tree. I've noticed them while browsing the code for something I'm
working on.
Stephen Boyd (4):
platform/chrome: cros_ec_typec: Use semi-colons instead of commas
platform/chrome: cros_ec_typec: Use dev_err_probe() more
platform/chrome: cros_typec_vdm: Mark port_amode_ops const
platform/chrome: cros_ec_proto: Mark outdata as const
drivers/platform/chrome/cros_ec_proto.c | 2 +-
drivers/platform/chrome/cros_ec_typec.c | 18 +++++++++---------
drivers/platform/chrome/cros_typec_vdm.c | 2 +-
drivers/platform/chrome/cros_typec_vdm.h | 2 +-
include/linux/platform_data/cros_ec_proto.h | 2 +-
5 files changed, 13 insertions(+), 13 deletions(-)
base-commit: 0bb80ecc33a8fb5a682236443c1e740d5c917d1d
--
https://chromeos.dev
next reply other threads:[~2023-10-03 0:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 0:34 Stephen Boyd [this message]
2023-10-03 0:34 ` [PATCH 1/4] platform/chrome: cros_ec_typec: Use semi-colons instead of commas Stephen Boyd
2023-10-03 0:34 ` [PATCH 2/4] platform/chrome: cros_ec_typec: Use dev_err_probe() more Stephen Boyd
2023-10-03 0:34 ` [PATCH 3/4] platform/chrome: cros_typec_vdm: Mark port_amode_ops const Stephen Boyd
2023-10-03 0:34 ` [PATCH 4/4] platform/chrome: cros_ec_proto: Mark outdata as const Stephen Boyd
2023-10-03 22:11 ` [PATCH 0/4] platform/chrome: Random driver cleanups Prashant Malani
2023-10-04 3:50 ` patchwork-bot+chrome-platform
2023-10-05 1:56 ` patchwork-bot+chrome-platform
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=20231003003429.1378109-1-swboyd@chromium.org \
--to=swboyd@chromium.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=tzungbi@kernel.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).