From: "Kevin D. Kissell" <kevink@paralogos.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Nick Andrew <nick@nick-andrew.net>,
Jonathan Corbet <corbet@lwn.net>, Lucas Woods <woodzy@gmail.com>,
linux-mips@linux-mips.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fix incorrect use of loose in vpe.c
Date: Fri, 05 Dec 2008 10:23:27 -0600 [thread overview]
Message-ID: <4939557F.1000609@paralogos.com> (raw)
In-Reply-To: <20081205155654.GA2765@linux-mips.org>
Ralf Baechle wrote:
> On Fri, Dec 05, 2008 at 11:36:54AM +1100, Nick Andrew wrote:
>
>> From: Nick Andrew <nick@nick-andrew.net>
>> Date: Fri, 05 Dec 2008 11:36:54 +1100
>> To: Jonathan Corbet <corbet@lwn.net>, "Kevin D. Kissell" <kevink@mips.com>,
>> Lucas Woods <woodzy@gmail.com>, Nick Andrew <nick@nick-andrew.net>,
>> Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
>> Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
>> Subject: Fix incorrect use of loose in vpe.c
>>
>> Fix incorrect use of loose in vpe.c
>>
>> From: Nick Andrew <nick@nick-andrew.net>
>>
>> It should be 'lose', not 'loose'.
>>
>> Signed-off-by: Nick Andrew <nick@nick-andrew.net>
>>
>
> Thanks, applied. Note that the address you used for Kevin Kissel to post
> your patch is no longer valid.
>
Yeah, but I'm still on the mailing list, so I saw it. I don't "own"
that particular module,
but for whatever it's worth, I'm OK with fixing the comment - though I'm
surprised
that checkpatch let a non-canonical multi-line comment block like that
go by. ;o)
Regards,
Kevin K.
next prev parent reply other threads:[~2008-12-05 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S24119814AbYLEAhF/20081205003705Z+5882@ftp.linux-mips.org>
2008-12-05 15:56 ` Fix incorrect use of loose in vpe.c Ralf Baechle
2008-12-05 16:23 ` Kevin D. Kissell [this message]
2008-12-05 21:02 ` Nick Andrew
2008-12-05 0:36 Nick Andrew
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=4939557F.1000609@paralogos.com \
--to=kevink@paralogos.com \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=nick@nick-andrew.net \
--cc=ralf@linux-mips.org \
--cc=woodzy@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.