LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Marc St-Jean <Marc_St-Jean@pmc-sierra.com> To: Andrew Morton <akpm@linux-foundation.org> Cc: Marc St-Jean <stjeanma@pmc-sierra.com>, linux-kernel@vger.kernel.org, linux-mips@linux-mips.org Subject: Re: [PATCH] drivers: PMC MSP71xx GPIO char driver Date: Wed, 7 Mar 2007 15:47:26 -0800 [thread overview] Message-ID: <45EF4F0E.50303@pmc-sierra.com> (raw) Andrew Morton wrote: > > On Fri, 23 Feb 2007 17:28:19 -0600 Marc St-Jean > <stjeanma@pmc-sierra.com> wrote: > > [PATCH] drivers: PMC MSP71xx GPIO char driver > > > > Patch to add a GPIO char driver for the PMC-Sierra > > MSP71xx devices. > > > > This patch references some platform support files previously > > submitted to the linux-mips@linux-mips.org list. > > Thanks for the feedback Andrew. I've implemented all your recommendations other than the kernel thread handling, which I still have to look into. [...] > > > +/* -- Module functions -- */ > > + > > +static int msp_gpio_blinkthread( void *none ) > > Why is this a "module function"? The reason is likely because it's only called by msp_gpio_init so it was considered part of the module code. I'll move the comment to only cover msp_gpio_init/exit. [...] > > +module_init(msp_gpio_init); > > +module_exit(msp_gpio_exit); > > + > > +EXPORT_SYMBOL(msp_gpio_in); > > +EXPORT_SYMBOL(msp_gpio_out); > > +EXPORT_SYMBOL(msp_gpio_mode); > > +EXPORT_SYMBOL(msp_gpio_blink); > > +EXPORT_SYMBOL(msp_gpio_noblink); > > What uses these exports? These exports are needed for other drivers compiled as modules can control the GPIO pins through this driver. [...] Marc
next reply other threads:[~2007-03-07 23:47 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-07 23:47 Marc St-Jean [this message] -- strict thread matches above, loose matches on Subject: below -- 2007-03-08 20:18 [PATCH] drivers: PMC MSP71xx GPIO char driver Marc St-Jean 2007-02-23 23:28 Marc St-Jean 2007-02-27 20:26 ` Andrew Morton
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=45EF4F0E.50303@pmc-sierra.com \ --to=marc_st-jean@pmc-sierra.com \ --cc=akpm@linux-foundation.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mips@linux-mips.org \ --cc=stjeanma@pmc-sierra.com \ /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: linkBe 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; as well as URLs for NNTP newsgroup(s).