From: Steven Rostedt <rostedt@goodmis.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org,
Piotr Maziarz <piotrx.maziarz@linux.intel.com>,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
Vaibhav Jain <vaibhav@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v7 2/5] seq_buf: Export seq_buf_printf() to external modules
Date: Fri, 8 May 2020 12:27:03 -0400 [thread overview]
Message-ID: <20200508122703.6ee5cae0@gandalf.local.home> (raw)
In-Reply-To: <20200508160935.GB19436@zn.tnic>
On Fri, 8 May 2020 18:09:35 +0200
Borislav Petkov <bp@alien8.de> wrote:
> On Fri, May 08, 2020 at 05:30:31PM +0530, Vaibhav Jain wrote:
> > I am referring to Kernel Loadable Modules with MODULE_LICENSE("GPL")
> > here.
>
> And what does "external" refer to? Because if it is out-of-tree, we
> don't export symbols for out-of-tree modules.
I've always wondered about this. Why not?
-- Steve
next prev parent reply other threads:[~2020-05-08 17:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 10:49 [PATCH v7 0/5] powerpc/papr_scm: Add support for reporting nvdimm health Vaibhav Jain
2020-05-08 10:49 ` [PATCH v7 1/5] powerpc: Document details on H_SCM_HEALTH hcall Vaibhav Jain
2020-05-08 10:49 ` [PATCH v7 2/5] seq_buf: Export seq_buf_printf() to external modules Vaibhav Jain
2020-05-08 11:31 ` Borislav Petkov
2020-05-08 12:00 ` Vaibhav Jain
2020-05-08 14:52 ` Joe Perches
2020-05-10 12:57 ` Vaibhav Jain
2020-05-08 16:09 ` Borislav Petkov
2020-05-08 16:27 ` Steven Rostedt [this message]
2020-05-10 13:03 ` Vaibhav Jain
2020-05-08 13:44 ` Michael Ellerman
2020-05-10 13:08 ` Vaibhav Jain
2020-05-08 10:49 ` [PATCH v7 3/5] powerpc/papr_scm: Fetch nvdimm health information from PHYP Vaibhav Jain
2020-05-08 10:49 ` [PATCH v7 4/5] ndctl/papr_scm, uapi: Add support for PAPR nvdimm specific methods Vaibhav Jain
2020-05-08 10:49 ` [PATCH v7 5/5] powerpc/papr_scm: Implement support for PAPR_SCM_PDSM_HEALTH Vaibhav Jain
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=20200508122703.6ee5cae0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bp@alien8.de \
--cc=cezary.rojewski@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=piotrx.maziarz@linux.intel.com \
--cc=vaibhav@linux.ibm.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: 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).