public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Avuton Olrich <avuton@gmail.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Rene Herman <rene.herman@gmail.com>,
	Len Brown <len.brown@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 53052feb6 (PNP: remove pnp_mem_flags() as an lvalue) breaks my ALSA intel8x0 sound card regression
Date: Sun, 01 Jun 2008 18:20:32 +0200	[thread overview]
Message-ID: <4842CC50.4030406@keyaccess.nl> (raw)
In-Reply-To: <3aa654a40806010742r1d61caa2j681882145533b56a@mail.gmail.com>

On 01-06-08 16:42, Avuton Olrich wrote:

> My intel8x0 card stops working due to a regression; bisection and
> information below.
> 
> May have relationship to this thread
> http://groups.google.com/group/linux.kernel/browse_thread/thread/d5857287a36e71af/d7ae0a1490b7d142?lnk=st
> 
> http://avuton.googlepages.com/intel8x0-config.gz
> http://avuton.googlepages.com/intel8x0-cpuinfo
> http://avuton.googlepages.com/intel8x0-dmesg

This dmesg seems to be 6-byte file consisting of "dmesg\n" ...

> http://avuton.googlepages.com/intel8x0-ioports
> http://avuton.googlepages.com/intel8x0-lspci-vvv
> http://avuton.googlepages.com/intel8x0-modules
> http://avuton.googlepages.com/intel8x0-ver-linux
> http://avuton.googlepages.com/intel8x0-version
> 
> commit 53052feb6ddd05cb2b5c6e89fb489bf83bbb6803
> Author: Bjorn Helgaas <bjorn.helgaas@hp.com>
> Date:   Mon Apr 28 16:34:15 2008 -0600
> 
>     PNP: remove pnp_mem_flags() as an lvalue
> 
>     A future change will change pnp_mem_flags() from a "#define that
>     simplifies to an lvalue" to "an inline function that returns the
>     flags value."
> 
>     Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
>     Acked-By: Rene Herman <rene.herman@gmail.com>
>     Signed-off-by: Len Brown <len.brown@intel.com>
> 

I'm probably just really blind but I don't see how that specific commit 
may have made any difference. It _is_ in the exact spot which would fix 
that overlap problem of yours but this should be an identity change as 
far as fuctionality goes. Are you _really_ sure it's this one?

(Is this racing with anything?)

Rene.

  reply	other threads:[~2008-06-01 16:17 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 [this message]
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
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=4842CC50.4030406@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --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 \
    /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