From: Khem Raj <raj.khem@gmail.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] trace-cmd: Update to version 2.3.2
Date: Wed, 6 Aug 2014 23:27:22 -0700 [thread overview]
Message-ID: <20140807062722.GB4171@haswell> (raw)
In-Reply-To: <53E2B628.7030507@linux.intel.com>
On 14-08-06 16:11:36, Saul Wold wrote:
> On 08/06/2014 10:23 AM, Yasir Khan wrote:
> >From: Yasir-Khan <yasir_khan@mentor.com>
> >
> >Current trace-cmd version 1.2 throws "recorder error in
> >splice input" error while recording a trace on kernel
> >version 3.10. Update the trace-cmd version to latest 2.3.2
> >to resolve this error.
> >
> >Signed-off-by: Yasir-Khan <yasir_khan@mentor.com>
> >---
> > ...dd-checks-for-invalid-pointers-to-fix-seg.patch | 61 -------------
> > ...o-not-call-stop_threads-if-doing-latency-.patch | 38 --------
> > ...etting-plugin-to-nop-clears-data-before-i.patch | 96 --------------------
> > .../trace-cmd-fix-syntax-error-of-shell.patch | 30 ------
>
> We like to know why the patches are removed in the commit message, I know
> most of the patches are backports, but tell us that in the commit message
> still.
>
> Thanks
> Sau!
>
> >
> > LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe \
> >- file://trace-cmd.c;beginline=6;endline=8;md5=2c22c965a649ddd7973d7913c5634a5e \
> >+ file://trace-cmd.c;beginline=6;endline=8;md5=2c22c965a649ddd7973d7913c5634a5e \
this change looks redundant as well.
next prev parent reply other threads:[~2014-08-07 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 17:23 [PATCH] trace-cmd: Update to version 2.3.2 Yasir Khan
2014-08-06 23:11 ` Saul Wold
2014-08-07 6:27 ` Khem Raj [this message]
2014-08-07 8:26 ` Fathi Boudra
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=20140807062722.GB4171@haswell \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.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