From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] scripts: ensure tinfoil is shut down correctly
Date: Wed, 31 Aug 2016 11:55:44 +0100 [thread overview]
Message-ID: <1472640944.29583.77.camel@linuxfoundation.org> (raw)
In-Reply-To: <88fde4c5d43e2b6ebced1462705241222fb9734a.1472607521.git.paul.eggleton@linux.intel.com>
On Wed, 2016-08-31 at 13:48 +1200, Paul Eggleton wrote:
> We should always shut down tinfoil when we're finished with it,
> either
> by explicitly calling the shutdown() method or by using it as a
> context manager ("with ...").
Could I trouble you to rebase this onto master-next please? It
currently has conflicts which didn't seem immediately obvious to me to
resolve.
Cheers,
Richard
next prev parent reply other threads:[~2016-08-31 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 1:48 [PATCH 0/2] Tinfoil usage fixes Paul Eggleton
2016-08-31 1:48 ` [PATCH 1/2] scripts: ensure tinfoil is shut down correctly Paul Eggleton
2016-08-31 10:55 ` Richard Purdie [this message]
2016-08-31 19:52 ` Paul Eggleton
2016-08-31 1:48 ` [PATCH 2/2] scripts/contrib: update scripts for changes to internal API Paul Eggleton
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=1472640944.29583.77.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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