From: Wolfram Sang <wsa@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: trivial@kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: Fix typo s/business/busyness/
Date: Thu, 7 Oct 2021 09:49:10 +0200 [thread overview]
Message-ID: <YV6mdpPHn4JJCTn+@kunai> (raw)
In-Reply-To: <20211007074457.2393322-1-u.kleine-koenig@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 319 bytes --]
On Thu, Oct 07, 2021 at 09:44:57AM +0200, Uwe Kleine-König wrote:
> While business is a real word here busyness is meant, so fix accordingly.
> I hope I didn't miss this being a funny play on words :-)
:) No, you didn't miss anything. But I think the comment can just go.
The function name is obvious enough.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-10-07 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 7:44 [PATCH] i2c: Fix typo s/business/busyness/ Uwe Kleine-König
2021-10-07 7:49 ` Wolfram Sang [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=YV6mdpPHn4JJCTn+@kunai \
--to=wsa@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=trivial@kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).