devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Keerthy <j-keerthy@ti.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Alexandre Courbot <gnurou@gmail.com>,
	Lee Jones <lee.jones@linaro.org>, Mark Brown <broonie@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	Linux-OMAP <linux-omap@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Linux Input <linux-input@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v6 4/6] gpio: tps65218-gpio: Add platform_device_id table
Date: Wed, 29 Jun 2016 10:56:21 +0200	[thread overview]
Message-ID: <CACRpkdb=jz-=K-itevZtvPtHF05pKdhkSp1USaf5LzQWaxckJw@mail.gmail.com> (raw)
In-Reply-To: <1467117054-12943-5-git-send-email-j-keerthy@ti.com>

On Tue, Jun 28, 2016 at 2:30 PM, Keerthy <j-keerthy@ti.com> wrote:

> platform_device_id table is needed for adding the tps65218-gpio
> module to the mfd_cell array.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> ---
>
> Changes in v4:
>
>   * Retained the compatible strings in order to interrogate the DT in the
>     normal way.

So do I just apply this or do you need it applied through another tree?

It looks standalone, should I just merge it?

Acked-by: Linus Walleij <linus.walleij@linaro.org>

Yours,
Linus Walleij

  reply	other threads:[~2016-06-29  8:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 12:30 [PATCH v6 0/6] mfd: tps65218: Clean ups Keerthy
2016-06-28 12:30 ` [PATCH v6 1/6] mfd: tps65218: Remove redundant read wrapper Keerthy
2016-06-28 12:30 ` [PATCH v6 2/6] Documentation: regulator: tps65218: Update examples Keerthy
2016-06-28 12:30 ` [PATCH v6 3/6] input: tps65218-pwrbutton: Add platform_device_id table Keerthy
2016-06-28 17:04   ` Dmitry Torokhov
     [not found] ` <1467117054-12943-1-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-06-28 12:30   ` [PATCH v6 4/6] gpio: tps65218-gpio: " Keerthy
2016-06-29  8:56     ` Linus Walleij [this message]
2016-06-29  9:32       ` Keerthy
     [not found]     ` <1467117054-12943-5-git-send-email-j-keerthy-l0cyMroinI0@public.gmane.org>
2016-07-04  9:50       ` Linus Walleij
2016-07-04  9:57         ` Keerthy
2016-06-28 12:30 ` [PATCH v6 5/6] mfd: tps65218: Use mfd_add_devices instead of of_platform_populate Keerthy
2016-06-28 12:30 ` [PATCH v6 6/6] regulator: tps65218: Remove all the compatibles Keerthy

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='CACRpkdb=jz-=K-itevZtvPtHF05pKdhkSp1USaf5LzQWaxckJw@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gnurou@gmail.com \
    --cc=j-keerthy@ti.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=tony@atomide.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).