Workflows

• Thread Index

• [PATCH v2] kernel-docs: Add new section for Rust learning materials
  • From: Carlos Bilbao <carlos.bilbao.osdev@xxxxxxxxx>
• Re: [PATCH] kernel-docs: Add new section for Rust learning materials
  • From: Carlos Bilbao <carlos.bilbao.osdev@xxxxxxxxx>
• Re: [PATCH] kernel-docs: Add new section for Rust learning materials
  • From: Dirk Behme <dirk.behme@xxxxxxxxxxxx>
• [PATCH] kernel-docs: Add new section for Rust learning materials
  • From: Carlos Bilbao <carlos.bilbao.osdev@xxxxxxxxx>
• Re: [PATCH v2] docs/process: fix typos
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [PATCH v2] docs/process: fix typos
  • From: Andrew Kreimer <algonell@xxxxxxxxx>
• Re: [PATCH] docs/process: fix typos
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [PATCH] docs/process: fix typos
  • From: Andrew Kreimer <algonell@xxxxxxxxx>
• Re: [PATCH V2] Documentation: Fix spelling mistakes
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v2] docs: Move fault injection section to dev-tools
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v2] docs: submitting-patches: Advertise b4
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v2] docs: submitting-patches: Advertise b4
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• [PATCH v2] docs: submitting-patches: Advertise b4
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v2] docs: Move fault injection section to dev-tools
  • From: Carlos Bilbao <carlos.bilbao.osdev@xxxxxxxxx>
• Re: [PATCH] docs: submitting-patches: Advertise b4
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH] docs: submitting-patches: Advertise b4
  • From: Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx>
• Re: [PATCH] docs: submitting-patches: Advertise b4
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• [PATCH] docs: submitting-patches: Advertise b4
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH] docs: submitting-patches: Advertise b4
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH] docs: submitting-patches: Advertise b4
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH] Documentation: maintainer: Improve grammar in mailing list participation section
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• [PATCH] Documentation: maintainer: Improve grammar in mailing list participation section
  • From: Steven Davis <goldside000@xxxxxxxxxxx>
• Re: [PATCH v2] docs: Move fault injection section to dev-tools
  • From: Alex Shi <seakeel@xxxxxxxxx>
• [PATCH v2] docs: Move fault injection section to dev-tools
  • From: Breno Leitao <leitao@xxxxxxxxxx>
• [PATCH] docs: Move fault injection section to dev-tools
  • From: Breno Leitao <leitao@xxxxxxxxxx>
• Re: [PATCH V2] Documentation: Fix spelling mistakes
  • From: Bjorn Helgaas <helgaas@xxxxxxxxxx>
• Re: [PATCH V2] Documentation: Fix spelling mistakes
  • From: Amit Vadhavana <av2082000@xxxxxxxxx>
• Re: [PATCH] docs: process: fix typos in Documentation/process/backporting.rst
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH] docs: process: fix typos in Documentation/process/backporting.rst
  • From: Bagas Sanjaya <bagasdotme@xxxxxxxxx>
• Re: [PATCH] docs: process: fix typos in Documentation/process/backporting.rst
  • From: Vegard Nossum <vegard.nossum@xxxxxxxxxx>
• [PATCH] docs: process: fix typos in Documentation/process/backporting.rst
  • From: Aryabhatta Dey <aryabhattadey35@xxxxxxxxx>
• [PATCH V2] Documentation: Fix spelling mistakes
  • From: Amit Vadhavana <av2082000@xxxxxxxxx>
• Re: [PATCH] Documentation: Fix spelling mistakes
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH] Documentation: Fix spelling mistakes
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH] Documentation: Fix spelling mistakes
  • From: Ivan Orlov <ivan.orlov0322@xxxxxxxxx>
• [PATCH] Documentation: Fix spelling mistakes
  • From: Amit Vadhavana <av2082000@xxxxxxxxx>
• Re: [PATCH] docs: improve comment consistency in .muttrc example configuration
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [PATCH] docs: improve comment consistency in .muttrc example configuration
  • From: Jiamu Sun <barroit@xxxxxxxxx>
• Re: [PATCH 1/2] Documentation: embargoed-hardware-issues.rst: minor cleanups and fixes
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] Documentation: embargoed-hardware-issues.rst: minor cleanups and fixes
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [PATCH 1/2] Documentation: embargoed-hardware-issues.rst: minor cleanups and fixes
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH 2/2] Documentation: embargoed-hardware-issues.rst: add a section documenting the "early access" process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] MAINTAINERS: add Documentation/dev-tools/ to workflows@
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [PATCH v2] MAINTAINERS: add Documentation/dev-tools/ to workflows@
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: add Documentation/dev-tools/ to workflows@
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH] MAINTAINERS: add Documentation/dev-tools/ to workflows@
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• [PATCH] MAINTAINERS: add Documentation/dev-tools/ to workflows@
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Is there an integrated b4 + patchwork guide for maintainers?
  • From: Jeff Johnson <quic_jjohnson@xxxxxxxxxxx>
• Re: [PATCH v2] docs: maintainer: discourage taking conversations off-list
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH v2] docs: maintainer: discourage taking conversations off-list
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Carlos Bilbao <carlos.bilbao.osdev@xxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Mauro Carvalho Chehab <mchehab+huawei@xxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] docs: maintainer: discourage taking conversations off-list
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: [PATCH v2 00/13] Support several Rust toolchain versions
  • From: Miguel Ojeda <miguel.ojeda.sandonis@xxxxxxxxx>
• [PATCH v2 13/13] docs: rust: quick-start: add section on Linux distributions
  • From: Miguel Ojeda <ojeda@xxxxxxxxxx>
• [PATCH v2 06/13] rust: start supporting several compiler versions
  • From: Miguel Ojeda <ojeda@xxxxxxxxxx>
