From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] usbutils 0.91: Fix NULL pointer crash.
Date: Sun, 29 Jul 2012 10:22:20 +0100 [thread overview]
Message-ID: <1343553740.16998.28.camel@ted> (raw)
In-Reply-To: <1343390587-27506-1-git-send-email-rongqing.li@windriver.com>
On Fri, 2012-07-27 at 20:03 +0800, rongqing.li@windriver.com wrote:
> From: Roy.Li <rongqing.li@windriver.com>
>
> [YOCTO #2847]
>
> Before use usbbuslist, we should check if it is valid.
>
> Signed-off-by: Roy.Li <rongqing.li@windriver.com>
> ---
> .../usbutils/usbutils/Fix-NULL-pointer-crash.patch | 28 ++++++++++++++++++++
> meta/recipes-bsp/usbutils/usbutils_0.91.bb | 5 ++-
> 2 files changed, 31 insertions(+), 2 deletions(-)
> create mode 100644 meta/recipes-bsp/usbutils/usbutils/Fix-NULL-pointer-crash.patch
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-07-29 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 12:03 [PATCH 1/1] usbutils 0.91: Fix NULL pointer crash rongqing.li
2012-07-29 9:22 ` 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=1343553740.16998.28.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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