From: Hugh Dickins <hughd@google.com>
To: Holger Macht <holger@homac.de>
Cc: Matthew Garrett <mjg@redhat.com>,
Jeff Garzik <jgarzik@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: dock_link_device is oopsy
Date: Fri, 17 Feb 2012 14:42:31 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.00.1202171436490.10222@eggly.anvils> (raw)
In-Reply-To: <20120217222922.GA2741@homac.suse.de>
On Fri, 17 Feb 2012, Holger Macht wrote:
> On Fr 17. Feb - 13:46:04, Hugh Dickins wrote:
> > Matthew,
> >
> > A linux-next oops at bootup in dock_link_device() tells me that you
> > were not feeling well when you wrote that and dock_unlink_device():
> > I hope you're feeling better now and can rewrite them soon.
>
> Andrew Morton experienced a similar problem. What system are you using?
> I didn't encounter this problem with the systems I tested with.
The two systems I got that on were both 4-year-old Core2 Duo systems,
one an HP quad desktop, one a Fujitsu-Siemens laptop.
>
> Do you actually have a /sys/devices/platform/dock.?/ directory with a
> file 'type' that contains 'dock_station'?
I'll have to report back on that this evening, I'm away from them now.
Hugh
next prev parent reply other threads:[~2012-02-17 22:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 21:46 Hugh Dickins
2012-02-17 22:29 ` Holger Macht
2012-02-17 22:42 ` Hugh Dickins [this message]
2012-02-17 23:01 ` Holger Macht
2012-02-17 23:49 ` Hugh Dickins
2012-02-18 11:14 ` Holger Macht
2012-02-18 13:05 ` Hillf Danton
2012-02-18 13:26 ` Holger Macht
2012-02-18 13:37 ` Hillf Danton
2012-02-18 14:04 ` Holger Macht
2012-02-18 14:35 ` Hillf Danton
2012-02-18 18:46 ` Hugh Dickins
2012-02-18 19:57 ` Holger Macht
2012-02-18 21:03 ` Hugh Dickins
2012-02-18 21:50 ` Holger Macht
2012-02-21 22:24 ` Jeff Garzik
2012-02-21 22:30 ` Holger Macht
2012-02-18 7:52 ` Hugh Dickins
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.LSU.2.00.1202171436490.10222@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=holger@homac.de \
--cc=jgarzik@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®