From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
dm-devel@redhat.com, linux-m68k@lists.linux-m68k.org,
linux-mips@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-can@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, io-uring@vger.kernel.org,
lvs-devel@vger.kernel.org, linux-mtd@lists.infradead.org,
kasan-dev@googlegroups.com, linux-mmc@vger.kernel.org,
nvdimm@lists.linux.dev, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, linux-perf-users@vger.kernel.org,
linux-raid@vger.kernel.org, linux-sctp@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org, linux-usb@vger.kernel.org,
virtualization@lists.linux-foundation.org,
v9fs-developer@lists.sourceforge.net, linux-rdma@vger.kernel.org,
alsa-devel@alsa-project.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] treewide: uapi: Replace zero-length arrays with flexible-array members
Date: Tue, 28 Jun 2022 16:18:23 +0200 [thread overview]
Message-ID: <20220628141823.GB25163@embeddedor> (raw)
In-Reply-To: <20220627125343.44e24c41@hermes.local>
On Mon, Jun 27, 2022 at 12:53:43PM -0700, Stephen Hemminger wrote:
> Thanks this fixes warning with gcc-12 in iproute2.
> In function ‘xfrm_algo_parse’,
> inlined from ‘xfrm_state_modify.constprop’ at xfrm_state.c:573:5:
> xfrm_state.c:162:32: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
> 162 | buf[j] = val;
> | ~~~~~~~^~~~~
Great! This gives me hope. :)
Thanks
--
Gustavo
WARNING: multiple messages have this Message-ID (diff)
From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: nvdimm@lists.linux.dev, alsa-devel@alsa-project.org,
kvm@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dm-devel@redhat.com,
target-devel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-hardening@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
linux-stm32@st-md-mailman.stormreply.com,
linux-s390@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-rdma@vger.kernel.org, x86@kernel.org,
kasan-dev@googlegroups.com, lvs-devel@vger.kernel.org,
coreteam@netfilter.org, v9fs-developer@lists.sourceforge.net,
Kees Cook <keescook@chromium.org>,
intel-gfx@lists.freedesktop.org, linux-can@vger.kernel.org,
linux-raid@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
virtualization@lists.linux-foundation.org,
io-uring@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-mmc@vger.kernel.org, linux-mips@vger.kernel.org,
linux-perf-users@vger.kernel.org, linux-sctp@vger.kernel.org,
netfilter-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
bpf@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [dm-devel] [PATCH][next] treewide: uapi: Replace zero-length arrays with flexible-array members
Date: Tue, 28 Jun 2022 16:18:23 +0200 [thread overview]
Message-ID: <20220628141823.GB25163@embeddedor> (raw)
In-Reply-To: <20220627125343.44e24c41@hermes.local>
On Mon, Jun 27, 2022 at 12:53:43PM -0700, Stephen Hemminger wrote:
> Thanks this fixes warning with gcc-12 in iproute2.
> In function ‘xfrm_algo_parse’,
> inlined from ‘xfrm_state_modify.constprop’ at xfrm_state.c:573:5:
> xfrm_state.c:162:32: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
> 162 | buf[j] = val;
> | ~~~~~~~^~~~~
Great! This gives me hope. :)
Thanks
--
Gustavo
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
dm-devel@redhat.com, linux-m68k@lists.linux-m68k.org,
linux-mips@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-can@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, io-uring@vger.kernel.org,
lvs-devel@vger.kernel.org, linux-mtd@lists.infradead.org,
kasan-dev@googlegroups.com, linux-mmc@vger.kernel.org,
nvdimm@lists.linux.dev, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, linux-perf-users@vger.kernel.org,
linux-raid@vger.kernel.org, linux-sctp@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org, linux-usb@vger.kernel.org,
virtualization@lists.linux-foundation.org,
v9fs-developer@lists.sourceforge.net, linux-rdma@vger.kernel.org,
alsa-devel@alsa-project.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] treewide: uapi: Replace zero-length arrays with flexible-array members
Date: Tue, 28 Jun 2022 16:18:23 +0200 [thread overview]
Message-ID: <20220628141823.GB25163@embeddedor> (raw)
In-Reply-To: <20220627125343.44e24c41@hermes.local>
On Mon, Jun 27, 2022 at 12:53:43PM -0700, Stephen Hemminger wrote:
> Thanks this fixes warning with gcc-12 in iproute2.
> In function ‘xfrm_algo_parse’,
> inlined from ‘xfrm_state_modify.constprop’ at xfrm_state.c:573:5:
> xfrm_state.c:162:32: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
> 162 | buf[j] = val;
> | ~~~~~~~^~~~~
Great! This gives me hope. :)
Thanks
--
Gustavo
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
dm-devel@redhat.com, linux-m68k@lists.linux-m68k.org,
linux-mips@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-can@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, io-uring@vger.kernel.org,
lvs-devel@vger.kernel.org, linux-mtd@lists.infradead.org,
kasan-dev@googlegroups.com, linux-mmc@vger.kernel.org,
nvdimm@lists.linux.dev, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, linux-perf-users@vger.kernel.org,
linux-raid@vger.kernel.org, linux-sctp@vger.kernel.org,
linux-stm32@st-md-mailman
Subject: Re: [PATCH][next] treewide: uapi: Replace zero-length arrays with flexible-array members
Date: Tue, 28 Jun 2022 16:18:23 +0200 [thread overview]
Message-ID: <20220628141823.GB25163@embeddedor> (raw)
In-Reply-To: <20220627125343.44e24c41@hermes.local>
On Mon, Jun 27, 2022 at 12:53:43PM -0700, Stephen Hemminger wrote:
> Thanks this fixes warning with gcc-12 in iproute2.
> In function ‘xfrm_algo_parse’,
> inlined from ‘xfrm_state_modify.constprop’ at xfrm_state.c:573:5:
> xfrm_state.c:162:32: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
> 162 | buf[j] = val;
> | ~~~~~~~^~~~~
Great! This gives me hope. :)
Thanks
--
Gustavo
WARNING: multiple messages have this Message-ID (diff)
From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
dm-devel@redhat.com, linux-m68k@lists.linux-m68k.org,
linux-mips@vger.kernel.org, linux-s390@vger.kernel.org,
kvm@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-can@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux1394-devel@lists.sourceforge.net, io-uring@vger.kernel.org,
lvs-devel@vger.kernel.org, linux-mtd@lists.infradead.org,
kasan-dev@googlegroups.com, linux-mmc@vger.kernel.org,
nvdimm@lists.linux.dev, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, linux-perf-users@vger.kernel.org,
linux-raid@vger.kernel.org, linux-sctp@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, linux-scsi@vger.kernel.org,
target-devel@vger.kernel.org, linux-usb@vger.kernel.org,
virtualization@lists.linux-foundation.org,
v9fs-developer@lists.sourceforge.net, linux-rdma@vger.kernel.org,
alsa-devel@alsa-project.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] treewide: uapi: Replace zero-length arrays with flexible-array members
Date: Tue, 28 Jun 2022 16:18:23 +0200 [thread overview]
Message-ID: <20220628141823.GB25163@embeddedor> (raw)
In-Reply-To: <20220627125343.44e24c41@hermes.local>
On Mon, Jun 27, 2022 at 12:53:43PM -0700, Stephen Hemminger wrote:
> Thanks this fixes warning with gcc-12 in iproute2.
> In function ‘xfrm_algo_parse’,
> inlined from ‘xfrm_state_modify.constprop’ at xfrm_state.c:573:5:
> xfrm_state.c:162:32: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
> 162 | buf[j] = val;
> | ~~~~~~~^~~~~
Great! This gives me hope. :)
Thanks
--
Gustavo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: "Gustavo A. R. Silva" <gustavoars@kernel.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: nvdimm@lists.linux.dev, alsa-devel@alsa-project.org,
kvm@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, dm-devel@redhat.com,
target-devel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-hardening@vger.kernel.org,
linux1394-devel@lists.sourceforge.net,
linux-stm32@st-md-mailman.stormreply.com,
linux-s390@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-rdma@vger.kernel.org, x86@kernel.org,
kasan-dev@googlegroups.com, lvs-devel@vger.kernel.org,
coreteam@netfilter.org, v9fs-developer@lists.sourceforge.net,
Kees Cook <keescook@chromium.org>,
intel-gfx@lists.freedesktop.org, linux-can@vger.kernel.org,
linux-raid@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
virtualization@lists.linux-foundation.org,
io-uring@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-mmc@vger.kernel.org, linux-mips@vger.kernel.org,
linux-perf-users@vger.kernel.org, linux-sctp@vger.kernel.org,
netfilter-devel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
bpf@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH][next] treewide: uapi: Replace zero-length arrays with flexible-array members
Date: Tue, 28 Jun 2022 16:18:23 +0200 [thread overview]
Message-ID: <20220628141823.GB25163@embeddedor> (raw)
In-Reply-To: <20220627125343.44e24c41@hermes.local>
On Mon, Jun 27, 2022 at 12:53:43PM -0700, Stephen Hemminger wrote:
> Thanks this fixes warning with gcc-12 in iproute2.
> In function ‘xfrm_algo_parse’,
> inlined from ‘xfrm_state_modify.constprop’ at xfrm_state.c:573:5:
> xfrm_state.c:162:32: warning: writing 1 byte into a region of size 0 [-Wstringop-overflow=]
> 162 | buf[j] = val;
> | ~~~~~~~^~~~~
Great! This gives me hope. :)
Thanks
--
Gustavo
next prev parent reply other threads:[~2022-06-28 14:18 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 18:04 [PATCH][next] treewide: uapi: Replace zero-length arrays with flexible-array members Gustavo A. R. Silva
2022-06-27 18:04 ` Gustavo A. R. Silva
2022-06-27 18:04 ` Gustavo A. R. Silva
2022-06-27 18:04 ` Gustavo A. R. Silva
2022-06-27 18:04 ` Gustavo A. R. Silva
2022-06-27 18:04 ` [dm-devel] " Gustavo A. R. Silva
2022-06-27 18:27 ` Daniel Borkmann
2022-06-27 18:27 ` Daniel Borkmann
2022-06-27 18:27 ` Daniel Borkmann
2022-06-27 18:27 ` Daniel Borkmann
2022-06-27 18:27 ` Daniel Borkmann
2022-06-27 18:27 ` Daniel Borkmann
2022-06-27 18:27 ` [Intel-gfx] " Daniel Borkmann
2022-06-27 18:27 ` [dm-devel] " Daniel Borkmann
2022-06-27 18:35 ` Gustavo A. R. Silva
2022-06-27 18:35 ` Gustavo A. R. Silva
2022-06-27 18:35 ` Gustavo A. R. Silva
2022-06-27 18:35 ` Gustavo A. R. Silva
2022-06-27 18:35 ` Gustavo A. R. Silva
2022-06-27 18:35 ` [dm-devel] " Gustavo A. R. Silva
2022-06-28 0:40 ` Jason Gunthorpe
2022-06-28 0:40 ` Jason Gunthorpe
2022-06-28 0:40 ` Jason Gunthorpe
2022-06-28 0:40 ` Jason Gunthorpe
2022-06-28 0:40 ` Jason Gunthorpe
2022-06-28 0:40 ` Jason Gunthorpe
2022-06-28 0:40 ` [dm-devel] " Jason Gunthorpe
2022-06-28 0:58 ` Gustavo A. R. Silva
2022-06-28 0:58 ` Gustavo A. R. Silva
2022-06-28 0:58 ` Gustavo A. R. Silva
2022-06-28 0:58 ` Gustavo A. R. Silva
2022-06-28 0:58 ` Gustavo A. R. Silva
2022-06-28 0:58 ` [dm-devel] " Gustavo A. R. Silva
2022-06-28 2:21 ` Gustavo A. R. Silva
2022-06-28 2:21 ` Gustavo A. R. Silva
2022-06-28 2:21 ` Gustavo A. R. Silva
2022-06-28 2:21 ` Gustavo A. R. Silva
2022-06-28 2:21 ` Gustavo A. R. Silva
2022-06-28 2:21 ` [dm-devel] " Gustavo A. R. Silva
2022-06-28 13:36 ` Jason Gunthorpe
2022-06-28 13:36 ` Jason Gunthorpe
2022-06-28 13:36 ` Jason Gunthorpe
2022-06-28 13:36 ` Jason Gunthorpe
2022-06-28 13:36 ` Jason Gunthorpe
2022-06-28 13:36 ` Jason Gunthorpe
2022-06-28 13:36 ` [dm-devel] " Jason Gunthorpe
2022-06-28 13:56 ` Gustavo A. R. Silva
2022-06-28 13:56 ` Gustavo A. R. Silva
2022-06-28 13:56 ` Gustavo A. R. Silva
2022-06-28 13:56 ` Gustavo A. R. Silva
2022-06-28 13:56 ` Gustavo A. R. Silva
2022-06-28 13:56 ` [dm-devel] " Gustavo A. R. Silva
2022-06-28 17:54 ` Kees Cook
2022-06-28 17:54 ` Kees Cook
2022-06-28 17:54 ` Kees Cook
2022-06-28 17:54 ` Kees Cook
2022-06-28 17:54 ` Kees Cook
2022-06-28 17:54 ` Kees Cook
2022-06-28 17:54 ` [Intel-gfx] " Kees Cook
2022-06-28 17:54 ` [dm-devel] " Kees Cook
2022-06-28 18:44 ` Jason Gunthorpe
2022-06-28 18:44 ` Jason Gunthorpe
2022-06-28 18:44 ` Jason Gunthorpe
2022-06-28 18:44 ` Jason Gunthorpe
2022-06-28 18:44 ` Jason Gunthorpe
2022-06-28 18:44 ` Jason Gunthorpe
2022-06-28 18:44 ` [dm-devel] " Jason Gunthorpe
2026-02-23 14:28 ` David Woodhouse
2026-02-23 3:38 ` Gustavo A. R. Silva
2026-02-23 19:57 ` David Woodhouse
2026-02-26 11:44 ` [PATCH] KVM: x86: Fix C++ user API for structures with variable length arrays David Woodhouse
2026-02-26 19:02 ` Kees Cook
2026-02-27 8:29 ` David Woodhouse
2026-02-28 0:43 ` Kees Cook
2026-02-28 8:54 ` David Woodhouse
2026-03-05 18:36 ` Sean Christopherson
2026-03-05 19:18 ` David Woodhouse
2026-03-05 19:31 ` Sean Christopherson
2026-03-05 19:49 ` [PATCH v2] KVM: x86: Use __DECLARE_FLEX_ARRAY() for UAPI structures with VLAs David Woodhouse
2026-04-03 15:13 ` Sean Christopherson
2022-06-27 19:53 ` [PATCH][next] treewide: uapi: Replace zero-length arrays with flexible-array members Stephen Hemminger
2022-06-27 19:53 ` Stephen Hemminger
2022-06-27 19:53 ` Stephen Hemminger
2022-06-27 19:53 ` Stephen Hemminger
2022-06-27 19:53 ` Stephen Hemminger
2022-06-27 19:53 ` [Intel-gfx] " Stephen Hemminger
2022-06-27 19:53 ` [dm-devel] " Stephen Hemminger
2022-06-28 14:18 ` Gustavo A. R. Silva [this message]
2022-06-28 14:18 ` Gustavo A. R. Silva
2022-06-28 14:18 ` Gustavo A. R. Silva
2022-06-28 14:18 ` Gustavo A. R. Silva
2022-06-28 14:18 ` Gustavo A. R. Silva
2022-06-28 14:18 ` [dm-devel] " Gustavo A. R. Silva
2022-06-27 22:31 ` Dan Williams
2022-06-27 22:31 ` Dan Williams
2022-06-27 22:31 ` Dan Williams
2022-06-27 22:31 ` Dan Williams
2022-06-27 22:31 ` Dan Williams
2022-06-27 22:31 ` Dan Williams
2022-06-27 22:31 ` [Intel-gfx] " Dan Williams
2022-06-27 22:31 ` [dm-devel] " Dan Williams
2022-06-28 7:27 ` Geert Uytterhoeven
2022-06-28 7:27 ` Geert Uytterhoeven
2022-06-28 7:27 ` Geert Uytterhoeven
2022-06-28 7:27 ` Geert Uytterhoeven
2022-06-28 7:27 ` Geert Uytterhoeven
2022-06-28 7:27 ` Geert Uytterhoeven
2022-06-28 7:27 ` [Intel-gfx] " Geert Uytterhoeven
2022-06-28 7:27 ` [dm-devel] " Geert Uytterhoeven
2022-06-28 18:05 ` Kees Cook
2022-06-28 18:05 ` Kees Cook
2022-06-28 18:05 ` Kees Cook
2022-06-28 18:05 ` Kees Cook
2022-06-28 18:05 ` Kees Cook
2022-06-28 18:05 ` Kees Cook
2022-06-28 18:05 ` [Intel-gfx] " Kees Cook
2022-06-28 18:05 ` [dm-devel] " Kees Cook
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=20220628141823.GB25163@embeddedor \
--to=gustavoars@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bpf@vger.kernel.org \
--cc=coreteam@netfilter.org \
--cc=dm-devel@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=io-uring@vger.kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=stephen@networkplumber.org \
--cc=target-devel@vger.kernel.org \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@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 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.