From: Jose Javier Rodriguez Barbarin <dev-josejavier.rodriguez@duagon.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
dev-jorge.sanjuangarcia@duagon.com
Subject: Re: [RESEND PATCH v2 0/1] iio: Remove MODULE_ALIAS from men_z188_adc
Date: Thu, 29 Jan 2026 17:48:54 +0100 [thread overview]
Message-ID: <aXuPdgiszetBRSsx@MNI-190> (raw)
In-Reply-To: <20260129160502.33cb6a0a@jic23-huawei>
On Thu, Jan 29, 2026 at 04:05:02PM +0000, Jonathan Cameron wrote:
> On Fri, 23 Jan 2026 11:48:04 +0100
> Jose Javier Rodriguez Barbarin <dev-josejavier.rodriguez@duagon.com> wrote:
>
> Hi Jose,
>
> When resending the first thing we should see is a clear statement here
> at the top of the cover letter for why? I applied the previous posted
> version and not seeing any indication here on why I would consider this one.
>
> Jonathan
>
Hi Jonathan,
Thanks for your answer. First of all I would like to apologize myself.
I just resent the patch because I was not aware the v2 patch was already
applied, I came across yesterday while updating my linux-next local copy.
For a reason I cannot understand, I didn't receive your previous answer.
My bad.
Regards,
Javier R.
>
> > The first patches I sent for fixing the autoload problem encountered
> > on mcb device drivers were 2. The first [1] was focused on updating the
> > modpost process for letting kbuild to access to the data within
> > MODULE_DEVICE_TABLE and the second one [2] for removing the MODULE_ALIAS
> > on all mcb client drivers.
> >
> > They were rejected and Andy suggested me to split the second patch
> > in a per-driver basis instead of sending all drivers' changes in a
> > single patch once the first patch was merged.
> >
> > The first patch is already merged on Linus's Git repository for 6.19-rc4
> >
> > commit 1f4ea4838b13 ("mcb: Add missing modpost build support")
> >
> > So now I am sending this patch for removing MODULE_ALIAS on the mcb driver
> > in this subsystem as it is no longer required. This cleanup is being sent
> > to each affected subsystem separately, as per the review suggestion to ease
> > the handling for maintainers.
> >
> > [1] https://lore.kernel.org/all/20251127155452.42660-2-dev-josejavier.rodriguez@duagon.com/
> > [2] https://lore.kernel.org/all/20251127155452.42660-3-dev-josejavier.rodriguez@duagon.com/
> >
> > changes in v2:
> > - Renane commit message
> >
> > Jose Javier Rodriguez Barbarin (1):
> > iio: adc: men_z188_adc: drop unneeded MODULE_ALIAS
> >
> > drivers/iio/adc/men_z188_adc.c | 1 -
> > 1 file changed, 1 deletion(-)
> >
next prev parent reply other threads:[~2026-01-29 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 10:48 Jose Javier Rodriguez Barbarin
2026-01-23 10:48 ` [RESEND PATCH v2 1/1] iio: adc: men_z188_adc: drop unneeded MODULE_ALIAS Jose Javier Rodriguez Barbarin
2026-01-29 16:05 ` [RESEND PATCH v2 0/1] iio: Remove MODULE_ALIAS from men_z188_adc Jonathan Cameron
2026-01-29 16:48 ` Jose Javier Rodriguez Barbarin [this message]
2026-01-29 18:26 ` Jonathan Cameron
2026-01-30 11:40 ` Jose Javier Rodriguez Barbarin
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=aXuPdgiszetBRSsx@MNI-190 \
--to=dev-josejavier.rodriguez@duagon.com \
--cc=andy@kernel.org \
--cc=dev-jorge.sanjuangarcia@duagon.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®