linux-kernel - Re: [PATCH] staging:iio:proof of concept in kernel interface.

lists.openwall.net		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 linux-cve-announce 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 Oct 2011 21:44:10 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Jonathan Cameron <jic23@....ac.uk>
Cc:	linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
	zdevai@...il.com, linus.walleij@...aro.org
Subject: Re: [PATCH] staging:iio:proof of concept in kernel interface.

On Thu, Oct 13, 2011 at 03:46:04PM +0100, Jonathan Cameron wrote:

> > I guess an actual implementation would have wrappers for doing the
> > indirections rather than having users peer into the ops table directly?

> Yup, for some reason the cover letter seems to have detached from this.
> It suggested exactly that.  There may be weird cases where peering this
> deep into the ops makes sense, but not for something like this one.

Oh, right.  As a general rule I don't read cover letters for single
patches until after I've read the patch, generally they're either
completely content free (if only by virtue of repeating the changelog)
or there's a problem with the changelog in the actual patch not
explaining what's going on.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/