From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] [next] dlm: replace one-element array with fixed size array
Date: Wed, 12 Oct 2022 08:28:54 +1300 [thread overview]
Message-ID: <Y0XD9tTd0ahj2jRZ@mail.google.com> (raw)
In-Reply-To: <Y0XDAtQ4eYTgwIgM@work>
On Tue, Oct 11, 2022 at 02:24:50PM -0500, Gustavo A. R. Silva wrote:
> On Wed, Oct 12, 2022 at 08:15:17AM +1300, Paulo Miguel Almeida wrote:
> > One-element arrays are deprecated. So, replace one-element array with
> > fixed size array member in struct dlm_ls, and refactor the rest of the
> > code, accordingly.
> >
> > Link: https://github.com/KSPP/linux/issues/79
> > Link: https://github.com/KSPP/linux/issues/228
> > Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101836
> > Link: https://lore.kernel.org/lkml/Y0W5jkiXUkpNl4ap at mail.google.com/
> >
> > Signed-off-by: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
>
> I think this should be versioned as v3.
>
I didn't add v3 here because the the patch got changed from 'replacing
[1]-array with flex-array' to 'replacing [1]-array to fixed-size array'.
Let me know if you still want me to send it as v3 instead.
Paulo A.
WARNING: multiple messages have this Message-ID (diff)
From: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: Christine Caulfield <ccaulfie@redhat.com>,
David Teigland <teigland@redhat.com>,
cluster-devel@redhat.com, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [PATCH] [next] dlm: replace one-element array with fixed size array
Date: Wed, 12 Oct 2022 08:28:54 +1300 [thread overview]
Message-ID: <Y0XD9tTd0ahj2jRZ@mail.google.com> (raw)
In-Reply-To: <Y0XDAtQ4eYTgwIgM@work>
On Tue, Oct 11, 2022 at 02:24:50PM -0500, Gustavo A. R. Silva wrote:
> On Wed, Oct 12, 2022 at 08:15:17AM +1300, Paulo Miguel Almeida wrote:
> > One-element arrays are deprecated. So, replace one-element array with
> > fixed size array member in struct dlm_ls, and refactor the rest of the
> > code, accordingly.
> >
> > Link: https://github.com/KSPP/linux/issues/79
> > Link: https://github.com/KSPP/linux/issues/228
> > Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101836
> > Link: https://lore.kernel.org/lkml/Y0W5jkiXUkpNl4ap@mail.google.com/
> >
> > Signed-off-by: Paulo Miguel Almeida <paulo.miguel.almeida.rodenas@gmail.com>
>
> I think this should be versioned as v3.
>
I didn't add v3 here because the the patch got changed from 'replacing
[1]-array with flex-array' to 'replacing [1]-array to fixed-size array'.
Let me know if you still want me to send it as v3 instead.
Paulo A.
next prev parent reply other threads:[~2022-10-11 19:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 19:15 [Cluster-devel] [PATCH] [next] dlm: replace one-element array with fixed size array Paulo Miguel Almeida
2022-10-11 19:15 ` Paulo Miguel Almeida
2022-10-11 19:24 ` [Cluster-devel] " Gustavo A. R. Silva
2022-10-11 19:24 ` Gustavo A. R. Silva
2022-10-11 19:28 ` Paulo Miguel Almeida [this message]
2022-10-11 19:28 ` Paulo Miguel Almeida
2022-10-11 19:37 ` [Cluster-devel] " Gustavo A. R. Silva
2022-10-11 19:37 ` Gustavo A. R. Silva
2022-10-11 19:55 ` [Cluster-devel] " Paulo Miguel Almeida
2022-10-11 19:55 ` Paulo Miguel Almeida
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=Y0XD9tTd0ahj2jRZ@mail.google.com \
--to=paulo.miguel.almeida.rodenas@gmail.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.