From: Henning Schild <henning.schild@siemens.com>
To: Claudius Heine <claudius.heine.ext@siemens.com>
Cc: <isar-users@googlegroups.com>, Claudius Heine <ch@denx.de>
Subject: Re: [PATCH] meta-isar/kernel: update linux-cip from 4.4.154-cip28 to 4.4.166-cip29
Date: Mon, 28 Jan 2019 12:51:58 +0100 [thread overview]
Message-ID: <20190128125158.0dce0711@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <321c0c6b-66c8-276a-3b4f-86d251bf6e4c@siemens.com>
Am Mon, 28 Jan 2019 11:27:41 +0100
schrieb Claudius Heine <claudius.heine.ext@siemens.com>:
> On 28/01/2019 11.17, Henning Schild wrote:
> > Am Thu, 17 Jan 2019 16:32:19 +0100
> > schrieb "[ext] claudius.heine.ext@siemens.com"
> > <claudius.heine.ext@siemens.com>:
> >
> >> From: Claudius Heine <ch@denx.de>
> >>
> >> Signed-off-by: Claudius Heine <ch@denx.de>
> >> ---
> >> .../{linux-cip_4.4.154-cip28.bb => linux-cip_4.4.166-cip29.bb}
> >> | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
> >> rename
> >> meta-isar/recipes-kernel/linux/{linux-cip_4.4.154-cip28.bb =>
> >> linux-cip_4.4.166-cip29.bb} (88%)
> >>
> >> diff --git
> >> a/meta-isar/recipes-kernel/linux/linux-cip_4.4.154-cip28.bb
> >> b/meta-isar/recipes-kernel/linux/linux-cip_4.4.166-cip29.bb
> >> similarity index 88% rename from
> >> meta-isar/recipes-kernel/linux/linux-cip_4.4.154-cip28.bb rename to
> >> meta-isar/recipes-kernel/linux/linux-cip_4.4.166-cip29.bb index
> >> af3f7e7..a8f7a71 100644 ---
> >> a/meta-isar/recipes-kernel/linux/linux-cip_4.4.154-cip28.bb +++
> >> b/meta-isar/recipes-kernel/linux/linux-cip_4.4.166-cip29.bb @@
> >> -11,6 +11,6 @@ SRC_URI += " \
> >> git://git.kernel.org/pub/scm/linux/kernel/git/bwh/linux-cip.git;branch=linux-4.4.y-cip;destsuffix=${P}
> >> \ file://x86_64_defconfig" -SRCREV =
> >> "5dcb70a7e56e2c00e1c8ca593c61e378cef22f51" +SRCREV =
> >> "af3adf9f9c633ac0e1d68487d7fad22285dda8a3"
> >> KERNEL_DEFCONFIG_qemuamd64 = "x86_64_defconfig"
> >
> > The remote we are using in SRC_URI does not contain that commit. The
> > cip maintainer changed and we need to switch the remote as well.
> > Current next is broken.
>
> Argh... I will send a working one... ASAP.
I already sent one.
Henning
> Sorry,
> Claudius
>
> >
> > Henning
> >
>
prev parent reply other threads:[~2019-01-28 11:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 15:32 claudius.heine.ext
2019-01-23 13:56 ` Claudius Heine
2019-01-23 14:01 ` Maxim Yu. Osipov
2019-01-23 14:04 ` Claudius Heine
2019-01-23 15:17 ` Maxim Yu. Osipov
2019-01-28 10:17 ` Henning Schild
2019-01-28 10:27 ` Claudius Heine
2019-01-28 11:51 ` Henning Schild [this message]
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=20190128125158.0dce0711@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.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