From: biju.das@bp.renesas.com (Biju Das)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Linux 4.4.126-cip22
Date: Mon, 30 Apr 2018 10:18:33 +0000 [thread overview]
Message-ID: <OSBPR01MB21030BA75D24294F1D731CC5B8820@OSBPR01MB2103.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <TYAPR01MB228513B0546B4029878033C9B7820@TYAPR01MB2285.jpnprd01.prod.outlook.com>
Hi Daniel,
We are trying to figure out the kernel defconfig used for this build error.
>From the logs you have provided, I am not able to locate "CONFIG_SERIAL_SH_SCI=m" in any of cip kernel config file for x86 (branch:-v4.4.126-cip22).
We planned to enable some more kernel-config option in shmobile defconfig (for eg:- CAN,SGTL5000 etc..) in future.
We would like to avoid the build error like the below one in future. So can you please help us in locating the defconfig file?
Regards,
Biju
> -----Original Message-----
> From: cip-dev-bounces at lists.cip-project.org [mailto:cip-dev-
> bounces at lists.cip-project.org] On Behalf Of Daniel Wagner
> Sent: 27 April 2018 12:24
> To: Ben Hutchings <ben.hutchings@codethink.co.uk>
> Cc: cip-dev at lists.cip-project.org
> Subject: Re: [cip-dev] Linux 4.4.126-cip22
>
> Hi Ben,
>
> On 04/11/2018 10:10 PM, Ben Hutchings wrote:
> > On Wed, 2018-04-11 at 20:54 +0100, Ben Hutchings wrote:
> > [...]
> >> I also tagged an intermediate version 4.4.120-cip21 before merging
> >> from 4.4-stable.
> >
> > Sorry, that intermediate version was actually 4.4.126-cip21. It
> > includes the stable changes but not the improvements to Renesas
> > hardware support that are in -cip22.
>
> While working on the cip-rt spin I got following error from our ci build
> server:
>
> Errors:
> -------
> all annotations:
> ~~~~~~~~~~~~~~~~
> ERROR: "mctrl_gpio_disable_ms" [drivers/tty/serial/sh-sci.ko] undefined!
>
> ERROR: "mctrl_gpio_init" [drivers/tty/serial/sh-sci.ko] undefined!
>
>
> I think this was introduced by 8bac17a7f510 ("serial: sh-sci: Add support for
> GPIO-controlled modem lines"). serial_mcrtl_gpio.h provides for GPIOLIB
> and !GPIOLIB an implementation.
>
> I am slightly confused, though I haven't spend a lot of time yet to figure out
> what's going on.
>
> Thanks,
> Daniel
Renesas Electronics Europe Ltd, Dukes Meadow, Millboard Road, Bourne End, Buckinghamshire, SL8 5FH, UK. Registered in England & Wales under Registered No. 04586709.
next prev parent reply other threads:[~2018-04-30 10:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 19:54 [cip-dev] Linux 4.4.126-cip22 Ben Hutchings
2018-04-11 20:10 ` Ben Hutchings
2018-04-27 11:23 ` Daniel Wagner
2018-04-27 11:33 ` Daniel Wagner
2018-04-27 12:10 ` Daniel Wagner
2018-04-27 13:29 ` Daniel Wagner
2018-05-04 14:55 ` Ben Hutchings
[not found] ` <TYAPR01MB228513B0546B4029878033C9B7820@TYAPR01MB2285.jpnprd01.prod.outlook.com>
2018-04-30 10:18 ` Biju Das [this message]
2018-05-02 6:35 ` Daniel Wagner
2018-05-02 11:57 ` Biju Das
2018-05-02 13:17 ` Daniel Wagner
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=OSBPR01MB21030BA75D24294F1D731CC5B8820@OSBPR01MB2103.jpnprd01.prod.outlook.com \
--to=biju.das@bp.renesas.com \
--cc=cip-dev@lists.cip-project.org \
/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.