• [PATCH v2 00/13] Support several Rust toolchain versions
  • From: Miguel Ojeda <ojeda@xxxxxxxxxx>
• Re: [PATCH 1/3] kbuild: raise the minimum GNU Make requirement to 4.0
  • From: Nathan Chancellor <nathan@xxxxxxxxxx>
• Re: [PATCH 13/13] docs: rust: quick-start: add section on Linux distributions
  • From: Miguel Ojeda <miguel.ojeda.sandonis@xxxxxxxxx>
• Re: [PATCH 13/13] docs: rust: quick-start: add section on Linux distributions
  • From: Fabian Grünbichler <debian@fabian.gruenbichler.email>
• Re: [PATCH 13/13] docs: rust: quick-start: add section on Linux distributions
  • From: Andrea Righi <righi.andrea@xxxxxxxxx>
• Re: [PATCH 13/13] docs: rust: quick-start: add section on Linux distributions
  • From: Miguel Ojeda <miguel.ojeda.sandonis@xxxxxxxxx>
• Re: [PATCH 13/13] docs: rust: quick-start: add section on Linux distributions
  • From: Miguel Ojeda <miguel.ojeda.sandonis@xxxxxxxxx>
• Re: [PATCH 13/13] docs: rust: quick-start: add section on Linux distributions
  • From: Fabian Grünbichler <debian@fabian.gruenbichler.email>
• Re: [PATCH 13/13] docs: rust: quick-start: add section on Linux distributions
  • From: Andrea Righi <righi.andrea@xxxxxxxxx>
• Re: [PATCH 06/13] rust: start supporting several compiler versions
  • From: Miguel Ojeda <miguel.ojeda.sandonis@xxxxxxxxx>
• Re: [PATCH 06/13] rust: start supporting several compiler versions
  • From: Miguel Ojeda <miguel.ojeda.sandonis@xxxxxxxxx>
• [PATCH 1/3] kbuild: raise the minimum GNU Make requirement to 4.0
  • From: Masahiro Yamada <masahiroy@xxxxxxxxxx>
• Re: [PATCH v2 0/2] Documentation: update information for mailing lists
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH 06/13] rust: start supporting several compiler versions
  • From: Andreas Hindborg <nmi@xxxxxxxxxxxx>
• Re: [PATCH v2 0/2] Documentation: update information for mailing lists
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• [PATCH 13/13] docs: rust: quick-start: add section on Linux distributions
  • From: Miguel Ojeda <ojeda@xxxxxxxxxx>
• [PATCH 06/13] rust: start supporting several compiler versions
  • From: Miguel Ojeda <ojeda@xxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH 0/7] minor document fixups
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH 7/7] Docs/process/email-clients: Document HacKerMaiL
  • From: SeongJae Park <sj@xxxxxxxxxx>
• Re: [PATCH 7/7] Docs/process/email-clients: Document HacKerMaiL
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH 3/7] Docs: Move magic-number from process to staging
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH 7/7] Docs/process/email-clients: Document HacKerMaiL
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 3/7] Docs: Move magic-number from process to staging
  • From: Federico Vaga <federico.vaga@xxxxxxxxxx>
• Re: [PATCH 4/7] Docs: Move clang-format from process/ to dev-tools/
  • From: Federico Vaga <federico.vaga@xxxxxxxxxx>
• Re: [PATCH 4/7] Docs: Move clang-format from process/ to dev-tools/
  • From: Miguel Ojeda <miguel.ojeda.sandonis@xxxxxxxxx>
• [PATCH 7/7] Docs/process/email-clients: Document HacKerMaiL
  • From: SeongJae Park <sj@xxxxxxxxxx>
• [PATCH 6/7] Docs/maintainer/maintainer-entry-profile: add DAMON maintainer profile
  • From: SeongJae Park <sj@xxxxxxxxxx>
• [PATCH 5/7] Docs/process/index: Remove unsorted docs section
  • From: SeongJae Park <sj@xxxxxxxxxx>
• [PATCH 4/7] Docs: Move clang-format from process/ to dev-tools/
  • From: SeongJae Park <sj@xxxxxxxxxx>
• [PATCH 3/7] Docs: Move magic-number from process to staging
  • From: SeongJae Park <sj@xxxxxxxxxx>
• [PATCH 2/7] Docs/process/index: Remove riscv/patch-acceptance from 'Other material' section
  • From: SeongJae Park <sj@xxxxxxxxxx>
• [PATCH 1/7] Docs/process/index: Remove unaligned-memory-access from 'Other material'
  • From: SeongJae Park <sj@xxxxxxxxxx>
• [PATCH 0/7] minor document fixups
  • From: SeongJae Park <sj@xxxxxxxxxx>
• Re: [PATCH v2 0/2] Documentation: update information for mailing lists
  • From: Carlos Bilbao <carlos.bilbao.osdev@xxxxxxxxx>
• Re: [PATCH 1/2] Documentation: fix links to mailing list services
  • From: Carlos Bilbao <carlos.bilbao.osdev@xxxxxxxxx>
• Re: [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: Carlos Bilbao <carlos.bilbao.osdev@xxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: Kees Cook <kees@xxxxxxxxxx>
• Re: [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [PATCH v2 2/2] Documentation: best practices for using Link trailers
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• [PATCH v2 1/2] Documentation: fix links to mailing list services
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• [PATCH v2 0/2] Documentation: update information for mailing lists
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5] Documentation: cve Korean translation
  • From: Yunseong Kim <yskelg@xxxxxxxxx>
• Re: [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: Jani Nikula <jani.nikula@xxxxxxxxx>
• Re: [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: Leon Romanovsky <leon@xxxxxxxxxx>
• Re: [PATCH 1/2] Documentation: fix links to mailing list services
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2/2] Documentation: best practices for using Link trailers
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• [PATCH 1/2] Documentation: fix links to mailing list services
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• [PATCH 0/2] Documentation: update information for mailing lists
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5] Documentation: cve Korean translation
  • From: SeongJae Park <sj@xxxxxxxxxx>
• Re: [PATCH v5] Documentation: cve Korean translation
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v2 2/2] docs: stable-kernel-rules: remind reader about DCO
  • From: Paul Barker <paul.barker.ct@xxxxxxxxxxxxxx>
