From: "최동혁/DONGHYEOK CHOE" <d7271.choe@samsung.com>
To: "'Will Deacon'" <will@kernel.org>
Cc: changki.kim@samsung.com, linux-kernel@vger.kernel.org,
youngmin.nam@samsung.com, hosung0.kim@samsung.com,
hajun.sung@samsung.com, gregkh@google.com,
linux-arm-kernel@lists.infradead.org
Subject: RE: Reqeust export symbol for API in arch/arm64/*
Date: Wed, 6 May 2020 22:05:56 +0900 [thread overview]
Message-ID: <000001d623a7$14bc6590$3e3530b0$@samsung.com> (raw)
In-Reply-To: <20200506125315.GH8043@willie-the-truck>
> -----Original Message-----
> From: Will Deacon <will@kernel.org>
> Sent: Wednesday, May 6, 2020 9:53 PM
> To: �ֵ���/DONGHYEOK CHOE <d7271.choe@samsung.com>
> Cc: linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> hosung0.kim@samsung.com; changki.kim@samsung.com; hajun.sung@samsung.com;
> gregkh@google.com; youngmin.nam@samsung.com
> Subject: Re: Reqeust export symbol for API in arch/arm64/*
>
> On Wed, May 06, 2020 at 09:46:45PM +0900, ֵ /DONGHYEOK CHOE wrote:
> > I am software engineer in charge of BSP (Samsung SOC vendor).
> >
> > Recently, Google introduced GKI from Android R version.
> > We cannot use mainline API without 'export symbol' by the GKI policy.
> > But we want to make an arm64 specific vendor driver in {kernel source
> > root}/drivers/soc/samsung/*.
> >
> > Could you support us to use the below APIs?
>
> Sorry, but as a general rule of thumb the kernel doesn't EXPORT symbols
> that are not used by in-tree modules. You'll need to submit your drivers
> along with the patches doing the exports if they are to be considered for
> inclusion.
>
> Thanks,
>
> Will
Thank you for your quick response.
I'll try.
Thanks
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "최동혁/DONGHYEOK CHOE" <d7271.choe@samsung.com>
To: "'Will Deacon'" <will@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <hosung0.kim@samsung.com>,
<changki.kim@samsung.com>, <hajun.sung@samsung.com>,
<gregkh@google.com>, <youngmin.nam@samsung.com>
Subject: RE: Reqeust export symbol for API in arch/arm64/*
Date: Wed, 6 May 2020 22:05:56 +0900 [thread overview]
Message-ID: <000001d623a7$14bc6590$3e3530b0$@samsung.com> (raw)
In-Reply-To: <20200506125315.GH8043@willie-the-truck>
> -----Original Message-----
> From: Will Deacon <will@kernel.org>
> Sent: Wednesday, May 6, 2020 9:53 PM
> To: �ֵ���/DONGHYEOK CHOE <d7271.choe@samsung.com>
> Cc: linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
> hosung0.kim@samsung.com; changki.kim@samsung.com; hajun.sung@samsung.com;
> gregkh@google.com; youngmin.nam@samsung.com
> Subject: Re: Reqeust export symbol for API in arch/arm64/*
>
> On Wed, May 06, 2020 at 09:46:45PM +0900, ֵ /DONGHYEOK CHOE wrote:
> > I am software engineer in charge of BSP (Samsung SOC vendor).
> >
> > Recently, Google introduced GKI from Android R version.
> > We cannot use mainline API without 'export symbol' by the GKI policy.
> > But we want to make an arm64 specific vendor driver in {kernel source
> > root}/drivers/soc/samsung/*.
> >
> > Could you support us to use the below APIs?
>
> Sorry, but as a general rule of thumb the kernel doesn't EXPORT symbols
> that are not used by in-tree modules. You'll need to submit your drivers
> along with the patches doing the exports if they are to be considered for
> inclusion.
>
> Thanks,
>
> Will
Thank you for your quick response.
I'll try.
Thanks
next prev parent reply other threads:[~2020-05-06 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200506124645epcas2p25a8efbe59fa20194e19d642227dd47ae@epcas2p2.samsung.com>
2020-05-06 12:46 ` Reqeust export symbol for API in arch/arm64/* 최동혁/DONGHYEOK CHOE
2020-05-06 12:53 ` Will Deacon
2020-05-06 12:53 ` Will Deacon
2020-05-06 13:05 ` 최동혁/DONGHYEOK CHOE [this message]
2020-05-06 13:05 ` 최동혁/DONGHYEOK CHOE
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='000001d623a7$14bc6590$3e3530b0$@samsung.com' \
--to=d7271.choe@samsung.com \
--cc=changki.kim@samsung.com \
--cc=gregkh@google.com \
--cc=hajun.sung@samsung.com \
--cc=hosung0.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will@kernel.org \
--cc=youngmin.nam@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.