All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Karthik S <karthik.s@oss.qualcomm.com>
Cc: Srinivas Kandagatla <srini@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ASoC: codecs: wcd937x: Add conditional regulator control for wcd937x
Date: Thu, 2 Apr 2026 09:50:25 +0200	[thread overview]
Message-ID: <3f057f41-6017-4f7c-a934-1d27993c5bad@kernel.org> (raw)
In-Reply-To: <CAPg2bp0DeOcQB-=VJDC5SSiFLLFL6PBPJUBHXSOP9EJZA3+bqw@mail.gmail.com>

On 02/04/2026 09:34, Karthik S wrote:
> hi Krzysztof,
> 
> Sorry for the absence of changelog, i updated the dt-binding property
> description to indicate that the power supplies for some boards such as the
> IA MEZZ is on always-on-rails, please let me know if details are sufficient
> or need to expand more on it.

Don't top post. You simply ignored the comments. Respond inline to them
and do not send new versions.

Best regards,
Krzysztof

  parent reply	other threads:[~2026-04-02  7:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02  7:22 [PATCH v2] ASoC: codecs: wcd937x: Add conditional regulator control for wcd937x karthik.s
2026-04-02  7:30 ` Krzysztof Kozlowski
     [not found]   ` <CAPg2bp0DeOcQB-=VJDC5SSiFLLFL6PBPJUBHXSOP9EJZA3+bqw@mail.gmail.com>
2026-04-02  7:50     ` Krzysztof Kozlowski [this message]
2026-04-06  9:52   ` Karthik S
2026-04-02  8:29 ` Rob Herring (Arm)
2026-04-06  9:58   ` Karthik S
2026-04-02 11:23 ` Mark Brown
2026-04-10  5:40   ` Karthik S
2026-04-10 10:25     ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2026-04-08  2:53 kernel test robot

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=3f057f41-6017-4f7c-a934-1d27993c5bad@kernel.org \
    --to=krzk@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=karthik.s@oss.qualcomm.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=robh@kernel.org \
    --cc=srini@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.