lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 28 Jul 2014 15:28:21 +0200
From:	Robert Richter <>
To:	"Chen, Gong" <>
Subject: Re: [RESEND RFC PATCH v1 0/70] Gloabl CPU Hot-plug flag _FROZEN
 Clean up

On 27.07.14 02:36:43, Chen, Gong wrote:
> On Fri, Jul 25, 2014 at 05:00:02PM +0200, Robert Richter wrote:
> > > Back to long time ago (about 1.5 years), Thomas began the work
> > > for CPU hot-plug, one first thing is CPU hotplug flag cleanup.
> > > Paul hoped all the _FROZEN variants of the notifier actions
> > > can be removed at that time. Now here it is.
> > > 
> > > Patch 1 ~ 69: remove all kinds of XXX_FROZEN usages
> > > Patch 70: remove XXX_FROZEN from the kernel thoroughly
> > 
> > You might want to update Documentation/ as well.
> > 
> Thanks for your reminder. I don't do that intentionally because
> 1) This is RFC patch and I'm not sure if maintainers agree
> to remove XXX_FROZEN thoroughtly
> 2) I have a little bit hesitation how to describe XXX_FROZEN
> status after they are removed.
> Anyway, I will do that in formal patch series. Thanks again!

Yes, thanks. It does not make sense to remove the XXX_FROZEN pattern
in the code while keeping it in the cpu hotplug description.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists