All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	linux-doc@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH v2] docs: submit-checklist: Expand on build tests against different word sizes
Date: Mon, 10 Feb 2025 11:01:28 -0700	[thread overview]
Message-ID: <8734gl1xxj.fsf@trenco.lwn.net> (raw)
In-Reply-To: <05c0b99c-c2e9-4702-90fd-8a4127586424@gmail.com>

Akira Yokosawa <akiyks@gmail.com> writes:

> Existing sentence on cross-compilation that mentions ppc64 does not
> make much sense in today's perspective.
>
> Expand it for the benefits of testing against architectures of
> different word sizes and endianness.
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> v2: Split out change in the English doc from v1 [1].
>     Keep Randy's Rb tag (as it was meant for the change in English doc).
>
> [1] https://lore.kernel.org/20250128102805.112691-2-akiyks@gmail.com/
> --
>  Documentation/process/submit-checklist.rst | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/process/submit-checklist.rst b/Documentation/process/submit-checklist.rst
> index e531dd504b6c..88b6358258d7 100644
> --- a/Documentation/process/submit-checklist.rst
> +++ b/Documentation/process/submit-checklist.rst
> @@ -91,9 +91,12 @@ Build your code
>       fix any issues.
>  
>  2) Builds on multiple CPU architectures by using local cross-compile tools
> -   or some other build farm. Note that ppc64 is a good architecture for
> -   cross-compilation checking because it tends to use ``unsigned long`` for
> -   64-bit quantities.
> +   or some other build farm.
> +   Note that testing against architectures of different word sizes
> +   (32- and 64-bit) and different endianness (big- and little-) is effective
> +   in catching various portability issues due to false assumptions on
> +   representable quantity range, data alignment, or endianness, among
> +   others.
>  

Applied, thanks.

jon

      reply	other threads:[~2025-02-10 18:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-30  7:28 [PATCH v2] docs: submit-checklist: Expand on build tests against different word sizes Akira Yokosawa
2025-02-10 18:01 ` Jonathan Corbet [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=8734gl1xxj.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=akiyks@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=rdunlap@infradead.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.