linux-kernel - Re: [PATCH] MAINTAINERS: Add source tree entry for kunit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20230613000130.85038-1-sj@kernel.org>
Date:   Tue, 13 Jun 2023 00:01:30 +0000
From:   SeongJae Park <sj@...nel.org>
To:     David Gow <davidgow@...gle.com>
Cc:     SeongJae Park <sj@...nel.org>, brendanhiggins@...gle.com,
        linux-kselftest@...r.kernel.org, kunit-dev@...glegroups.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add source tree entry for kunit

On Tue, 13 Jun 2023 07:54:01 +0800 David Gow <davidgow@...gle.com> wrote:

> [-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
> 
> On Sun, 11 Jun 2023 at 02:05, SeongJae Park <sj@...nel.org> wrote:
> >
> > Patches for kunit are managed in linux-kselftest tree before merged into
> > the mainline, but the MAINTAINERS section for kunit doesn't have the
> > entry for the tree.  Add it.
> >
> > Signed-off-by: SeongJae Park <sj@...nel.org>
> > ---
> 
> Thanks very much.

My pleasure! :)

> 
> Given KUnit work happens in the kunit and kunit-fixes branches here,
> should we note those as well?

That makes sense, I will add those in the commit message with the next version
of this.

> 
> -- David
> 
> 
> >  MAINTAINERS | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index ce5f343c1443..8a217438956b 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -11327,6 +11327,7 @@ L:      linux-kselftest@...r.kernel.org
> >  L:     kunit-dev@...glegroups.com
> >  S:     Maintained
> >  W:     https://google.github.io/kunit-docs/third_party/kernel/docs/
> > +T:     git git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git
> 
> Should we also mention the branch here:
> git git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git
> kunit

I think so.  Would you prefer having only one 'T' line with 'kunit' branch?
Or, both branches like below?  I have no strong opinion.

T:     git git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git kunit
T:     git git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git kunit-fixes


Thanks,
SJ

> 
> >  F:     Documentation/dev-tools/kunit/
> >  F:     include/kunit/
> >  F:     lib/kunit/
> > --
> > 2.25.1
> >
>