From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Martin Wilck <mwilck@suse.com>,
Brian Bunker <brian@purestorage.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
DM-DEVEL ML <dm-devel@lists.linux.dev>
Subject: Re: [PATCH 1/1] checkers: add alua path checker
Date: Fri, 13 Mar 2026 01:34:06 +0100 [thread overview]
Message-ID: <e6f003e6-0469-4d27-a777-e9935aec63ab@gmail.com> (raw)
In-Reply-To: <8653507a25c02727037e7e8bad4b2178a9702040.camel@suse.com>
On 3/12/26 5:32 PM, Martin Wilck wrote:
> On Wed, 2026-03-11 at 17:16 -0700, Brian Bunker wrote:
>> diff --git a/libmultipath/checkers/alua.c
>> b/libmultipath/checkers/alua.c
>> new file mode 100644
>> index 00000000..cb3d7000
>> --- /dev/null
>> +++ b/libmultipath/checkers/alua.c
>> @@ -0,0 +1,426 @@
>> +/*
>> + * ALUA Path Checker
>> + *
>> + * Copyright (c) 2024
There is no Copyright holder.
>> + * This file is released under the GPL.
>
> Please add a proper license header.
If the code comes from libmultipath/prioritizers/alua*
For consistency with:
libmultipath/prioritizers/alua.c: * This file is released under the GPL.
libmultipath/prioritizers/alua_rtpg.c: * This file is released under the GPL.
libmultipath/prioritizers/alua_rtpg.h: * This file is released under the GPL.
libmultipath/prioritizers/alua_spc3.h: * This file is released under the GPL.
Otherwise, the license should be explicitly specified.
next prev parent reply other threads:[~2026-03-13 0:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 0:16 [PATCH 0/1] checkers: add alua path checker Brian Bunker
2026-03-12 0:16 ` [PATCH 1/1] " Brian Bunker
2026-03-12 16:32 ` Martin Wilck
[not found] ` <CAHZQxy+V5YSiHnB5sp8A_jbN_n1OQ633KiDeFa+vXQrNafHzDA@mail.gmail.com>
2026-03-12 19:31 ` Martin Wilck
2026-03-12 19:33 ` Brian Bunker
2026-03-13 0:34 ` Xose Vazquez Perez [this message]
2026-03-15 2:37 ` Benjamin Marzinski
2026-03-12 7:10 ` [PATCH 0/1] " Hannes Reinecke
2026-03-12 16:48 ` Martin Wilck
2026-03-12 21:05 ` Xose Vazquez Perez
2026-03-12 19:19 ` Brian Bunker
2026-03-13 0:43 ` [PATCH 0/1] pr: " Xose Vazquez Perez
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=e6f003e6-0469-4d27-a777-e9935aec63ab@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=bmarzins@redhat.com \
--cc=brian@purestorage.com \
--cc=dm-devel@lists.linux.dev \
--cc=mwilck@suse.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.