From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <gregkh@suse.de>
Cc: kernel list <linux-kernel@vger.kernel.org>,
KMoorman@transy.edu, w.sang@pengutronix.de,
ken_kawasaki@spring.nifty.jp, davem@davemloft.net,
Andrew Morton <akpm@osdl.org>,
alan@lxorguk.ukuu.org.uk
Subject: Re: serial_cs: oxsemi quirk breaks resume
Date: Sat, 16 Jan 2010 08:38:34 +0100 [thread overview]
Message-ID: <20100116073833.GA15822@elf.ucw.cz> (raw)
In-Reply-To: <20100115235425.GB20493@suse.de>
On Fri 2010-01-15 15:54:25, Greg KH wrote:
> On Fri, Jan 15, 2010 at 03:53:33PM -0800, Greg KH wrote:
> > On Fri, Jan 15, 2010 at 09:01:00PM +0100, Pavel Machek wrote:
> > > On Tue 2009-11-10 08:54:10, Pavel Machek wrote:
> > > >
> > > > Quirk is applied on all cards with given manfid (is it that
> > > > correct?). Unfortunately, that quirk breaks resume on zaurus with
> > > > billionton bluetooth card inserted: c950ctrl is 0 and outb() faults.
> > > >
> > > > Signed-off-by: Pavel Machek <pavel@ucw.cz>
> > >
> > > I believe this patch got enough acks and is waiting in the tree
> > > somewhere (greg?) (possibly with slightly different changelog), but I
> > > don't see it in 33-rc4. Could it get pushed? It is quite simple
> > > bugfix, and is important for my zaurus... Pavel
> >
> > I thought others complained about it.
> >
> > If not, care to resend it to me, with the acks added to it, so that I
> > can forward it on?
>
> Oh nevermind, it's in my tree already, I'll include it in the next round
> of patches to go to Linus (looking like Monday now, too late for
> today...)
Thanks!
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2010-01-16 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-10 7:54 Pavel Machek
2009-11-10 10:32 ` Alan Cox
2009-11-10 10:53 ` Pavel Machek
2010-01-15 20:01 ` Pavel Machek
2010-01-15 23:53 ` Greg KH
2010-01-15 23:54 ` Greg KH
2010-01-16 7:38 ` Pavel Machek [this message]
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=20100116073833.GA15822@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=KMoorman@transy.edu \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=ken_kawasaki@spring.nifty.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=w.sang@pengutronix.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
Powered by JetHome