From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: Lee Jones <lee@kernel.org>
Subject: [PATCH v1 0/5] mfd: intel-lpss: Set of cleanups
Date: Fri, 24 Nov 2023 21:31:23 +0200 [thread overview]
Message-ID: <20231124200258.3682979-1-andriy.shevchenko@linux.intel.com> (raw)
After looking into the latest changes in the driver I noticed one
wrong patch. That induced looking closer to the current state of
affairs in the driver. It appears that some code is outdated and
may be cleaned up. Hence this series.
Andy Shevchenko (5):
mfd: intel-lpss: Revert "Add missing check for platform_get_resource"
mfd: intel-lpss: Use device_get_match_data()
mfd: intel-lpss: Adjust header inclusions
mfd: intel-lpss: Move exported symbols to INTEL_LPSS namespace
mfd: intel-lpss: Provide Intel LPSS PM ops structure
drivers/mfd/intel-lpss-acpi.c | 27 ++++++++++++------------
drivers/mfd/intel-lpss-pci.c | 19 ++++++++++-------
drivers/mfd/intel-lpss.c | 39 +++++++++++++++++++++--------------
drivers/mfd/intel-lpss.h | 28 +------------------------
4 files changed, 51 insertions(+), 62 deletions(-)
--
2.43.0.rc1.1.gbec44491f096
next reply other threads:[~2023-11-24 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 19:31 Andy Shevchenko [this message]
2023-11-24 19:31 ` [PATCH v1 1/5] mfd: intel-lpss: Revert "Add missing check for platform_get_resource" Andy Shevchenko
2023-11-24 19:31 ` [PATCH v1 2/5] mfd: intel-lpss: Use device_get_match_data() Andy Shevchenko
2023-11-24 19:31 ` [PATCH v1 3/5] mfd: intel-lpss: Adjust header inclusions Andy Shevchenko
2023-11-24 19:31 ` [PATCH v1 4/5] mfd: intel-lpss: Move exported symbols to INTEL_LPSS namespace Andy Shevchenko
2023-11-24 19:31 ` [PATCH v1 5/5] mfd: intel-lpss: Provide Intel LPSS PM ops structure Andy Shevchenko
2023-11-30 14:45 ` [PATCH v1 0/5] mfd: intel-lpss: Set of cleanups Lee Jones
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=20231124200258.3682979-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.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