[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <55392d3d-6173-4add-9476-434c0ca1d4a5@sirena.org.uk>
Date: Tue, 28 Mar 2023 13:39:43 +0100
From: Mark Brown <broonie@...nel.org>
To: Richard Leitner <richard.leitner@...ux.dev>
Cc: Liam Girdwood <lgirdwood@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Ladislav Michl <ladis@...ux-mips.org>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Benjamin Bara <benjamin.bara@...data.com>,
Benjamin Bara <bbara93@...il.com>, alsa-devel@...a-project.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Richard Leitner <richard.leitner@...data.com>
Subject: Re: [PATCH v2 0/3] Add "mclk" support for maxim,max9867
On Tue, Mar 28, 2023 at 07:59:16AM +0200, Richard Leitner wrote:
> As Krzysztof requested some changes on the clocks property dt-bindings
> patch (#2) commit message... How should I handle this?
> The changes requested on the patch content (dts example) should be sent
> as incremental patch to the original series, I guess?
If it's just the commit message it's too late. Otherwise incremental
patches against current git.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists