From: Alex Courbot <acourbot@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v3 4/4] gpiolib: update inline documentation of gpiod_get_index()
Date: Tue, 10 Dec 2013 10:12:14 +0900 [thread overview]
Message-ID: <52A66A6E.8060808@nvidia.com> (raw)
In-Reply-To: <CACRpkdZAvGyOUWny-tqNYcasFx4FpS8fS92i+CROgPs3ttJ1VQ@mail.gmail.com>
On 12/09/2013 10:20 PM, Linus Walleij wrote:
> On Thu, Dec 5, 2013 at 10:26 AM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
>
>> The patch just accents that @dev could be NULL.
>>
>> There is no functional change.
>>
>> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>
> Patch applied.
>
> (Unless Alexandre says it's wrong!)
Nope, this patch is correct. Should have ack'ed it, sorry.
next prev parent reply other threads:[~2013-12-10 1:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 9:26 [PATCH v3 0/4] gpiolib: clean up messaging part Andy Shevchenko
2013-12-05 9:26 ` [PATCH v3 1/4] gpiolib: unify pr_* messages format Andy Shevchenko
2013-12-09 13:15 ` Linus Walleij
2013-12-05 9:26 ` [PATCH v3 2/4] gpiolib: introduce chip_* to print with chip->label prefix Andy Shevchenko
2013-12-09 13:17 ` Linus Walleij
2013-12-05 9:26 ` [PATCH v3 3/4] gpiolib: convert gpiod_lookup description to kernel-doc Andy Shevchenko
2013-12-09 13:18 ` Linus Walleij
2013-12-05 9:26 ` [PATCH v3 4/4] gpiolib: update inline documentation of gpiod_get_index() Andy Shevchenko
2013-12-09 13:20 ` Linus Walleij
2013-12-10 1:12 ` Alex Courbot [this message]
2013-12-06 1:40 ` [PATCH v3 0/4] gpiolib: clean up messaging part Alex Courbot
2013-12-09 8:49 ` Andy Shevchenko
2013-12-09 13:12 ` Linus Walleij
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=52A66A6E.8060808@nvidia.com \
--to=acourbot@nvidia.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.