From: Cezary Rojewski <cezary.rojewski@intel.com>
To: <Ryan.Wanner@microchip.com>, <Claudiu.Beznea@microchip.com>,
<nicolas.ferre@microchip.com>, <alexandre.berna@microchip.com>,
<robh+dt@kernel.org>, <broonie@kernel.org>, <lgirdwood@gmail.com>,
<alsa-devel@alsa-project.org>,
<krzysztof.kozlowski+dt@linaro.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2] Fixes: 1ca81883c557 ("ARM: dts: at91: sama5d2: add nodes for I2S controllers")
Date: Wed, 6 Jul 2022 22:06:42 +0200 [thread overview]
Message-ID: <d318e4d1-fdf8-e6d0-8dec-bf05c4e9aa59@intel.com> (raw)
In-Reply-To: <20220706162144.66831-1-Ryan.Wanner@microchip.com>
On 2022-07-06 6:21 PM, Ryan.Wanner@microchip.com wrote:
> From: Ryan Wanner <Ryan.Wanner@microchip.com>
>
> Fixed typo in i2s1 node
Perhaps this email got twisted by my client but what I'm seeing is
fixes-tag instead of a proper commit title.
If that's really the case, please reword your title - Fixes-tag belongs
to the tag area and should be placed before your final signed-off tag.
Also, as commit message is _not_ a title and is made of sentences, it is
expected to have each end with '.'.
Another suggestion - nothing is "Fixed" when patch lands on the mailing
list. It's just a proposal until it actually gets integrated by the
maintainer. As change targets _current_ code, s/Fixed/Fix/ is the
recommended phrasing.
Czarek
> Signed-off-by: Ryan Wanner <Ryan.Wanner@microchip.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-07-06 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 16:21 [PATCH v2] Fixes: 1ca81883c557 ("ARM: dts: at91: sama5d2: add nodes for I2S controllers") Ryan.Wanner
2022-07-06 16:26 ` Nicolas Ferre
2022-07-06 20:06 ` Cezary Rojewski [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=d318e4d1-fdf8-e6d0-8dec-bf05c4e9aa59@intel.com \
--to=cezary.rojewski@intel.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Ryan.Wanner@microchip.com \
--cc=alexandre.berna@microchip.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@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