All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [patch] fix typo in pm.h
Date: Tue, 08 Mar 2005 18:48:20 +0000	[thread overview]
Message-ID: <20050308184820.GB3897@us.ibm.com> (raw)
In-Reply-To: <2cd57c90050308103414c5aef6@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

On Wed, Mar 09, 2005 at 02:34:00AM +0800, Coywolf Qi Hunt wrote:
> This patch fixes a typo in PMSG_ comment in pm.h.
> 
> Signed-off-by: Coywolf Qi Hunt <coywolf@gmail.com>
> 
> diff -Nrup 2.6.11/include/linux/pm.h 2.6.11-cy/include/linux/pm.h
> --- 2.6.11/include/linux/pm.h	2005-03-03 17:12:14.000000000 +0800
> +++ 2.6.11-cy/include/linux/pm.h	2005-03-09 02:27:07.000000000 +0800
> @@ -208,7 +208,7 @@ typedef u32 __bitwise pm_message_t;
>   *           pci D3.
>   *
>   * Unfortunately, current drivers only recognize numeric values 0
> (ON) and 3 (SUSPEND).
> - * We'll need to fix the drivers. So yes, putting 3 to all diferent
> defines is intentional,
> + * We'll need to fix the drivers. So yes, putting 3 to all different
> defines is intentional,
>   * and will go away as soon as drivers are fixed. Also note that
> typedef is neccessary,
>   * we'll probably want to switch to
>   *   typedef struct pm_message_t { int event; int flags; } pm_message_t

Your patch got wrapped.

Thanks,
Nish

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  reply	other threads:[~2005-03-08 18:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 18:34 [KJ] [patch] fix typo in pm.h Coywolf Qi Hunt
2005-03-08 18:48 ` Nishanth Aravamudan [this message]
2005-03-08 19:08 ` Coywolf Qi Hunt
2005-03-08 21:13 ` Nicolas Kaiser
2005-03-08 21:23 ` Tobias Klauser
2005-03-08 22:12 ` Alexey Dobriyan

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=20050308184820.GB3897@us.ibm.com \
    --to=nacc@us.ibm.com \
    --cc=kernel-janitors@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 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.