[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161205210951.79e54ba5@lxorguk.ukuu.org.uk>
Date: Mon, 5 Dec 2016 21:09:51 +0000
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: David Howells <dhowells@...hat.com>
Cc: Jean Delvare <jdelvare@...e.de>, minyard@....org,
linux-kernel@...r.kernel.org, Wolfram Sang <wsa@...-dreams.de>,
linux-security-module@...r.kernel.org, keyrings@...r.kernel.org,
linux-i2c@...r.kernel.org
Subject: Re: [PATCH 09/39] Annotate hardware config module parameters in
drivers/i2c/
O> > > Suggested-by: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
> >
> > I know this is only a Suggested-by and not a Signed-off-by, but still I
> > believe the Developer's Certificate of Origin applies, and it says:
> > "using your real name (sorry, no pseudonyms or anonymous
> > contributions.)"
>
> I asked him what he prefers - but no response.
I didn't see that question but "Alan Cox" is probably saner - the
thousand gnomes is an old Linus joke 8)
> > i2c-piix4.c:module_param (force, int, 0);
> > i2c-sis630.c:module_param(force, bool, 0);
> > i2c-viapro.c:module_param(force, bool, 0);
>
> I don't know either. One could argue it *should* be locked down because its
> need appears to reflect a BIOS bug.
And none of those should show up in that usage form on a box new enough
to have EFI secure boot. Those that do have i2c busses will report them
via ACPI by that period.
Alan
Powered by blists - more mailing lists