Thorsten Leemhuis ([email protected])

Number of posts: 521 (0.19 per day)
First post: 2016-12-27 07:48:20
Last post: 2024-06-12 09:16:06

Date List Subject
2024-06-12 09:16:06 linux-kernel Re: [PATCH v5] checkpatch: check for missing Fixes tags
2024-06-12 06:48:14 linux-kernel Re: [PATCH v5] checkpatch: check for missing Fixes tags
2024-06-11 09:05:55 linux-kernel Re: [PATCH 05/14] tracefs: replace call_rcu by kfree_rcu for simple kmem_cache_free callback
2024-06-06 18:24:02 linux-kernel Re: [PATCH 6.9 000/374] 6.9.4-rc1 review
2024-06-06 10:35:13 linux-kernel Re: [PATCH net-next v2] net: ti: icssg-prueth: Split out common object into module
2024-06-05 09:45:04 linux-kernel Re: [PATCH net-next] net: ethernet: ti: Makefile: Add icssg_queues.o in TI_ICSSG_PRUETH_SR1
2024-06-03 09:24:48 linux-kernel Re: "ERROR: modpost: "icssg_queue_pop" [...] undefined" on arm64
2024-06-03 07:09:55 linux-kernel "ERROR: modpost: "icssg_queue_pop" [...] undefined" on arm64 (was: [PATCH net-next v6 1/3] net: ti: icssg-prueth: Add helper functions to configure FDB)
2024-05-13 06:49:53 linux-kernel Re: [PATCH docs-next v2] docs: handling-regressions.rst: recommend using "Closes:" tags
2024-05-12 07:47:47 linux-kernel Re: [PATCH docs-next v2] docs: handling-regressions.rst: recommend using "Closes:" tags
2024-04-29 08:31:11 linux-kernel Re: [PATCH v2 4/5] docs: stable-kernel-rules: explain use of [email protected] (w/o @vger.)
2024-04-29 07:19:49 linux-kernel [PATCH v2 0/5] docs: stable-kernel-rules: fine-tuning and 'no stable backport' tag
2024-04-29 07:19:23 linux-kernel [PATCH v2 3/5] docs: stable-kernel-rules: remove code-labels tags and a indention level
2024-04-29 07:19:13 linux-kernel [PATCH v2 4/5] docs: stable-kernel-rules: explain use of [email protected] (w/o @vger.)
2024-04-29 07:19:09 linux-kernel [PATCH v2 1/5] docs: stable-kernel-rules: reduce redundancy
2024-04-29 07:19:03 linux-kernel [PATCH v2 5/5] docs: stable-kernel-rules: create special tag to flag 'no backporting'
2024-04-29 07:18:54 linux-kernel [PATCH v2 2/5] docs: stable-kernel-rules: call mainline by its name and change example
2024-04-23 07:28:59 linux-kernel Re: Please create the email alias [email protected] -> /dev/null
2024-04-22 15:50:33 linux-kernel Re: Please create the email alias [email protected] -> /dev/null
2024-04-18 07:05:19 linux-kernel Re: Please create the email alias [email protected] -> /dev/null
2024-04-17 13:32:51 linux-kernel Re: Please create the email alias [email protected] -> /dev/null
2024-04-17 07:48:36 linux-kernel Please create the email alias [email protected] -> /dev/null
2024-04-11 09:58:08 linux-kernel Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
2024-04-11 07:51:06 linux-kernel Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
2024-04-11 07:18:51 linux-kernel Re: [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example
2024-04-11 06:59:56 linux-kernel Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
2024-04-11 06:59:18 linux-kernel Re: [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example
2024-04-11 05:50:44 linux-kernel Re: [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example
2024-04-11 05:30:27 linux-kernel Re: Do we need a "DoNotBackPort" tag?
2024-04-11 05:26:04 linux-kernel [PATCH v1 1/4] docs: stable-kernel-rules: reduce redundancy
2024-04-11 05:26:00 linux-kernel [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example
2024-04-11 05:25:44 linux-kernel [PATCH v1 0/4] docs: stable-kernel-rules: fine-tuning and 'no semi-automatic backport'
2024-04-11 05:25:36 linux-kernel [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
2024-04-11 05:25:35 linux-kernel [PATCH v1 4/4] docs: stable-kernel-rules: remove code-labels tags
2024-04-09 07:35:33 linux-kernel [PATCH v2 3/6] docs: verify/bisect: proper headlines and more spacing
2024-04-09 07:33:02 linux-kernel [PATCH v2 5/6] docs: verify/bisect: describe how to use a build host
2024-04-09 07:32:14 linux-kernel [PATCH v2 4/6] docs: verify/bisect: explain testing reverts, patches and newer code
2024-04-09 07:32:12 linux-kernel [PATCH v2 6/6] docs: verify/bisect: stable regressions: first stable, then mainline
2024-04-09 07:32:08 linux-kernel [PATCH v2 2/6] docs: verify/bisect: add and fetch stable branches ahead of time
2024-04-09 07:32:06 linux-kernel [PATCH v2 0/6] docs: verify/bisect: fine tuning, testing fixes, build host, order
2024-04-09 07:31:51 linux-kernel [PATCH v2 1/6] docs: verify/bisect: use git switch, tag kernel, and various fixes
2024-04-03 14:16:56 linux-kernel Re: [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too
2024-04-02 09:28:19 linux-kernel Re: [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too
2024-04-01 09:30:52 linux-kernel [PATCH v1 1/3] docs: verify/bisect: git switch; proper headlines; various fixes;
2024-04-01 09:30:25 linux-kernel [PATCH v1 2/3] docs: verify/bisect: explain testing reverts, patches and newer code
2024-04-01 09:30:07 linux-kernel [PATCH v1 3/3] docs: verify/bisect: describe how to use a build host
2024-04-01 09:30:06 linux-kernel [PATCH v1 0/3] docs: verify/bisect: fine tuning, testing fixes, and using a build host
2024-04-01 08:39:31 linux-kernel Re: [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too
2024-03-26 12:26:51 linux-kernel [RFC PATCH v1 2/2] docs: reporting-issue: rework the TLDR
2024-03-26 12:22:53 linux-kernel [RFC PATCH v1 1/2] docs: reporting-issue: rework the detailed guide
2024-03-26 12:22:37 linux-kernel [RFC PATCH v1 0/2] docs: reporting-issues: rework while involving the 'verify bugs' text