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:	Sun, 9 Mar 2014 13:33:37 +0800
From:	Lennox Wu <>
To:	Paul Bolle <>
Cc:	Michael Opdenacker <>,
	open list <>
Subject: Re: [PATCH] [RESEND] score: remove unused CPU_SCORE7 Kconfig parameter

Actually, people I don't want to brother are guys intergrate all
patches on the maillist.
There are too many patches whaic are waiting they to process.
I will check the development progress of the another Score and
consider if we should remove the config.
Thanks for your suggestion.


2014-03-09 5:02 GMT+08:00 Paul Bolle <>:
> On Sun, 2014-03-09 at 04:27 +0800, Lennox Wu wrote:
>> 2014-03-09 4:00 GMT+08:00 Paul Bolle <>:
>> > In I already reported that this
>> > Kconfig symbol was unused. Why can't it be dropped and re-added when
>> > code is added to the tree that actually uses it?
>> Because I don't think droping it is meaningful, since it will be used.
> But, again, it isn't used now and hasn't actually been used in years.
>> Moreover, the symbol never affect other architectures or subsystems.
>> I feel that is not good to brother people to process the unimportant patch.
> Sure, this is just a small cleanup. But the scripts people use to see
> whether more serious Kconfig related issues have entered the tree will
> likely notice CPU_SCORE7. (And those people will have to investigate why
> that symbol is unused - which might take quite a bit of work - to
> determine what needs to be done about it.) So whenever someone, not
> following this thread, runs a script like that the score maintainers
> might receive a similar patch again.
> And I don't believe that handling a single cleanup patch is particularly
> burdensome for the score maintainers.
> Paul Bolle
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