[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230329235108.iwrk2m6ozsi3bsyh@intel.intel>
Date: Thu, 30 Mar 2023 01:51:08 +0200
From: Andi Shyti <andi.shyti@...nel.org>
To: Wolfram Sang <wsa@...nel.org>, Andi Shyti <andi.shyti@...nel.org>,
linux-i2c@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Chris Packham <chris.packham@...iedtelesis.co.nz>,
Ryan Chen <ryan_chen@...eedtech.com>
Subject: Re: [PATCH v5 0/3] Add the clock stretching i2c property
Hi Wolfram,
On Wed, Mar 29, 2023 at 09:06:43PM +0200, Wolfram Sang wrote:
>
> > The DTS schema has been applied in commit c83dd2cb836e ("schemas:
> > i2c: Add the clock stretching property").
>
> Everyone, A general remark: If bindings for the dtschema are added,
> please include the linux-i2c mailing list. This binding is OK, but it
> would be good to have the discussion also here for additional input.
Thanks for letting me know. It's actually my mistake, as I didn't
check how to properly distribute the patch to all relevant
parties.
Regarding dtschema patches, they are typically submitted as
GitHub pull requests. How should I send it to the linux-i2c?
Should I also send it to the mailing list like any other patch?
(This might make the code review process somewhat confusing,
though).
Thanks,
Andi
Powered by blists - more mailing lists