All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: bhe@redhat.com, vgoyal@redhat.com, dyoung@redhat.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] kexec: Remove duplicated include in crash_reserve.c
Date: Fri, 26 Jan 2024 11:19:25 +0000	[thread overview]
Message-ID: <20240126111925.GD253507@kernel.org> (raw)
In-Reply-To: <20240126004449.118407-1-yang.lee@linux.alibaba.com>

On Fri, Jan 26, 2024 at 08:44:49AM +0800, Yang Li wrote:
> The header files kexec.h is included twice in crash_reserve.c,
> so one inclusion can be removed.
> 
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>

Reviewed-by: Simon Horman <horms@kernel.org>


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Yang Li <yang.lee@linux.alibaba.com>
Cc: bhe@redhat.com, vgoyal@redhat.com, dyoung@redhat.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] kexec: Remove duplicated include in crash_reserve.c
Date: Fri, 26 Jan 2024 11:19:25 +0000	[thread overview]
Message-ID: <20240126111925.GD253507@kernel.org> (raw)
In-Reply-To: <20240126004449.118407-1-yang.lee@linux.alibaba.com>

On Fri, Jan 26, 2024 at 08:44:49AM +0800, Yang Li wrote:
> The header files kexec.h is included twice in crash_reserve.c,
> so one inclusion can be removed.
> 
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>

Reviewed-by: Simon Horman <horms@kernel.org>


  reply	other threads:[~2024-01-26 11:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26  0:44 [PATCH -next] kexec: Remove duplicated include in crash_reserve.c Yang Li
2024-01-26  0:44 ` Yang Li
2024-01-26 11:19 ` Simon Horman [this message]
2024-01-26 11:19   ` Simon Horman

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=20240126111925.GD253507@kernel.org \
    --to=horms@kernel.org \
    --cc=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    --cc=yang.lee@linux.alibaba.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.