All of lore.kernel.org
 help / color / mirror / Atom feed
From: "svdb" <sam.van.den.berge@gmail.com>
To: Andrey Zhizhikin <andrey.z@gmail.com>
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] Cannot run "devtool mofidy linux-fslc" in Dunfell branch
Date: Tue, 16 Feb 2021 12:05:39 +0100	[thread overview]
Message-ID: <CAJPofo=OBJOPdBoQc9P2Tt54NTWuS9-CWXLoe65BkOmb-SWoWw@mail.gmail.com> (raw)
In-Reply-To: <CAHtQpK4P1xx4iTo-zG8EUvk5fbOUau3n2R5qS6Bpo95UfB3Jbg@mail.gmail.com>

On Mon, Feb 15, 2021 at 11:10 PM Andrey Zhizhikin <andrey.z@gmail.com> wrote:
>
> Hello Sam,
>
> On Mon, Feb 15, 2021 at 9:35 PM <sam.van.den.berge@gmail.com> wrote:
> >
> > I also have the exact same error with linux-fslc 5.10.12.
>
> Can you try to change SRCBRANCH in
> recipes-kernel/linux/linux-fslc_5.10.bb to KBRANCH? I've just tried it
> out and it should solve the problem.
>
> I have a patch for this and made a PR to address the issue, please
> have a look at https://github.com/Freescale/meta-freescale/pull/652. I
> would appreciate if you test it locally on your end and report here if
> that solves your devtool errors.

Unfortunately it's not solved in my case. Depending on the path that
gets executed in
devtool/standard.py, I do think your patch does solve the issue in some cases.

>
>
> > 
> >
>
> --
> Regards,
> Andrey.

  reply	other threads:[~2021-02-16 11:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Groupsio.2.8T6j.1596182415784285232.EDu6@lists.yoctoproject.org>
2020-10-27  8:24 ` [meta-freescale] Cannot run "devtool mofidy linux-fslc" in Dunfell branch Ks89
2020-10-27  8:46   ` bartvanderlaan
2021-02-15 20:35     ` sam.van.den.berge
2021-02-15 22:10       ` [meta-freescale] " Andrey Zhizhikin
2021-02-16 11:05         ` svdb [this message]
2021-02-16 11:13           ` Andrey Zhizhikin
2021-02-16 15:00             ` svdb
2021-02-17 13:50               ` Andrey Zhizhikin

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='CAJPofo=OBJOPdBoQc9P2Tt54NTWuS9-CWXLoe65BkOmb-SWoWw@mail.gmail.com' \
    --to=sam.van.den.berge@gmail.com \
    --cc=andrey.z@gmail.com \
    --cc=meta-freescale@lists.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.