From: David Lechner <dlechner@baylibre.com>
To: Marius.Cristea@microchip.com, robh@kernel.org,
krzk+dt@kernel.org, jic23@kernel.org, nuno.sa@analog.com,
conor+dt@kernel.org, andy@kernel.org
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH 0/2] Add support for Microchip EMC1812
Date: Wed, 17 Sep 2025 08:38:31 -0500 [thread overview]
Message-ID: <a86f859e-d70e-4444-a867-b54fc2ff01a8@baylibre.com> (raw)
In-Reply-To: <5b46303db0c9efbd2c2adcba39b59082db82aa71.camel@microchip.com>
On 9/17/25 8:30 AM, Marius.Cristea@microchip.com wrote:
> Hi David,
>
>>>
>>> Current version of driver does not support interrupts, events and
>>> data
>>> buffering.
>>>
>>> Differences related to previous patch:
>>
>> This is confusing. I think this version is v1, so there is
>> no previous patch. So why does this say "previous patch"?
>> Is this actually v2?
>>
>
> No, this is the first patch. I put it there as a patch history and fill
> it up as the patch versioning progress.
>
Got it. Next time, it would be better to not add the changelog
until v2. We are not used to seeing that in v1. :-)
next prev parent reply other threads:[~2025-09-17 13:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 12:21 [PATCH 0/2] Add support for Microchip EMC1812 Marius Cristea
2025-09-17 12:21 ` [PATCH 1/2] dt-bindings: iio: temperature: add support for EMC1812 Marius Cristea
2025-09-17 14:31 ` Rob Herring (Arm)
2025-09-17 23:34 ` David Lechner
2025-09-25 14:27 ` Marius.Cristea
2025-09-17 12:21 ` [PATCH 2/2] " Marius Cristea
2025-09-18 3:07 ` kernel test robot
2025-09-20 11:51 ` Jonathan Cameron
2025-09-20 15:05 ` David Lechner
2025-09-23 5:31 ` Dan Carpenter
2025-09-17 13:25 ` [PATCH 0/2] Add support for Microchip EMC1812 David Lechner
2025-09-17 13:30 ` Marius.Cristea
2025-09-17 13:38 ` David Lechner [this message]
2025-09-20 11:33 ` Jonathan Cameron
2025-09-24 2:11 ` Guenter Roeck
2025-09-25 9:09 ` Marius.Cristea
2025-09-25 14:32 ` Guenter Roeck
2025-09-27 15:04 ` Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2025-10-29 15:50 Marius Cristea
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=a86f859e-d70e-4444-a867-b54fc2ff01a8@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Marius.Cristea@microchip.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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).