• [PATCH v2 2/2] docs: stable-kernel-rules: remind reader about DCO
  • From: Shung-Hsi Yu <shung-hsi.yu@xxxxxxxx>
• [PATCH v2 1/2] docs: stable-kernel-rules: provide example of specifing target series
  • From: Shung-Hsi Yu <shung-hsi.yu@xxxxxxxx>
• Re: [PATCH 2/2] docs: stable-kernel-rules: remind reader about DCO
  • From: Shung-Hsi Yu <shung-hsi.yu@xxxxxxxx>
• Re: [PATCH 05/14] tracefs: replace call_rcu by kfree_rcu for simple kmem_cache_free callback
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 05/14] tracefs: replace call_rcu by kfree_rcu for simple kmem_cache_free callback
  • From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
• Re: [PATCH 05/14] tracefs: replace call_rcu by kfree_rcu for simple kmem_cache_free callback
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 05/14] tracefs: replace call_rcu by kfree_rcu for simple kmem_cache_free callback
  • From: Steven Rostedt <rostedt@xxxxxxxxxxx>
• Re: [PATCH 05/14] tracefs: replace call_rcu by kfree_rcu for simple kmem_cache_free callback
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH 05/14] tracefs: replace call_rcu by kfree_rcu for simple kmem_cache_free callback
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH 05/14] tracefs: replace call_rcu by kfree_rcu for simple kmem_cache_free callback
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 05/14] tracefs: replace call_rcu by kfree_rcu for simple kmem_cache_free callback
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH 2/2] docs: stable-kernel-rules: remind reader about DCO
  • From: Paul Barker <paul.barker.ct@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] docs: stable-kernel-rules: provide example of specifying target series
  • From: Paul Barker <paul.barker.ct@xxxxxxxxxxxxxx>
• [PATCH 2/2] docs: stable-kernel-rules: remind reader about DCO
  • From: Shung-Hsi Yu <shung-hsi.yu@xxxxxxxx>
• [PATCH 1/2] docs: stable-kernel-rules: provide example of specifying target series
  • From: Shung-Hsi Yu <shung-hsi.yu@xxxxxxxx>
• [PATCH v5] Documentation: cve Korean translation
  • From: yskelg@xxxxxxxxx
• Re: [PATCH v4] Documentation: cve Korean translation
  • From: SeongJae Park <sj@xxxxxxxxxx>
• [PATCH v4] Documentation: cve Korean translation
  • From: yskelg@xxxxxxxxx
• Re: [PATCH] docs: document python version used for compilation
  • From: "Thierry Reding" <thierry.reding@xxxxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH docs-next v3] docs: handling-regressions.rst: recommend using "Closes:" tags
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v1] Documentation: process: Revert "Document suitability of Proton Mail for kernel development"
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: "Thierry Reding" <thierry.reding@xxxxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: "Thierry Reding" <thierry.reding@xxxxxxxxx>
• Re: [PATCH v3] Documentation: cve Korean translation
  • From: Yunseong Kim <yskelg@xxxxxxxxx>
• Re: [PATCH v2] Documentation: cve Korean translation
  • From: Yunseong Kim <yskelg@xxxxxxxxx>
• Re: [PATCH v2] Documentation: cve Korean translation
  • From: Austin Kim <austindh.kim@xxxxxxxxx>
• Re: [PATCH v3] Documentation: cve Korean translation
  • From: SeongJae Park <sj@xxxxxxxxxx>
• Re: [PATCH net] docs: netdev: Fix typo in Signed-off-by tag
  • From: patchwork-bot+netdevbpf@xxxxxxxxxx
• Re: [PATCH net] docs: netdev: Fix typo in Signed-off-by tag
  • From: Thorsten Blum <thorsten.blum@xxxxxxxxxx>
• Re: [PATCH net] docs: netdev: Fix typo in Signed-off-by tag
  • From: Andrew Lunn <andrew@xxxxxxx>
• Re: [PATCH v3] Documentation: cve Korean translation
  • From: Jinwoo Park <pmnxis@xxxxxxxxx>
• Re: [PATCH v3] Documentation: cve Korean translation
  • From: Yunseong Kim <yskelg@xxxxxxxxx>
• Re: [PATCH v3] Documentation: cve Korean translation
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v3] Documentation: cve Korean translation
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v3] Documentation: cve Korean translation
  • From: Yunseong Kim <yskelg@xxxxxxxxx>
• Re: [PATCH v3] Documentation: cve Korean translation
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [PATCH net] docs: netdev: Fix typo in Signed-off-by tag
  • From: Thorsten Blum <thorsten.blum@xxxxxxxxxx>
• [PATCH v2] Documentation: security-bugs Korean translation
  • From: yskelg@xxxxxxxxx
• [PATCH v3] Documentation: cve Korean translation
  • From: yskelg@xxxxxxxxx
• [PATCH v2] Documentation: cve Korean translation
  • From: yskelg@xxxxxxxxx
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Daniel Vetter <daniel@xxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: "Jarkko Sakkinen" <jarkko@xxxxxxxxxx>
• Re: [PATCH] Documentation: cve Korean translation
  • From: Yunseong Kim <yskelg@xxxxxxxxx>
