netdev - Re: [PATCH v3] net: fec: Do a sanity check on the gpio number

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:	Mon, 18 Feb 2013 16:51:49 -0300
From:	Fabio Estevam <festevam@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	s.hauer@...gutronix.de, shawn.guo@...aro.org, marex@...x.de,
	netdev@...r.kernel.org, fabio.estevam@...escale.com
Subject: Re: [PATCH v3] net: fec: Do a sanity check on the gpio number

On Mon, Feb 18, 2013 at 4:47 PM, David Miller <davem@...emloft.net> wrote:
> From: Fabio Estevam <festevam@...il.com>
> Date: Sun, 17 Feb 2013 12:29:24 -0300
>
>> Since commit 372e722ea4d (gpiolib: use descriptors internally) the following
>> warning is seen on a mx28evk board:
>
> [davem@drr linux]$ git describe 372e722ea4d
> fatal: Not a valid object name 372e722ea4d
> [davem@drr linux]$
>
> That commit ID doesn't exist in any tree I have access to.

It exists in linux-next.

Anyway, even without this commit the gpio validation should be done.

> I'm not applying this.

Ok, would you apply it if I remove the mention to 372e722ea4d from the
commit log?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html