From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 1/3] linux-yocto: Update linux-yocto for 3.2 and 3.4
Date: Wed, 05 Sep 2012 11:16:52 -0700 [thread overview]
Message-ID: <50479714.6090607@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sr-e_vdd=pUBUNjo5tq1qbCyK2fDrhFn696NaHyCv0DXw@mail.gmail.com>
On 09/05/2012 10:43 AM, Khem Raj wrote:
> On Wed, Sep 5, 2012 at 10:15 AM, Saul Wold <sgw@linux.intel.com> wrote:
>>
>>
>> It will add another .1 to the PR, if PR = 4.1, it will become 4.1.1
>
> sorry, I was more interested in the time limited kernel option.
>
>
Sorry, you had put that right under the PR line and JaMa had also asked
about it!
This is to prevent the HW BSP generated by the autobuild from being used
in production, it's added by the autobuilder to the HW bsps.
It's a kernel configuration that a patch in the linux-yocto code base,
Bruce would have to fill you in on those details.
Sau!
next prev parent reply other threads:[~2012-09-05 18:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 16:56 [PATCH 0/3 v3] Meta-tlk update Saul Wold
2012-09-05 16:56 ` [PATCH 1/3] linux-yocto: Update linux-yocto for 3.2 and 3.4 Saul Wold
2012-09-05 17:08 ` Khem Raj
2012-09-05 17:15 ` Saul Wold
2012-09-05 17:43 ` Khem Raj
2012-09-05 18:16 ` Saul Wold [this message]
2012-09-05 19:03 ` Khem Raj
2012-09-05 19:06 ` Bruce Ashfield
2012-09-05 19:23 ` Khem Raj
2012-09-05 21:38 ` Tom Zanussi
2012-09-05 16:56 ` [PATCH 2/3] base-files: add /etc/motd with TLK info Saul Wold
2012-09-05 21:38 ` Tom Zanussi
2012-09-05 16:56 ` [PATCH 3/3] psplash: Add TLK info to psplash image Saul Wold
2012-09-05 21:38 ` Tom Zanussi
2012-09-05 21:38 ` [PATCH 0/3 v3] Meta-tlk update Tom Zanussi
-- strict thread matches above, loose matches on Subject: below --
2012-09-04 20:57 [PATCH 1/3] linux-yocto: Update linux-yocto for 3.2 and 3.4 Saul Wold
2012-09-04 21:00 ` Martin Jansa
2012-09-05 4:18 ` Saul Wold
2012-09-05 19:45 ` Martin Jansa
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=50479714.6090607@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.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 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.