From: "Rune Torgersen" <runet@innovsys.com>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, linux-ide@vger.kernel.org
Subject: RE: locking problem in sata_sil24?
Date: Mon, 3 Mar 2008 17:13:31 -0600 [thread overview]
Message-ID: <DCEAAC0833DD314AB0B58112AD99B93B0410A5BA@ismail.innsys.innovsys.com> (raw)
In-Reply-To: <1204585095.21545.37.camel@pasglop>
> From: Benjamin Herrenschmidt
> In fact, I remember working on 64 bits lockdep, based on patches from
> Johannes, but I didn't do 32 bits. I think somebody worked on it, but
> now I can't find the patches...
http://patchwork.ozlabs.org/linuxppc/patch?id=16652
> Whoever did it can bounce them back to me ? I intend to do some more
> work on this soon.
next prev parent reply other threads:[~2008-03-03 23:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 22:10 locking problem in sata_sil24? Rune Torgersen
2008-03-03 22:37 ` Benjamin Herrenschmidt
2008-03-03 22:44 ` Rune Torgersen
2008-03-03 22:58 ` Benjamin Herrenschmidt
2008-03-03 23:13 ` Rune Torgersen [this message]
2008-03-03 23:28 ` Johannes Berg
2008-03-04 14:39 ` Rune Torgersen
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=DCEAAC0833DD314AB0B58112AD99B93B0410A5BA@ismail.innsys.innovsys.com \
--to=runet@innovsys.com \
--cc=benh@kernel.crashing.org \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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