From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Alexander Kanavin <alex@linutronix.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [mdadm][PATCH] util.c: add limits.h include for NAME_MAX definition
Date: Tue, 12 Mar 2024 13:41:13 +0100 [thread overview]
Message-ID: <20240312134113.00000c70@linux.intel.com> (raw)
In-Reply-To: <20240312100150.392586-1-alex@linutronix.de>
On Tue, 12 Mar 2024 11:01:50 +0100
Alexander Kanavin <alex@linutronix.de> wrote:
> Signed-off-by: Alexander Kanavin <alex@linutronix.de>
checkpatch raised:
> WARNING: Missing commit description - Add an appropriate one
>
> total: 0 errors, 1 warnings, 0 checks, 8 lines checked
I added description and applied it. No need to resend.
Thanks,
Mariusz
prev parent reply other threads:[~2024-03-12 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 10:01 [mdadm][PATCH] util.c: add limits.h include for NAME_MAX definition Alexander Kanavin
2024-03-12 12:41 ` Mariusz Tkaczyk [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=20240312134113.00000c70@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=alex@linutronix.de \
--cc=linux-raid@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).