From: ChenQi <Qi.Chen@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/4] runqemu-internal: change the lock acquire/release logic
Date: Wed, 28 Aug 2013 10:25:46 +0800 [thread overview]
Message-ID: <521D5FAA.3000503@windriver.com> (raw)
In-Reply-To: <1377598192.32502.3.camel@ted>
On 08/27/2013 06:09 PM, Richard Purdie wrote:
> On Tue, 2013-08-27 at 15:08 +0800, Qi.Chen@windriver.com wrote:
>> From: Chen Qi <Qi.Chen@windriver.com>
>>
>> Checking whether the lock file exists is sufficient for runqemu.
>> The contents of the lock file is not important.
> What happens if the runqemu script crashes and leaves the lockfile
> around? Why are we removing perfectly functional code?
>
> Cheers,
>
> Richard
>
>
>
>
Yes. You're right.
I'll drop this patch and send out a V2.
Best Regards,
Chen Qi
next prev parent reply other threads:[~2013-08-28 2:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 7:07 [PATCH 0/4] runqemu fixes about iptables rules and preconfigured tap Qi.Chen
2013-08-27 7:08 ` [PATCH 1/4] runqemu-ifdown: clean up the remaining iptables rules Qi.Chen
2013-08-27 7:08 ` [PATCH 2/4] runqemu-internal: don't bring down preconfigured tap interface Qi.Chen
2013-08-27 7:08 ` [PATCH 3/4] runqemu-internal: change the lock acquire/release logic Qi.Chen
2013-08-27 10:09 ` Richard Purdie
2013-08-28 2:25 ` ChenQi [this message]
2013-08-27 10:14 ` Phil Blundell
2013-08-28 2:32 ` ChenQi
2013-08-27 7:08 ` [PATCH 4/4] runqemu-internal: provide more info if a preconfigured tap is used Qi.Chen
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=521D5FAA.3000503@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox