From: Cong Wang <amwang@redhat.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
gcosta@redhat.com, mingo@elte.hu
Subject: Re: [Patch] i386: remove 'usedac' kernel parameter
Date: Mon, 14 Dec 2009 15:49:23 +0800 [thread overview]
Message-ID: <4B25EE03.9090303@redhat.com> (raw)
In-Reply-To: <20091209190649I.fujita.tomonori@lab.ntt.co.jp>
FUJITA Tomonori wrote:
> On Wed, 9 Dec 2009 01:25:48 -0500
> Amerigo Wang <amwang@redhat.com> wrote:
>
>> It is scheduled to be removed.
>>
>> Signed-off-by: WANG Cong <amwang@redhat.com>
>> Cc: Glauber Costa <gcosta@redhat.com>
>> Cc: Ingo Molnar <mingo@elte.hu>
>>
>> ---
>> diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
>> index 591e944..8c895f6 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>
>> -
>> ----------------------------
>> -
>
> I'm not sure about the above description, I'm not against removing
> this option though.
>
> IIUC, 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. I can't see how we can do the same thing with "allowdac" and
> "nodac" combination.
Hmm, yes, right, I missed this point.
Thanks!
prev parent reply other threads:[~2009-12-14 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 6:25 [Patch] i386: remove 'usedac' kernel parameter Amerigo Wang
2009-12-09 10:07 ` FUJITA Tomonori
2009-12-14 7:49 ` Cong Wang [this message]
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=4B25EE03.9090303@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