From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>, isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH] meta-isar/linux-cip: Update SRC_URI to new cip kernel path
Date: Wed, 30 Jan 2019 10:37:16 +0100 [thread overview]
Message-ID: <7c575336-a364-bcfa-378b-ad2ccdd418d4@ilbers.de> (raw)
In-Reply-To: <20190128102647.19923-1-henning.schild@siemens.com>
On 1/28/19 11:26 AM, Henning Schild wrote:
> From: Henning Schild <henning.schild@siemens.com>
Applied to the 'next'.
Thanks,
Maxim.
> Upstream developement has changed to another repository. The bump from
> 22f2387b3791 need the SRC_URI update to work.
>
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
> meta-isar/recipes-kernel/linux/linux-cip_4.4.166-cip29.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-isar/recipes-kernel/linux/linux-cip_4.4.166-cip29.bb b/meta-isar/recipes-kernel/linux/linux-cip_4.4.166-cip29.bb
> index a8f7a71..b1a45df 100644
> --- a/meta-isar/recipes-kernel/linux/linux-cip_4.4.166-cip29.bb
> +++ b/meta-isar/recipes-kernel/linux/linux-cip_4.4.166-cip29.bb
> @@ -8,7 +8,7 @@
> require recipes-kernel/linux/linux-custom.inc
>
> SRC_URI += " \
> - git://git.kernel.org/pub/scm/linux/kernel/git/bwh/linux-cip.git;branch=linux-4.4.y-cip;destsuffix=${P} \
> + git://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git;branch=linux-4.4.y-cip;destsuffix=${P} \
> file://x86_64_defconfig"
>
> SRCREV = "af3adf9f9c633ac0e1d68487d7fad22285dda8a3"
>
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
prev parent reply other threads:[~2019-01-30 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 10:26 Henning Schild
2019-01-30 9:37 ` Maxim Yu. Osipov [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=7c575336-a364-bcfa-378b-ad2ccdd418d4@ilbers.de \
--to=mosipov@ilbers.de \
--cc=ch@denx.de \
--cc=henning.schild@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