[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAB=NE6XiuZCzWXROi35no0nnU4F7-=d_FwX90xEKgSgFGVbfYg@mail.gmail.com>
Date: Thu, 29 Nov 2012 12:51:37 -0800
From: "Luis R. Rodriguez" <mcgrof@...not-panic.com>
To: Hauke Mehrtens <hauke@...ke-m.de>
Cc: backports@...r.kernel.org, linux-kernel@...r.kernel.org,
Arend Van Spriel <arend@...adcom.com>,
linux-wireless <linux-wireless@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Srinidhi Kasagar <srinidhi.kasagar@...ricsson.com>,
Linus Walleij <linus.walleij@...aro.org>,
Kyungmin Park <kyungmin.park@...sung.com>,
Sylwester Nawrocki <s.nawrocki@...sung.com>,
Alexander Stein <alexander.stein@...tec-electronic.com>
Subject: Re: [PATCH 6/6] compat-drivers: do not use struct spinlock
On Thu, Nov 29, 2012 at 11:47 AM, Luis R. Rodriguez
<mcgrof@...not-panic.com> wrote:
> On Wed, Nov 28, 2012 at 3:07 PM, Hauke Mehrtens <hauke@...ke-m.de> wrote:
>
> IMHO your patch should go upstream and a respective patch should be
> submitted as well as for these drivers:
>
> mcgrof@...jol ~/linux-next (git::master)$ git grep "struct spinlock" drivers/
> drivers/crypto/ux500/cryp/cryp.h: struct spinlock ctx_lock;
> drivers/crypto/ux500/cryp/cryp.h: struct spinlock power_state_spinlock;
> drivers/crypto/ux500/hash/hash_alg.h: struct spinlock ctx_lock;
> drivers/crypto/ux500/hash/hash_alg.h: struct spinlock
> power_state_lock;
> drivers/gpu/drm/i915/i915_drv.h: struct spinlock gt_lock;
> drivers/gpu/drm/i915/i915_drv.h: struct spinlock lock;
> drivers/media/platform/s5p-fimc/mipi-csis.c: struct spinlock slock;
> drivers/media/platform/s5p-jpeg/jpeg-core.h: struct spinlock slock;
> drivers/watchdog/ie6xx_wdt.c: struct spinlock unlock_sequence;
>
> Alexander, please also add your driver to the MAINTAINERS file.
Hauke, I'll add your patch for now into compat-drivers until shit
catches up on linux-next if the series I just posted goes through.
Luis
--
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