The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] gpiolib: export gpiochip_find
Date: Fri, 13 May 2011 10:52:20 +0200	[thread overview]
Message-ID: <20110513105220.4b61a5be@endymion.delvare> (raw)
In-Reply-To: <20110416093015.3befd780@endymion.delvare>

Hi Grant,

On Sat, 16 Apr 2011 09:30:15 +0200, Jean Delvare wrote:
> Export function gpiochip_find so that modules can use it.
> 
> Signed-off-by: Jean Delvare <khali@linux-fr.org>
> Cc: Grant Likely <grant.likely@secretlab.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.

I am sorry to insist, but this patch seems quite straightforward, it
shouldn't take long to review. Do you have any problem with it? If not,
please apply it. I really would like to have it in kernel 2.6.40, as
the rest of my SMBus multiplexing support effort depends on it.

Thanks,
-- 
Jean Delvare

  parent reply	other threads:[~2011-05-13  8:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-16  7:30 [PATCH] gpiolib: export gpiochip_find Jean Delvare
2011-04-20 12:52 ` Jean Delvare
2011-05-13  8:52 ` Jean Delvare [this message]
2011-05-15 21:35   ` Grant Likely
2011-05-16  7:34     ` Jean Delvare

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110513105220.4b61a5be@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=akpm@linux-foundation.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox