LKML Archive on
help / color / mirror / Atom feed
From: Hareesh Gundu <>
To: Peter Zijlstra <>
Cc: Linus Torvalds <>,
	Steven Rostedt <>,, Mel Gorman <>,,,
Subject: Re: [PATCH] lib/plist.c: Export plist_*() APIs
Date: Wed, 30 May 2018 17:55:05 +0530	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 12/6/2017 9:29 PM, Peter Zijlstra wrote:
> On Wed, Dec 06, 2017 at 08:59:27PM +0530, Hareesh Gundu wrote:
>> On 12/5/2017 8:11 PM, Peter Zijlstra wrote:
>>> On Tue, Dec 05, 2017 at 08:05:43PM +0530, Hareesh Gundu wrote:
>>>> Allow plist_add(), plist_del() and plist_requeue() APIs to
>>>> be referenced by kernel modules by adding the EXPORT_SYMBOL().
>> This change is not for in-tree kernel module. It's for modules built outside
>> of kernel tree modules.
>> Is it really required to show out tree kernel modules ?
> Typically we don't add EXPORTs for functions not used in in-tree
> modules.
We changed our design and planned to have our module in-tree kernel 
instead of out tree kernel module.
Below is the reference for in-tree kernel module proposal for 
"drviers/gpu/msm" which is referring to plist_* symbols.

Could you please revisit the patch and approve for upstream.

  reply	other threads:[~2018-05-30 12:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 14:35 Hareesh Gundu
2017-12-05 14:41 ` Peter Zijlstra
2017-12-06 15:29   ` Hareesh Gundu
2017-12-06 15:59     ` Peter Zijlstra
2018-05-30 12:25       ` Hareesh Gundu [this message]
2018-05-30 14:12         ` Peter Zijlstra

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:

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

  git send-email \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] lib/plist.c: Export plist_*() APIs' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).