From: Andy Shevchenko <andy@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-pwm@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 0/2] pwm: lpss: module namespace fixes
Date: Mon, 3 Feb 2025 17:25:34 +0200 [thread overview]
Message-ID: <Z6Df7lmckX_gPgJG@smile.fi.intel.com> (raw)
In-Reply-To: <20250123101110.339337-4-u.kleine-koenig@baylibre.com>
On Thu, Jan 23, 2025 at 11:11:09AM +0100, Uwe Kleine-König wrote:
> Hello,
>
> in (implicit) v1[1] I suggested to move the MODULE_IMPORT_NS magic into
> include/linux/platform_data/x86/pwm-lpss.h. While I still consider that
> a good idea I was overruled and so here comes the variant with the
> explicit MODULE_IMPORT_NS in each module that makes use of the
> respective symbols.
>
> I don't have a fixed merge plan for this series (assuming it gets the
> expected Acks). Either way (both via pwm, both via pinctrl or the
> pinctrl patch first and the pwm one in the next cycle) is fine for me.
Pushed to my review and testing queue, thanks!
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2025-02-03 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 10:11 [PATCH v2 0/2] pwm: lpss: module namespace fixes Uwe Kleine-König
2025-01-23 10:11 ` [PATCH v2 1/2] pinctrl: intel: Import namespace for pwm_lpss function Uwe Kleine-König
2025-01-23 11:45 ` Andy Shevchenko
2025-01-23 14:52 ` Uwe Kleine-König
2025-01-23 15:48 ` Andy Shevchenko
2025-01-23 16:30 ` Uwe Kleine-König
2025-02-03 15:19 ` Andy Shevchenko
2025-01-23 10:11 ` [PATCH v2 2/2] pwm: lpss: Actually use a module namespace by defining the namespace earlier Uwe Kleine-König
2025-01-23 11:46 ` [PATCH v2 0/2] pwm: lpss: module namespace fixes Andy Shevchenko
2025-02-03 15:25 ` Andy Shevchenko [this message]
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=Z6Df7lmckX_gPgJG@smile.fi.intel.com \
--to=andy@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=u.kleine-koenig@baylibre.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.