• Re: [PATCH] Documentation: cve Korean translation
  • From: Jinwoo Park <pmnxis@xxxxxxxxx>
• Re: [PATCH v1] Documentation: process: Revert "Document suitability of Proton Mail for kernel development"
  • From: Kanak Shilledar <kanakshilledar111@xxxxxxxxxxxxxx>
• Re: [PATCH v1] Documentation: process: Revert "Document suitability of Proton Mail for kernel development"
  • From: Conor Dooley <conor@xxxxxxxxxx>
• Re: [PATCH v1] Documentation: process: Revert "Document suitability of Proton Mail for kernel development"
  • From: Kanak Shilledar <kanakshilledar111@xxxxxxxxxxxxxx>
• [PATCH v1] Documentation: process: Revert "Document suitability of Proton Mail for kernel development"
  • From: Conor Dooley <conor@xxxxxxxxxx>
• Re: [PATCH v2] docs: document python version used for compilation
  • From: Jon Hunter <jonathanh@xxxxxxxxxx>
• [PATCH docs-next v3] docs: handling-regressions.rst: recommend using "Closes:" tags
  • From: Karel Balej <balejk@xxxxxxxxx>
• Re: [PATCH docs-next v2] docs: handling-regressions.rst: recommend using "Closes:" tags
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH docs-next v2] docs: handling-regressions.rst: recommend using "Closes:" tags
  • From: "Karel Balej" <balejk@xxxxxxxxx>
• Re: [PATCH docs-next v2] docs: handling-regressions.rst: recommend using "Closes:" tags
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH v2] docs: document python version used for compilation
  • From: Abhinav Kumar <quic_abhinavk@xxxxxxxxxxx>
• [PATCH v2] docs: document python version used for compilation
  • From: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx>
• [PATCH] Documentation: cve Korean translation
  • From: yskelg@xxxxxxxxx
• [PATCH] Documentation: security-bugs Korean translation
  • From: yskelg@xxxxxxxxx
• Re: [PATCH] docs: document python version used for compilation
  • From: Rob Clark <robdclark@xxxxxxxxx>
• [PATCH docs-next v2] docs: handling-regressions.rst: recommend using "Closes:" tags
  • From: Karel Balej <balejk@xxxxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: Jon Hunter <jonathanh@xxxxxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: Jani Nikula <jani.nikula@xxxxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: Jani Nikula <jani.nikula@xxxxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: Abhinav Kumar <quic_abhinavk@xxxxxxxxxxx>
• Re: [PATCH] docs: document python version used for compilation
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [PATCH] docs: document python version used for compilation
  • From: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx>
• [PATCH v7 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH v7 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH v7 0/2] codingstyle: avoid unused parameters for a function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH v3 1/1] coding-style: recommend split headers instead of kernel.h
  • From: Yueh-Shun Li <shamrocklee@xxxxxxxxxx>
• Re: [PATCH RESEND v6 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH RESEND v6 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH RESEND v6 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [PATCH RESEND v6 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH RESEND v6 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH RESEND v6 0/2] codingstyle: avoid unused parameters for a function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH] docs: stable-kernel-rules: fix typo sent->send
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v2 0/5] docs: stable-kernel-rules: fine-tuning and 'no stable backport' tag
  • From: Jonathan Corbet <corbet@xxxxxxx>
• RE: [PATCH] docs: stable-kernel-rules: fix typo sent->send
  • From: "Bird, Tim" <Tim.Bird@xxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 4/5] docs: stable-kernel-rules: explain use of stable@xxxxxxxxxx (w/o @vger.)
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 4/5] docs: stable-kernel-rules: explain use of stable@xxxxxxxxxx (w/o @vger.)
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] docs: stable-kernel-rules: create special tag to flag 'no backporting'
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 4/5] docs: stable-kernel-rules: explain use of stable@xxxxxxxxxx (w/o @vger.)
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 3/5] docs: stable-kernel-rules: remove code-labels tags and a indention level
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 2/5] docs: stable-kernel-rules: call mainline by its name and change example
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 1/2] Documentation: process: Avoid unneeded Cc: tags
  • From: Krzysztof Kozlowski <krzk@xxxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Krzysztof Kozlowski <krzk@xxxxxxxxxx>
• [PATCH v2 0/5] docs: stable-kernel-rules: fine-tuning and 'no stable backport' tag
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [PATCH v2 4/5] docs: stable-kernel-rules: explain use of stable@xxxxxxxxxx (w/o @vger.)
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [PATCH v2 3/5] docs: stable-kernel-rules: remove code-labels tags and a indention level
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [PATCH v2 1/5] docs: stable-kernel-rules: reduce redundancy
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [PATCH v2 5/5] docs: stable-kernel-rules: create special tag to flag 'no backporting'
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [PATCH v2 2/5] docs: stable-kernel-rules: call mainline by its name and change example
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH] docs: stable-kernel-rules: fix typo sent->send
  • From: Bagas Sanjaya <bagasdotme@xxxxxxxxx>
• Re: [PATCH] docs: stable-kernel-rules: fix typo sent->send
  • From: Greg KroahHartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] docs: stable-kernel-rules: fix typo sent->send
  • From: "Bird, Tim" <Tim.Bird@xxxxxxxx>
