cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Pavel Machek" <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Cc: Pavel Machek <pavel@denx.de>
Subject: Re: Starting testing of 5.10-stable? was Re: [cip-dev] Testing of -stable-rc fails completely
Date: Mon, 4 Jan 2021 13:15:16 +0100	[thread overview]
Message-ID: <20210104121516.GA11126@duo.ucw.cz> (raw)
In-Reply-To: <OSAPR01MB2385B98A7415E26F2FECE904B7D20@OSAPR01MB2385.jpnprd01.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 1370 bytes --]

Hi!

> > From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> > Behalf Of Pavel Machek via lists.cip-project.org
> > Sent: 30 December 2020 12:46
> >
> 
> [...]
> 
> >
> > Now... I believe we should start testing 5.10-stable trees, as we want
> > to maintain that tree "soon" it would be good to know how we are
> > doing...
> >
> > I guess it will need some configs.
> 
> I can use some generic defconfigs to start if you like.
> But yes, ideally we need CIP configs added to cip-kernel-config.
> Perhaps an email needs to go to cip-members for this?

Starting some testing would be good; defconfigs would work. We'll need
to notify cip-members, but I assume actual replies from members will
need some time. 

> > I believe we could just take 4.19 configs for a start.
> That's one option, assuming that all relevant platforms are supported in v5.10.

They should be, thanks to our upstream-first policy.

If it helps, I believe we can create symlinks in cip-kernel-config
repository for now, so you could point testing at 5.10.y
configurations, and we would have opportunity to replace configs with
final ones as they become available.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5992): https://lists.cip-project.org/g/cip-dev/message/5992
Mute This Topic: https://lists.cip-project.org/mt/79311303/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


      reply	other threads:[~2021-01-04 12:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29  8:53 [cip-dev] Testing of -stable-rc fails completely Pavel Machek
2020-12-29 21:27 ` Chris Paterson
2020-12-30 12:45   ` Starting testing of 5.10-stable? was " Pavel Machek
2021-01-04 10:48     ` Chris Paterson
2021-01-04 12:15       ` Pavel Machek [this message]

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=20210104121516.GA11126@duo.ucw.cz \
    --to=pavel@denx.de \
    --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;
as well as URLs for NNTP newsgroup(s).