From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Ariana.Lazar@microchip.com
Cc: jic23@kernel.org, dlechner@baylibre.com, nuno.sa@analog.com,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, linux-kernel@vger.kernel.org, andy@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/2] iio: adc: adding support for PAC1711
Date: Wed, 19 Nov 2025 17:58:22 +0200 [thread overview]
Message-ID: <aR3pHtpdfnqcPahC@smile.fi.intel.com> (raw)
In-Reply-To: <9741143f091acf1a2791ced6ea26f5cac720a283.camel@microchip.com>
On Wed, Nov 19, 2025 at 03:31:24PM +0000, Ariana.Lazar@microchip.com wrote:
>
> There has been an unsuccessful attempt to submit this function to the
> unaligned set. It was rejected because of the lack of current possible
> shared uses. Please see the discussion thread below:
>
> https://yhbt.net/lore/lkml/20240927083543.80275-1-
> marius.cristea@microchip.com/T/#u
Please, make sure you provide working links which should be this one if I am
not mistaken:
https://lore.kernel.org/r/20240927083543.80275-1-marius.cristea@microchip.com/T/#u
Also put lore site directly. I don't want to make my browser crawling from
whatever possibly fishing and malware sites.
What you provided is two non-working links.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-11-19 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 10:12 [PATCH 0/2] Adding support for Microchip PAC1711 Ariana Lazar
2025-10-15 10:12 ` [PATCH 1/2] dt-bindings: iio: adc: adding support for PAC1711 Ariana Lazar
2025-10-16 16:19 ` Conor Dooley
2025-10-19 9:04 ` Jonathan Cameron
2025-11-25 17:25 ` Ariana.Lazar
2025-10-15 10:12 ` [PATCH 2/2] " Ariana Lazar
2025-10-16 5:31 ` kernel test robot
2025-10-19 10:28 ` Jonathan Cameron
2025-11-19 15:31 ` Ariana.Lazar
2025-11-19 15:58 ` Andy Shevchenko [this message]
2025-10-23 7:31 ` Dan Carpenter
2025-10-19 10:31 ` [PATCH 0/2] Adding support for Microchip PAC1711 Jonathan Cameron
2025-10-19 15:02 ` Guenter Roeck
2025-10-23 12:36 ` Ariana.Lazar
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=aR3pHtpdfnqcPahC@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Ariana.Lazar@microchip.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@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).