From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Joel Selvaraj <jo@jsfamily.in>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: Re: [PATCH 0/5] Add support for Xiaomi Poco F1 EBBG variant
Date: Wed, 13 Jul 2022 08:51:44 +0200 [thread overview]
Message-ID: <3184e602-33ea-14fb-485c-5f54d020cd8b@linaro.org> (raw)
In-Reply-To: <BY5PR02MB700920503721C0C490BDAE2FD9899@BY5PR02MB7009.namprd02.prod.outlook.com>
On 13/07/2022 06:35, Joel Selvaraj wrote:
> Hi Krzysztof Kozlowski
>
> On 12/07/22 18:57, Krzysztof Kozlowski wrote:
>> None of your patches reached recipients and mailing lists.
>
> Thanks for letting me know. I didnt notice. It was shown in patchwork
> website and I thought it reached the mailing list too. I have RESEND the
> patches. This time, the cover letter (0/5) seems to be in a different
> thread and the rest of the patches (1 to 5/5) seems to be in a different
> thread. But all of them reached the mailing list though. I am not sure
> what is causing the issue though. Can this accepted? or do I need to
> resend them again?
I saw your patches but not connected to cover letter. As you said, lore
also misses them from cover letter:
https://lore.kernel.org/all/BY5PR02MB700954C6003BC5D5B6AAB1B7D9899@BY5PR02MB7009.namprd02.prod.outlook.com/
but they are on the lists:
https://lore.kernel.org/all/BY5PR02MB7009A49AD394747ACB80F746D9899@BY5PR02MB7009.namprd02.prod.outlook.com/
It's fine, but you should fix your setup. You can use whatever tools you
prefer as long as you create proper result. The easiest is however to
use git format-patch --cover-letter -5 && git send-email ....
(and useful also git branch --edit-description && git git format-patch
--cover-letter --cover-from-description=subject).
Best regards,
Krzysztof
prev parent reply other threads:[~2022-07-13 6:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 11:12 [PATCH 0/5] Add support for Xiaomi Poco F1 EBBG variant Joel Selvaraj
2022-07-08 20:43 ` Konrad Dybcio
2022-07-09 11:15 ` Joel Selvaraj
2022-08-04 16:21 ` Pavel Machek
2022-08-19 2:45 ` Caleb Connolly
2022-07-12 13:27 ` Krzysztof Kozlowski
2022-07-13 4:35 ` Joel Selvaraj
2022-07-13 6:51 ` Krzysztof Kozlowski [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=3184e602-33ea-14fb-485c-5f54d020cd8b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jo@jsfamily.in \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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;
as well as URLs for NNTP newsgroup(s).