public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: kernelci@groups.io, tkjos@google.com, will@kernel.org
Subject: Re: Branch for kernelci
Date: Wed, 16 Oct 2019 13:38:34 +0100	[thread overview]
Message-ID: <20191016123833.GG49619@arrakis.emea.arm.com> (raw)
In-Reply-To: <20191016095636.GA4881@sirena.co.uk>

On Wed, Oct 16, 2019 at 10:56:36AM +0100, Mark Brown wrote:
> On Tue, Oct 15, 2019 at 01:52:36PM -0700, Todd Kjos via Groups.Io wrote:
> > Please add testing for Will Deacon's ARM64 staging tree to kernelci:
> 
> > [web] https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/log/?h=for-kernelci
> > [git] git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
> 
> > It would make sense to have dashboard available as "arm64" or some
> > other unique tree name (eg "https://kernelci.org/job/arm64").
> 
> > The owners of this tree are the ARM64 maintainers: will@kernel.org and
> > catalin.marinas@arm.com (CC'd)
> 
> Are you sure they are interested in this?  When asked previously they
> indicated that they didn't see any extra value in covering their tree
> specifically separately to -next.

Will can comment on the reasoning but I guess it came as a request from
him since he also created the arm64/for-kernelci branch. This might as
well be the same as for-next/core but tested in isolation rather than
with the whole linux-next tree.

-- 
Catalin

  reply	other threads:[~2019-10-16 12:38 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 [this message]
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
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=20191016123833.GG49619@arrakis.emea.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=broonie@kernel.org \
    --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