From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] usbutils: Upgrade usbutils to upstream v002
Date: Thu, 2 Aug 2012 16:40:01 +0200 [thread overview]
Message-ID: <20120802144001.GV16306@jama.jama.net> (raw)
In-Reply-To: <501A6AA4.7030804@intel.com>
[-- Attachment #1: Type: text/plain, Size: 476 bytes --]
On Thu, Aug 02, 2012 at 02:55:16PM +0300, Radu Moisan wrote:
>
> On 08/02/2012 12:10 PM, Martin Jansa wrote:
> > On Thu, Aug 02, 2012 at 12:08:50PM +0300, Radu Moisan wrote:
> >> Signed-off-by: Radu Moisan <radu.moisan@intel.com>
> > Why not current 006? And lsusb link is not needed anymore?
> I really don't know why I chose 002, I'll follow with a new patch for 006
Can you answer *both* questions?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2012-08-02 14:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 9:08 [PATCH] usbutils: Upgrade usbutils to upstream v002 Radu Moisan
2012-08-02 9:10 ` Martin Jansa
2012-08-02 11:55 ` Radu Moisan
2012-08-02 14:40 ` Martin Jansa [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=20120802144001.GV16306@jama.jama.net \
--to=martin.jansa@gmail.com \
--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