From: Cong Wang <amwang@redhat.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: mingo@elte.hu, gcosta@redhat.com, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove usedac in feature-removal-schedule.txt
Date: Mon, 14 Dec 2009 15:50:25 +0800 [thread overview]
Message-ID: <4B25EE41.4020809@redhat.com> (raw)
In-Reply-To: <20091214104423X.fujita.tomonori@lab.ntt.co.jp>
FUJITA Tomonori wrote:
> The reason of removal, "replaced by allowdac and no dac combination"
> is incorrect. There is no way to do the same thing with "allowdac" and
> "nodac" combination.
>
> The usedac option enables us to stop via_no_dac() setting forbid_dac
> to 1. That is, someone who uses VIA bridges can use DAC with this
> option even if some of VIA bridges seem to be broken about DAC.
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Hi,
This sounds reasonable for me.
Acked-by: WANG Cong <amwang@redhat.com>
> ---
> Documentation/feature-removal-schedule.txt | 7 -------
> 1 files changed, 0 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
> index 2a4d779..eb2c138 100644
> --- a/Documentation/feature-removal-schedule.txt
> +++ b/Documentation/feature-removal-schedule.txt
> @@ -291,13 +291,6 @@ Who: Michael Buesch <mb@bu3sch.de>
>
> ---------------------------
>
> -What: usedac i386 kernel parameter
> -When: 2.6.27
> -Why: replaced by allowdac and no dac combination
> -Who: Glauber Costa <gcosta@redhat.com>
> -
> ----------------------------
> -
> What: print_fn_descriptor_symbol()
> When: October 2009
> Why: The %pF vsprintf format provides the same functionality in a
next prev parent reply other threads:[~2009-12-14 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 2:06 [PATCH] remove usedac in feature-removal-schedule.txt FUJITA Tomonori
2009-12-14 7:50 ` Cong Wang [this message]
2009-12-14 7:58 ` [tip:x86/urgent] x86: Remove " tip-bot for FUJITA Tomonori
2009-12-14 14:57 ` Valdis.Kletnieks
2009-12-14 23:13 ` FUJITA Tomonori
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=4B25EE41.4020809@redhat.com \
--to=amwang@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=gcosta@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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