From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH v1] libata: export ata_get_cmd_descript()
Date: Fri, 12 Dec 2014 19:35:47 +0200 [thread overview]
Message-ID: <1418405747.17201.64.camel@linux.intel.com> (raw)
In-Reply-To: <548B2524.9050806@cogentembedded.com>
On Fri, 2014-12-12 at 20:25 +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 12/12/2014 06:16 PM, Andy Shevchenko wrote:
>
> > The driver sata_dwc_460ex is using this symbol. To build it as a module we have
> > to have the symbol exported. This patch adds EXPORT_SYMBOL() macro for that.
>
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> > ---
> > drivers/ata/libata-eh.c | 1 +
> > 1 file changed, 1 insertion(+)
>
> > diff --git a/drivers/ata/libata-eh.c b/drivers/ata/libata-eh.c
> > index 3dbec89..74fef87 100644
> > --- a/drivers/ata/libata-eh.c
> > +++ b/drivers/ata/libata-eh.c
> > @@ -2389,6 +2389,7 @@ const char *ata_get_cmd_descript(u8 command)
> >
> > return NULL;
> > }
> > +EXPORT_SYMBOL(ata_get_cmd_descript);
>
> Why not EXPORT_SYMBOL_GPL()?
Some of the symbols are exported in that way. I think better to wait the
maintainer to tell which is preferred there.
>
> MBR, Sergei
>
--
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy
next prev parent reply other threads:[~2014-12-12 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 15:16 [PATCH v1] libata: export ata_get_cmd_descript() Andy Shevchenko
2014-12-12 17:25 ` Sergei Shtylyov
2014-12-12 17:35 ` Andy Shevchenko [this message]
2015-01-05 16:21 ` Tejun Heo
2015-01-05 17:44 ` Andy Shevchenko
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=1418405747.17201.64.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).