[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160222143231.GB14970@lunn.ch>
Date: Mon, 22 Feb 2016 15:32:31 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Laxman Dewangan <ldewangan@...dia.com>
Cc: linus.walleij@...aro.org, gnurou@...il.com,
michael.hennerich@...log.com, corbet@....net, albeu@...e.fr,
rjui@...adcom.com, shc_work@...l.ru,
support.opensource@...semi.com, swarren@...dotorg.org,
thierry.reding@...il.com, linux-tegra@...r.kernel.org,
linux-doc@...r.kernel.org, gregkh@...uxfoundation.org,
patches@...nsource.wolfsonmicro.com, linux-kernel@...r.kernel.org,
linux-gpio@...r.kernel.org, bcm-kernel-feedback-list@...adcom.com,
bjorn.andersson@...ymobile.com, catalin.marinas@....com,
a.kesavan@...sung.com, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 01/61] gpio: Add devm_ apis for gpiochip_add_data and
gpiochip_remove
> +/**
> + * devm_gpiochip_add_data() - Resource manager piochip_add_data()
^
missing g.
> + * @dev: the device pointer on which irq_chip belongs to.
> + * @chip: the chip to register, with chip->base initialized
> + * Context: potentially before irqs will work
> + *
> + * Returns a negative errno if the chip can't be registered, such as
> + * because the chip->base is invalid or already associated with a
> + * different chip. Otherwise it returns zero as a success code.
> + *
> + * The gpio chip automatically be released when the device is unbound.
^
will
Andrew
Powered by blists - more mailing lists