public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Mark Einon <mark.einon@gmail.com>
Cc: linux-kernel@vger.kernel.org, sfr@canb.auug.org.au,
	Trivial patch monkey <trivial@kernel.org>
Subject: Re: [PATCH] [TRIVIAL] linux-next: Fixed spelling typo in types.h
Date: Tue, 06 Dec 2011 17:32:14 -0800	[thread overview]
Message-ID: <4EDEC21E.4050103@xenotime.net> (raw)
In-Reply-To: <1323213494-21947-1-git-send-email-mark.einon@gmail.com>

On 12/06/2011 03:18 PM, Mark Einon wrote:
> Spelling change, architetures -> architectures
> 
> Signed-off-by: Mark Einon <mark.einon@gmail.com>

You should Cc: trivial@kernel.org also.
[done]

> ---
>  include/linux/types.h |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/include/linux/types.h b/include/linux/types.h
> index 57a9723..cbcef6e 100644
> --- a/include/linux/types.h
> +++ b/include/linux/types.h
> @@ -188,7 +188,7 @@ typedef __u32 __bitwise __wsum;
>   * aligned_u64 should be used in defining kernel<->userspace ABIs to avoid
>   * common 32/64-bit compat problems.
>   * 64-bit values align to 4-byte boundaries on x86_32 (and possibly other
> - * architectures) and to 8-byte boundaries on 64-bit architetures.  The new
> + * architectures) and to 8-byte boundaries on 64-bit architectures.  The new
>   * aligned_64 type enforces 8-byte alignment so that structs containing
>   * aligned_64 values have the same alignment on 32-bit and 64-bit architectures.
>   * No conversions are necessary between 32-bit user-space and a 64-bit kernel.


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

      reply	other threads:[~2011-12-07  0:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 23:18 [PATCH] [TRIVIAL] linux-next: Fixed spelling typo in types.h Mark Einon
2011-12-07  1:32 ` Randy Dunlap [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=4EDEC21E.4050103@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.einon@gmail.com \
    --cc=sfr@canb.auug.org.au \
    --cc=trivial@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