From: Denys Dmytriyenko <denys@ti.com>
To: "Nelson, Sam" <sam.nelson@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH] mpm-transport: Update commit id with fixes
Date: Tue, 6 Dec 2016 20:28:34 -0500 [thread overview]
Message-ID: <20161207012833.GN28380@edge> (raw)
In-Reply-To: <4F9216F96E5DF9428610502835A9F490584F273E@DLEE11.ent.ti.com>
Can you please resubmit it? I already dropped it from patchwork.
On Mon, Nov 28, 2016 at 03:36:52PM +0000, Nelson, Sam wrote:
> This patch is good to go. Previously NAK because of reported failures. Looks like they are false alarm.
> So this patch can be picked up.
>
> > -----Original Message-----
> > From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-
> > bounces@yoctoproject.org] On Behalf Of Nelson, Sam
> > Sent: Monday, November 14, 2016 10:49 AM
> > To: meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] [PATCH] mpm-transport: Update commit id with fixes
> >
> > NAK
> > Ignore this.
> >
> > > -----Original Message-----
> > > From: Nelson, Sam
> > > Sent: Saturday, November 12, 2016 9:46 AM
> > > To: meta-ti@yoctoproject.org
> > > Cc: Nelson, Sam
> > > Subject: [PATCH] mpm-transport: Update commit id with fixes
> > >
> > > Update and fixes to handle different type of memory sections in sysfs
> > > entry or device tree.
> > >
> > > Signed-off-by: Sam Nelson <sam.nelson@ti.com>
> > > ---
> > > recipes-ti/mpm-transport/mpm-transport_git.bb | 6 +++---
> > > 1 file changed, 3 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/recipes-ti/mpm-transport/mpm-transport_git.bb b/recipes-
> > > ti/mpm-transport/mpm-transport_git.bb
> > > index 51b5e9e..ee28f2f 100644
> > > --- a/recipes-ti/mpm-transport/mpm-transport_git.bb
> > > +++ b/recipes-ti/mpm-transport/mpm-transport_git.bb
> > > @@ -15,11 +15,11 @@ PACKAGE_ARCH = "${MACHINE_ARCH}"
> > > SRC_URI = "git://git.ti.com/keystone-linux/mpm-
> > > transport.git;protocol=git;branch=${BRANCH}"
> > >
> > > BRANCH = "master"
> > > -# This commit corresponds to tag DEV.MPM-TRANSPORT-02.00.02.00 -
> > > SRCREV = "696a9ec37559b671860ef393194c6032b7b6d9ef"
> > > +# This commit corresponds to tag DEV.MPM-TRANSPORT-02.00.02.00A
> > > SRCREV
> > > += "7284e75d36b265ef8535d2e2ee54d1f2c700e862"
> > >
> > > PV = "2.0.2.0"
> > > -PR = "r0"
> > > +PR = "r1"
> > >
> > > EXTRA_OEMAKE = "PDK_INSTALL_PATH=${STAGING_INCDIR}"
> > > EXTRA_OEMAKE_append_k2hk-evm += "HYPLNK_TRANSPORT=true
> > > SRIO_TRANSPORT=true"
> > > --
> > > 1.9.1
> >
> > --
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
> --
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
next prev parent reply other threads:[~2016-12-07 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 14:46 [PATCH] mpm-transport: Update commit id with fixes Sam Nelson
2016-11-14 15:49 ` Nelson, Sam
2016-11-28 15:36 ` Nelson, Sam
2016-12-07 1:28 ` Denys Dmytriyenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-12-07 16:33 Sam Nelson
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=20161207012833.GN28380@edge \
--to=denys@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=sam.nelson@ti.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 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.