linux-kernel - Re: [PATCH -next v2] Shorten constant names for EFI variable attributes

lists.openwall.net		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 linux-cve-announce 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:	Tue, 25 Sep 2012 17:06:32 -0600
From:	Khalid Aziz <khalid.aziz@...com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Matthew Garrett <mjg@...hat.com>, hpa@...or.com,
	keescook@...omium.org, tony.luck@...el.com,
	Greg KH <gregkh@...uxfoundation.org>, cbouatmailru@...il.com,
	ccross@...roid.com, paul.gortmaker@...driver.com,
	maxin.john@...il.com, matt.fleming@...el.com, olof@...om.net,
	dhowells@...hat.com, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, khalid@...ehiking.org
Subject: Re: [PATCH -next v2] Shorten constant names for EFI variable
 attributes

On Wed, 2012-09-26 at 07:55 +1000, Stephen Rothwell wrote:
> Hi,
> 
> On Tue, 25 Sep 2012 09:41:00 -0600 Khalid Aziz <khalid.aziz@...com> wrote:
> >
> > Replace very long constants for EFI variable attributes with
> > shorter and more convenient names. Also create an alias for
> > the current longer names so as to not break compatibility
> > with current API since these constants are used by
> > userspace programs.
> 
> Why do this?  It just looks like churn for no real gain.
> 

This is for code cleanup and does not impact functionality. This is
based upon an earlier discussion -
<https://lkml.org/lkml/2012/7/13/320>. The goal is to make the code more
readable. V1 of this patch was discussed at
<https://lkml.org/lkml/2012/7/20/414>.

-- 
Khalid Aziz <khalid.aziz@...com>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/