From: Darren Hart <dvhart@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] i2c-tools: Add i2c-tools to the core
Date: Wed, 28 May 2014 07:44:00 -0700 [thread overview]
Message-ID: <CFAB4426.94179%dvhart@linux.intel.com> (raw)
In-Reply-To: <1401266574.2607.17.camel@ted>
On 5/28/14, 1:42, "Richard Purdie" <richard.purdie@linuxfoundation.org>
wrote:
>On Tue, 2014-05-27 at 13:38 -0700, Darren Hart wrote:
>> The following changes since commit
>>f3d62a9eb9c47356e6150fdd55f790c159e620c7:
>>
>> eglinfo: updated to compile with mesa10+ (2014-05-27 16:11:55 +0100)
>>
>> are available in the git repository at:
>>
>> git://git.yoctoproject.org/poky-contrib dvhart/i2c-tools
>>
>>http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=dvhart/i2c-tools
>>
>> Darren Hart (1):
>> i2c-tools: Add i2c-tools to the core
>>
>> meta/recipes-devtools/i2c-tools/files/Module.mk | 72
>>++++++++++++++++++++
>> .../i2c-tools/i2c-tools-3.1.0/Module.mk | 72
>>++++++++++++++++++++
>> meta/recipes-devtools/i2c-tools/i2c-tools_3.1.0.bb | 26 +++++++
>> 3 files changed, 170 insertions(+)
>> create mode 100644 meta/recipes-devtools/i2c-tools/files/Module.mk
>> create mode 100644
>>meta/recipes-devtools/i2c-tools/i2c-tools-3.1.0/Module.mk
>> create mode 100644 meta/recipes-devtools/i2c-tools/i2c-tools_3.1.0.bb
>
>I merged this, I've said I wanted this patch for long enough to multiple
>people, thanks! :)
>
>I removed the duplicate Module.mk file...
Oops, thanks.
What follow-up is necessary/appropriate with meta-oe?
--
Darren Hart Open Source Technology Center
darren.hart@intel.com Intel Corporation
next prev parent reply other threads:[~2014-05-28 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 20:38 [PATCH 0/1] i2c-tools: Add i2c-tools to the core Darren Hart
2014-05-28 8:42 ` Richard Purdie
2014-05-28 14:44 ` Darren Hart [this message]
2014-05-28 15:02 ` Khem Raj
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=CFAB4426.94179%dvhart@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.