From: Mark Brown <broonie@kernel.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Caleb Connolly <caleb.connolly@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Revert "regulator: qcom-rpmh: Revert "regulator: qcom-rpmh: Use PROBE_FORCE_SYNCHRONOUS""
Date: Tue, 16 May 2023 09:51:55 +0900 [thread overview]
Message-ID: <ZGLTq02Uq5mPJvxE@finisterre.sirena.org.uk> (raw)
In-Reply-To: <CAMi1Hd2-sZ9xFwq0-neoN+G93pv9Qgc94L71cwoimmpnVOkf6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
On Mon, May 15, 2023 at 11:01:31PM +0530, Amit Pundir wrote:
> On Mon, 15 May 2023 at 21:26, Bjorn Andersson <andersson@kernel.org> wrote:
> > PS. this is a patch in the regulator code, but I don't see Mark in the
> > recipients list...
> Sorry about that. I thought I had Mark copied over from the other
> thread, after-all he was the one who suggested this patch, but I
> didn't :facepalm:
Please resend a copy of the patch to me and...
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resemble what they're doing.
There's no need to resubmit to fix this alone.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-05-16 0:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 14:53 Amit Pundir
2023-05-15 15:05 ` Doug Anderson
2023-05-15 16:00 ` Bjorn Andersson
2023-05-15 17:31 ` Amit Pundir
2023-05-16 0:51 ` Mark Brown [this message]
2023-05-24 13:51 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-24 15:18 ` Amit Pundir
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=ZGLTq02Uq5mPJvxE@finisterre.sirena.org.uk \
--to=broonie@kernel.org \
--cc=agross@kernel.org \
--cc=amit.pundir@linaro.org \
--cc=andersson@kernel.org \
--cc=caleb.connolly@linaro.org \
--cc=dianders@chromium.org \
--cc=konrad.dybcio@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®