archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <>
To: Anshuman Khandual <>
Cc: Catalin Marinas <>,
	Will Deacon <>,
	Suzuki K Poulose <>,
Subject: Re: [PATCH] arm64: Generate cpucaps.h
Date: Thu, 13 May 2021 13:45:30 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 1427 bytes --]

On Thu, May 13, 2021 at 10:35:04AM +0530, Anshuman Khandual wrote:

> Small nit. So going forward this new directory (arch/arm64/tools/), will
> be used to hold similar scripts that generate header or similar things ?

Yes, anything we need to run in the build process.  Some of the other
architectures have some tools to verify generated binaries have
particular properties as well for example.

> At first the directory name 'tool' was bit confusing but seems like other
> archs (arm, m68k, mips, powerpc, s390, sh) have this directory as well.

Yes, it's the standard pattern.

> > +/^[vA-Z0-9_]+$/ {

> Small nit. Should this be length restricted at the least ?
> Like each CAP entries should not exceed a certain length.

If you want to send a patch by all means, I don't think it's useful
though - it doesn't matter to the software and the main issue is taste
which is going to get considered regardless of what software says, if
people are happy with an identifer that hits some limit they're just
going to raise the limit.

> Small nit. Should it be print "#endif /* __ASM_CPUCAPS_H */" instead
> in order to be complete.

I guess.  Given that this is merged that'd need to be an incremental

Please delete unneeded context from mails when replying.  Doing this
makes it much easier to find your reply in the message, helping ensure
it won't be missed by people scrolling through the irrelevant quoted

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

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

linux-arm-kernel mailing list

  parent reply	other threads:[~2021-05-13 12:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 12:12 [PATCH] arm64: Generate cpucaps.h Mark Brown
2021-04-29 12:32 ` Catalin Marinas
2021-05-04 11:43 ` Mark Rutland
2021-05-10 12:55 ` Catalin Marinas
2021-05-13  5:05 ` Anshuman Khandual
2021-05-13 11:51   ` Mark Rutland
2021-05-13 12:45   ` Mark Brown [this message]
2021-05-13 11:30 ` Geert Uytterhoeven
2021-05-13 13:03   ` Mark Brown
2021-09-21 18:08 ` dann frazier
2021-09-21 18:35   ` Mark Brown
2021-09-21 21:09     ` Suzuki K Poulose
2021-09-22 13:45       ` dann frazier

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).