From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Request for guidance: removal of old config files [was: Kernel configurations for 4.19?]
Date: Fri, 12 Jul 2019 17:34:47 +0100 [thread overview]
Message-ID: <fae9b423882c15f5e31eaef237086f38055dcfce.camel@codethink.co.uk> (raw)
In-Reply-To: <909b4353-87c9-08e2-46f1-4ef8ce3fb6d2@siemens.com>
On Thu, 2019-07-11 at 18:51 +0200, Jan Kiszka wrote:
[...]
> > 4.19/arm/hitachi_omap_defconfig
> > 4.19/arm/moxa_mxc_defconfig
> > 4.19/arm/siemens_am335x-axm2_defconfig
> > 4.19/arm/siemens_am335x-draco_defconfig
> > 4.19/arm/siemens_am335x-dxr2_defconfig
> > 4.19/arm/siemens_am335x-etamin_defconfig
> > 4.19/arm/siemens_am57xx-pxm3_defconfig
>
> Those can go, I'm not aware of their usage on 4.19. But do we have one for the
> am335-x-based BBB, our reference board?
Good point. I have not yet tried running 4.19 on the BBB, but I can
look at adding one - or perhaps Nobuhiro or Pavel already has a
suitable config?
> > 4.19/arm/toshiba_tegra_defconfig
> > 4.19/arm/toshiba_zynq_defconfig
> > 4.19/powerpc/toshiba_defconfig
> > 4.19/x86/plathome_obsvx1.config
> > 4.19/x86/siemens_i386-rt.config
>
> I do not recall the history of that one anymore. We should have at least one -rt
> config for x86 somewhere.
Yes, and also the build rules should check out -rt branches instead of
the main CIP branches when processing an -rt configuration.
> > 4.19/x86/siemens_iot2000.config
> > 4.19/x86/siemens_server_defconfig
>
> Those two should stay.
But they need to be reviewed, as automatic config updates usually don't
cope with renaming of config symbols.
Ben.
> > 4.19/x86/toshiba_defconfig
> >
> > Ben.
>
> Thanks,
> Jan
>
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
next prev parent reply other threads:[~2019-07-12 16:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 11:53 [cip-dev] Kernel configurations for 4.19? Ben Hutchings
2019-04-19 6:03 ` daniel.sangorrin at toshiba.co.jp
2019-05-22 8:57 ` daniel.sangorrin at toshiba.co.jp
2019-05-09 10:11 ` Chris Paterson
2019-06-12 0:12 ` Masato Minda
2019-06-16 21:49 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-07-09 13:49 ` Ben Hutchings
2019-07-09 14:40 ` Ben Hutchings
2019-07-12 0:57 ` daniel.sangorrin at toshiba.co.jp
[not found] ` <7c8d175eaa43357d6484c6fee89c4d0f@codethink.co.uk>
[not found] ` <909b4353-87c9-08e2-46f1-4ef8ce3fb6d2@siemens.com>
2019-07-12 16:34 ` Ben Hutchings [this message]
2019-07-14 22:42 ` [cip-dev] Request for guidance: removal of old config files [was: Kernel configurations for 4.19?] nobuhiro1.iwamatsu at toshiba.co.jp
2019-07-21 16:25 ` Pavel Machek
2019-07-21 17:58 ` Zoran S
2019-07-21 18:28 ` Pavel Machek
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=fae9b423882c15f5e31eaef237086f38055dcfce.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox