From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] runqemu: Add error handling for unexpected tap devices
Date: Sun, 09 Aug 2015 08:21:31 -0700 [thread overview]
Message-ID: <1439133691.30467.100.camel@linuxfoundation.org> (raw)
In-Reply-To: <37380D15-6A67-405F-ACFF-7E03F6843595@gmail.com>
On Sun, 2015-08-09 at 00:31 -0700, Khem Raj wrote:
> > On Aug 9, 2015, at 12:03 AM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> >
> > In theory the code reduces the tap device number to an integer. This
> > patch adds error checking to ensure that does happen and that the script
> > exits if something unexpected happens.
> >
>
> I see these patches are already on master. Are you sending them again by mistake for review or something else ?
Sorry, I've hit the wrong commands. The plan was to queue them for a
fast turnaround into master once the current build completed and they'd
spent some time on the list for review. It looks like I pushed them
early :/.
The good news is that with these patches, one of the "random" issues
we've been seeing is fixed and we might be able to start trusting the
autobuilder a bit more again. There are still other issues but this is
perhaps the one with the most visible impact.
It does look like we're going to need an M2 rc2 once we figure out the
libpam issues so I'm going to hold off the various queued upgrades until
we figure out a good rc2 build combination of changes.
Cheers,
Richard
prev parent reply other threads:[~2015-08-09 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-09 7:03 [PATCH] runqemu: Add error handling for unexpected tap devices Richard Purdie
2015-08-09 7:31 ` Khem Raj
2015-08-09 15:21 ` 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=1439133691.30467.100.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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