All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: William Breathitt Gray <vilhelm.gray@gmail.com>
Cc: Alexandre Courbot <gnurou@gmail.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/5] gpio: 104-idio-16: Remove unnecessary driver_data set
Date: Wed, 1 Feb 2017 14:23:59 +0100	[thread overview]
Message-ID: <CACRpkdZBctbHV2+8LJVO0eku-nFGa6R+92h-Eg_7S6FxTAOThw@mail.gmail.com> (raw)
In-Reply-To: <2c89ad9a9c55346e1187c05bca5eac62ce0df0ac.1485786703.git.vilhelm.gray@gmail.com>

On Mon, Jan 30, 2017 at 3:39 PM, William Breathitt Gray
<vilhelm.gray@gmail.com> wrote:

> Setting driver_data was necessary to access private data in the
> idio_16_remove function. Now that the idio_16_remove function is gone,
> driver_data is no longer used. This patch removes the relevant code.
>
> Signed-off-by: William Breathitt Gray <vilhelm.gray@gmail.com>

Patch applied.

Yours,
Linus Walleij

  reply	other threads:[~2017-02-01 13:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 14:39 [PATCH 0/5] gpio: Remove unnecessary driver_data set operations William Breathitt Gray
2017-01-30 14:39 ` [PATCH 1/5] gpio: 104-dio-48e: Remove unnecessary driver_data set William Breathitt Gray
2017-02-01 13:21   ` Linus Walleij
2017-01-30 14:39 ` [PATCH 2/5] gpio: 104-idi-48: " William Breathitt Gray
2017-02-01 13:22   ` Linus Walleij
2017-01-30 14:39 ` [PATCH 3/5] gpio: 104-idio-16: " William Breathitt Gray
2017-02-01 13:23   ` Linus Walleij [this message]
2017-01-30 14:40 ` [PATCH 4/5] gpio: gpio-mm: " William Breathitt Gray
2017-02-01 13:44   ` Linus Walleij
2017-01-30 14:40 ` [PATCH 5/5] gpio: ws16c48: " William Breathitt Gray
2017-02-01 13:45   ` 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=CACRpkdZBctbHV2+8LJVO0eku-nFGa6R+92h-Eg_7S6FxTAOThw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=gnurou@gmail.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vilhelm.gray@gmail.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.