From: Khem Raj <raj.khem@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/5] linux-yocto: consolidated pull request
Date: Wed, 6 May 2015 23:33:12 -0700 [thread overview]
Message-ID: <B72FAFCA-6F01-4EFC-8C11-BD7DBDEA0217@gmail.com> (raw)
In-Reply-To: <20150506153325.GB2067@jama>
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
> On May 6, 2015, at 8:33 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
>
> I'm considering providing simple old-style recipes for vanilla kernels
> and using them in my jenkins builds instead linux-yocto, because kernel
> shouldn't block testing other recipes from meta-oe and other layers as
> often as linux-yocto does.
just for build sake to avoid full kernel builds, having a dummy kernel recipe should be another alternative
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2015-05-07 6:33 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 1:34 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2015-05-01 1:34 ` [PATCH 1/5] linux-yocto/3.14: refresh -rt support Bruce Ashfield
2015-05-01 1:34 ` [PATCH 2/5] linux-yocto: add core bluetooth support to qemux86* and common-pc* Bruce Ashfield
2015-05-01 1:34 ` [PATCH 3/5] linux-yocto/3.19: Braswell support and bug fixes Bruce Ashfield
2015-05-01 1:34 ` [PATCH 4/5] perf: fix build (and feature tests) for 4.1-rcX Bruce Ashfield
2015-05-01 1:34 ` [PATCH 5/5] linux-yocto-dev: introduce 4.1-rc development kernel Bruce Ashfield
2015-05-01 22:59 ` [PATCH 0/5] linux-yocto: consolidated pull request Richard Purdie
2015-05-01 23:30 ` Bruce Ashfield
2015-05-02 8:13 ` Martin Jansa
2015-05-03 2:50 ` Bruce Ashfield
2015-05-06 14:42 ` Martin Jansa
2015-05-06 14:58 ` Bruce Ashfield
2015-05-06 15:33 ` Martin Jansa
2015-05-06 15:44 ` Richard Purdie
2015-05-06 16:07 ` Martin Jansa
2015-05-06 17:46 ` Bruce Ashfield
2015-05-06 21:32 ` Richard Purdie
2015-05-06 22:49 ` Martin Jansa
2015-05-07 15:33 ` Bruce Ashfield
2015-05-07 6:33 ` Khem Raj [this message]
2015-05-02 9:00 ` Richard Purdie
2015-05-03 2:53 ` Bruce Ashfield
2015-05-03 3:52 ` Bruce Ashfield
2015-05-03 10:48 ` Richard Purdie
2015-05-03 21:30 ` Richard Purdie
2015-05-04 4:36 ` Bruce Ashfield
2015-05-04 15:01 ` Bruce Ashfield
-- strict thread matches above, loose matches on Subject: below --
2024-08-11 18:04 bruce.ashfield
2024-08-12 9:47 ` Richard Purdie
2024-08-12 12:47 ` Bruce Ashfield
2023-02-01 16:28 bruce.ashfield
2020-11-19 19:17 Bruce Ashfield
2020-05-29 1:29 Bruce Ashfield
2020-05-03 15:44 Bruce Ashfield
2020-05-04 8:30 ` Richard Purdie
2020-05-04 12:56 ` Bruce Ashfield
2020-03-24 23:04 Bruce Ashfield
2016-07-27 16:57 Bruce Ashfield
2016-06-21 15:20 Bruce Ashfield
2016-04-13 16:12 Bruce Ashfield
2015-03-24 18:57 Bruce Ashfield
2015-03-25 9:26 ` Richard Purdie
2015-03-25 12:13 ` Bruce Ashfield
2015-03-25 13:26 ` Bruce Ashfield
2015-03-25 13:52 ` Richard Purdie
2013-08-23 18:08 Bruce Ashfield
2013-08-23 21:30 ` Bruce Ashfield
2013-08-24 6:33 ` Saul Wold
2013-08-24 13:34 ` Bruce Ashfield
2013-08-24 13:45 ` Bruce Ashfield
2013-08-24 13:50 ` Saul Wold
2013-08-24 13:53 ` Bruce Ashfield
2013-08-24 14:47 ` Bruce Ashfield
2013-08-24 14:59 ` Bruce Ashfield
2013-08-24 16:05 ` Bruce Ashfield
2012-02-05 6:31 Bruce Ashfield
2012-02-08 4:09 ` Saul Wold
2012-01-11 18:52 Bruce Ashfield
2012-01-17 19:28 ` Saul Wold
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=B72FAFCA-6F01-4EFC-8C11-BD7DBDEA0217@gmail.com \
--to=raj.khem@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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