linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	Linux PM mailing list <linux-pm@vger.kernel.org>,
	Discussions about the Letux Kernel 
	<letux-kernel@openphoenux.org>,
	Grazvydas Ignotas <notasas@gmail.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	Nikolaus Schaller <hns@goldelico.com>,
	Marek Belisko <marek@goldelico.com>,
	Russell King <linux@armlinux.org.uk>,
	Mark Rutland <mark.rutland@arm.com>,
	Rob Herring <robh+dt@kernel.org>, NeilBrown <neil@brown.name>,
	Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH v7 0/2] More fixes for twl4030 charger
Date: Sat, 1 Jul 2017 13:49:16 +0200	[thread overview]
Message-ID: <B93260EC-F61D-4B51-9B2C-707917CEBC53@goldelico.com> (raw)
In-Reply-To: <cover.1497861705.git.hns@goldelico.com>

Hi Sebastian,

> Am 19.06.2017 um 10:41 schrieb H. Nikolaus Schaller <hns@goldelico.com>:
> 
> Changes V7:
> * removed already merged patches from patch set
> * further fix for potentially wrong irq and notifier initialization sequence (suggested by Sebastian Reichel)
> * NULLify transceiver pointer in case of errors (suggested by Sebastian Reichel)

Did you find time to review the updated v7 patches?
I have not seen them arrive in linux-next.

BR and thanks,
Nikolaus

      parent reply	other threads:[~2017-07-01 11:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19  8:41 [PATCH v7 0/2] More fixes for twl4030 charger H. Nikolaus Schaller
2017-06-19  8:41 ` [PATCH v7 1/2] power: supply: twl4030-charger: move irq allocation to just before irqs are enabled H. Nikolaus Schaller
2017-07-03 12:55   ` Sebastian Reichel
2017-07-03 16:36     ` H. Nikolaus Schaller
2017-06-19  8:41 ` [PATCH v7 2/2] power: supply: twl4030-charger: add deferred probing for phy and iio H. Nikolaus Schaller
2017-07-03 12:59   ` Sebastian Reichel
2017-07-01 11:49 ` H. Nikolaus Schaller [this message]

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=B93260EC-F61D-4B51-9B2C-707917CEBC53@goldelico.com \
    --to=hns@goldelico.com \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=marek@goldelico.com \
    --cc=mark.rutland@arm.com \
    --cc=neil@brown.name \
    --cc=notasas@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=sre@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).