linux-kernel - Re: [PATCH] gpiolib: export gpiochip

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]

Message-ID: <20110420145207.0e24e50d@endymion.delvare>
Date:	Wed, 20 Apr 2011 14:52:07 +0200
From:	Jean Delvare <khali@...ux-fr.org>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gpiolib: export gpiochip_find

Hi Grant,

On Sat, 16 Apr 2011 09:30:15 +0200, Jean Delvare wrote:
> Export function gpiochip_find so that modules can use it.

Any problem with this patch? If not, the earlier it gets upstream, the
happier I'll be. I think it should even be considered for stable kernel
series.

Thanks.

> Signed-off-by: Jean Delvare <khali@...ux-fr.org>
> Cc: Grant Likely <grant.likely@...retlab.ca>
> ---
> I need this to add support for SMBus multiplexing on my Asus Z8NA-D6
> board.
> 
>  drivers/gpio/gpiolib.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> --- linux-2.6.39-rc3.orig/drivers/gpio/gpiolib.c	2011-03-30 10:57:19.000000000 +0200
> +++ linux-2.6.39-rc3/drivers/gpio/gpiolib.c	2011-04-16 09:00:25.000000000 +0200
> @@ -1165,6 +1165,7 @@ struct gpio_chip *gpiochip_find(void *da
>  
>  	return chip;
>  }
> +EXPORT_SYMBOL_GPL(gpiochip_find);
>  
>  /* These "optional" allocation calls help prevent drivers from stomping
>   * on each other, and help provide better diagnostics in debugfs.
> 

-- 
Jean Delvare
--
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/