[PATCH 0/5] x86/cpu: Introduce <asm/cpuid/types.h> and <asm/cpuid/api.h> and clean them up

mingo@kernel.org posted 5 patches 9 months ago
arch/x86/include/asm/cpuid.h       | 217 +--------------------------------------------------------
arch/x86/include/asm/cpuid/api.h   | 210 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
arch/x86/include/asm/cpuid/types.h |  32 +++++++++
3 files changed, 243 insertions(+), 216 deletions(-)
create mode 100644 arch/x86/include/asm/cpuid/api.h
create mode 100644 arch/x86/include/asm/cpuid/types.h
[PATCH 0/5] x86/cpu: Introduce <asm/cpuid/types.h> and <asm/cpuid/api.h> and clean them up
Posted by mingo@kernel.org 9 months ago
From: Ingo Molnar <mingo@kernel.org>

This series contains Ahmed S. Darwish's splitting up of <asm/cpuid.h>
into <asm/cpuid/types.h> and <asm/cpuid/api.h>, followed by a couple
of cleanups that create a more maintainable base.

[ This is a resend with a proper SMTP setup. Apologies for the duplication. ]

Thanks,

	Ingo

================>
Ahmed S. Darwish (1):
  x86/cpuid: Refactor <asm/cpuid.h>

Ingo Molnar (4):
  x86/cpuid: Clean up <asm/cpuid/types.h>
  x86/cpuid: Clean up <asm/cpuid/api.h>
  x86/cpuid: Standardize on u32 in <asm/cpuid/api.h>
  x86/cpuid: Use u32 in instead of uint32_t in <asm/cpuid/api.h>

 arch/x86/include/asm/cpuid.h       | 217 +--------------------------------------------------------
 arch/x86/include/asm/cpuid/api.h   | 210 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 arch/x86/include/asm/cpuid/types.h |  32 +++++++++
 3 files changed, 243 insertions(+), 216 deletions(-)
 create mode 100644 arch/x86/include/asm/cpuid/api.h
 create mode 100644 arch/x86/include/asm/cpuid/types.h

-- 
2.45.2
Re: [PATCH 0/5] x86/cpu: Introduce <asm/cpuid/types.h> and <asm/cpuid/api.h> and clean them up
Posted by Ahmed S. Darwish 9 months ago
Hi,

On Mon, 17 Mar 2025, mingo@kernel.org wrote:
>
> From: Ingo Molnar <mingo@kernel.org>
>
> This series contains Ahmed S. Darwish's splitting up of <asm/cpuid.h>
> into <asm/cpuid/types.h> and <asm/cpuid/api.h>, followed by a couple
> of cleanups that create a more maintainable base.
>
> [ This is a resend with a proper SMTP setup. Apologies for the duplication. ]
>

Thanks a lot!

Just a small hint that I see this PQ in tip/master, merge commit
b8fefef00c0d ("Merge branch into tip/master: 'x86/cpu'"):

   # New commits in x86/cpu:
      ba501f14e1e6 ("x86/cpuid: Use u32 in instead of uint32_t in <asm/cpuid/api.h>")
      aec28d852ed2 ("x86/cpuid: Standardize on u32 in <asm/cpuid/api.h>")
      f2f828b547ab ("x86/cpuid: Clean up <asm/cpuid/api.h>")
      67a7ae050e7c ("x86/cpuid: Clean up <asm/cpuid/types.h>")
      02b63b33dfc9 ("x86/cpuid: Refactor <asm/cpuid.h>")

But for some reason the above 5 commits are not yet pushed to x86/cpu.

(Sorry if this is expected.)

All the best,

--
Ahmed S. Darwish
Linutronix GmbH
Re: [PATCH 0/5] x86/cpu: Introduce <asm/cpuid/types.h> and <asm/cpuid/api.h> and clean them up
Posted by Ingo Molnar 9 months ago
* Ahmed S. Darwish <darwi@linutronix.de> wrote:

> Hi,
> 
> On Mon, 17 Mar 2025, mingo@kernel.org wrote:
> >
> > From: Ingo Molnar <mingo@kernel.org>
> >
> > This series contains Ahmed S. Darwish's splitting up of <asm/cpuid.h>
> > into <asm/cpuid/types.h> and <asm/cpuid/api.h>, followed by a couple
> > of cleanups that create a more maintainable base.
> >
> > [ This is a resend with a proper SMTP setup. Apologies for the duplication. ]
> >
> 
> Thanks a lot!
> 
> Just a small hint that I see this PQ in tip/master, merge commit
> b8fefef00c0d ("Merge branch into tip/master: 'x86/cpu'"):
> 
>    # New commits in x86/cpu:
>       ba501f14e1e6 ("x86/cpuid: Use u32 in instead of uint32_t in <asm/cpuid/api.h>")
>       aec28d852ed2 ("x86/cpuid: Standardize on u32 in <asm/cpuid/api.h>")
>       f2f828b547ab ("x86/cpuid: Clean up <asm/cpuid/api.h>")
>       67a7ae050e7c ("x86/cpuid: Clean up <asm/cpuid/types.h>")
>       02b63b33dfc9 ("x86/cpuid: Refactor <asm/cpuid.h>")
> 
> But for some reason the above 5 commits are not yet pushed to x86/cpu.

Yeah, that was a temporary status until a bit more testing could be 
done - I've pushed it out now.

Thanks,

	Ingo
Re: [PATCH 0/5] x86/cpu: Introduce <asm/cpuid/types.h> and <asm/cpuid/api.h> and clean them up
Posted by Linus Torvalds 9 months ago
On Mon, 17 Mar 2025 at 15:30, <mingo@kernel.org> wrote:
>
> [ This is a resend with a proper SMTP setup. Apologies for the duplication. ]

Yes, now it looks correct from a DKIM standpoint.

But please still fix your name. Now your "From" line is just this:

    From: mingo@kernel.org

rather than your previous series, that had a much more legible

    From: Ingo Molnar <mingo@kernel.org>

in it.

No need to re-send, but for next time...

              Linus
Re: [PATCH 0/5] x86/cpu: Introduce <asm/cpuid/types.h> and <asm/cpuid/api.h> and clean them up
Posted by Ingo Molnar 9 months ago
* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Mon, 17 Mar 2025 at 15:30, <mingo@kernel.org> wrote:
> >
> > [ This is a resend with a proper SMTP setup. Apologies for the duplication. ]
> 
> Yes, now it looks correct from a DKIM standpoint.
> 
> But please still fix your name. Now your "From" line is just this:
> 
>     From: mingo@kernel.org
> 
> rather than your previous series, that had a much more legible
> 
>     From: Ingo Molnar <mingo@kernel.org>
> 
> in it.
> 
> No need to re-send, but for next time...

Oh, that's probably the result of me copy-pasting the documentation:

    # https://korg.docs.kernel.org/mail.html

    [sendemail]
            smtpserver     = mail.kernel.org
            smtpserverport = 465
            smtpencryption = ssl
            from           = [username]@kernel.org
            smtpuser       = [username]

Which I did as:

            from           = mingo@kernel.org

... while it should probably be:

            from           = Ingo Molnar <mingo@kernel.org>

I just did a test-send to myself, and this appears to have done the 
trick.

So maybe the mail.html documentation should be updated to say:

            from           = "Your Real Name" <[username]@kernel.org>

or so?

Thanks,

	Ingo