From: "Belal, Awais" <Awais_Belal@mentor.com>
To: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"Reyna, David" <david.reyna@windriver.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [sumo][PATCH] toaster: localhostbecontroller: fix bitbake path resolution
Date: Fri, 28 Sep 2018 10:38:15 +0000 [thread overview]
Message-ID: <1538131095353.74870@mentor.com> (raw)
In-Reply-To: <573089240e7086a6091c1123454a842cec4cff78.camel@linuxfoundation.org>
>> The patch doesn't apply to master so could you send a version which
>> applies there please?
>> I can then apply the sumo one at the same time which does presumably
>> apply to sumo (I've not tried that as yet).
Extremely sorry, this is only needed for sumo (1.38), master doesn't have this problem.
BR,
Awais
________________________________________
From: richard.purdie@linuxfoundation.org <richard.purdie@linuxfoundation.org>
Sent: Friday, September 28, 2018 12:52 PM
To: Belal, Awais; Reyna, David; bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [sumo][PATCH] toaster: localhostbecontroller: fix bitbake path resolution
On Fri, 2018-09-28 at 07:37 +0000, Belal, Awais wrote:
> > > I'm confused. Does master need the patch? or only sumo?
>
> Both.
The patch doesn't apply to master so could you send a version which
applies there please?
I can then apply the sumo one at the same time which does presumably
apply to sumo (I've not tried that as yet).
Thanks,
Richard
next prev parent reply other threads:[~2018-09-28 10:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 9:35 [sumo][PATCH] toaster: localhostbecontroller: fix bitbake path resolution Belal, Awais
2018-09-14 7:18 ` Reyna, David
2018-09-20 7:59 ` Belal, Awais
2018-09-27 7:54 ` Belal, Awais
2018-09-27 16:53 ` Richard Purdie
2018-09-28 7:37 ` Belal, Awais
2018-09-28 7:52 ` richard.purdie
2018-09-28 10:38 ` Belal, Awais [this message]
2018-09-28 16:08 ` akuster808
2018-09-30 7:06 ` Reyna, David
2018-09-30 7:40 ` Reyna, David
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=1538131095353.74870@mentor.com \
--to=awais_belal@mentor.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=david.reyna@windriver.com \
--cc=richard.purdie@linuxfoundation.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.