From: Fabio Estevam <festevam@gmail.com>
To: Pierluigi Passaro <pierluigi.passaro@gmail.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, linux-imx@nxp.com,
pierluigi.p@variscite.com, marex@denx.de, peng.fan@nxp.com,
marcel.ziswiler@toradex.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, eran.m@variscite.com,
nate.d@variscite.com
Subject: Re: [PATCH] arm64: dts: imx8mm: Fix pad control for UART1_DTE_RX
Date: Sun, 15 Jan 2023 17:58:47 -0300 [thread overview]
Message-ID: <CAOMZO5DGGgPTCVps8XGgUR992VKyKaQxY6cu6L1q-0mX0KqUGg@mail.gmail.com> (raw)
In-Reply-To: <CAJ=UCjVX212EdAoCe62BxA9T6CEs-jXPwfXMN_gjd5=Z-8w3zA@mail.gmail.com>
On Sun, Jan 15, 2023 at 5:54 PM Pierluigi Passaro
<pierluigi.passaro@gmail.com> wrote:
> I have a temporary SMTP configuration problem with my company account.
> As soon as it will be fixed, the patch will have no changes, will only change
> the SMTP mail server: is this warning so critical ?
You can manually edit the From line of your patch and change:
From: Pierluigi Passaro <pierluigi.passaro@gmail.com>
to
From: Pierluigi Passaro <pierluigi.p@variscite.com>
and then send it from your Gmail account.
prev parent reply other threads:[~2023-01-15 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 10:32 [PATCH] arm64: dts: imx8mm: Fix pad control for UART1_DTE_RX Pierluigi Passaro
2023-01-15 12:27 ` Fabio Estevam
2023-01-15 20:48 ` Fabio Estevam
2023-01-15 20:54 ` Pierluigi Passaro
2023-01-15 20:58 ` Fabio Estevam [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=CAOMZO5DGGgPTCVps8XGgUR992VKyKaQxY6cu6L1q-0mX0KqUGg@mail.gmail.com \
--to=festevam@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=eran.m@variscite.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=marex@denx.de \
--cc=nate.d@variscite.com \
--cc=peng.fan@nxp.com \
--cc=pierluigi.p@variscite.com \
--cc=pierluigi.passaro@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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;
as well as URLs for NNTP newsgroup(s).