From: Michael Tokarev <mjt@tls.msk.ru>
To: Tejun Heo <htejun@gmail.com>
Cc: Pedro Francisco <pedrogfrancisco@gmail.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: ahci rmmodable and shouldn't
Date: Tue, 21 Sep 2010 10:14:28 +0400 [thread overview]
Message-ID: <4C984D44.1080109@msgid.tls.msk.ru> (raw)
In-Reply-To: <4C97DBE2.8070707@gmail.com>
21.09.2010 02:10, Tejun Heo wrote:
> On 09/21/2010 12:09 AM, Tejun Heo wrote:
>> Hello,
>>
>> On 09/20/2010 10:44 PM, Pedro Francisco wrote:
>>> To which tree shall I apply it? It currently fails both on Linus'
>>> linux-2.6 and
>>> git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata-dev.git .
>>
>> Hmm... weird. It's against Linus' tree. Checking, yeap, it applies
>> cleanly to 2.6.36-rc4, commit 2422084a (Merge branch 'for-linus' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/mattst88/alpha-2.6).
>
> Attaching the patch just in case.
I tried it on 2.6.35 kernel. The ahci module usage count now
increases and decreases properly, at least from what I see here.
That's definitely better than previous 2.6.35 variant.
Thanks!
/mjt
next prev parent reply other threads:[~2010-09-21 6:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 21:56 ahci rmmodable and shouldn't Pedro Francisco
2010-09-16 21:58 ` Randy Dunlap
2010-09-17 9:53 ` Tejun Heo
2010-09-19 10:28 ` Pedro Francisco
2010-09-19 12:32 ` Tejun Heo
2010-09-20 9:25 ` Pedro Francisco
2010-09-20 9:31 ` Tejun Heo
2010-09-20 9:41 ` Tejun Heo
2010-09-20 20:44 ` Pedro Francisco
2010-09-20 22:09 ` Tejun Heo
2010-09-20 22:10 ` Tejun Heo
2010-09-21 6:14 ` Michael Tokarev [this message]
2010-09-21 7:25 ` [PATCH #upstream-fixes] ahci: fix module refcount breakage introduced by libahci split Tejun Heo
2010-09-21 7:32 ` Michael Tokarev
2010-09-21 8:17 ` Tejun Heo
2010-09-23 15:14 ` ahci rmmodable and shouldn't Pedro Francisco
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=4C984D44.1080109@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pedrogfrancisco@gmail.com \
/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.