From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Khalid Aziz <khalid.aziz@hp.com>
Cc: Matthew Garrett <mjg@redhat.com>,
hpa@zytor.com, keescook@chromium.org, tony.luck@intel.com,
Greg KH <gregkh@linuxfoundation.org>,
cbouatmailru@gmail.com, ccross@android.com,
paul.gortmaker@windriver.com, maxin.john@gmail.com,
matt.fleming@intel.com, olof@lixom.net, dhowells@redhat.com,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
khalid@gonehiking.org
Subject: Re: [PATCH -next v2] Shorten constant names for EFI variable attributes
Date: Wed, 26 Sep 2012 07:55:28 +1000 [thread overview]
Message-ID: <20120926075528.e497436227403ecaf1b845d3@canb.auug.org.au> (raw)
In-Reply-To: <20120925154100.GA13412@ldl.usa.hp.com>
[-- Attachment #1: Type: text/plain, Size: 485 bytes --]
Hi,
On Tue, 25 Sep 2012 09:41:00 -0600 Khalid Aziz <khalid.aziz@hp.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.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-09-25 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120720220841.GA32642@hp.com>
[not found] ` <5009D770.1050905@zytor.com>
[not found] ` <20120723132656.GC21495@srcf.ucam.org>
[not found] ` <50117E40.8090904@hp.com>
[not found] ` <20120726173332.GA19851@srcf.ucam.org>
2012-09-25 15:41 ` [PATCH -next v2] Shorten constant names for EFI variable attributes Khalid Aziz
2012-09-25 21:55 ` Stephen Rothwell [this message]
2012-09-25 23:06 ` Khalid Aziz
2012-09-25 23:12 ` Matthew Garrett
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=20120926075528.e497436227403ecaf1b845d3@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cbouatmailru@gmail.com \
--cc=ccross@android.com \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=khalid.aziz@hp.com \
--cc=khalid@gonehiking.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=maxin.john@gmail.com \
--cc=mjg@redhat.com \
--cc=olof@lixom.net \
--cc=paul.gortmaker@windriver.com \
--cc=tony.luck@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).