All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Christoph Fritz <chf.fritz@googlemail.com>
Cc: Tony Lindgren <tony@atomide.com>,
	devicetree <devicetree@vger.kernel.org>,
	linux-omap@vger.kernel.org, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v2] dt-bindings: mfd: fix documentation of tps65911
Date: Tue, 3 Jul 2018 08:41:19 +0100	[thread overview]
Message-ID: <20180703074119.GK20176@dell> (raw)
In-Reply-To: <1529781960.2215.2.camel@googlemail.com>

On Sat, 23 Jun 2018, Christoph Fritz wrote:
> On Mon, 2018-06-11 at 12:27 -0600, Rob Herring wrote:
> > On Tue, Jun 05, 2018 at 11:26:49AM +0200, Christoph Fritz wrote:
> > > This patch fixes documentation of tps65911 because its list of
> > > compatible regulators contains wrongly vdd3 instead of vdd2.
> > > 
> > > Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
> > > ---
> > >  Documentation/devicetree/bindings/mfd/tps65910.txt | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > Acked-by: Rob Herring <robh@kernel.org>
> 
> any chance to get this patch queued soon?

It's in the queue to be reviewed.  I have just returned from paternity
leave and have 290 emails to get through.  Please bear with me.

-- 
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2018-07-03  7:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04 21:14 [PATCH] regulator: tps65911: fix regulator-compatible documentation Christoph Fritz
2018-06-05  7:04 ` Lee Jones
2018-06-05  9:26   ` [PATCH v2] dt-bindings: mfd: fix documentation of tps65911 Christoph Fritz
2018-06-11 18:27     ` Rob Herring
2018-06-23 19:26       ` Christoph Fritz
2018-07-03  7:41         ` Lee Jones [this message]
2018-07-04  7:41     ` Lee Jones

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=20180703074119.GK20176@dell \
    --to=lee.jones@linaro.org \
    --cc=chf.fritz@googlemail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=robh@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 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.