All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Richard Leitner <richard.leitner@linux.dev>,
	Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Ladislav Michl <ladis@linux-mips.org>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Benjamin Bara <benjamin.bara@skidata.com>,
	Benjamin Bara <bbara93@gmail.com>,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Richard Leitner <richard.leitner@skidata.com>
Subject: Re: [PATCH v2 0/3] Add "mclk" support for maxim,max9867
Date: Tue, 28 Mar 2023 09:41:50 +0200	[thread overview]
Message-ID: <0aea4e60-f835-3bb0-f082-b7b799f2ad95@linaro.org> (raw)
In-Reply-To: <20230328055916.GA11037@g0hl1n.net>

On 28/03/2023 07:59, Richard Leitner wrote:
>> should be sent as incremental updates against current git, existing
>> patches will not be replaced.
> 
> 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?

Incremental updates, so new patch. Rebase on maintainer's tree next
branch or linux-next (usually linux-next is the easiest but for
cross-tree patches might create inapplicable series).

Best regards,
Krzysztof


WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Richard Leitner <richard.leitner@linux.dev>,
	Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Ladislav Michl <ladis@linux-mips.org>,
	Takashi Iwai <tiwai@suse.com>,
	Benjamin Bara <benjamin.bara@skidata.com>,
	Benjamin Bara <bbara93@gmail.com>,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Richard Leitner <richard.leitner@skidata.com>
Subject: Re: [PATCH v2 0/3] Add "mclk" support for maxim,max9867
Date: Tue, 28 Mar 2023 09:41:50 +0200	[thread overview]
Message-ID: <0aea4e60-f835-3bb0-f082-b7b799f2ad95@linaro.org> (raw)
In-Reply-To: <20230328055916.GA11037@g0hl1n.net>

On 28/03/2023 07:59, Richard Leitner wrote:
>> should be sent as incremental updates against current git, existing
>> patches will not be replaced.
> 
> 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?

Incremental updates, so new patch. Rebase on maintainer's tree next
branch or linux-next (usually linux-next is the easiest but for
cross-tree patches might create inapplicable series).

Best regards,
Krzysztof


  reply	other threads:[~2023-03-28  7:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 10:04 [PATCH v2 0/3] Add "mclk" support for maxim,max9867 richard.leitner
2023-03-03 10:04 ` [PATCH v2 1/3] ASoC: dt-bindings: maxim,max9867: convert txt bindings to yaml richard.leitner
2023-03-03 10:08   ` Krzysztof Kozlowski
2023-03-03 10:04 ` [PATCH v2 2/3] ASoC: dt-bindings: maxim,max9867: add clocks property richard.leitner
2023-03-03 10:09   ` Krzysztof Kozlowski
2023-03-03 10:19     ` Richard Leitner
2023-03-03 10:19       ` Richard Leitner
2023-03-03 10:04 ` [PATCH v2 3/3] ASoC: maxim,max9867: add "mclk" support richard.leitner
2023-03-06 13:32 ` [PATCH v2 0/3] Add "mclk" support for maxim,max9867 Mark Brown
2023-03-28  5:59   ` Richard Leitner
2023-03-28  5:59     ` Richard Leitner
2023-03-28  7:41     ` Krzysztof Kozlowski [this message]
2023-03-28  7:41       ` Krzysztof Kozlowski
2023-03-28 12:39     ` Mark Brown
2023-03-28 12:39       ` Mark Brown

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=0aea4e60-f835-3bb0-f082-b7b799f2ad95@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bbara93@gmail.com \
    --cc=benjamin.bara@skidata.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=ladis@linux-mips.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=richard.leitner@linux.dev \
    --cc=richard.leitner@skidata.com \
    --cc=robh+dt@kernel.org \
    --cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.