From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: Pgowda <pgowda.cve@gmail.com>,
openembedded-core@lists.openembedded.org,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Randy MacLeod <rwmacleod@gmail.com>,
alex.kanavin@gmail.com, umesh.kalappa0@gmail.com,
Vinay Kumar <vinay.m.engg@gmail.com>
Subject: Re: [OE-core] [PATCH v2 3/3] Rust oe-selftest file
Date: Tue, 5 Oct 2021 18:21:47 +0200 [thread overview]
Message-ID: <YVx7m1AFrSsNGtAW@piout.net> (raw)
In-Reply-To: <e2ff8b3f-a9e1-00f6-7536-3bb8712fad84@windriver.com>
On 05/10/2021 12:13:56-0400, Randy MacLeod wrote:
> On 2021-09-30 12:31 a.m., Pgowda wrote:
> > Hi Alexandre,
> >
> > Thanks for mentioning it.
> >
> > It's already been taken care of as the following patch:-
> > http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=50f7a13e69e8987b3629d455f9f56720c376e89b
>
> Hi Naveen,
>
> That link is for a commit in master-next that is no longer valid.
> I guess you should send a v3.
>
That's fine, I'm also carrying the patch in kirkstone-next now
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-10-05 16:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 8:04 [PATCH v2 1/3] Rust oe-selftest script Pgowda
2021-09-29 8:04 ` [PATCH v2 2/3] Rust cross testing file Pgowda
2021-09-29 23:03 ` [OE-core] " Alexandre Belloni
2021-09-30 7:27 ` [PATCH v3] " Pgowda
[not found] ` <16A988E1BC842A91.3292@lists.openembedded.org>
2021-10-20 7:08 ` pgowda cve
2021-10-20 7:42 ` Alexandre Belloni
2021-11-02 5:12 ` pgowda cve
2021-11-26 18:34 ` Randy MacLeod
2021-09-29 8:04 ` [PATCH v2 3/3] Rust oe-selftest file Pgowda
2021-09-29 22:59 ` [OE-core] " Alexandre Belloni
2021-09-30 4:31 ` pgowda cve
2021-10-05 16:13 ` Randy MacLeod
2021-10-05 16:21 ` Alexandre Belloni [this message]
2021-10-05 18:19 ` [OE-core] [PATCH v2 1/3] Rust oe-selftest script Alexandre Belloni
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=YVx7m1AFrSsNGtAW@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pgowda.cve@gmail.com \
--cc=randy.macleod@windriver.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=rwmacleod@gmail.com \
--cc=umesh.kalappa0@gmail.com \
--cc=vinay.m.engg@gmail.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