* [PATCH 00/18] use ARRAY_SIZE macro @ 2017-10-01 19:30 Jérémy Lefaure 2017-10-01 19:30 ` [PATCH 13/18] tpm: use ARRAY_SIZE Jérémy Lefaure 2017-10-01 22:01 ` [PATCH 00/18] use ARRAY_SIZE macro Tobin C. Harding 0 siblings, 2 replies; 12+ messages in thread From: Jérémy Lefaure @ 2017-10-01 19:30 UTC (permalink / raw) Cc: alsa-devel, amd-gfx, brcm80211-dev-list, brcm80211-dev-list.pdl, devel, devel, dm-devel, dri-devel, ecryptfs, intel-gfx, intel-gvt-dev, intel-wired-lan, Jason Gunthorpe, linux-acpi, linux-integrity, linux-kernel, linux-media, linux-nfs, linux-raid, linux-rdma, linux-scsi, linux-usb, linux-video, linux-wireless, netdev, nouveau, openipmi-developer Hi everyone, Using ARRAY_SIZE improves the code readability. I used coccinelle (I made a change to the array_size.cocci file [1]) to find several places where ARRAY_SIZE could be used instead of other macros or sizeof division. I tried to divide the changes into a patch per subsystem (excepted for staging). If one of the patch should be split into several patches, let me know. In order to reduce the size of the To: and Cc: lines, each patch of the series is sent only to the maintainers and lists concerned by the patch. This cover letter is sent to every list concerned by this series. This series is based on linux-next next-20170929. Each patch has been tested by building the relevant files with W=1. This series contains the following patches: [PATCH 01/18] sound: use ARRAY_SIZE [PATCH 02/18] tracing/filter: use ARRAY_SIZE [PATCH 03/18] media: use ARRAY_SIZE [PATCH 04/18] IB/mlx5: Use ARRAY_SIZE [PATCH 05/18] net: use ARRAY_SIZE [PATCH 06/18] drm: use ARRAY_SIZE [PATCH 07/18] scsi: bfa: use ARRAY_SIZE [PATCH 08/18] ecryptfs: use ARRAY_SIZE [PATCH 09/18] nfsd: use ARRAY_SIZE [PATCH 10/18] orangefs: use ARRAY_SIZE [PATCH 11/18] dm space map metadata: use ARRAY_SIZE [PATCH 12/18] x86: use ARRAY_SIZE [PATCH 13/18] tpm: use ARRAY_SIZE [PATCH 14/18] ipmi: use ARRAY_SIZE [PATCH 15/18] acpi: use ARRAY_SIZE [PATCH 16/18] media: staging: atomisp: use ARRAY_SIZE [PATCH 17/18] staging: rtl8723bs: use ARRAY_SIZE [PATCH 18/18] staging: rtlwifi: use ARRAY_SIZE [1]: https://lkml.org/lkml/2017/9/13/689 ^ permalink raw reply [flat|nested] 12+ messages in thread
* [PATCH 13/18] tpm: use ARRAY_SIZE 2017-10-01 19:30 [PATCH 00/18] use ARRAY_SIZE macro Jérémy Lefaure @ 2017-10-01 19:30 ` Jérémy Lefaure 2017-10-04 12:14 ` Jarkko Sakkinen 2017-10-01 22:01 ` [PATCH 00/18] use ARRAY_SIZE macro Tobin C. Harding 1 sibling, 1 reply; 12+ messages in thread From: Jérémy Lefaure @ 2017-10-01 19:30 UTC (permalink / raw) To: Peter Huewe, Jarkko Sakkinen, Jason Gunthorpe Cc: Jérémy Lefaure, linux-integrity, linux-kernel Using the ARRAY_SIZE macro improves the readability of the code. Found with Coccinelle with the following semantic patch: @r depends on (org || report)@ type T; T[] E; position p; @@ ( (sizeof(E)@p /sizeof(*E)) | (sizeof(E)@p /sizeof(E[...])) | (sizeof(E)@p /sizeof(T)) ) Signed-off-by: Jeremy Lefaure <jeremy.lefaure@lse.epita.fr> --- drivers/char/tpm/tpm_tis.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/char/tpm/tpm_tis.c b/drivers/char/tpm/tpm_tis.c index ebd0e75a3e4d..e2d1055fb814 100644 --- a/drivers/char/tpm/tpm_tis.c +++ b/drivers/char/tpm/tpm_tis.c @@ -30,6 +30,7 @@ #include <linux/freezer.h> #include <linux/of.h> #include <linux/of_device.h> +#include <linux/kernel.h> #include "tpm.h" #include "tpm_tis_core.h" @@ -365,7 +366,7 @@ static struct pnp_driver tis_pnp_driver = { }, }; -#define TIS_HID_USR_IDX sizeof(tpm_pnp_tbl)/sizeof(struct pnp_device_id) -2 +#define TIS_HID_USR_IDX (ARRAY_SIZE(tpm_pnp_tbl) - 2) module_param_string(hid, tpm_pnp_tbl[TIS_HID_USR_IDX].id, sizeof(tpm_pnp_tbl[TIS_HID_USR_IDX].id), 0444); MODULE_PARM_DESC(hid, "Set additional specific HID for this driver to probe"); -- 2.14.1 ^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: [PATCH 13/18] tpm: use ARRAY_SIZE 2017-10-01 19:30 ` [PATCH 13/18] tpm: use ARRAY_SIZE Jérémy Lefaure @ 2017-10-04 12:14 ` Jarkko Sakkinen 2017-10-10 20:30 ` Jérémy Lefaure 0 siblings, 1 reply; 12+ messages in thread From: Jarkko Sakkinen @ 2017-10-04 12:14 UTC (permalink / raw) To: Jérémy Lefaure Cc: Peter Huewe, Jason Gunthorpe, linux-integrity, linux-kernel On Sun, Oct 01, 2017 at 03:30:51PM -0400, Jeremy Lefaure wrote: > Using the ARRAY_SIZE macro improves the readability of the code. > > Found with Coccinelle with the following semantic patch: > @r depends on (org || report)@ > type T; > T[] E; > position p; > @@ > ( > (sizeof(E)@p /sizeof(*E)) > | > (sizeof(E)@p /sizeof(E[...])) > | > (sizeof(E)@p /sizeof(T)) > ) > > Signed-off-by: Jeremy Lefaure <jeremy.lefaure@lse.epita.fr> Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> /Jarkko > --- > drivers/char/tpm/tpm_tis.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/drivers/char/tpm/tpm_tis.c b/drivers/char/tpm/tpm_tis.c > index ebd0e75a3e4d..e2d1055fb814 100644 > --- a/drivers/char/tpm/tpm_tis.c > +++ b/drivers/char/tpm/tpm_tis.c > @@ -30,6 +30,7 @@ > #include <linux/freezer.h> > #include <linux/of.h> > #include <linux/of_device.h> > +#include <linux/kernel.h> > #include "tpm.h" > #include "tpm_tis_core.h" > > @@ -365,7 +366,7 @@ static struct pnp_driver tis_pnp_driver = { > }, > }; > > -#define TIS_HID_USR_IDX sizeof(tpm_pnp_tbl)/sizeof(struct pnp_device_id) -2 > +#define TIS_HID_USR_IDX (ARRAY_SIZE(tpm_pnp_tbl) - 2) > module_param_string(hid, tpm_pnp_tbl[TIS_HID_USR_IDX].id, > sizeof(tpm_pnp_tbl[TIS_HID_USR_IDX].id), 0444); > MODULE_PARM_DESC(hid, "Set additional specific HID for this driver to probe"); > -- > 2.14.1 > ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 13/18] tpm: use ARRAY_SIZE 2017-10-04 12:14 ` Jarkko Sakkinen @ 2017-10-10 20:30 ` Jérémy Lefaure 2017-10-11 11:48 ` Jarkko Sakkinen 0 siblings, 1 reply; 12+ messages in thread From: Jérémy Lefaure @ 2017-10-10 20:30 UTC (permalink / raw) To: Jarkko Sakkinen Cc: Peter Huewe, Jason Gunthorpe, linux-integrity, linux-kernel On Wed, 4 Oct 2017 15:14:49 +0300 Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> wrote: > On Sun, Oct 01, 2017 at 03:30:51PM -0400, Jeremy Lefaure wrote: > > Using the ARRAY_SIZE macro improves the readability of the code. > > > > Found with Coccinelle with the following semantic patch: > > @r depends on (org || report)@ > > type T; > > T[] E; > > position p; > > @@ > > ( > > (sizeof(E)@p /sizeof(*E)) > > | > > (sizeof(E)@p /sizeof(E[...])) > > | > > (sizeof(E)@p /sizeof(T)) > > ) > > > > Signed-off-by: Jeremy Lefaure <jeremy.lefaure@lse.epita.fr> > > Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> > Hi Jarkko, This patch is an individual patch, it's not really part of a series (my fault, sorry). Could you apply this patch to your tree ? Thank you, Jeremy ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 13/18] tpm: use ARRAY_SIZE 2017-10-10 20:30 ` Jérémy Lefaure @ 2017-10-11 11:48 ` Jarkko Sakkinen 0 siblings, 0 replies; 12+ messages in thread From: Jarkko Sakkinen @ 2017-10-11 11:48 UTC (permalink / raw) To: Jérémy Lefaure Cc: Peter Huewe, Jason Gunthorpe, linux-integrity, linux-kernel On Tue, Oct 10, 2017 at 04:30:11PM -0400, Jeremy Lefaure wrote: > On Wed, 4 Oct 2017 15:14:49 +0300 > Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> wrote: > > > On Sun, Oct 01, 2017 at 03:30:51PM -0400, Jeremy Lefaure wrote: > > > Using the ARRAY_SIZE macro improves the readability of the code. > > > > > > Found with Coccinelle with the following semantic patch: > > > @r depends on (org || report)@ > > > type T; > > > T[] E; > > > position p; > > > @@ > > > ( > > > (sizeof(E)@p /sizeof(*E)) > > > | > > > (sizeof(E)@p /sizeof(E[...])) > > > | > > > (sizeof(E)@p /sizeof(T)) > > > ) > > > > > > Signed-off-by: Jeremy Lefaure <jeremy.lefaure@lse.epita.fr> > > > > Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> > > > Hi Jarkko, > This patch is an individual patch, it's not really part of a series > (my fault, sorry). > > Could you apply this patch to your tree ? > > Thank you, > Jeremy It is already applied :-) I'll take it as part of my next pull request. Thank you. /JarkkO ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 00/18] use ARRAY_SIZE macro 2017-10-01 19:30 [PATCH 00/18] use ARRAY_SIZE macro Jérémy Lefaure 2017-10-01 19:30 ` [PATCH 13/18] tpm: use ARRAY_SIZE Jérémy Lefaure @ 2017-10-01 22:01 ` Tobin C. Harding 2017-10-02 0:52 ` Jérémy Lefaure 1 sibling, 1 reply; 12+ messages in thread From: Tobin C. Harding @ 2017-10-01 22:01 UTC (permalink / raw) To: Jérémy Lefaure Cc: alsa-devel, nouveau, dri-devel, dm-devel, brcm80211-dev-list, devel, linux-scsi, linux-rdma, amd-gfx, Jason Gunthorpe, linux-acpi, linux-video, intel-wired-lan, linux-media, intel-gfx, ecryptfs, linux-nfs, linux-raid, openipmi-developer, intel-gvt-dev, devel, brcm80211-dev-list.pdl, netdev, linux-usb, linux-wireless, linux-kernel, linux-integrity On Sun, Oct 01, 2017 at 03:30:38PM -0400, Jeremy Lefaure wrote: > Hi everyone, > Using ARRAY_SIZE improves the code readability. I used coccinelle (I > made a change to the array_size.cocci file [1]) to find several places > where ARRAY_SIZE could be used instead of other macros or sizeof > division. > > I tried to divide the changes into a patch per subsystem (excepted for > staging). If one of the patch should be split into several patches, let > me know. > > In order to reduce the size of the To: and Cc: lines, each patch of the > series is sent only to the maintainers and lists concerned by the patch. > This cover letter is sent to every list concerned by this series. Why don't you just send individual patches for each subsystem? I'm not a maintainer but I don't see how any one person is going to be able to apply this whole series, it is making it hard for maintainers if they have to pick patches out from among the series (if indeed any will bother doing that). I get that this will be more work for you but AFAIK we are optimizing for maintainers. Good luck, Tobin. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 00/18] use ARRAY_SIZE macro 2017-10-01 22:01 ` [PATCH 00/18] use ARRAY_SIZE macro Tobin C. Harding @ 2017-10-02 0:52 ` Jérémy Lefaure 2017-10-02 5:35 ` Greg KH 2017-10-02 16:37 ` Mauro Carvalho Chehab 0 siblings, 2 replies; 12+ messages in thread From: Jérémy Lefaure @ 2017-10-02 0:52 UTC (permalink / raw) To: Tobin C. Harding Cc: alsa-devel, nouveau, dri-devel, dm-devel, brcm80211-dev-list, devel, linux-scsi, linux-rdma, amd-gfx, Jason Gunthorpe, linux-acpi, linux-video, intel-wired-lan, linux-media, intel-gfx, ecryptfs, linux-nfs, linux-raid, openipmi-developer, intel-gvt-dev, devel, brcm80211-dev-list.pdl, netdev, linux-usb, linux-wireless, linux-kernel, linux-integrity On Mon, 2 Oct 2017 09:01:31 +1100 "Tobin C. Harding" <me@tobin.cc> wrote: > > In order to reduce the size of the To: and Cc: lines, each patch of the > > series is sent only to the maintainers and lists concerned by the patch. > > This cover letter is sent to every list concerned by this series. > > Why don't you just send individual patches for each subsystem? I'm not a maintainer but I don't see > how any one person is going to be able to apply this whole series, it is making it hard for > maintainers if they have to pick patches out from among the series (if indeed any will bother > doing that). Yeah, maybe it would have been better to send individual patches. >From my point of view it's a series because the patches are related (I did a git format-patch from my local branch). But for the maintainers point of view, they are individual patches. As each patch in this series is standalone, the maintainers can pick the patches they want and apply them individually. So yeah, maybe I should have sent individual patches. But I also wanted to tie all patches together as it's the same change. Anyway, I can tell to each maintainer that they can apply the patches they're concerned about and next time I may send individual patches. Thank you for your answer, Jeremy ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 00/18] use ARRAY_SIZE macro 2017-10-02 0:52 ` Jérémy Lefaure @ 2017-10-02 5:35 ` Greg KH 2017-10-02 19:22 ` J. Bruce Fields 2017-10-02 16:37 ` Mauro Carvalho Chehab 1 sibling, 1 reply; 12+ messages in thread From: Greg KH @ 2017-10-02 5:35 UTC (permalink / raw) To: Jérémy Lefaure Cc: Tobin C. Harding, alsa-devel, nouveau, dri-devel, dm-devel, brcm80211-dev-list, devel, linux-scsi, linux-rdma, amd-gfx, Jason Gunthorpe, linux-acpi, linux-video, intel-wired-lan, linux-media, intel-gfx, ecryptfs, linux-nfs, linux-raid, openipmi-developer, intel-gvt-dev, devel, brcm80211-dev-list.pdl, netdev, linux-usb, linux-wireless, linux-kernel, linux-integrity On Sun, Oct 01, 2017 at 08:52:20PM -0400, Jeremy Lefaure wrote: > On Mon, 2 Oct 2017 09:01:31 +1100 > "Tobin C. Harding" <me@tobin.cc> wrote: > > > > In order to reduce the size of the To: and Cc: lines, each patch of the > > > series is sent only to the maintainers and lists concerned by the patch. > > > This cover letter is sent to every list concerned by this series. > > > > Why don't you just send individual patches for each subsystem? I'm not a maintainer but I don't see > > how any one person is going to be able to apply this whole series, it is making it hard for > > maintainers if they have to pick patches out from among the series (if indeed any will bother > > doing that). > Yeah, maybe it would have been better to send individual patches. > > From my point of view it's a series because the patches are related (I > did a git format-patch from my local branch). But for the maintainers > point of view, they are individual patches. And the maintainers view is what matters here, if you wish to get your patches reviewed and accepted... thanks, greg k-h ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 00/18] use ARRAY_SIZE macro 2017-10-02 5:35 ` Greg KH @ 2017-10-02 19:22 ` J. Bruce Fields 2017-10-03 1:33 ` Jérémy Lefaure 0 siblings, 1 reply; 12+ messages in thread From: J. Bruce Fields @ 2017-10-02 19:22 UTC (permalink / raw) To: Greg KH Cc: Jérémy Lefaure, Tobin C. Harding, alsa-devel, nouveau, dri-devel, dm-devel, brcm80211-dev-list, devel, linux-scsi, linux-rdma, amd-gfx, Jason Gunthorpe, linux-acpi, linux-video, intel-wired-lan, linux-media, intel-gfx, ecryptfs, linux-nfs, linux-raid, openipmi-developer, intel-gvt-dev, devel, brcm80211-dev-list.pdl, netdev, linux-usb, linux-wireless, linux-kernel, linux-integrity On Mon, Oct 02, 2017 at 07:35:54AM +0200, Greg KH wrote: > On Sun, Oct 01, 2017 at 08:52:20PM -0400, Jeremy Lefaure wrote: > > On Mon, 2 Oct 2017 09:01:31 +1100 > > "Tobin C. Harding" <me@tobin.cc> wrote: > > > > > > In order to reduce the size of the To: and Cc: lines, each patch of the > > > > series is sent only to the maintainers and lists concerned by the patch. > > > > This cover letter is sent to every list concerned by this series. > > > > > > Why don't you just send individual patches for each subsystem? I'm not a maintainer but I don't see > > > how any one person is going to be able to apply this whole series, it is making it hard for > > > maintainers if they have to pick patches out from among the series (if indeed any will bother > > > doing that). > > Yeah, maybe it would have been better to send individual patches. > > > > From my point of view it's a series because the patches are related (I > > did a git format-patch from my local branch). But for the maintainers > > point of view, they are individual patches. > > And the maintainers view is what matters here, if you wish to get your > patches reviewed and accepted... Mainly I'd just like to know which you're asking for. Do you want me to apply this, or to ACK it so someone else can? If it's sent as a series I tend to assume the latter. But in this case I'm assuming it's the former, so I'll pick up the nfsd one.... --b. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 00/18] use ARRAY_SIZE macro 2017-10-02 19:22 ` J. Bruce Fields @ 2017-10-03 1:33 ` Jérémy Lefaure 2017-10-05 17:57 ` J. Bruce Fields 0 siblings, 1 reply; 12+ messages in thread From: Jérémy Lefaure @ 2017-10-03 1:33 UTC (permalink / raw) To: J. Bruce Fields Cc: Greg KH, Tobin C. Harding, alsa-devel, nouveau, dri-devel, dm-devel, brcm80211-dev-list, devel, linux-scsi, linux-rdma, amd-gfx, Jason Gunthorpe, linux-acpi, linux-video, intel-wired-lan, linux-media, intel-gfx, ecryptfs, linux-nfs, linux-raid, openipmi-developer, intel-gvt-dev, devel, brcm80211-dev-list.pdl, netdev, linux-usb, linux-wireless, linux-kernel, linux-integrity, jlayton On Mon, 2 Oct 2017 15:22:24 -0400 bfields@fieldses.org (J. Bruce Fields) wrote: > Mainly I'd just like to know which you're asking for. Do you want me to > apply this, or to ACK it so someone else can? If it's sent as a series > I tend to assume the latter. > > But in this case I'm assuming it's the former, so I'll pick up the nfsd > one.... Could you to apply the NFSD patch ("nfsd: use ARRAY_SIZE") with the Reviewed-by: Jeff Layton <jlayton@redhat.com>) tag please ? This patch is an individual patch and it should not have been sent in a series (sorry about that). Thank you, Jeremy ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 00/18] use ARRAY_SIZE macro 2017-10-03 1:33 ` Jérémy Lefaure @ 2017-10-05 17:57 ` J. Bruce Fields 0 siblings, 0 replies; 12+ messages in thread From: J. Bruce Fields @ 2017-10-05 17:57 UTC (permalink / raw) To: Jérémy Lefaure Cc: Greg KH, Tobin C. Harding, alsa-devel, nouveau, dri-devel, dm-devel, brcm80211-dev-list, devel, linux-scsi, linux-rdma, amd-gfx, Jason Gunthorpe, linux-acpi, linux-video, intel-wired-lan, linux-media, intel-gfx, ecryptfs, linux-nfs, linux-raid, openipmi-developer, intel-gvt-dev, devel, brcm80211-dev-list.pdl, netdev, linux-usb, linux-wireless, linux-kernel, linux-integrity, jlayton On Mon, Oct 02, 2017 at 09:33:12PM -0400, Jeremy Lefaure wrote: > On Mon, 2 Oct 2017 15:22:24 -0400 > bfields@fieldses.org (J. Bruce Fields) wrote: > > > Mainly I'd just like to know which you're asking for. Do you want me to > > apply this, or to ACK it so someone else can? If it's sent as a series > > I tend to assume the latter. > > > > But in this case I'm assuming it's the former, so I'll pick up the nfsd > > one.... > Could you to apply the NFSD patch ("nfsd: use ARRAY_SIZE") with the > Reviewed-by: Jeff Layton <jlayton@redhat.com>) tag please ? > > This patch is an individual patch and it should not have been sent in a > series (sorry about that). Applying for 4.15, thanks.--b. ^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 00/18] use ARRAY_SIZE macro 2017-10-02 0:52 ` Jérémy Lefaure 2017-10-02 5:35 ` Greg KH @ 2017-10-02 16:37 ` Mauro Carvalho Chehab 1 sibling, 0 replies; 12+ messages in thread From: Mauro Carvalho Chehab @ 2017-10-02 16:37 UTC (permalink / raw) To: Jérémy Lefaure Cc: Tobin C. Harding, alsa-devel, nouveau, dri-devel, dm-devel, brcm80211-dev-list, devel, linux-scsi, linux-rdma, amd-gfx, Jason Gunthorpe, linux-acpi, linux-video, intel-wired-lan, linux-media, intel-gfx, ecryptfs, linux-nfs, linux-raid, openipmi-developer, intel-gvt-dev, devel, brcm80211-dev-list.pdl, netdev, linux-usb, linux-wireless, linux-kernel, linux-integrity Em Sun, 1 Oct 2017 20:52:20 -0400 Jeremy Lefaure <jeremy.lefaure@lse.epita.fr> escreveu: > Anyway, I can tell to each maintainer that they can apply the patches > they're concerned about and next time I may send individual patches. In the case of media, we'll handle it as if they were individual ones. Thanks, Mauro ^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2017-10-11 11:48 UTC | newest] Thread overview: 12+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2017-10-01 19:30 [PATCH 00/18] use ARRAY_SIZE macro Jérémy Lefaure 2017-10-01 19:30 ` [PATCH 13/18] tpm: use ARRAY_SIZE Jérémy Lefaure 2017-10-04 12:14 ` Jarkko Sakkinen 2017-10-10 20:30 ` Jérémy Lefaure 2017-10-11 11:48 ` Jarkko Sakkinen 2017-10-01 22:01 ` [PATCH 00/18] use ARRAY_SIZE macro Tobin C. Harding 2017-10-02 0:52 ` Jérémy Lefaure 2017-10-02 5:35 ` Greg KH 2017-10-02 19:22 ` J. Bruce Fields 2017-10-03 1:33 ` Jérémy Lefaure 2017-10-05 17:57 ` J. Bruce Fields 2017-10-02 16:37 ` Mauro Carvalho Chehab
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 NNTP newsgroup(s).