From: Greg KH <gregkh@linuxfoundation.org>
To: Andreas Noever <andreas.noever@gmail.com>
Cc: Colin King <colin.king@canonical.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] thunderbolt: fix spelling mistake: "missmatch" -> "mismatch"
Date: Fri, 9 Jun 2017 11:32:52 +0200 [thread overview]
Message-ID: <20170609093252.GA22159@kroah.com> (raw)
In-Reply-To: <CAMxnaaVyst2dGeb3sSyRpdpwD1zkBP633Xw0MvrWPHXfAgA=jA@mail.gmail.com>
On Mon, Jun 05, 2017 at 07:02:54PM +0200, Andreas Noever wrote:
> On Thu, May 18, 2017 at 9:42 AM, Colin King <colin.king@canonical.com> wrote:
> > From: Colin Ian King <colin.king@canonical.com>
> >
> > Trivial fix to spelling mistake in tb_sw_warn warning message
> >
> > Signed-off-by: Colin Ian King <colin.king@canonical.com>
> > ---
> > drivers/thunderbolt/eeprom.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/thunderbolt/eeprom.c b/drivers/thunderbolt/eeprom.c
> > index 6392990c984d..1c3eb937a728 100644
> > --- a/drivers/thunderbolt/eeprom.c
> > +++ b/drivers/thunderbolt/eeprom.c
> > @@ -283,7 +283,7 @@ int tb_drom_read_uid_only(struct tb_switch *sw, u64 *uid)
> >
> > crc = tb_crc8(data + 1, 8);
> > if (crc != data[0]) {
> > - tb_sw_warn(sw, "uid crc8 missmatch (expected: %#x, got: %#x)\n",
> > + tb_sw_warn(sw, "uid crc8 mismatch (expected: %#x, got: %#x)\n",
> > data[0], crc);
> > return -EIO;
> > }
> > --
> > 2.11.0
> >
>
> Signed-off-by: Andreas Noever <andreas.noever@gmail.com>
>
> Greg, I believe that this line survived Mika's series. Would you add it as well?
Will do, thanks.
greg k-h
next prev parent reply other threads:[~2017-06-09 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 7:42 Colin King
2017-06-05 17:02 ` Andreas Noever
2017-06-09 9:32 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-28 12:19 Colin King
2016-07-12 21:45 ` Andreas Noever
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=20170609093252.GA22159@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.noever@gmail.com \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.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
Powered by JetHome