From: "vijaikumar....@gmail.com" <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v4] Add recipe for linux kselftest
Date: Thu, 22 Apr 2021 04:49:54 -0700 (PDT) [thread overview]
Message-ID: <e6217dcf-0384-4647-aa0a-bd67ae144703n@googlegroups.com> (raw)
In-Reply-To: <CALLGG_KNgGEWyi5hoPy-S_m9Ef85eWWJTT02hGG=qHfeen3ieA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2407 bytes --]
Are there any more review comments on this?
On Tuesday, March 30, 2021 at 2:41:20 PM UTC+5:30 vijaikumar....@gmail.com
wrote:
> On Thu, Feb 18, 2021 at 10:41 AM vijaikumar....@gmail.com
> <vijaikumar....@gmail.com> wrote:
> >
> > Hi Baurzhan,
> > On Monday, February 15, 2021 at 8:46:13 PM UTC+5:30 i...@radix50.net
> wrote:
> >>
> >> On Wed, Feb 10, 2021 at 11:21:46AM +0100, Henning Schild wrote:
> >> > 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.
> >>
> >> Thanks Henning for the feedback.
> >>
> >> @Vijai Kumar: After seeing the perf implementation, I wonder whether we
> could
> >> harmonize towards the existing kernel infrastructure here as well. What
> do you
> >> think?
> >
> >
> > I did not get a chance to look at that series yet. Will have a look and
> get back.
>
> Hi Baurzhan,
>
> Just had a look at that series. Seems like we backport the necessary
> patches for the particular kernel version.
> This might be hard here, since the changes might me more.
>
> The original intention to have this package as a separate recipe is to
> provide means to use the latest kernel
> kselftest testcases. Those seem to be more mature than one available
> in lower kernel versions like 4.19.
>
> The changes might be too much to backport making the approach more
> complicated.
>
> In our usecase we are using the cip kernel, and if someone feels like
> some testcases needs to be backported,
> it needs to be done in the cip-kernel project and not it ISAR. But
> there is no strong requirement from the users
> for that, they are just okay with using the version that is available
> in the latest kernel. This recipe just makes them
> achieve that.
>
> Thanks,
> Vijai Kumar K
>
> >
> > Thanks,
> > Vijai Kumar K
> >
> >>
> >>
> >> With kind regards,
> >> Baurzhan.
> >
> > --
> > You received this message because you are subscribed to a topic in the
> Google Groups "isar-users" group.
> > To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/isar-users/_GrkFK64py4/unsubscribe.
> > To unsubscribe from this group and all its topics, send an email to
> isar-users+...@googlegroups.com.
> > To view this discussion on the web visit
> https://groups.google.com/d/msgid/isar-users/96f074be-a70e-43d7-9eab-e74be12ed444n%40googlegroups.com
> .
>
[-- Attachment #1.2: Type: text/html, Size: 3727 bytes --]
next prev parent reply other threads:[~2021-04-22 11:49 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
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 [this message]
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=e6217dcf-0384-4647-aa0a-bd67ae144703n@googlegroups.com \
--to=vijaikumar.kanagarajan@gmail.com \
--cc=isar-users@googlegroups.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