From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Kristian Amlie <kristian.amlie@mender.io>,
openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for Make SSTATE_SCAN_CMD vars configurable using weak defaults.
Date: Wed, 25 Jan 2017 14:38:49 +0000 [thread overview]
Message-ID: <1485355129.17309.0.camel@linuxfoundation.org> (raw)
In-Reply-To: <129d261e-6f76-b471-48cd-99ddd06c3667@mender.io>
On Wed, 2017-01-25 at 15:34 +0100, Kristian Amlie wrote:
> Sorry I forgot the right patch format, but let me know if you agree
> with the patch first, and I'll repost.
Yes, I'm ok with it. The sdk class is long gone.
Cheers,
Richard
next prev parent reply other threads:[~2017-01-25 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 10:43 Overriding fixmepath Kristian Amlie
2017-01-25 11:24 ` Richard Purdie
2017-01-25 12:22 ` Kristian Amlie
2017-01-25 12:39 ` Richard Purdie
2017-01-25 13:53 ` Kristian Amlie
2017-01-25 13:53 ` [PATCH] Make SSTATE_SCAN_CMD vars configurable using weak defaults Kristian Amlie
2017-01-25 14:23 ` ✗ patchtest: failure for " Patchwork
2017-01-25 14:34 ` Kristian Amlie
2017-01-25 14:38 ` Richard Purdie [this message]
2017-01-25 14:46 ` [PATCH] sstate: " Kristian Amlie
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=1485355129.17309.0.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=kristian.amlie@mender.io \
--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