From: Abel Vesa <abel.vesa@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Amol Maheshwari <amahesh@qti.qualcomm.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-remoteproc@vger.kernel.org
Subject: Re: [PATCH v9 2/2] MAINTAINERS: Update fastrpc documentation file from txt to yaml
Date: Tue, 6 Sep 2022 14:11:51 +0300 [thread overview]
Message-ID: <Yxcq9xQFmpsTlqC4@linaro.org> (raw)
In-Reply-To: <872bffe6-416e-0d15-5994-0cf80c2063b4@linaro.org>
On 22-09-06 12:57:58, Krzysztof Kozlowski wrote:
> On 06/09/2022 12:30, Abel Vesa wrote:
> > The documentation for fastrpc bingings is now YAML. So update the
> > MAINTAINERS file.
> >
> > Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
>
> Abel, I sent you two messages about this patch that it is not
> bisectable. You did not respond to them, regarding maintainers entry, so
> I don't know what to think.
Hmm, for some reason I thought the MAINTAINERS file update needs to go through a
different tree.
Sorry for the missunderstanding.
Will squash it then.
>
> This must be squashed.
>
> Best regards,
> Krzysztof
prev parent reply other threads:[~2022-09-06 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 10:30 [PATCH v9 1/2] dt-bindings: misc: fastrpc convert bindings to yaml Abel Vesa
2022-09-06 10:30 ` [PATCH v9 2/2] MAINTAINERS: Update fastrpc documentation file from txt " Abel Vesa
2022-09-06 10:57 ` Krzysztof Kozlowski
2022-09-06 11:11 ` Abel Vesa [this message]
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=Yxcq9xQFmpsTlqC4@linaro.org \
--to=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=amahesh@qti.qualcomm.com \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
/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