• Re: [PATCH v6 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH v1 0/2] Documentation: process: Clarify use of Cc:
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v1 1/2] Documentation: process: Avoid unneeded Cc: tags
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Jani Nikula <jani.nikula@xxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Jani Nikula <jani.nikula@xxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Jani Nikula <jani.nikula@xxxxxxxxx>
• Re: [PATCH v1 0/2] Documentation: process: Clarify use of Cc:
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• [PATCH v1 0/2] Documentation: process: Clarify use of Cc:
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v1 1/2] Documentation: process: Avoid unneeded Cc: tags
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v1 2/2] Documentation: process: Recommend to put Cc: tags after cutter '---' line
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: David Hildenbrand <david@xxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: John Hubbard <jhubbard@xxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Eric Biggers <ebiggers@xxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Jason Gunthorpe <jgg@xxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Florian Fainelli <f.fainelli@xxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Willy Tarreau <w@xxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Re: Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Please create the email alias do-not-apply-to-stable@xxxxxxxxxx -> /dev/null
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Alex Elder <alex.elder@xxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
• [PATCH] Documentation: coding-style: don't encourage WARN*()
  • From: Alex Elder <elder@xxxxxxxxxx>
• Re: [PATCH v12 0/2] arm64: Add a build target for Flat Image Tree
  • From: Will Deacon <will@xxxxxxxxxx>
• Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH v1 4/4] docs: stable-kernel-rules: remove code-labels tags
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 1/4] docs: stable-kernel-rules: reduce redundancy
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH v1 1/4] docs: stable-kernel-rules: reduce redundancy
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [PATCH v1 3/4] docs: stable-kernel-rules: call mainline by its name and change example
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [PATCH v1 2/4] docs: stable-kernel-rules: mention "no semi-automatic backport"
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [PATCH v1 4/4] docs: stable-kernel-rules: remove code-labels tags
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [PATCH v1 0/4] docs: stable-kernel-rules: fine-tuning and 'no semi-automatic backport'
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] docs: *-regressions.rst: unify quoting, add missing word
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [RFC PATCH v1 2/2] docs: reporting-issue: rework the TLDR
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [RFC PATCH v1 1/2] docs: reporting-issue: rework the detailed guide
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH] docs: submitting-patches: describe additional tags
  • From: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx>
• [PATCH v6 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH v6 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH v6 0/2] codingstyle: avoid unused parameters for a function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] docs: *-regressions.rst: unify quoting, add missing word
  • From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@xxxxxxxxxxxxx>
• Re: [PATCH v5 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH v5 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH] docs: submitting-patches: describe additional tags
  • From: Bjorn Andersson <quic_bjorande@xxxxxxxxxxx>
