From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Joel Selvaraj <joel.selvaraj@outlook.com>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
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 v2 0/3] Add support for Xiaomi Poco F1 EBBG variant
Date: Mon, 1 Aug 2022 18:00:19 +0300 [thread overview]
Message-ID: <CAA8EJpqBVaPt6dc+=u1YZwxEo9i4Y6+QFK5ko0Gd3091pKYXjw@mail.gmail.com> (raw)
In-Reply-To: <BY5PR02MB700972E09CC9D8ED6EFBA59AEA9A9@BY5PR02MB7009.namprd02.prod.outlook.com>
Hi,
On Mon, 1 Aug 2022 at 14:44, Joel Selvaraj <joel.selvaraj@outlook.com> wrote:
>
> To be honest, I have no idea why my patch series doesn't get linked
> properly. I think there is some issue in my OS. I use git format-patch
> and git send-mail to send patches. It used to work fine. But it doesn't
> want to work anymore :/ Is there a mailing list for sending test mails?
> or how do I debug this? Kindly let me know if anyone has any
> suggestions.
Judging from the following headers, it's not your OS, it is M$
rewriting the headers.
Message-ID: <BY5PR02MB70099020AC1D181D15909F64EA9A9@BY5PR02MB7009.namprd02.prod.outlook.com>
X-Microsoft-Original-Message-ID:
<20220801112512.209047-1-joel.selvaraj@outlook.com>
According to some mentions on the Internet, M$ relies on headers
rewriting and will not change this behaviour.
I'd suggest switching to another SMTP submission host. I think it
should be e.g. possible to tell GMail to send mails with @outlook.com
addresses. However this might confuse some of the mail clients into
believing it is spam since the email will SOFTFAIL the SPF check.
Switching to another mail provider might be an option too.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2022-08-01 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 11:25 [PATCH v2 0/3] Add support for Xiaomi Poco F1 EBBG variant Joel Selvaraj
2022-08-01 11:43 ` Joel Selvaraj
2022-08-01 15:00 ` Dmitry Baryshkov [this message]
2022-08-02 21:48 ` Joel Selvaraj
[not found] <20220801112512.209047-1-joel.selvaraj@outlook.com>
2022-08-01 11:25 ` [PATCH v2 1/3] arm64: dts: qcom: sdm845-xiaomi-beryllium: rename to sdm845-xiaomi-beryllium-tianma.dts Joel Selvaraj
2022-08-02 7:42 ` Krzysztof Kozlowski
2022-08-01 11:25 ` [PATCH v2 2/3] arm64: dts: qcom: sdm845-xiaomi-beryllium-common: move common nodes to a common dtsi Joel Selvaraj
2022-08-01 18:53 ` Marijn Suijten
2022-08-02 7:46 ` Krzysztof Kozlowski
2022-08-02 21:26 ` Joel Selvaraj
2022-08-02 7:41 ` Krzysztof Kozlowski
2022-08-01 11:25 ` [PATCH v3 3/3] arm64: dts: qcom: sdm845-xiaomi-beryllium-ebbg: introduce Xiaomi Poco F1 EBBG variant Joel Selvaraj
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='CAA8EJpqBVaPt6dc+=u1YZwxEo9i4Y6+QFK5ko0Gd3091pKYXjw@mail.gmail.com' \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=joel.selvaraj@outlook.com \
--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).