From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org,
Alexandre Courbot <acourbot@nvidia.com>
Cc: Clemens Gruber <clemens.gruber@pqgruber.com>,
Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH v2] gpio: provide lockdep keys for nested/unnested irqchips
Date: Wed, 11 Jan 2017 11:59:47 -0600 [thread overview]
Message-ID: <b63d16dc-d226-36a7-70db-ab78172a999d@ti.com> (raw)
In-Reply-To: <20170111154311.11260-1-linus.walleij@linaro.org>
On 01/11/2017 09:43 AM, Linus Walleij wrote:
> The helper function for adding a GPIO chip compiles in a lockdep
> key for debugging, the same key is needed for nested chips as
> well.
>
> The macro construction is unreadable, replace this with two
> static inlines instead.
>
> The _gpiochip_irqchip_add prefixed function is not helpful,
> rename it with gpiochip_irqchip_add_key() that tell us what the
> function is actually doing.
>
> Fixes: d245b3f9bd36 ("gpio: simplify adding threaded interrupts")
> Cc: Grygorii Strashko <grygorii.strashko@ti.com>
> Cc: Clemens Gruber <clemens.gruber@pqgruber.com>
> Cc: Roger Quadros <rogerq@ti.com>
> Reported-by: Clemens Gruber <clemens.gruber@pqgruber.com>
> Reported-by: Roger Quadros <rogerq@ti.com>
> Reported-by: Grygorii Strashko <grygorii.strashko@ti.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - Write code that actually compiles on LOCKDEP too, now I've
> had it with confusing _underscores.
> ---
> drivers/gpio/gpiolib.c | 18 ++++++------
> include/linux/gpio/driver.h | 70 ++++++++++++++++++++++++++++++++-------------
> 2 files changed, 59 insertions(+), 29 deletions(-)
>
Tested-by: Grygorii Strashko <grygorii.strashko@ti.com>
regards,
-grygorii
prev parent reply other threads:[~2017-01-11 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 15:43 [PATCH v2] gpio: provide lockdep keys for nested/unnested irqchips Linus Walleij
2017-01-11 16:00 ` Clemens Gruber
2017-01-11 17:59 ` Grygorii Strashko [this message]
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=b63d16dc-d226-36a7-70db-ab78172a999d@ti.com \
--to=grygorii.strashko@ti.com \
--cc=acourbot@nvidia.com \
--cc=clemens.gruber@pqgruber.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=rogerq@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).