All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <baoquan.he@linux.dev>
To: Sourabh Jain <sourabhjain@linux.ibm.com>
Cc: akpm@linux-foundation.org, Baoquan He <bhe@redhat.com>,
	Dave Young <dyoung@redhat.com>, Vivek Goyal <vgoyal@redhat.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: remove stale kdump project URL
Date: Tue, 21 Apr 2026 13:27:23 +0800	[thread overview]
Message-ID: <aecKux2mdmlSPxnM@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20260418080226.40415-1-sourabhjain@linux.ibm.com>

On 04/18/26 at 01:32pm, Sourabh Jain wrote:
> The kdump project URL in MAINTAINERS points to
> http://lse.sourceforge.net/kdump/, but it is no longer maintained.
> 
> Remove this outdated link to avoid confusion and keep the file
> up to date.
> 
> Discussion to remove this link:
> https://lore.kernel.org/all/e1e9e200-17d7-4ae9-b0eb-71300f4eb1ac@linux.ibm.com/
> 
> Cc: Baoquan He <bhe@redhat.com>
> Cc: Dave Young <dyoung@redhat.com>
> Cc: Vivek Goyal <vgoyal@redhat.com>
> Cc: kexec@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
> ---
>  MAINTAINERS | 1 -
>  1 file changed, 1 deletion(-)

Acked-by: Baoquan He <baoquan.he@linux.dev>

> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 288866c32ade..46aa9a48ec15 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -13870,7 +13870,6 @@ R:	Vivek Goyal <vgoyal@redhat.com>
>  R:	Dave Young <dyoung@redhat.com>
>  L:	kexec@lists.infradead.org
>  S:	Maintained
> -W:	http://lse.sourceforge.net/kdump/
>  F:	Documentation/admin-guide/kdump/
>  F:	fs/proc/vmcore.c
>  F:	include/linux/crash_core.h
> -- 
> 2.52.0
> 
> 


      reply	other threads:[~2026-04-21  5:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-18  8:02 [PATCH] MAINTAINERS: remove stale kdump project URL Sourabh Jain
2026-04-21  5:27 ` Baoquan He [this message]

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=aecKux2mdmlSPxnM@MiWiFi-R3L-srv \
    --to=baoquan.he@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sourabhjain@linux.ibm.com \
    --cc=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.