From: Randy Dunlap <rdunlap@infradead.org>
To: Masahiro Yamada <masahiroy@kernel.org>, Simon Glass <sjg@chromium.org>
Cc: linux-arm-kernel@lists.infradead.org,
U-Boot Mailing List <u-boot@lists.denx.de>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicolas Schier <nicolas@fjasle.eu>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] kbuild: Correct missing architecture-specific hyphens
Date: Sat, 28 Oct 2023 09:00:34 -0700 [thread overview]
Message-ID: <8fba0cd3-6666-4ea0-822b-006a457e0101@infradead.org> (raw)
In-Reply-To: <CAK7LNAReQB4KF_Ka=SUWSJ2psvqCrEm=BOkKXCYDK7Ux9uYutg@mail.gmail.com>
On 10/28/23 02:50, Masahiro Yamada wrote:
> On Thu, Oct 26, 2023 at 4:27 PM Simon Glass <sjg@chromium.org> wrote:
>>
>> These should add a hyphen to indicate that it makes a adjective. Fix
>> them.
>>
>> Signed-off-by: Simon Glass <sjg@chromium.org>
>> ---
>
>
> This is trivial.
> Applied to linux-kbuild. Thanks.
>
>
> git grep -i 'arch specific'
>
> or
>
> git grep -i 'architecture specific'
>
> finds similar patterns, but presumably we are not
> keen on fixing them tree-wide.
or '32 bit', '64 bit', but I agree with "not keen on
fixing them tree-wide."
--
~Randy
next prev parent reply other threads:[~2023-10-28 16:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 7:26 [PATCH 0/3] arm64: Add a build target for Flat Image Tree Simon Glass
2023-10-26 7:26 ` [PATCH 1/3] kbuild: Correct missing architecture-specific hyphens Simon Glass
2023-10-28 9:50 ` Masahiro Yamada
2023-10-28 16:00 ` Randy Dunlap [this message]
2023-10-26 7:26 ` [PATCH 2/3] kbuild: arm64: Add BOOT_TARGETS variable Simon Glass
2023-10-26 7:26 ` [PATCH 3/3] arm64: boot: Support Flat Image Tree Simon Glass
2023-10-26 13:24 ` Masahiro Yamada
2023-10-28 16:46 ` Simon Glass
2023-10-30 15:35 ` Russell King (Oracle)
2023-10-30 16:12 ` Tom Rini
2023-10-31 7:03 ` Masahiro Yamada
2023-10-31 11:46 ` Tom Rini
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=8fba0cd3-6666-4ea0-822b-006a457e0101@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/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
all inboxes | Powered by JetHome®