[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFNjLiVZ+g6eeHjpwMm+KiAA69Kpm_nVjWxkm2wCuV58RZwj4A@mail.gmail.com>
Date: Thu, 24 May 2018 11:21:31 -0700
From: John Sperbeck <jsperbeck@...gle.com>
To: peda@...ntia.se
Cc: linux-kernel@...r.kernel.org, wsa@...-dreams.de,
peterz@...radead.org, mingo@...hat.com, will.deacon@....com,
dave@...olabs.net, pombredanne@...b.com, tglx@...utronix.de,
gregkh@...uxfoundation.org, linux-i2c@...r.kernel.org,
Peter Chang <dpf@...gle.com>,
Deepa Dinamani <deepadinamani@...gle.com>
Subject: Re: [PATCH v3 0/2] Re: Problem: lockdep warning with nested instances
of i2c-mux
On Thu, May 24, 2018 at 6:52 AM Peter Rosin <peda@...ntia.se> wrote:
> Hi!
> Sorry for spamming. At least I'm finding these embarrassing f$&%ups
> myself, not that it helps all that much, but...
> Changes since v2 https://lkml.org/lkml/2018/5/24/176
> - EXPORT_SYMBOL_GPL(rt_mutex_lock_nested) is more appropriate (the
> rt_ prefix was missing).
Yes, after fixing the "rt_" typo, this addresses our use case. Thanks for
the quick response.
Powered by blists - more mailing lists