From: Randy Dunlap <rdunlap@infradead.org>
To: Nick Crews <ncrews@chromium.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Duncan Laurie <dlaurie@chromium.org>
Subject: Re: linux-next: Tree for Feb 12 (chrome/wilco_ec/)
Date: Tue, 12 Feb 2019 15:31:58 -0800 [thread overview]
Message-ID: <341fc51d-aa50-6f8e-1c03-e6a0edfe4905@infradead.org> (raw)
In-Reply-To: <CAHX4x87=Myx45wBYtFY=rwz8jVmYY-tYVQjnzod-V8HaWJSy+g@mail.gmail.com>
On 2/12/19 3:26 PM, Nick Crews wrote:
> Hi Randy,
>
> This looks like we have a bad dependency structure in our Kconfig. I'll figure it out, and then where should I send the patch?
AFAICT, all drivers/platform/chrome/ patches go to its maintainers (& to
linux-kernel@vger.kernel.org):
CHROME HARDWARE PLATFORM SUPPORT
M: Benson Leung <bleung@chromium.org>
M: Enric Balletbo i Serra <enric.balletbo@collabora.com>
S: Maintained
T: git git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git
F: drivers/platform/chrome/
> Nick
>
> On Tue, Feb 12, 2019 at 9:44 AM Randy Dunlap <rdunlap@infradead.org <mailto:rdunlap@infradead.org>> wrote:
>
> On 2/11/19 10:50 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20190211:
> >
>
>
> on i386 or x86_64:
>
> ld: drivers/platform/chrome/wilco_ec/core.o: in function `wilco_ec_remove':
> core.c:(.text+0x46): undefined reference to `cros_ec_lpc_mec_destroy'
> ld: drivers/platform/chrome/wilco_ec/core.o: in function `wilco_ec_probe':
> core.c:(.text+0x285): undefined reference to `cros_ec_lpc_mec_init'
> ld: core.c:(.text+0x39a): undefined reference to `cros_ec_lpc_mec_destroy'
> ld: drivers/platform/chrome/wilco_ec/mailbox.o: in function `wilco_ec_transfer':
> mailbox.c:(.text+0x26): undefined reference to `cros_ec_lpc_io_bytes_mec'
> ld: mailbox.c:(.text+0x47): undefined reference to `cros_ec_lpc_io_bytes_mec'
> ld: mailbox.c:(.text+0x242): undefined reference to `cros_ec_lpc_io_bytes_mec'
>
>
> Full randconfig file is attached.
>
> --
> ~Randy
>
--
~Randy
next prev parent reply other threads:[~2019-02-12 23:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 6:50 linux-next: Tree for Feb 12 Stephen Rothwell
2019-02-12 16:44 ` linux-next: Tree for Feb 12 (chrome/wilco_ec/) Randy Dunlap
[not found] ` <CAHX4x87=Myx45wBYtFY=rwz8jVmYY-tYVQjnzod-V8HaWJSy+g@mail.gmail.com>
2019-02-12 23:31 ` Randy Dunlap [this message]
[not found] ` <CAHX4x87nRpTR5880y6hc=r7k0OFV9YKate21U=2kkqC-ihdmCQ@mail.gmail.com>
2019-02-13 0:04 ` Randy Dunlap
2019-02-13 0:13 ` Randy Dunlap
2019-02-13 17:26 ` Nick Crews
2019-02-13 21:29 ` Randy Dunlap
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=341fc51d-aa50-6f8e-1c03-e6a0edfe4905@infradead.org \
--to=rdunlap@infradead.org \
--cc=dlaurie@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ncrews@chromium.org \
--cc=sfr@canb.auug.org.au \
/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).