[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200520094359.GV5029@MiWiFi-R3L-srv>
Date: Wed, 20 May 2020 17:43:59 +0800
From: Baoquan He <bhe@...hat.com>
To: Dave Young <dyoung@...hat.com>
Cc: akpm@...ux-foundation.org, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org, vgoyal@...hat.com
Subject: Re: [PATCH] MAINTAINERS: add files related to kdump
On 05/20/20 at 05:14pm, Dave Young wrote:
> Hi Baoquan,
> On 05/20/20 at 04:05pm, Baoquan He wrote:
> > Kdump is implemented based on kexec, however some files are only
> > related to crash dumping and missing, add them to KDUMP entry.
> >
> > Signed-off-by: Baoquan He <bhe@...hat.com>
> > ---
> > MAINTAINERS | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 83cf5c43242a..2f9eefd33114 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -9251,6 +9251,11 @@ L: kexec@...ts.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
> > +F: include/linux/crash_dump.h
> > +F: include/uapi/linux/vmcore.h
> > +F: kernel/crash.*
>
> ls kernel/crash.*
> ls: cannot access 'kernel/crash.*': No such file or directory
>
> But ls kernel/crash*
> kernel/crash_core.c kernel/crash_dump.c
Is below patten ok? Surely kernel/crash* is also OK to me. Thanks.
F: kernel/crash_*.c
Powered by blists - more mailing lists