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:	Thu, 13 Feb 2014 10:34:31 +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 Thu, Feb 13, 2014 at 9:14 AM, Laszlo Papp <> wrote:
> On Thu, Feb 13, 2014 at 8:23 AM, Lee Jones <> wrote:
>> Laszlo,
>>> > +const struct regmap_config max665x_regmap_config = {
>>> > +   .reg_bits = 5,
>>> > +};
>>> This would normally be static too, and I'd *really* expect to see a
>>> val_bits set here.  I'm a bit surprised this works without one.
>> Mark (privately) mentioned to me that this patch can't possibly work
>> given the current Regmap configuration.
> Strange because I have tested the change, although not for days and
> weeks. What exactly cannot possible work?

Hmm, yes, as it seems, I have not actually tested the patch set
_after_ all the modifications. I deemed some of them trivial enough,
but apparently I was wrong. In this case, sending trivial updates will
slow down, but I guess that is the way to follow. Well, I apologize.
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