From: Tejun Heo <tj@kernel.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux-ide@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] libata-sff: clarification and trivial correction to Kconfig text
Date: Sun, 30 May 2010 17:05:08 +0200 [thread overview]
Message-ID: <4C027EA4.5050900@kernel.org> (raw)
In-Reply-To: <tkrat.acb772e71ffffd6e@s5r6.in-berlin.de>
On 05/30/2010 04:00 PM, Stefan Richter wrote:
> Change the text of the ATA_BMDMA prompt to indicate that it lets one access a class of
> device drivers (rather than only add a certain feature to libata). The divisions of
> the "ATA SFF support" menu now read
> - SFF controllers with custom DMA interface,
> - SFF controllers with bus master DMA (was: "ATA BMDMA support"),
> - SATA SFF controllers with BMDMA,
> - PATA SFF controllers with BMDMA,
> - PIO-only SFF controllers.
> This hopefully helps convince users of "make oldconfig" to follow the
> recommendation to switch that option on.
>
> Also let the help text of this prompt say more precisely what it is about: It adds a
> little bit of support code to libata that is required by many but not all SFF drivers.
> This option alone does not add support of respective controllers though; according
> drivers are chosen at subsequent dependent Kconfig prompts. --- And fix a typo.
>
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
next prev parent reply other threads:[~2010-05-30 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 10:47 [PATCH] libata-sff: trivial corrections to Kconfig help text Stefan Richter
2010-05-29 12:38 ` Tejun Heo
2010-05-29 15:41 ` Stefan Richter
2010-05-30 8:46 ` Tejun Heo
2010-05-30 14:00 ` [PATCH] libata-sff: clarification and trivial correction to Kconfig text Stefan Richter
2010-05-30 15:05 ` Tejun Heo [this message]
2010-06-02 17:50 ` [PATCH] libata-sff: trivial corrections to Kconfig help text Jeff Garzik
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=4C027EA4.5050900@kernel.org \
--to=tj@kernel.org \
--cc=jeff@garzik.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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).