linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Reichel <sre@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-kernel@vger.kernel.org,
	Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: Status of Power Supply Subsystem
Date: Sat, 14 Jun 2014 17:36:58 +0200	[thread overview]
Message-ID: <20140614153658.GA13614@earth.universe> (raw)
In-Reply-To: <1946020.rieJTheGae@vostro.rjw.lan>

[-- Attachment #1: Type: text/plain, Size: 1726 bytes --]

Hi Rafael,

> You can volunteer to take over the maintainership, but then I guess it would
> make sense to push this through the PM tree anyway, so please feel free to
> send a pull request with those fixes to me.

I waited a bit to see if maybe Dmitry or David want to give feedback. But I
haven't received anything, so I volunteer to take this subsystem over.

For now I have prepared a branch containing a single fix, which should be
applied to 3.16 and added a signed tag. Since linux-next still uses the
unmaintained power supply git tree the patch has not been in linux-next.
Apart from that I created a new branch for 3.17 stuff (DT support for
drivers, non-critical fixes, ...).

I will also send a patch for the MAINTAINERS file in a jiffy. I have not
included it in the branch, so that all involved persons get another chance
to complain.

-- Sebastian

The following changes since commit 951e273060d15b233a7f7ccaf76ba682b5b05a03:

  Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2014-06-05 12:51:05 -0700)

are available in the git repository at:


  git://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git tags/power-supply-for-3.16

for you to fetch changes up to 381078e8865725ee95efadf0d988d8e24cddf088:

  bq2415x_charger: Fix Atomic Sleep Bug (2014-06-08 14:46:16 +0200)

----------------------------------------------------------------
power supply changes for the 3.16 series:

- Just a fix for atomic sleep bug

----------------------------------------------------------------
Sebastian Reichel (1):
      bq2415x_charger: Fix Atomic Sleep Bug

 drivers/power/bq2415x_charger.c | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2014-06-14 15:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16 18:38 Status of Power Supply Subsystem Sebastian Reichel
2014-05-16 20:54 ` Rafael J. Wysocki
2014-06-14 15:32   ` [PATCH] MAINTAINERS: power_supply: update maintainership Sebastian Reichel
2014-06-15  1:20     ` Stephen Rothwell
2014-06-15  9:31       ` Dmitry Eremin-Solenikov
2014-06-15 23:24         ` Stephen Rothwell
2014-06-15  9:38       ` Sebastian Reichel
2014-07-16 18:14     ` [PATCHv2] " Sebastian Reichel
2014-07-16 20:21       ` Dmitry Eremin-Solenikov
2014-07-16 21:09         ` Rafael J. Wysocki
2014-07-17 23:50           ` Sebastian Reichel
2014-06-14 15:36   ` Sebastian Reichel [this message]
2014-06-14 15:53     ` Status of Power Supply Subsystem David Woodhouse
2014-06-14 16:59       ` Dmitry Eremin-Solenikov
2014-06-14 17:20         ` Sebastian Reichel

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=20140614153658.GA13614@earth.universe \
    --to=sre@kernel.org \
    --cc=dbaryshkov@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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).