lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 31 May 2020 16:06:11 +0200
From:   Markus Elfring <>
To:     Dinghao Liu <>,
        Linus Walleij <>,
        Hartmut Knaack <>,
        Jonathan Cameron <>, Kangjie Lu <>,
        Lars-Peter Clausen <>,
        Peter Meerwald-Stadler <>
Subject: Re: [PATCH v2] iio: magnetometer: ak8974: Fix runtime PM imbalance on
 error in ak8974_probe()

> When devm_regmap_init_i2c() returns an error code, a pairing
> runtime PM usage counter decrement is needed to keep the
> counter balanced.

How do you think about to replace the word “pairing” by “corresponding”?

> For error paths after ak8974_set_power(),
> ak8974_detect() and ak8974_reset(), things are the same.

Will an other wording become more helpful than this information?

> However, When iio_triggered_buffer_setup() returns an error
> code, there will be two PM usgae counter decrements.

Please avoid two typos in this sentence.

Would you like to add the tag “Fixes” to the commit message?

+++ b/drivers/iio/magnetometer/ak8974.c
@@ -854,7 +856,6 @@  static int ak8974_probe(struct i2c_client *i2c,

Can a source code variant like the following make sense
for a more complete exception handling?

	ak8974_set_power(ak8974, AK8974_PWR_OFF);
	regulator_bulk_disable(ARRAY_SIZE(ak8974->regs), ak8974->regs);
	return ret;


Powered by blists - more mailing lists