public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: Denys Fedoryshchenko <denys.f@collabora.com>
To: Todd Kjos <tkjos@google.com>
Cc: kernelci@groups.io, kernelci@lists.linux.dev,
	Kevin Hilman <khilman@baylibre.com>
Subject: Re: Please add android14-6.1
Date: Thu, 02 Feb 2023 13:14:32 +0200	[thread overview]
Message-ID: <5fa4e2b7e98d01bcdf6a7f24f99bb0259c80d882.camel@collabora.com> (raw)
In-Reply-To: <CAHRSSEw0D9nYg2jHLNtWXMZHqR29gtk8qnNr181NuBt=_MTQAg@mail.gmail.com>

It seems queue is cleared, maybe it was caused by high activity in
all kernel trees for last 1-2 weeks.
I will try to do PR today and will delete old trees.



On Wed, 2023-02-01 at 10:18 -0800, Todd Kjos wrote:
> [non-HTML version this time. Sigh.]
> 
> According to the bug, this is blocked by build capacity issues... you
> can delete android-4.9-q, android-4.14-q, and android-4.19-q. Does
> that help with capacity? We'd really like to get our 6.1 kernel into
> the tests...
> 
> 
> On Thu, Jan 19, 2023 at 6:14 AM Denys Fedoryshchenko
> <denys.f@collabora.com> wrote:
> > 
> > Hi,
> > 
> > i will take care about that, will post progress in:
> > https://github.com/kernelci/kernelci-core/issues/1659
> > 
> > On Wed, 2023-01-18 at 16:08 -0800, Todd Kjos wrote:
> > > Any progress on this?
> > > 
> > > (sorry if you got this twice - 1st one was sent with rich text
> > > and
> > > rejected by lists.linux.dev)
> > > 
> > > 
> > > On Fri, Dec 16, 2022 at 12:17 PM Todd Kjos <tkjos@google.com>
> > > wrote:
> > > > 
> > > > +kernelci@lists.linux.dev
> > > > 
> > > > 
> > > > On Fri, Dec 16, 2022 at 11:45 AM Todd Kjos <tkjos@google.com>
> > > > wrote:
> > > > > 
> > > > > Please add android14-6.1 branch to kernelci testing.
> > > > > 
> > > > > repo: https://android.googlesource.com/kernel/common
> > > > > branches: android14-6.1
> > > > > 
> > > > > Thanks,
> > > > > 
> > > > > -Todd
> > > 
> > 
> > 
> 



  reply	other threads:[~2023-02-02 11:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHRSSEzfMO06w8cimnG9W_NnvnupxcF93tVVJOybUWjoQzNY3w@mail.gmail.com>
2022-12-16 20:17 ` Please add android14-6.1 Todd Kjos
2023-01-19  0:08   ` Todd Kjos
2023-01-19 14:14     ` Denys Fedoryshchenko
2023-02-01 18:18       ` Todd Kjos
2023-02-02 11:14         ` Denys Fedoryshchenko [this message]
2023-02-02 16:53   ` 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=5fa4e2b7e98d01bcdf6a7f24f99bb0259c80d882.camel@collabora.com \
    --to=denys.f@collabora.com \
    --cc=kernelci@groups.io \
    --cc=kernelci@lists.linux.dev \
    --cc=khilman@baylibre.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox