linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v3 0/3] Input: gpio-keys - clean up series
Date: Fri, 25 Apr 2014 19:22:14 +0300	[thread overview]
Message-ID: <1398442937-15309-1-git-send-email-andriy.shevchenko@linux.intel.com> (raw)

This is a 3rd iteration of the small cleanup against gpio-keys driver.

Changes since v2:
 - append received Acks
 - rebase against recent linux-next
 - test on Intel Medfield based product

Andy Shevchenko (3):
  Input: gpio_keys - use dev instead of pdev in gpio_keys_setup_key()
  Input: gpio_keys - convert to use devm_*
  Input: gpio_keys - convert struct descriptions to kernel-doc

 drivers/input/keyboard/gpio_keys.c | 82 +++++++++++++-------------------------
 include/linux/gpio_keys.h          | 45 +++++++++++++++------
 2 files changed, 61 insertions(+), 66 deletions(-)

-- 
1.9.2


             reply	other threads:[~2014-04-25 16:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 16:22 Andy Shevchenko [this message]
2014-04-25 16:22 ` [PATCH v3 1/3] Input: gpio_keys - use dev instead of pdev in gpio_keys_setup_key() Andy Shevchenko
2014-04-25 21:21   ` Dmitry Torokhov
2014-04-28  9:42     ` Andy Shevchenko
2014-04-25 16:22 ` [PATCH v3 2/3] Input: gpio_keys - convert to use devm_* Andy Shevchenko
2014-04-26  4:43   ` Dmitry Torokhov
2014-04-28  9:40     ` Andy Shevchenko
2014-04-25 16:22 ` [PATCH v3 3/3] Input: gpio_keys - convert struct descriptions to kernel-doc Andy Shevchenko
2014-04-26  4:41   ` Dmitry Torokhov

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=1398442937-15309-1-git-send-email-andriy.shevchenko@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).