All of
 help / color / mirror / Atom feed
From: Sebastian Reichel <>
To: Linus Torvalds <>
Subject: [GIT PULL] power-supply changes for 5.1
Date: Wed, 1 May 2019 23:26:10 +0200	[thread overview]
Message-ID: <20190501212610.5qrl7gyttdyzs2dq@earth.universe> (raw)

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

Hi Linus,

I have two more fixes for the 5.1 cycle. One division by zero fix
in a specific driver and one core workaround for bad userspace
behaviour from systemd regarding uevents. IMHO this can be considered
to be a userspace bug, but the debug messages are useless anyways.

-- Sebastian

The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:

  Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)

are available in the Git repository at:

  ssh:// tags/for-v5.1-rc

for you to fetch changes up to 349ced9984ff540ce74ca8a0b2e9b03dc434b9dd:

  power: supply: sysfs: prevent endless uevent loop with CONFIG_POWER_SUPPLY_DEBUG (2019-04-26 00:06:56 +0200)

Power Supply Fixes for 5.1 cycle

* cpcap-battery: fix a division by zero
* core: fix systemd issue due to log messages produced by uevent

Andrey Smirnov (1):
      power: supply: sysfs: prevent endless uevent loop with CONFIG_POWER_SUPPLY_DEBUG

Tony Lindgren (1):
      power: supply: cpcap-battery: Fix division by zero

 drivers/power/supply/cpcap-battery.c      | 3 +++
 drivers/power/supply/power_supply_sysfs.c | 6 ------
 2 files changed, 3 insertions(+), 6 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2019-05-01 21:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 21:26 Sebastian Reichel [this message]
2019-05-01 22:10 ` [GIT PULL] power-supply changes for 5.1 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2019-03-05 22:04 Sebastian Reichel
2019-03-08 18:35 ` pr-tracker-bot

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190501212610.5qrl7gyttdyzs2dq@earth.universe \ \ \ \ \

* 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.