[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <AANLkTimQSmzObOzuN3rq9CwzyCzdJ3V9WQrkqZ7fuDnY@mail.gmail.com>
Date: Fri, 22 Oct 2010 18:03:24 +0200
From: Sedat Dilek <sedat.dilek@...glemail.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: LKML <linux-kernel@...r.kernel.org>, sfr@...b.auug.org.au,
Jan Harkes <jaharkes@...cmu.edu>
Subject: Re: linux-next: next-20101022 broken with unset CONFIG_BKL
On Fri, Oct 22, 2010 at 1:34 PM, Sedat Dilek <sedat.dilek@...glemail.com> wrote:
> On Fri, Oct 22, 2010 at 11:36 AM, Arnd Bergmann <arnd@...db.de> wrote:
>> On Friday 22 October 2010 11:30:17 Sedat Dilek wrote:
>>
>>> Wow, you answer in realtime :-), Arnd.
>>> Thanks for the explanations and I agree with you to wait for 27-rc1
>>> and then to remove BKL.
>>> Me just doing early-testing...
>>>
>>> A pointer to the patch?
>>> Thanks in advance.
>>
>> The thread is "Coda: remove BKL", You can find it on patchwork.
>>
>> Arnd
>>
>
> Yeah, I found the triple patch-series, but #3 does not apply, here is
> a v2 for that.
>
> Please have a look at it, Thanks.
>
> [ debian/changelog ]
> ...
> * debian/patches/for-linux-next/coda-fixes:
> - RFC-1-3-Coda-add-spin-lock-to-protect-accesses-to-struct-coda_inode_info.patch
> (Patch from <https://patchwork.kernel.org/patch/269131/>)
> - RFC-2-3-Coda-push-BKL-regions-into-coda_upcall.patch
> (Patch from <https://patchwork.kernel.org/patch/269141/>)
> - RFC-3-3-Coda-replace-BKL-with-mutex-v2.patch (refreshed)
> (Patch from <https://patchwork.kernel.org/patch/269151/>)
> ...
>
> Applying OK, but not compile-tested, yet.
>
> - Sedat -
>
Compilation was successful.
# modinfo coda
filename: /lib/modules/2.6.36-next-20101022.1-686/kernel/fs/coda/coda.ko
version: 6.6
license: GPL
alias: char-major-67-*
description: Coda Distributed File System VFS interface
author: Jan Harkes, Peter J. Braam
srcversion: AB8F3FBC43B1EBA43CEDEE5
depends:
vermagic: 2.6.36-next-20101022.1-686 SMP mod_unload modversions 686
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists