From: Ben Dooks <ben.dooks@sifive.com>
To: Conor.Dooley@microchip.com, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Cc: sudip.mukherjee@sifive.com, jude.onyenegecha@sifive.com
Subject: Re: [PATCH] kernel/hung_task: fix address space of proc_dohung_task_timeout_secs
Date: Thu, 14 Jul 2022 09:20:04 +0100 [thread overview]
Message-ID: <ab363f25-0d35-c84f-ce11-c10eb32cabe2@sifive.com> (raw)
In-Reply-To: <aa78a638-a201-1a58-f168-f36a9f272fbb@microchip.com>
On 14/07/2022 09:10, Conor.Dooley@microchip.com wrote:
> On 14/07/2022 08:47, Ben Dooks wrote:
>
> Hey Ben,
> Odd CC list here? I assume you're piping get_maintainer into
> send-email or something, but idk who is going to see or apply
> this patch! Ditto your other one for this file.
Since (see below) the script wasn't clear I just cc our management.
>
> Might be worth adding some of what get_maintainer spits out:
> Petr Mladek <pmladek@suse.com> (commit_signer:4/4=100%,authored:1/4=25%,removed_lines:10/15=67%)
> Andrew Morton <akpm@linux-foundation.org> (commit_signer:2/4=50%)
> Rasmus Villemoes <linux@rasmusvillemoes.dk> (commit_signer:1/4=25%,authored:1/4=25%,removed_lines:1/15=7%)
> John Ogness <john.ogness@linutronix.de> (commit_signer:1/4=25%,authored:1/4=25%,added_lines:10/90=11%,removed_lines:1/15=7%)
> Kees Cook <keescook@chromium.org> (commit_signer:1/4=25%)
> Xiaoming Ni <nixiaoming@huawei.com> (authored:1/4=25%,added_lines:78/90=87%,removed_lines:3/15=20%)
I think only akpm would be one of those, given no overall
maintainer I had a look and just use the kernel list and
hope someone picks it up.
next prev parent reply other threads:[~2022-07-14 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 7:47 Ben Dooks
2022-07-14 8:10 ` Conor.Dooley
2022-07-14 8:20 ` Ben Dooks [this message]
2022-07-14 8:23 ` Conor.Dooley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ab363f25-0d35-c84f-ce11-c10eb32cabe2@sifive.com \
--to=ben.dooks@sifive.com \
--cc=Conor.Dooley@microchip.com \
--cc=akpm@linux-foundation.org \
--cc=jude.onyenegecha@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sudip.mukherjee@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®