From: Khalid Ali <khaliidcaliy@gmail.com>
To: kai.huang@intel.com, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de
Cc: x86@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] x86/boot: Don't return encryption mask from __startup_64()
Date: Wed, 25 Jun 2025 12:34:21 +0000 [thread overview]
Message-ID: <20250625123517.4333-1-khaliidcaliy@gmail.com> (raw)
In-Reply-To: <487c2747bb4c02d643324292489243fdc82e1c6a.camel@intel.com>
> Sigh... this comment is broken, since there's no '*' before the last '/'.
>Here's how I find it:
>
>So I went to see why this patch caused early boot failure, since the code
>change doesn't seem wrong to me.
>
>After staring at the code for half hour and yet unable to see any issue, I
>went to disassemble the kernel image, then I found the above two lines of
>code wasn't there at all.
>
>Then looking at this again, it's obvious that the reason is the change to
>the comment is broken, leading the above two lines of code being commented
>out.
So what i was wringling all along was the comment. I don't know why i couldn't spot it
if those two lines where commented out then even boot was supposed to fail on my side too.
I guess toolchain difference. Probably this is the reason since i compiled with gcc not clang.
Thanks though. :)
>And this patch has other style issues too like the broken indent of function
>parameters after changing returning value from 'unsigned int' to 'void', and
Could please clarify more as checkpatch.pl didn't notice it.
>So, please, before posting patches, test them, and run
>./scripts/checkpatch.pl against them.
I used it, well the tool seems broken and giving me false positive. I fixed all your suggestions and sent
v5, as my best i could, i fixed all issues and that patch seems good.
Could you please check it?
prev parent reply other threads:[~2025-06-25 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 7:36 [PATCH v4] x86/boot: Don't return encryption mask from __startup_64() Khalid Ali
2025-06-23 11:26 ` Huang, Kai
2025-06-25 6:40 ` kernel test robot
2025-06-25 10:55 ` Huang, Kai
2025-06-25 12:34 ` Khalid Ali [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=20250625123517.4333-1-khaliidcaliy@gmail.com \
--to=khaliidcaliy@gmail.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=kai.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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.