On Wed, Sep 22, 2010 at 13:04, Arnd Bergmann <arnd@xxxxxxxx> wrote:
On Tuesday 21 September 2010, Andreas Schwab wrote:
Arnd Bergmann <arnd@xxxxxxxx> writes:
The cache flush code only locks against itself, so there
is no excuse to use the BKL here. This replaces it with
a local mutex in order to maintain serialization of flushes.
I don't think this needs a lock at all.
Quite likely, I just took the most conservative approach.
If you want to queue a patch to drop the BKL from m68k, I'll
happily drop this one from my series.
I'm dropping the locking completely. Patch will follow.
Gr{oetje,eeting}s,
            Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
             Â Â -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
