linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Yannick Roehlly <yannick.roehlly@free.fr>,
	Yinghai Lu <yinghai@kernel.org>,
	Jesse Barnes <jesse.barnes@intel.com>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Andrew Morton <akpm@linux-foundation.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	berndl81@gmx.at, Greg KH <greg@kroah.com>
Subject: Reverting 5d423 fixes loading of ath9k on Acer Extensa 7630EZ
Date: Wed, 4 Nov 2009 15:40:59 -0800	[thread overview]
Message-ID: <43e72e890911041540hd1e5f87u8d282d9c95857504@mail.gmail.com> (raw)

Ingo,

reverting the commit 5d423, titled "x86/pci: remove rounding quirk
from e820_setup_gap()" fixes loading of ath9k on an Acer Extensa
7630EZ. We've troubleshooted the issue with the user,  Bernhard, who
eventually did a full bisect between 2.6.30 and 2.6.31 and found 5d423
was the culprit. For details please feel free to check:

http://bugzilla.kernel.org/show_bug.cgi?id=14402

Can you please consider reviewing this issue and help determine if
this indeed needs to be reverted for 2.6.32 and the next 2.6.31.y.

I am curious if other devices would work by reverting this as well.

  Luis

             reply	other threads:[~2009-11-04 23:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 23:40 Luis R. Rodriguez [this message]
2009-11-04 23:57 ` Reverting 5d423 fixes loading of ath9k on Acer Extensa 7630EZ Linus Torvalds
2009-11-05  0:16   ` Luis R. Rodriguez
2009-11-05  1:30     ` Yinghai Lu
2009-11-05  1:40       ` Luis R. Rodriguez
2009-11-05  7:14   ` Ingo Molnar
2009-11-08 19:35     ` Luis R. Rodriguez
2009-11-09  7:15       ` Ingo Molnar
2009-11-09 15:49         ` Luis R. Rodriguez
2009-11-10 20:30           ` Luis R. Rodriguez
2009-11-10 20:50             ` Luis R. Rodriguez

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=43e72e890911041540hd1e5f87u8d282d9c95857504@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=berndl81@gmx.at \
    --cc=greg@kroah.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jesse.barnes@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    --cc=yannick.roehlly@free.fr \
    --cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).