From: richard.purdie@linuxfoundation.org
To: liu.ming50@gmail.com, openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
Alexander Kanavin <alex@linutronix.de>,
Luca Ceresoli <luca.ceresoli@bootlin.com>
Subject: Re: [OE-core] [kirkstone] [PATCH 1/1] mmc-utils: upgrade to latest revision
Date: Sun, 15 May 2022 22:46:13 +0100 [thread overview]
Message-ID: <d5f96822345d8ac0eaee74a5a4169a4882b397a9.camel@linuxfoundation.org> (raw)
In-Reply-To: <16EF654890391C3F.10172@lists.openembedded.org>
On Sun, 2022-05-15 at 22:42 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Sun, 2022-05-15 at 14:43 +0200, liu.ming50@gmail.com wrote:
> > From: Alexander Kanavin <alex.kanavin@gmail.com>
> >
> > Signed-off-by: Alexander Kanavin <alex@linutronix.de>
> > Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
> > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > (cherry picked from commit d98b06c9c6f480de1e5167bfe8392e39300fc02c)
> > Signed-off-by: Ming Liu <liu.ming50@gmail.com>
> > ---
> > meta/recipes-devtools/mmc/mmc-utils_git.bb | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
>
> Why does kirkstone need this though?
Sorry, you cc'd me on the patch but not the cover letter which meant
this sorted badly in my mail folders but I noticed the cover letter
now.
You mention a compile failure in the cover letter, it would probably be
useful to give a little more info about the kind of compile failure
given we've not seen this anywhere else?
Cheers,
Richard
prev parent reply other threads:[~2022-05-15 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-15 12:43 [OE-core] [kirkstone] [PATCH 0/1] Fix a compilation issue of mmc-utils liu.ming50
2022-05-15 12:43 ` [OE-core] [kirkstone] [PATCH 1/1] mmc-utils: upgrade to latest revision liu.ming50
2022-05-15 21:42 ` richard.purdie
2022-05-16 7:17 ` Ming Liu
2022-05-16 14:29 ` Steve Sakoman
2022-05-17 7:37 ` Ming Liu
[not found] ` <16EF654890391C3F.10172@lists.openembedded.org>
2022-05-15 21:46 ` richard.purdie [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=d5f96822345d8ac0eaee74a5a4169a4882b397a9.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=liu.ming50@gmail.com \
--cc=luca.ceresoli@bootlin.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox