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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 14 Feb 2014 10:59:08 +0000
From:	Laszlo Papp <>
To:	Lee Jones <>
Cc:	Mark Brown <>,
	Linus Walleij <>,
	LKML <>,
	Krzysztof Kozlowski <>,
	Sachin Kamat <>,
	Jean Delvare <>,
	Guenter Roeck <>
Subject: Re: [PATCH v6] mfd: MAX6650/6651 support

On Fri, Feb 14, 2014 at 10:19 AM, Lee Jones <> wrote:
>> >> +     mutex_init(&max665x->iolock);
>> >
>> > What is this needed for?
>> It was done for consistency with the other mfd drivers (maxim), e.g.
>> 8997 or 8998 as the closest resemblence in this family. Would you
>> prefer me removing this mutex locker?
> If you're not using mutexes, why would you need to initialise it?

Yeah, I had the same thought about an hour ago that this sneaked in
because I was not originally using regmap, but now with the regmap
usage, it is just a left-over. So, it is not even for consistency
anymore. I was wrong claiming that.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists