From: Hans de Goede <hdegoede@redhat.com>
To: Luca Tettamanti <kronos.it@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jean Delvare <khali@linux-fr.org>,
Matthew Garrett <mjg@redhat.com>, Len Brown <lenb@kernel.org>,
Thomas Renninger <trenn@suse.de>,
linux-acpi@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] ACPI: add "auto" to acpi_enforce_resources
Date: Tue, 24 Mar 2009 14:21:21 +0100 [thread overview]
Message-ID: <49C8DE51.2010103@redhat.com> (raw)
In-Reply-To: <68676e00903240539i119b6d26j516ee131d4cd6781@mail.gmail.com>
On 03/24/2009 01:39 PM, Luca Tettamanti wrote:
> On Fri, Feb 27, 2009 at 2:27 PM, Pavel Machek<pavel@ucw.cz> wrote:
>> Hi!
>>
>>>> For the record we have changed the default to strict in Fedora's
>>>> development branch, for 2 weeks or so now, including in the recently
>>>> released Fedora 11 release and we've had 0 complaints so far.
>>> Well, if the number of affected systems is small, this is good news.
>>> But this is only 2 weeks and one distribution, coverage isn't
>>> sufficient to claim anything yet IMHO.
>>>
>>> That being said... if there's a common consensus that switching to
>>> strict and dealing with fallouts is the best thing to do, and I'm the
>>> only one objecting to this, then I am ready to admit that I was wrong
>>> and let you proceed.
>> I believe that 'enable strict, deal with fallout' is the best
>> long-term strategy...
>
> Hello,
> the merge window for .30 is now open, what are we going to do with this issue?
>
I think the consensus was to make the default strict and to merge the atk0110
driver, right?
Note that we've been running this setup in Fedora kernels for quite a while now,
and have had only one bug report, which was solved by simply explaining why this
was done.
Regards,
Hans
next prev parent reply other threads:[~2009-03-24 13:21 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 21:05 [PATCH] ACPI: add "auto" to acpi_enforce_resources Luca Tettamanti
2009-01-26 8:37 ` Hans de Goede
2009-01-29 10:30 ` Thomas Renninger
2009-01-29 15:16 ` Luca Tettamanti
2009-01-29 16:29 ` Thomas Renninger
2009-01-29 18:58 ` Hans de Goede
2009-01-29 21:31 ` Jean Delvare
2009-01-30 14:29 ` Thomas Renninger
2009-02-01 21:22 ` Luca Tettamanti
2009-02-02 9:11 ` Jean Delvare
2009-02-02 11:38 ` Luca Tettamanti
2009-02-02 17:22 ` [PATCH 1/2] RFC: ACPI: Interface for ACPI drivers to place quirk code which gets executed early Thomas Renninger
2009-02-02 20:22 ` Luca Tettamanti
2009-02-03 13:08 ` Thomas Renninger
2009-02-03 13:45 ` Luca Tettamanti
2009-02-03 14:19 ` Jean Delvare
2009-02-04 13:37 ` Thomas Renninger
2009-02-02 17:22 ` [PATCH 2/2] RFC: ACPI: Set enforce_resources to strict if a ATK0110 device is found in namespace Thomas Renninger
2009-02-02 20:29 ` Luca Tettamanti
2009-02-02 11:38 ` [PATCH] ACPI: add "auto" to acpi_enforce_resources Thomas Renninger
2009-01-29 21:15 ` Luca Tettamanti
2009-02-04 5:52 ` Len Brown
2009-02-04 6:05 ` Matthew Garrett
2009-02-04 8:37 ` Hans de Goede
2009-02-04 13:17 ` Matthew Garrett
2009-02-04 13:26 ` Jean Delvare
2009-02-04 14:20 ` Matthew Garrett
2009-02-10 13:57 ` Jean Delvare
2009-02-10 14:08 ` Matthew Garrett
2009-02-10 15:32 ` Hans de Goede
2009-02-10 16:24 ` Jean Delvare
2009-02-27 13:27 ` Pavel Machek
2009-03-24 12:39 ` Luca Tettamanti
2009-03-24 13:21 ` Hans de Goede [this message]
2009-03-24 13:43 ` Jean Delvare
2009-03-24 14:29 ` Hans de Goede
2009-03-29 20:16 ` Luca Tettamanti
2009-03-29 20:33 ` Pavel Machek
2009-03-29 20:55 ` Jean Delvare
2009-03-29 22:01 ` Luca Tettamanti
2009-03-30 7:36 ` Jean Delvare
2009-04-02 22:59 ` Len Brown
2009-04-03 9:40 ` Jean Delvare
2009-02-12 12:44 ` Jean Delvare
2009-04-02 22:45 ` polling (Re: [PATCH] ACPI: add "auto" to acpi_enforce_resources) Len Brown
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=49C8DE51.2010103@redhat.com \
--to=hdegoede@redhat.com \
--cc=khali@linux-fr.org \
--cc=kronos.it@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=pavel@ucw.cz \
--cc=trenn@suse.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