mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Robert Love <robert.w.love@intel.com>,
	Robert Love <rlove@rlove.org>, Robert Love <rml@tech9.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: drop PREEMPTIBLE KERNEL section entry
Date: Sat, 12 Jan 2019 09:55:50 +0100	[thread overview]
Message-ID: <20190112085550.GC119110@gmail.com> (raw)
In-Reply-To: <20190112060613.7115-1-lukas.bulwahn@gmail.com>


* Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:

> The PREEMPTIBLE KERNEL section entry seems quite outdated:
> 
> Robert Love is not actively maintaining the file anymore, nor a recorded
> contributor to the files in the PREEMPTIBLE KERNEL section for the last
> few years.
> 
> The mailing list kpreempt-tech@lists.sourceforge.net does not exist
> anymore; the website just points to some very old patches for v2.4/v2.5.
> 
> So, let's delete the PREEMPTIBLE KERNEL section entry and clean this up:
> 
> - Documentation/preempt-locking.txt is not modified much anyway, and the
>   changes in that file are generally maintained by Jonathan Corbet. So,
>   we do not need to explicitly mention Documentation/preempt-locking.txt
>   in MAINTAINERS.
> 
> - include/linux/preempt.h is maintained by Peter and Ingo, so we simply
>   add that file to the SCHEDULER section entry.
> 
> I got directed to this issue, as I could not subscribe to the outdated
> mailing list address and decided to investigate and then cleaned this up.
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
>  MAINTAINERS | 9 +--------
>  1 file changed, 1 insertion(+), 8 deletions(-)


Indeed - this all was many years out of date - thanks for the update, I 
merged the patch into tip:sched/urgent.

Thanks,

	Ingo

  reply	other threads:[~2019-01-12  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-12  6:06 Lukas Bulwahn
2019-01-12  8:55 ` Ingo Molnar [this message]
2019-01-21 11:33 ` [tip:sched/core] MAINTAINERS, sched: Drop " tip-bot for Lukas Bulwahn
2019-01-27 11:34 ` tip-bot for Lukas Bulwahn

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=20190112085550.GC119110@gmail.com \
    --to=mingo@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rlove@rlove.org \
    --cc=rml@tech9.net \
    --cc=robert.w.love@intel.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

Powered by JetHome