public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Veronika Kabatova" <vkabatov@redhat.com>
To: Will Deacon <will@kernel.org>
Cc: kernelci@groups.io, Mark Brown <broonie@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	tkjos@google.com
Subject: Re: Branch for kernelci
Date: Thu, 17 Oct 2019 13:01:25 -0400 (EDT)	[thread overview]
Message-ID: <1783449691.4379913.1571331685575.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20191017160242.qgp5y56gnbxnmkaa@willie-the-truck>



----- Original Message -----
> From: "Will Deacon" <will@kernel.org>
> To: "Veronika Kabatova" <vkabatov@redhat.com>
> Cc: kernelci@groups.io, "Mark Brown" <broonie@kernel.org>, "Catalin Marinas" <catalin.marinas@arm.com>,
> tkjos@google.com
> Sent: Thursday, October 17, 2019 6:02:43 PM
> Subject: Re: Branch for kernelci
> 
> Hi Veronika,
> 
> On Thu, Oct 17, 2019 at 07:31:14AM -0400, Veronika Kabatova wrote:
> > > On Wed, Oct 16, 2019 at 01:28:44PM -0400, Veronika Kabatova wrote:
> > > > > I asked Todd about this yesterday because we're dealing with an ABI
> > > > > regression in 5.4 which wasn't picked up until -rc3, so figured that
> > > > > this
> > > > > was probably worth doing after all. Perhaps it wouldn't have helped
> > > > > for
> > > > > this
> > > > > specific case, but it turns out that one person's LTP isn't quite the
> > > > > same
> > > > > as another person's LTP!
> > > > > 
> > > > 
> > > > if you're mentioning the regression from this thread [0] you'd need to
> > > > have
> > > > the tree added to CKI, not KernelCI. Not sure if we're ready to handle
> > > > mainline/next speed of development yet but we can discuss the specifics
> > > > and
> > > > decide based on that. The issue/PR with details be submitted here [1].
> > > 
> > > Hopefully the two aren't mutually exclusive, so if you're able to add the
> > > branch to CKI as well then that would be great.
> > > 
> > 
> > Of course not. Is testing on aarch64 sufficient or do you need other
> > architectures too?
> 
> Oh, good question! I suppose the two targets we care about the most are
> arm64 kernel with both arm64 and arm32 userspace.
> 

I think we only have arm64. Thanks for answer, I'll adjust the tree
config to only use aarch64 for now.

> > I submitted [0] the initial config, please check if the repo and email
> > information are correct or if we should add e.g. ARM list (didn't see
> > it in the initial email but checking just in case).
> 
> Brilliant, thanks very much. I hadn't considered adding the list, but I
> guess it doesn't hurt so please feel free to add
> linux-arm-kernel@lists.infradead.org as well.
> 

Will add!

> Curious: why 'olddefconfig' instead of 'defconfig'? Are there some options
> required by CKI that aren't present in defconfig?
> 

We're using Fedora config files with this option. I honestly don't know if
there are any tests depending on it, but we are trying to build kernels
close to the Fedora ones.


I'll get all the CKI configs in place and the first test run should start
soon after they are merged.


Veronika

> Will
> 

  parent reply	other threads:[~2019-10-17 17:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191015202114.GA120152@google.com>
2019-10-15 20:52 ` Branch for kernelci Todd Kjos
2019-10-16  9:56   ` Mark Brown
2019-10-16 12:38     ` Catalin Marinas
2019-10-16 12:54       ` Mark Brown
2019-10-16 16:46         ` Will Deacon
2019-10-16 17:28           ` Veronika Kabatova
2019-10-16 23:50             ` Will Deacon
2019-10-17 11:31               ` Veronika Kabatova
2019-10-17 16:02                 ` Will Deacon
2019-10-17 16:11                   ` Mark Brown
2019-10-17 17:01                   ` Veronika Kabatova [this message]
2019-10-22 19:53           ` Guillaume Tucker
2019-10-23 16:42             ` Will Deacon
2019-10-23 18:16               ` Guillaume Tucker
2019-10-25 16:01                 ` Will Deacon
2019-10-28 21:10                   ` Guillaume Tucker

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=1783449691.4379913.1571331685575.JavaMail.zimbra@redhat.com \
    --to=vkabatov@redhat.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernelci@groups.io \
    --cc=tkjos@google.com \
    --cc=will@kernel.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