• Re: [PATCH v5 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v5 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Mac Xu <mac.xxn@xxxxxxxxxxx>
• Re: [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too
  • From: "Karel Balej" <balejk@xxxxxxxxx>
• Re: [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH v5 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH v5 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Mac Xu <mac.xxn@xxxxxxxxxxx>
• Re: [PATCH] docs: submitting-patches: describe additional tags
  • From: Nikita Travkin <nikita@xxxxxxx>
• Re: [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [PATCH] docs: submitting-patches: describe additional tags
  • From: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx>
• Re: [PATCH v5 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [PATCH v5 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH v5 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH v5 0/2] codingstyle: avoid unused parameters for a function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH v4 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Mac Xu <mac.xxn@xxxxxxxxxxx>
• Re: [PATCH v4 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH v4 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Mac Xu <mac.xxn@xxxxxxxxxxx>
• Re: [PATCH v4 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Mac Xu <mac.xxn@xxxxxxxxxxx>
• Re: [PATCH v3 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH v3 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Charlemagne Lasse <charlemagnelasse@xxxxxxxxx>
• Re: [PATCH v12 2/2] arm64: boot: Support Flat Image Tree
  • From: Masahiro Yamada <masahiroy@xxxxxxxxxx>
• [PATCH v12 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• [PATCH v12 0/2] arm64: Add a build target for Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• Re: [PATCH v11 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• Re: [PATCH v4 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH 2/2] docs: handling-regressions.rst: clarify that "Closes:" tags work too
  • From: Karel Balej <balejk@xxxxxxxxx>
• [PATCH 1/2] docs: *-regressions.rst: unify quoting, add missing word
  • From: Karel Balej <balejk@xxxxxxxxx>
• [PATCH 0/2] regressions documentation improvements
  • From: Karel Balej <balejk@xxxxxxxxx>
• Re: [PATCH v4 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Jeff Johnson <quic_jjohnson@xxxxxxxxxxx>
• Re: [PATCH v4 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH v4 0/2] codingstyle: avoid unused parameters for a function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH v4 2/2] scripts: checkpatch: check unused parameters for function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH v4 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH v4 0/2] codingstyle: avoid unused parameters for a function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH v11 2/2] arm64: boot: Support Flat Image Tree
  • From: Masahiro Yamada <masahiroy@xxxxxxxxxx>
• [RFC PATCH v1 1/2] docs: reporting-issue: rework the detailed guide
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [RFC PATCH v1 0/2] docs: reporting-issues: rework while involving the 'verify bugs' text
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• [RFC PATCH v1 2/2] docs: reporting-issue: rework the TLDR
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH v3 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH] Documentation: embargoed-hardware-issues.rst: Add myself for Power
  • From: Michael Ellerman <mpe@xxxxxxxxxxxxxx>
• [PATCH v3 2/2] scripts: checkpatch: Check unused parameters for function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH v3 1/2] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• [PATCH v3 0/2] codingstyle: avoid unused parameters for a function-like macro
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Meiyong Yu <meiyong.yu@xxxxxxx>
• Re: [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Meiyong Yu <meiyong.yu@xxxxxxx>
• Re: [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [PATCH v2] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
• [PATCH] Documentation: coding-style: ask function-like macros to evaluate parameters
  • From: Barry Song <21cnbao@xxxxxxxxx>
• Re: [PATCH v2 0/2] docs: *-regressions.rst: Tweaks to the commands
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [PATCH v11 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• [PATCH v11 0/2] arm64: Add a build target for Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• Re: [PATCH 1/3] docs: submitting-patches: divert focus from PATCH in the subject line
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v10 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• [PATCH v2 2/2] docs: handling-regressions.rst: Update regzbot command fixed-by to fix
  • From: Nícolas F. R. A. Prado <nfraprado@xxxxxxxxxxxxx>
• [PATCH v2 1/2] docs: *-regressions.rst: Add colon to regzbot commands
  • From: Nícolas F. R. A. Prado <nfraprado@xxxxxxxxxxxxx>
• [PATCH v2 0/2] docs: *-regressions.rst: Tweaks to the commands
  • From: Nícolas F. R. A. Prado <nfraprado@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] docs: *-regressions.rst: Use collon after regzbot introduced command
  • From: Nícolas F. R. A. Prado <nfraprado@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] docs: handling-regressions.rst: Update regzbot command fixed-by to fix
  • From: Thorsten Leemhuis <regressions@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] docs: *-regressions.rst: Use collon after regzbot introduced command
  • From: Thorsten Leemhuis <regressions@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Maxime Ripard <mripard@xxxxxxxxxx>
• Re: [PATCH v10 2/2] arm64: boot: Support Flat Image Tree
  • From: Masahiro Yamada <masahiroy@xxxxxxxxxx>
• [PATCH 2/2] docs: handling-regressions.rst: Update regzbot command fixed-by to fix
  • From: Nícolas F. R. A. Prado <nfraprado@xxxxxxxxxxxxx>
• [PATCH 1/2] docs: *-regressions.rst: Use collon after regzbot introduced command
  • From: Nícolas F. R. A. Prado <nfraprado@xxxxxxxxxxxxx>
• [PATCH 0/2] docs: *-regressions.rst: Tweaks to the commands
  • From: Nícolas F. R. A. Prado <nfraprado@xxxxxxxxxxxxx>
• Re: [PATCH v10 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• Re: [PATCH v10 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Leonardo Brás <leobras.c@xxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Nicolas Dufresne <nicolas.dufresne@xxxxxxxxxxxxx>
• Re: [PATCH 0/3] Towards a re-organized submitting patches
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH 0/3] Towards a re-organized submitting patches
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH 0/3] Towards a re-organized submitting patches
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Michel Dänzer <michel.daenzer@xxxxxxxxxxx>
• Re: [PATCH 0/3] Towards a re-organized submitting patches
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Guenter Roeck <groeck@xxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Guenter Roeck <groeck@xxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Maxime Ripard <mripard@xxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Guenter Roeck <groeck@xxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Maxime Ripard <mripard@xxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Guenter Roeck <groeck@xxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Maxime Ripard <mripard@xxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Maxime Ripard <mripard@xxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Maxime Ripard <mripard@xxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Maxime Ripard <mripard@xxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Guillaume Tucker <gtucker@xxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH v2 3/3] docs: submit-checklist: change to autonumbered lists
  • From: Akira Yokosawa <akiyks@xxxxxxxxx>
• Re: [PATCH v2 3/3] docs: submit-checklist: change to autonumbered lists
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH 0/3] Towards a re-organized submitting patches
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v2 0/3] docs: submit-checklist: structure by category
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v2 3/3] docs: submit-checklist: change to autonumbered lists
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Guenter Roeck <groeck@xxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: "Gustavo Padovan" <gustavo.padovan@xxxxxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Guillaume Tucker <gtucker@xxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Nikolai Kondrashov <spbnick@xxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• [PATCH 3/3] docs: submitting-patches: move backtraces to patch description
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• [PATCH 2/3] docs: submitting-patches: move split_changes before describe_change
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• [PATCH 1/3] docs: submitting-patches: divert focus from PATCH in the subject line
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• [PATCH 0/3] Towards a re-organized submitting patches
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Nikolai Kondrashov <spbnick@xxxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Nicolas Dufresne <nicolas.dufresne@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Nicolas Dufresne <nicolas.dufresne@xxxxxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Nikolai Kondrashov <spbnick@xxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Nikolai Kondrashov <spbnick@xxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Guillaume Tucker <gtucker@xxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Guillaume Tucker <gtucker@xxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Nikolai Kondrashov <spbnick@xxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Nikolai Kondrashov <spbnick@xxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v2 0/3] docs: submit-checklist: structure by category
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: [PATCH v2 0/3] docs: submit-checklist: structure by category
  • From: Jani Nikula <jani.nikula@xxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Maxime Ripard <mripard@xxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Sakari Ailus <sakari.ailus@xxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Nikolai Kondrashov <spbnick@xxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Nikolai Kondrashov <spbnick@xxxxxxxxx>
• Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Maxime Ripard <mripard@xxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Maxime Ripard <mripard@xxxxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v2 3/3] docs: submit-checklist: change to autonumbered lists
  • From: Akira Yokosawa <akiyks@xxxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v2 3/3] docs: submit-checklist: change to autonumbered lists
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/3] docs: submit-checklist: use subheadings
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• RE: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: "Bird, Tim" <Tim.Bird@xxxxxxxx>
• [PATCH v2 3/3] docs: submit-checklist: change to autonumbered lists
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• [PATCH v2 2/3] docs: submit-checklist: use subheadings
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• [PATCH v2 1/3] docs: submit-checklist: structure by category
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• [PATCH v2 0/3] docs: submit-checklist: structure by category
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• [PATCH v2-squashed] docs: submit-checklist: structure by category
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>
• Re: [PATCH] docs: submit-checklist: structure by category
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• [PATCH 3/3] kci-gitlab: docs: Add images
  • From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
• [PATCH 2/3] kci-gitlab: Add documentation
  • From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
