From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Xu Yilun <yilun.xu@intel.com>
Cc: Wu Hao <hao.wu@intel.com>, Tom Rix <trix@redhat.com>,
Moritz Fischer <mdf@kernel.org>,
linux-fpga@vger.kernel.org, Lee Jones <lee@kernel.org>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
linux-hwmon@vger.kernel.org,
Russ Weight <russell.h.weight@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/4] mfd: intel-m10-bmc: Move core symbols to own namespace
Date: Tue, 11 Apr 2023 14:40:33 +0300 (EEST) [thread overview]
Message-ID: <a67058bc-8265-add0-3b89-8ee310e871b6@linux.intel.com> (raw)
In-Reply-To: <ZC+3msi6ovoF55tr@yilunxu-OptiPlex-7050>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
On Fri, 7 Apr 2023, Xu Yilun wrote:
> On 2023-04-05 at 11:01:49 +0300, Ilpo Järvinen wrote:
> > Create INTEL_M10_BMC_CORE namespace for symbols exported by
> > intel-m10-bmc-core.
>
> Is it necessary for handshake register, or just an independent
> improvement?
It's independent improvement.
> > Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > ---
> > drivers/mfd/intel-m10-bmc-core.c | 2 +-
> > drivers/mfd/intel-m10-bmc-pmci.c | 1 +
> > drivers/mfd/intel-m10-bmc-spi.c | 1 +
> > 3 files changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/mfd/intel-m10-bmc-core.c b/drivers/mfd/intel-m10-bmc-core.c
> > index dac9cf7bcb4a..b94412813887 100644
> > --- a/drivers/mfd/intel-m10-bmc-core.c
> > +++ b/drivers/mfd/intel-m10-bmc-core.c
> > @@ -98,7 +98,7 @@ const struct attribute_group *m10bmc_dev_groups[] = {
> > &m10bmc_group,
> > NULL,
> > };
> > -EXPORT_SYMBOL_GPL(m10bmc_dev_groups);
> > +EXPORT_SYMBOL_NS_GPL(m10bmc_dev_groups, INTEL_M10_BMC_CORE);
> >
> > int m10bmc_dev_init(struct intel_m10bmc *m10bmc, const struct intel_m10bmc_platform_info *info)
>
> Why this function is not included in namespace?
It was not left out on purpose, I'll add it there.
--
i.
next prev parent reply other threads:[~2023-04-11 11:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 8:01 [PATCH 0/4] Manage register access to control delay during sec update Ilpo Järvinen
2023-04-05 8:01 ` [PATCH 1/4] mfd: intel-m10-bmc: Move core symbols to own namespace Ilpo Järvinen
2023-04-05 18:38 ` Russ Weight
2023-04-07 6:26 ` Xu Yilun
2023-04-11 11:40 ` Ilpo Järvinen [this message]
2023-04-05 8:01 ` [PATCH 2/4] mfd: intel-m10-bmc: Create m10bmc_sys_update_bits() Ilpo Järvinen
2023-04-05 8:01 ` [PATCH 3/4] mfd: intel-m10-bmc: Move m10bmc_sys_read() away from header Ilpo Järvinen
2023-04-05 12:43 ` Guenter Roeck
2023-04-05 18:40 ` Russ Weight
2023-04-05 8:01 ` [PATCH 4/4] mfd: intel-m10-bmc: Manage access to MAX 10 fw handshake registers Ilpo Järvinen
2023-04-07 6:10 ` Xu Yilun
2023-04-11 11:45 ` Ilpo Järvinen
2023-04-07 6:18 ` Xu Yilun
2023-04-11 11:54 ` Ilpo Järvinen
2023-04-14 11:45 ` Xu Yilun
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=a67058bc-8265-add0-3b89-8ee310e871b6@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hao.wu@intel.com \
--cc=jdelvare@suse.com \
--cc=lee@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mdf@kernel.org \
--cc=russell.h.weight@intel.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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
all inboxes | Powered by JetHome®