From: elfring@users.sourceforge.net (SF Markus Elfring)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM: s3c2410: Fix a typo in a comment line
Date: Tue, 10 Oct 2017 10:29:05 +0200 [thread overview]
Message-ID: <0f6ea076-2d41-103a-b1a1-40edc38e2daf@users.sourceforge.net> (raw)
In-Reply-To: <20171004181420.lctwaocrvg6rxokk@kozik-lap>
> Thanks, applied, squashed and changed commit msg.
Would it be more appropriate to use a commit subject like
?ARM: s3c241x: Fix typos in two comments? (instead of
?ARM: s3c2410: Fix typos in a comments?)?
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=6c7a7db2e4c25acf8bd8086797d39a51728139e0
Regards,
Markus
next prev parent reply other threads:[~2017-10-10 8:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 17:56 [PATCH 0/6] ARM-S3C24xx: Adjustments for four function implementations SF Markus Elfring
2017-10-02 17:58 ` [PATCH 1/6] ARM: s3c24xx: Delete an error message for a failed memory allocation in s3c2410_iotiming_get() SF Markus Elfring
2017-10-04 17:59 ` Krzysztof Kozlowski
2017-10-02 17:59 ` [PATCH 2/6] ARM: s3c24xx: Improve a size determination " SF Markus Elfring
2017-10-04 18:12 ` Krzysztof Kozlowski
2017-10-02 18:00 ` [PATCH 3/6] ARM: s3c2410: Fix a typo in a comment line SF Markus Elfring
2017-10-04 18:14 ` Krzysztof Kozlowski
2017-10-10 8:29 ` SF Markus Elfring [this message]
2017-10-10 8:35 ` Krzysztof Kozlowski
2017-10-10 8:48 ` SF Markus Elfring
2017-10-02 18:01 ` [PATCH 4/6] ARM: s3c24xx: Delete an error message for a failed memory allocation in s3c2412_iotiming_get() SF Markus Elfring
2017-10-04 18:03 ` Krzysztof Kozlowski
2017-10-02 18:03 ` [PATCH 5/6] ARM: s3c24xx: Improve a size determination " SF Markus Elfring
2017-10-02 18:04 ` [PATCH 6/6] ARM: s3c2412: Fix a typo in a comment line SF Markus Elfring
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=0f6ea076-2d41-103a-b1a1-40edc38e2daf@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=linux-arm-kernel@lists.infradead.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).