mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Con Kolivas <kernel@kolivas.org>
Cc: Tim Cambrant <cambrant@acc.umu.se>, Pavel Machek <pavel@ucw.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: power/disk.c: small fixups
Date: Thu, 21 Oct 2004 16:24:37 +1000	[thread overview]
Message-ID: <41775625.6050102@yahoo.com.au> (raw)
In-Reply-To: <cone.1098338726.500663.12209.502@pc.kolivas.org>

Con Kolivas wrote:
> Tim Cambrant writes:
> 
>> On Wed, Oct 20, 2004 at 08:16:17PM +0200, Pavel Machek wrote:
>>
>>> power_down may never ever fail, so it does not really need to return
>>> anything. Kill obsolete code and fixup old comments. Please apply,
>>>
>>
>> ...
>>
>>> @@ -162,7 +163,7 @@
>>>   *
>>>   *    If we're going through the firmware, then get it over with 
>>> quickly.
>>>   *
>>> - *    If not, then call pmdis to do it's thing, then figure out how
>>> + *    If not, then call swsusp to do it's thing, then figure out how
>>>   *    to power down the system.
>>>   */
>>
>>
>> I hate to be picky, but changing "it's" to the more correct "its" would
>> perhaps be nice to do when you're at it?
> 
> 
> "it's" means it belongs to, so therefore "it's" is correct usage here.
> 

Actually this is an exception. "it's" is an abbreviation for "it is",
"its" is possessive.

  reply	other threads:[~2004-10-21  6:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20 18:16 Pavel Machek
2004-10-20 19:37 ` Tim Cambrant
2004-10-20 19:44   ` Pavel Machek
2004-10-21  6:05   ` Con Kolivas
2004-10-21  6:24     ` Nick Piggin [this message]
2004-10-21 19:31     ` Bill Davidsen
2004-10-24 10:09     ` Matthias Urlichs
2004-10-24 14:17       ` Maciej W. Rozycki
2004-10-26  6:12 Clayton Weaver
2004-10-26  8:55 ` David Weinehall

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=41775625.6050102@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=cambrant@acc.umu.se \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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