From: Sasha Levin <sashal@kernel.org>
To: kernelci@groups.io
Subject: branch inclusion request
Date: Fri, 26 Oct 2018 11:19:56 -0400 [thread overview]
Message-ID: <20181026151956.GG2015@sasha-vm> (raw)
Hi all,
Right now I'm pushing stable patches to Greg for his weekly releases,
and for those branches I only do basic cross-compilation and no
boot/functional testing at all.
I'd like to modify my process to rely on KernelCI testing instead. This
means I'd like to include my branches (one for each stable kernel) into
the build system.
These branches get pushed a few times per week, and sometimes a few
times a day, so this will generate a fair amount of builds. OTOH, I
don't really need to keep the build results for too long as I try to
address any issues that come up the same day.
--
Thanks,
Sasha
next reply other threads:[~2018-10-26 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 15:19 Sasha Levin [this message]
2018-10-26 16:34 ` [kernelci] branch inclusion request Guillaume Tucker
2018-10-29 15:35 ` Kevin Hilman
2018-11-09 16:26 ` 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=20181026151956.GG2015@sasha-vm \
--to=sashal@kernel.org \
--cc=kernelci@groups.io \
/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