• [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
• [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
  • From: Helen Koike <helen.koike@xxxxxxxxxxxxx>
• Re: [PATCH] docs: submit-checklist: structure by category
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Shuah Khan <skhan@xxxxxxxxxxxxxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Luis Chamberlain <mcgrof@xxxxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Alex Elder <elder@xxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Willy Tarreau <w@xxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Willy Tarreau <w@xxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Willy Tarreau <w@xxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Willy Tarreau <w@xxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Willy Tarreau <w@xxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxx>
• Re: Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Junio C Hamano <gitster@xxxxxxxxx>
• Toy/demo: using ChatGPT to summarize lengthy LKML threads (b4 integration)
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] docs: submit-checklist: structure by category
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH] docs: submit-checklist: structure by category
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: [PATCH] docs: submit-checklist: structure by category
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: [PATCH] docs: submit-checklist: structure by category
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: [PATCH] docs: submit-checklist: structure by category
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: [PATCH] docs: submit-checklist: structure by category
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: Simple analytics for docs.kernel.org and patchwork, please?
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: Simple analytics for docs.kernel.org and patchwork, please?
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: Simple analytics for docs.kernel.org and patchwork, please?
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: Simple analytics for docs.kernel.org and patchwork, please?
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: Simple analytics for docs.kernel.org and patchwork, please?
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: [PATCH] docs: submit-checklist: structure by category
  • From: Jani Nikula <jani.nikula@xxxxxxxxx>
• [PATCH] docs: submit-checklist: structure by category
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: [PATCH v10 2/2] arm64: boot: Support Flat Image Tree
  • From: Masahiro Yamada <masahiroy@xxxxxxxxxx>
• Re: Simple analytics for docs.kernel.org and patchwork, please?
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: Simple analytics for docs.kernel.org and patchwork, please?
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: Simple analytics for docs.kernel.org and patchwork, please?
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx>
• Simple analytics for docs.kernel.org and patchwork, please?
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Re: [PATCH v10 2/2] arm64: boot: Support Flat Image Tree
  • From: Masahiro Yamada <masahiroy@xxxxxxxxxx>
• Re: CVE-2023-52435: net: prevent mss overflow in skb_segment()
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: CVE-2023-52435: net: prevent mss overflow in skb_segment()
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH] MAINTAINERS: add memory mapping entry with reviewers
  • From: Vlastimil Babka <vbabka@xxxxxxx>
• Re: [PATCH v5] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v5] Documentation: Document the Linux Kernel CVE process
  • From: Vegard Nossum <vegard.nossum@xxxxxxxxxx>
• Re: [PATCH v10 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• Re: [PATCH] Documentation: update mailing list addresses
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [PATCH v5] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v4] Documentation: Document the Linux Kernel CVE process
  • From: Jiri Kosina <jikos@xxxxxxxxxx>
• Re: [PATCH v4] Documentation: Document the Linux Kernel CVE process
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v4] Documentation: Document the Linux Kernel CVE process
  • From: Jiri Kosina <jikos@xxxxxxxxxx>
• Re: [PATCH v4] Documentation: Document the Linux Kernel CVE process
  • From: Josh Poimboeuf <jpoimboe@xxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Michal Hocko <mhocko@xxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Michal Hocko <mhocko@xxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Jani Nikula <jani.nikula@xxxxxxxxx>
• Re: [PATCH v4] Documentation: Document the Linux Kernel CVE process
  • From: Jürgen Groß <jgross@xxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Michal Hocko <mhocko@xxxxxxxx>
• Re: [PATCH v4] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Michal Hocko <mhocko@xxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v4] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v4] Documentation: Document the Linux Kernel CVE process
  • From: Jiri Kosina <jikos@xxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Oleksandr Natalenko <oleksandr@xxxxxxxxxxxxxx>
• Re: [PATCH v4] Documentation: Document the Linux Kernel CVE process
  • From: Jürgen Groß <jgross@xxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Vegard Nossum <vegard.nossum@xxxxxxxxxx>
• [PATCH v4] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Thorsten Leemhuis <linux@xxxxxxxxxxxxx>
• Re: [PATCH] Documentation: update mailing list addresses
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH] Documentation: embargoed-hardware-issues.rst: Fix Trilok's email
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [PATCH] Documentation: update mailing list addresses
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: Document the Linux Kernel CVE process
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH] Documentation: Document the Linux Kernel CVE process
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Jiri Kosina <jikos@xxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Jiri Kosina <jikos@xxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Jiri Kosina <jikos@xxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Krzysztof Kozlowski <krzk@xxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Vegard Nossum <vegard.nossum@xxxxxxxxxx>
• Re: [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• [PATCH v3] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH v2] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: Document the Linux Kernel CVE process
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH] Documentation: Document the Linux Kernel CVE process
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH] Documentation: Document the Linux Kernel CVE process
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] Documentation: Document the Linux Kernel CVE process
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Documentation: embargoed-hardware-issues.rst: Fix Trilok's email
  • From: Trilok Soni <quic_tsoni@xxxxxxxxxxx>
• [PATCH] get_maintainer: Survive querying missing files
  • From: Nikolai Kondrashov <Nikolai.Kondrashov@xxxxxxxxxx>
• Re: [PATCH v2] Documentation: multiple .rst files: Fix grammar and more consistent formatting
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH] Documentation: coding-style: Update syntax highlighting for code-blocks
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH] Documentation: coding-style: Fix indentation in code-blocks
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH] docs: maintainer: add existing SoC and netdev profiles
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [PATCH v2] Documentation: multiple .rst files: Fix grammar and more consistent formatting
  • From: Thorsten Blum <thorsten.blum@xxxxxxxxxx>
• Re: [PATCH] Documentation: multiple .rst files: Fix grammar and more consistent formatting
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH] Documentation: multiple .rst files: Fix grammar and more consistent formatting
  • From: Bagas Sanjaya <bagasdotme@xxxxxxxxx>
