From: Jeff Garzik <jgarzik@pobox.com>
To: Aaron Lu <aaron.lu@intel.com>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Tejun Heo <tj@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Jeff Garzik <jgarzik@redhat.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
LKML <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v2] [libata] Avoid specialized TLA's in ZPODD's Kconfig
Date: Mon, 04 Mar 2013 17:14:55 -0500 [thread overview]
Message-ID: <51351CDF.6070003@pobox.com> (raw)
In-Reply-To: <51318775.1060309@intel.com>
On 03/02/2013 12:00 AM, Aaron Lu wrote:
> ODD is not a common TLA for non-ATA people so they will get confused
> by its meaning when they are configuring the kernel. This patch fixed
> this problem by using ODD only after stating what it is.
>
> Signed-off-by: Aaron Lu <aaron.lu@intel.com>
> ---
> v2:
> Add a space before open paren as suggested by Sergei Shtylyov.
>
> drivers/ata/Kconfig | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
applied
next prev parent reply other threads:[~2013-03-04 22:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 14:29 [GIT PULL] ACPI and power management fixes for v3.9-rc1 Rafael J. Wysocki
2013-02-26 3:17 ` Rafael J. Wysocki
2013-02-26 5:31 ` Linus Torvalds
2013-02-26 15:55 ` Rafael J. Wysocki
2013-02-26 16:10 ` Nishanth Menon
2013-02-26 16:27 ` Linus Torvalds
2013-02-26 16:28 ` Linus Torvalds
2013-02-26 16:37 ` Tejun Heo
2013-02-26 16:47 ` Linus Torvalds
2013-02-26 16:58 ` Tejun Heo
2013-02-26 17:59 ` Jeff Garzik
2013-03-01 1:32 ` [PATCH] [libata] Avoid specialized TLA's in ZPODD's Kconfig Aaron Lu
2013-03-01 13:10 ` Sergei Shtylyov
2013-03-02 5:00 ` [PATCH v2] " Aaron Lu
2013-03-04 22:14 ` Jeff Garzik [this message]
2013-02-27 2:24 ` [GIT PULL] ACPI and power management fixes for v3.9-rc1 Aaron Lu
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=51351CDF.6070003@pobox.com \
--to=jgarzik@pobox.com \
--cc=aaron.lu@intel.com \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
/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