public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: srinuvasanasv@gmail.com, isar-users <isar-users@googlegroups.com>
Subject: Re: linux perf_4.19
Date: Tue, 2 Jul 2019 13:38:00 +0200	[thread overview]
Message-ID: <866f4164-0dc6-beba-ea97-c9904b4bc391@siemens.com> (raw)
In-Reply-To: <4aafffd4-e6ed-4db1-a93b-dc853aa5dc84@googlegroups.com>

On 02.07.19 13:30, srinuvasanasv@gmail.com wrote:
> Hi All,
> 
>                 We need to support perf tool in linux-cip 4.19 kernel, Is it 
> available perf_4.19 in ISAR?
> 

Let's start differently:

- describe the problem you are facing (Debian perf vs. perf from custom
   kernels)
- describe your current downstream approach to resolve that (ideally
   with code)
- ask for feedback / suggestions how to address that in Isar generically

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2019-07-02 11:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-02 11:30 srinuvasanasv
2019-07-02 11:38 ` Jan Kiszka [this message]
2019-07-02 12:14   ` chombourger
2019-07-02 17:31     ` Jan Kiszka

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=866f4164-0dc6-beba-ea97-c9904b4bc391@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=srinuvasanasv@gmail.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