From: Rene Herman <rene.herman@keyaccess.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bjorn.helgaas@hp.com, torvalds@linux-foundation.org,
avuton@gmail.com, rene.herman@gmail.com, len.brown@intel.com,
linux-kernel@vger.kernel.org, rjw@sisk.pl
Subject: Re: 53052feb6 (PNP: remove pnp_mem_flags() as an lvalue) breaks my ALSA intel8x0 sound card regression
Date: Tue, 03 Jun 2008 02:31:13 +0200 [thread overview]
Message-ID: <484490D1.2040303@keyaccess.nl> (raw)
In-Reply-To: <20080602170309.6f9aea47.akpm@linux-foundation.org>
On 03-06-08 02:03, Andrew Morton wrote:
> On Tue, 03 Jun 2008 01:58:42 +0200
> Rene Herman <rene.herman@keyaccess.nl> wrote:
>
>> On 03-06-08 01:49, Andrew Morton wrote:
>>
>>> This broke
>>> pnp-replace-pnp_resource_table-with-dynamically-allocated-resources.patch:
>> I expect the patch was meant solely for 2.6.26...
>
> Sure. When this patch
> (pnp-mark-resources-that-conflict-with-pci-devices-disabled.patch) is
> applied to 2.6.26, the for-2.6.27
> pnp-replace-pnp_resource_table-with-dynamically-allocated-resources.patch
> broke, as I described here.
Err, yes, got them mixed up. There are just so many of them -- after .27
Bjorn will have basically rewritten all of PnP...
>> Bjorn, before you repost the option series due to this, wait a minute.
>> Am now looking at/testing 14/15 and see some stuff that needs changing
>> as well.
>
> "the option series" == "PNP: convert resource options to unified
> dynamic list, v1".
>
> I haven't got onto that yet. Strategic lagginess is working out
> nicely.
My bloody ISA test machine decided to up and die on me during a BIOS
flash. I'm sitting right smack in the middle of huge heap of old ISA
gunk hardware, cases and motherboards here -- and now I have to try and
dig out my bed ... :-(
Rene.
next prev parent reply other threads:[~2008-06-03 0:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 14:42 53052feb6 (PNP: remove pnp_mem_flags() as an lvalue) breaks my ALSA intel8x0 sound card regression Avuton Olrich
2008-06-01 16:20 ` Rene Herman
2008-06-02 3:25 ` Avuton Olrich
2008-06-02 19:06 ` Rene Herman
2008-06-02 22:05 ` Bjorn Helgaas
2008-06-02 22:23 ` Avuton Olrich
2008-06-02 22:42 ` Bjorn Helgaas
2008-06-02 23:49 ` Andrew Morton
2008-06-02 23:58 ` Rene Herman
2008-06-03 0:03 ` Andrew Morton
2008-06-03 0:31 ` Rene Herman [this message]
2008-06-03 0:15 ` Rene Herman
2008-06-03 18:40 ` Bjorn Helgaas
2008-06-04 23:38 ` Tony Luck
2008-06-05 16:18 ` Bjorn Helgaas
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=484490D1.2040303@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=akpm@linux-foundation.org \
--cc=avuton@gmail.com \
--cc=bjorn.helgaas@hp.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@gmail.com \
--cc=rjw@sisk.pl \
--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