public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "vijaikumar....@gmail.com" <vijaikumar.kanagarajan@gmail.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v4] Add recipe for linux kselftest
Date: Wed, 10 Feb 2021 11:21:46 +0100	[thread overview]
Message-ID: <20210210112146.511b395a@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <3cfa4810-eeb3-4a66-9558-bbd52b89731cn@googlegroups.com>

Am Tue, 9 Feb 2021 22:34:42 -0800 (PST)
schrieb "vijaikumar....@gmail.com" <vijaikumar.kanagarajan@gmail.com>:

> On Monday, February 8, 2021 at 9:03:56 PM UTC+5:30 ami...@ilbers.de
> wrote:
> 
> > 26.11.2020 21:38, vijaikumar....@gmail.com wrote:
> >
> >
> >
> > On Friday, November 6, 2020 at 7:08:25 PM UTC+5:30 Henning Schild
> > wrote: 
> >> Am Wed, 4 Nov 2020 22:17:29 -0800 (PST) 
> >> schrieb "vijaikumar....@gmail.com" <vijaikumar....@gmail.com>: 
> >>  
> >> > On Thursday, November 5, 2020 at 2:14:50 AM UTC+5:30 Henning
> >> > Schild wrote: 
> >> >   
> >> > > Did not follow the thread and coming late to the table. Did
> >> > > anyone consider pushing this upstream into the kernel? 
> >> > >   
> >> > 
> >> > No. Atleast, I did not try it.   
> >>
> >> Ok, we already have other tools like perf and the kernel does not
> >> seem to like debianizations in its tree. 
> >>
> >> Henning 
> >>  
> >
> > Hi Henning,
> >
> > Is this good to go? Or should we try to do this upstream? Maybe
> > both.
> >
> > Thanks,
> > Vijai Kumar K
> >
> > Hello, what is the status of this? Can we proceed with apply?
> >  
> 
> 
> Ok from my end. Lets see what Henning has to say.

I did not actually review it. The one question with the mainlining has
been answered. It is not nice but the debianization of the kernel is
isar business.

So for this one question ... good to go.

Henning

> 
> > -- 
> > Anton Mikanovich
> > Promwad Ltd.
> > External service provider of ilbers GmbH
> > Maria-Merian-Str. 8
> > 85521 Ottobrunn, Germany
> > +49 (89) 122 67 24-0
> > Commercial register Munich, HRB 214197
> > General Manager: Baurzhan Ismagulov
> >
> >  
> 


  reply	other threads:[~2021-02-10 10:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02  7:25 Vijai Kumar K
2020-11-04 20:44 ` Henning Schild
2020-11-05  6:17   ` vijaikumar....@gmail.com
2020-11-06 13:38     ` Henning Schild
2020-11-26 18:38       ` vijaikumar....@gmail.com
2021-02-08 15:33         ` Anton Mikanovich
2021-02-10  6:34           ` vijaikumar....@gmail.com
2021-02-10 10:21             ` Henning Schild [this message]
2021-02-15 15:16               ` Baurzhan Ismagulov
2021-02-18  5:11                 ` vijaikumar....@gmail.com
2021-03-30  9:11                   ` vijai kumar
2021-04-22 11:49                     ` vijaikumar....@gmail.com
2021-04-26 13:40                     ` Baurzhan Ismagulov
2021-05-06 12:20 ` Anton Mikanovich

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=20210210112146.511b395a@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=vijaikumar.kanagarajan@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