From: Dave Young <dyoung@redhat.com>
To: Baoquan He <bhe@redhat.com>
Cc: akpm@linux-foundation.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, vgoyal@redhat.com
Subject: Re: [PATCH] MAINTAINERS: add files related to kdump
Date: Wed, 20 May 2020 17:48:29 +0800 [thread overview]
Message-ID: <20200520094829.GA21486@dhcp-128-65.nay.redhat.com> (raw)
In-Reply-To: <20200520094359.GV5029@MiWiFi-R3L-srv>
On 05/20/20 at 05:43pm, Baoquan He wrote:
> 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@redhat.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@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
> > > +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
Yes, looks good, thanks!
Acked-by: Dave Young <dyoung@redhat.com>
Thanks
Dave
next prev parent reply other threads:[~2020-05-20 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 8:05 [PATCH] MAINTAINERS: add files related to kdump Baoquan He
2020-05-20 9:14 ` Dave Young
2020-05-20 9:43 ` Baoquan He
2020-05-20 9:48 ` Dave Young [this message]
2020-05-20 10:36 ` [PATCH v2] " Baoquan He
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=20200520094829.GA21486@dhcp-128-65.nay.redhat.com \
--to=dyoung@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).