From: Aditya <yashsri421@gmail.com>
To: Joe Perches <joe@perches.com>, linux-kernel@vger.kernel.org
Cc: lukas.bulwahn@gmail.com, dwaipayanray1@gmail.com,
broonie@kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
clang-built-linux@googlegroups.com
Subject: Re: [PATCH] checkpatch: add warning for avoiding .L prefix symbols in assembly files
Date: Sat, 23 Jan 2021 01:43:18 +0530 [thread overview]
Message-ID: <bd560a8e-7949-933a-e4a9-508cb42c2570@gmail.com> (raw)
In-Reply-To: <27366417ad75e0300d4647f776ca61bb1b132507.camel@perches.com>
On 23/1/21 12:40 am, Joe Perches wrote:
> On Fri, 2021-01-22 at 18:48 +0530, Aditya wrote:
>> On 21/1/21 12:13 am, Joe Perches wrote:
>>> I believe the test should be:
>>>
>>> if ($realfile =~ /\.S$/ &&
>>> $line =~ /^\+\s*SYM_[A-Z]+_(?:START|END)(?:_[A-Z_]+)?\s*\(\s*\.L/) {
>>
>> Joe, with this regex, we won't be able to match
>> "jmp .L_restore
>> SYM_FUNC_END(\name)"
>
> I think that's not an issue.
>
>> which was replaced in this patch in the discussion:
>> https://groups.google.com/g/clang-built-linux/c/-drkmLgu-cU/m/phKe-Tb6CgAJ
>>
>> Here, "jmp .L_restore" was also replaced to fix the error.
>
> Notice that this line was also replaced in the same patch:
>
> #ifdef CONFIG_PREEMPTION
> -SYM_CODE_START_LOCAL_NOALIGN(.L_restore)
> +SYM_CODE_START_LOCAL_NOALIGN(__thunk_restore)
>
>
>> However, if this
>> regex(/^\+\s*SYM_[A-Z]+_(?:START|END)(?:_[A-Z_]+)?\s*\(\s*\.L/) is
>> correct, maybe we don't need to check for $file as we are now checking
>> for just one line.
>>
>> What do you think?
>
> The test I wrote was complete, did not use $file and emits a
> warning on the use of CODE_SYM_START_LOCAL_NOALIGN(.L_restore)
>
> I think it's sufficient.
>
Okay, Thanks.. I will send the modified patch :)
Thanks
Aditya
next prev parent reply other threads:[~2021-01-22 21:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 7:25 Aditya Srivastava
2021-01-20 9:21 ` Joe Perches
2021-01-20 12:53 ` Aditya
2021-01-20 18:43 ` Joe Perches
2021-01-20 18:57 ` Nick Desaulniers
2021-01-20 22:59 ` Josh Poimboeuf
2021-01-22 13:18 ` Aditya
2021-01-22 19:10 ` Joe Perches
2021-01-22 20:13 ` Aditya [this message]
2021-01-22 20:36 ` Fāng-ruì Sòng
2021-01-23 15:14 ` [PATCH v2] " Aditya Srivastava
2021-01-23 17:21 ` Joe Perches
2021-01-23 18:23 ` Aditya
2021-01-23 19:04 ` [PATCH v3] " Aditya Srivastava
2021-01-23 21:01 ` Joe Perches
2021-01-25 18:15 ` Nick Desaulniers
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=bd560a8e-7949-933a-e4a9-508cb42c2570@gmail.com \
--to=yashsri421@gmail.com \
--cc=broonie@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
/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®