All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	linux-wireless <linux-wireless@vger.kernel.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: Re: Reverting 5d423 fixes loading of ath9k on Acer Extensa 7630EZ
Date: Wed, 4 Nov 2009 15:57:45 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.01.0911041551220.31845@localhost.localdomain> (raw)
In-Reply-To: <43e72e890911041540hd1e5f87u8d282d9c95857504@mail.gmail.com>



On Wed, 4 Nov 2009, Luis R. Rodriguez wrote:
> 
> 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.
> [ ... ] For details please feel free to check:
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=14402

That same commit was the cause for

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

and we just increased the rounding to make it go away (see commit 
15b812f1). But that was a hack.

And if that didn't help the ath9k case, then we should just revert 
entirely.

			Linus

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 23:40 Reverting 5d423 fixes loading of ath9k on Acer Extensa 7630EZ Luis R. Rodriguez
2009-11-04 23:57 ` Linus Torvalds [this message]
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=alpine.LFD.2.01.0911041551220.31845@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --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=mcgrof@gmail.com \
    --cc=mingo@elte.hu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.