From: Colin Ian King <colin.king@canonical.com>
To: Dan Carpenter <dan.carpenter@oracle.com>,
Ladislav Michl <ladis@linux-mips.org>
Cc: Nicolas Ferre <nicolas.ferre@microchip.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: atmel_ssc_dai: fix spelling mistake: "Stoping" -> "Stopping"
Date: Wed, 4 Apr 2018 11:41:23 +0100 [thread overview]
Message-ID: <9b1399de-3834-cd22-2bca-42a1048e0901@canonical.com> (raw)
In-Reply-To: <20180404102425.cwj7vzvrvi2obcoi@mwanda>
On 04/04/18 11:24, Dan Carpenter wrote:
> On Tue, Apr 03, 2018 at 03:45:40PM +0200, Ladislav Michl wrote:
>> On Fri, Mar 30, 2018 at 04:44:20PM +0100, Colin King wrote:
>>> From: Colin Ian King <colin.king@canonical.com>
>>
>> Hello Colin,
>>
>>> Trivial fix to spelling mistake in pr_debug message text
>>
>> would you mind making this patch a bit less non-trivial and
>> change pr_debug to dev_dbg dropping Atmel_ssc_dai prefix?
>>
>> Thank you.
>>
>
> Trivial patches should just be trivial instead of evolving into a thread
> that lasts for days.
Yep, this feels like this scenario for sure.
>
> I sometimes write trivial clean up patches for things like:
>
> arch/x86/lib/csum-partial_64.c:97 do_csum() warn: inconsistent indenting
> 88 /* last up to 7 8byte blocks */
> 89 count %= 8;
> 90 while (count) {
> 91 asm("addq %1,%0\n\t"
> 92 "adcq %2,%0\n"
> 93 : "=r" (result)
> 94 : "m" (*(unsigned long *)buff),
> 95 "r" (zero), "0" (result));
> 96 --count;
> 97 buff += 8;
> 98 }
>
> Why is "buff += 8;" indented too far? And why does every line end in a
> space character? And I think about it for 10 minutes and then delete my
> patch because it's too much hassle to deal with for something small.
Same here. Hence stuff never gets fixed.
>
> regards,
> dan carpenter
>
> --
> To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2018-04-04 10:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 15:44 Colin King
2018-03-31 8:54 ` Alexandre Belloni
2018-04-03 8:50 ` Nicolas Ferre
2018-04-03 13:45 ` [alsa-devel] " Ladislav Michl
2018-04-03 15:49 ` Joe Perches
2018-04-03 17:30 ` Ladislav Michl
2018-04-03 18:17 ` Joe Perches
2018-04-03 18:54 ` Ladislav Michl
2018-04-03 23:08 ` Joe Perches
2018-04-04 10:24 ` Dan Carpenter
2018-04-04 10:41 ` Colin Ian King [this message]
2018-04-04 12:30 ` Ladislav Michl
2018-04-04 14:46 ` Mark Brown
2018-04-12 16:16 ` Applied "ASoC: atmel_ssc_dai: fix spelling mistake: "Stoping" -> "Stopping"" to the asoc tree Mark Brown
2018-04-13 10:56 ` Mark Brown
2018-04-13 11:24 ` Mark Brown
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=9b1399de-3834-cd22-2bca-42a1048e0901@canonical.com \
--to=colin.king@canonical.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=ladis@linux-mips.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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
all inboxes | Powered by JetHome®