All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	kernelci@groups.io, tkjos@google.com
Subject: Re: Branch for kernelci
Date: Wed, 16 Oct 2019 17:46:22 +0100	[thread overview]
Message-ID: <20191016164621.xa2nc6li2luiujug@willie-the-truck> (raw)
In-Reply-To: <20191016125416.GA11371@sirena.co.uk>

On Wed, Oct 16, 2019 at 01:54:16PM +0100, Mark Brown wrote:
> On Wed, Oct 16, 2019 at 01:38:34PM +0100, Catalin Marinas wrote:
> > On Wed, Oct 16, 2019 at 10:56:36AM +0100, Mark Brown wrote:
> 
> > > 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.
> 
> Yeah, that was what you'd both rejected doing before which was why I was
> surprised (plus the fact that this was coming via Todd rather than one
> of you).

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!

So yes, I'm interested in having our for-kernelci branch picked up despite
not seeing the benefit in the past.

Thanks,

Will

  reply	other threads:[~2019-10-16 16:46 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 [this message]
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=20191016164621.xa2nc6li2luiujug@willie-the-truck \
    --to=will@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernelci@groups.io \
    --cc=tkjos@google.com \
    /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.