• Re: [PATCH] Documentation: multiple .rst files: Fix grammar and more consistent formatting
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• [PATCH] Documentation: coding-style: Update syntax highlighting for code-blocks
  • From: Thorsten Blum <thorsten.blum@xxxxxxxxxx>
• [PATCH] Documentation: multiple .rst files: Fix grammar and more consistent formatting
  • From: Thorsten Blum <thorsten.blum@xxxxxxxxxx>
• [PATCH] Documentation: coding-style: Fix indentation in code-blocks
  • From: Thorsten Blum <thorsten.blum@xxxxxxxxxx>
• [PATCH v10 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• [PATCH v10 0/2] arm64: Add a build target for Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• Re: [PATCH] Documentation: embargoed-hardware-issues.rst: Fix Trilok's email
  • From: Carlos Bilbao <carlos.bilbao@xxxxxxx>
• Re: [PATCH] Documentation: embargoed-hardware-issues.rst: Fix Trilok's email
  • From: Jeffrey Hugo <quic_jhugo@xxxxxxxxxxx>
• Re: [PATCH] Documentation: embargoed-hardware-issues.rst: Fix Trilok's email
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] Documentation: embargoed-hardware-issues.rst: Fix Trilok's email
  • From: Jeffrey Hugo <quic_jhugo@xxxxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Masahiro Yamada <masahiroy@xxxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Rob Herring <robh@xxxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Masahiro Yamada <masahiroy@xxxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Rob Herring <robh@xxxxxxxxxx>
• Re: [RFC PATCH v2 01/10] get_maintainer: Survive querying missing files
  • From: Nikolai Kondrashov <Nikolai.Kondrashov@xxxxxxxxxx>
• [PATCH] docs: maintainer: add existing SoC and netdev profiles
  • From: Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxx>
• Re: [kees:devel/overflow/sanitizers] [overflow] 660787b56e: UBSAN:signed-integer-overflow_in_lib/test_memcat_p.c
  • From: Oliver Sang <oliver.sang@xxxxxxxxx>
• Re: [kees:devel/overflow/sanitizers] [overflow] 660787b56e: UBSAN:signed-integer-overflow_in_lib/test_memcat_p.c
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH] coding-style: Add guidance to prefer dev_dbg
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [kees:devel/overflow/sanitizers] [overflow] 660787b56e: UBSAN:signed-integer-overflow_in_lib/test_memcat_p.c
  • From: kernel test robot <oliver.sang@xxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Masahiro Yamada <masahiroy@xxxxxxxxxx>
• Re: [PATCH v3 1/1] coding-style: recommend split headers instead of kernel.h
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: [PATCH] coding-style: Add guidance to prefer dev_dbg
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] coding-style: Add guidance to prefer dev_dbg
  • From: Abhishek Pandit-Subedi <abhishekpandit@xxxxxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• [PATCH 04/82] docs: deprecated.rst: deprecate open-coded arithmetic wrap-around
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: Patchwork Acked-by question
  • From: Jakub Kicinski <kuba@xxxxxxxxxx>
• Patchwork Acked-by question
  • From: Jeff Johnson <quic_jjohnson@xxxxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>
• Re: PSA: nullmailer should be avoided
  • From: Rob Herring <robh@xxxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Chen-Yu Tsai <wenst@xxxxxxxxxxxx>
• PSA: nullmailer should be avoided
  • From: Konstantin Ryabitsev <konstantin@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Rasmus Villemoes <rasmus.villemoes@xxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Tom Rini <trini@xxxxxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Masahiro Yamada <masahiroy@xxxxxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Masahiro Yamada <masahiroy@xxxxxxxxxx>
• [PATCH v3 1/1] coding-style: recommend split headers instead of kernel.h
  • From: Yueh-Shun Li <shamrocklee@xxxxxxxxxx>
• [PATCH v3 0/1] coding-style: recommend reusing macros from split headers instead of kernel.h
  • From: Yueh-Shun Li <shamrocklee@xxxxxxxxxx>
• Re: [PATCH v2 0/3] coding-style: recommend reusing macros from split headers instead of kernel.h
  • From: Yueh-Shun Li <shamrocklee@xxxxxxxxxx>
• [PATCH v2 0/3] coding-style: recommend reusing macros from split headers instead of kernel.h
  • From: Yueh-Shun Li <shamrocklee@xxxxxxxxxx>
• Re: [PATCH 2/4] coding-style: show how reusing macros prevents naming collisions
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH 2/4] coding-style: show how reusing macros prevents naming collisions
  • From: Yueh-Shun Li <shamrocklee@xxxxxxxxxx>
• Re: [PATCH 2/4] coding-style: show how reusing macros prevents naming collisions
  • From: Jonathan Corbet <corbet@xxxxxxx>
• [PATCH 2/4] coding-style: show how reusing macros prevents naming collisions
  • From: Yueh-Shun Li <shamrocklee@xxxxxxxxxx>
• [PATCH 1/4] coding-style: recommend split headers instead of kernel.h
  • From: Yueh-Shun Li <shamrocklee@xxxxxxxxxx>
• [PATCH 0/4] coding-style: recommend reusing macros from split headers instead of kernel.h
  • From: Yueh-Shun Li <shamrocklee@xxxxxxxxxx>
• Re: [RFC PATCH v2 00/10] MAINTAINERS: Introduce V: entry for tests
  • From: Nikolai Kondrashov <Nikolai.Kondrashov@xxxxxxxxxx>
• Re: [PATCH] Docs: remove mentions of fdformat from util-linux
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v2] CREDITS, MAINTAINERS, docs/process/howto: Update man-pages' maintainer
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH v9 2/2] arm64: boot: Support Flat Image Tree
  • From: Simon Glass <sjg@xxxxxxxxxxxx>