From: Catalin Marinas <catalin.marinas@arm.com>
To: Prathu Baronia <quic_pbaronia@quicinc.com>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/cpucaps: increase string width to properly format cpucaps.h
Date: Fri, 26 May 2023 10:28:22 +0100 [thread overview]
Message-ID: <ZHB7tvDa7d6T6SEq@arm.com> (raw)
In-Reply-To: <20230517100452.382174-1-quic_pbaronia@quicinc.com>
On Wed, May 17, 2023 at 03:34:50PM +0530, Prathu Baronia wrote:
> The lengthiest capability is `WORKAROUND_TRBE_OVERWRITE_FILL_MODE` and
> its length is 35 characters so increase the width of left justified
> strings to 35 and adjust the tab space for `ARM64_NCAPS` accordingly.
> Now the generated cpucaps.h is properly formatted.
>
> Signed-off-by: Prathu Baronia <quic_pbaronia@quicinc.com>
Why not make it larger, say 40, just in case.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Prathu Baronia <quic_pbaronia@quicinc.com>
Cc: Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64/cpucaps: increase string width to properly format cpucaps.h
Date: Fri, 26 May 2023 10:28:22 +0100 [thread overview]
Message-ID: <ZHB7tvDa7d6T6SEq@arm.com> (raw)
In-Reply-To: <20230517100452.382174-1-quic_pbaronia@quicinc.com>
On Wed, May 17, 2023 at 03:34:50PM +0530, Prathu Baronia wrote:
> The lengthiest capability is `WORKAROUND_TRBE_OVERWRITE_FILL_MODE` and
> its length is 35 characters so increase the width of left justified
> strings to 35 and adjust the tab space for `ARM64_NCAPS` accordingly.
> Now the generated cpucaps.h is properly formatted.
>
> Signed-off-by: Prathu Baronia <quic_pbaronia@quicinc.com>
Why not make it larger, say 40, just in case.
--
Catalin
next prev parent reply other threads:[~2023-05-26 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 10:04 [PATCH] arm64/cpucaps: increase string width to properly format cpucaps.h Prathu Baronia
2023-05-17 10:04 ` Prathu Baronia
2023-05-26 9:28 ` Catalin Marinas [this message]
2023-05-26 9:28 ` Catalin Marinas
2023-05-27 12:27 ` Prathu Baronia
2023-05-27 12:27 ` Prathu Baronia
2023-05-27 12:38 ` [PATCH v2] " Prathu Baronia
2023-05-27 12:38 ` Prathu Baronia
2023-06-06 17:30 ` Catalin Marinas
2023-06-06 17:30 ` Catalin Marinas
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=ZHB7tvDa7d6T6SEq@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_pbaronia@quicinc.com \
--cc=will@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.