Skip to contentSkip to conversation

MAINTAINERS: Add source tree entry for kunit

PATCH Superseded SeongJae Park 2 participants 4 messages Jun 10, 2023 – Jun 13, 2023 Kselftest

v1 of 2 Superseded Latest is v2 →

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 MAINTAINERS: Add source tree entry for kunit

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.

---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)
MAINTAINERS +1 -0
index ce5f343c1443..8a217438956b 100644
@@ -11327,6 +11327,7 @@ L:	[email protected]
 L:	[email protected]
 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
 F:	Documentation/dev-tools/kunit/
 F:	include/kunit/
 F:	lib/kunit/
Signature · 1 line
2.25.1
#1 lore raw
Quoted 7 lines · SeongJae Park

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.

---

Thanks very much.

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

-- David

MAINTAINERS L: [email protected] · line 11330

Quoted 12 lines
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)
MAINTAINERS +1 -0
index ce5f343c1443..8a217438956b 100644
@@ -11327,6 +11327,7 @@ L:      [email protected]
 L:     [email protected]
 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

Quoted 6 lines
MAINTAINERS +0 -1
 F:     Documentation/dev-tools/kunit/
 F:     include/kunit/
 F:     lib/kunit/
--

2.25.1

#2 lore raw
Quoted 4 lines · On Tue, 13 Jun 2023 07:54:01 +0800 David Gow <[email protected]> wrote:

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]

Quoted 1 line · SeongJae Park
Quoted 8 lines
Quoted 6 lines

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.

---

Thanks very much.

My pleasure! :)

Quoted 3 lines

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.

Quoted 7 lines

-- David

Quoted 3 lines
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)
Quoted 13 lines

MAINTAINERS L: [email protected] · line 11330

Quoted 9 lines
MAINTAINERS +1 -0
index ce5f343c1443..8a217438956b 100644
@@ -11327,6 +11327,7 @@ L:      [email protected]
 L:     [email protected]
 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

Quoted 8 lines
Quoted 7 lines
MAINTAINERS +0 -1
 F:     Documentation/dev-tools/kunit/
 F:     include/kunit/
 F:     lib/kunit/
--

2.25.1

#3 lore raw
Quoted 46 lines · SeongJae Park
Quoted 4 lines · On Tue, 13 Jun 2023 07:54:01 +0800 David Gow <[email protected]> wrote:

[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]

Quoted 1 line · SeongJae Park
Quoted 8 lines
Quoted 6 lines

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.

---

Thanks very much.

My pleasure! :)

Quoted 3 lines

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.

Quoted 7 lines

-- David

Quoted 3 lines
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)
Quoted 13 lines

MAINTAINERS L: [email protected] · line 11330

Quoted 9 lines
MAINTAINERS +1 -0
index ce5f343c1443..8a217438956b 100644
@@ -11327,6 +11327,7 @@ L:      [email protected]
 L:     [email protected]
 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

Quoted 7 lines

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

Let's go with both, assuming no-one else objects.

Cheers,
-- David