From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@lst.de>
Cc: iommu@lists.linux-foundation.org,
Russell King <linux@armlinux.org.uk>,
Santosh Shilimkar <ssantosh@kernel.org>,
Jim Quinlan <james.quinlan@broadcom.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Robin Murphy <robin.murphy@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
devicetree@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 3/3] dma-mapping: introduce DMA range map, supplanting dma_pfn_offset
Date: Thu, 10 Sep 2020 09:53:51 +0200 [thread overview]
Message-ID: <20200910075351.GA1092435@kroah.com> (raw)
In-Reply-To: <20200910054038.324517-4-hch@lst.de>
On Thu, Sep 10, 2020 at 07:40:38AM +0200, Christoph Hellwig wrote:
> From: Jim Quinlan <james.quinlan@broadcom.com>
>
> The new field 'dma_range_map' in struct device is used to facilitate the
> use of single or multiple offsets between mapping regions of cpu addrs and
> dma addrs. It subsumes the role of "dev->dma_pfn_offset" which was only
> capable of holding a single uniform offset and had no region bounds
> checking.
>
> The function of_dma_get_range() has been modified so that it takes a single
> argument -- the device node -- and returns a map, NULL, or an error code.
> The map is an array that holds the information regarding the DMA regions.
> Each range entry contains the address offset, the cpu_start address, the
> dma_start address, and the size of the region.
>
> of_dma_configure() is the typical manner to set range offsets but there are
> a number of ad hoc assignments to "dev->dma_pfn_offset" in the kernel
> driver code. These cases now invoke the function
> dma_attach_offset_range(dev, cpu_addr, dma_addr, size).
So if an error happens, we don't do anything?
ice_init(dev->dev);
> diff --git a/drivers/usb/core/message.c b/drivers/usb/core/message.c
> index 6197938dcc2d8f..935ee98e049f65 100644
> --- a/drivers/usb/core/message.c
> +++ b/drivers/usb/core/message.c
> @@ -1956,10 +1956,11 @@ int usb_set_configuration(struct usb_device *dev, int configuration)
> intf->dev.groups = usb_interface_groups;
> /*
> * Please refer to usb_alloc_dev() to see why we set
> - * dma_mask and dma_pfn_offset.
> + * dma_mask and dma_range_map.
> */
> intf->dev.dma_mask = dev->dev.dma_mask;
> - intf->dev.dma_pfn_offset = dev->dev.dma_pfn_offset;
> + if (dma_direct_copy_range_map(&intf->dev, &dev->dev))
> + dev_err(&dev->dev, "failed to copy DMA map\n");
We tell the user, but then just keep on running? Is there anything that
we can do here?
If not, why not have dma_direct_copy_range_map() print out the error?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@lst.de>
Cc: devicetree@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
linux-sh@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
linux-usb@vger.kernel.org, linux-pci@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
Jim Quinlan <james.quinlan@broadcom.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Nathan Chancellor <natechancellor@gmail.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] dma-mapping: introduce DMA range map, supplanting dma_pfn_offset
Date: Thu, 10 Sep 2020 09:53:51 +0200 [thread overview]
Message-ID: <20200910075351.GA1092435@kroah.com> (raw)
In-Reply-To: <20200910054038.324517-4-hch@lst.de>
On Thu, Sep 10, 2020 at 07:40:38AM +0200, Christoph Hellwig wrote:
> From: Jim Quinlan <james.quinlan@broadcom.com>
>
> The new field 'dma_range_map' in struct device is used to facilitate the
> use of single or multiple offsets between mapping regions of cpu addrs and
> dma addrs. It subsumes the role of "dev->dma_pfn_offset" which was only
> capable of holding a single uniform offset and had no region bounds
> checking.
>
> The function of_dma_get_range() has been modified so that it takes a single
> argument -- the device node -- and returns a map, NULL, or an error code.
> The map is an array that holds the information regarding the DMA regions.
> Each range entry contains the address offset, the cpu_start address, the
> dma_start address, and the size of the region.
>
> of_dma_configure() is the typical manner to set range offsets but there are
> a number of ad hoc assignments to "dev->dma_pfn_offset" in the kernel
> driver code. These cases now invoke the function
> dma_attach_offset_range(dev, cpu_addr, dma_addr, size).
So if an error happens, we don't do anything?
ice_init(dev->dev);
> diff --git a/drivers/usb/core/message.c b/drivers/usb/core/message.c
> index 6197938dcc2d8f..935ee98e049f65 100644
> --- a/drivers/usb/core/message.c
> +++ b/drivers/usb/core/message.c
> @@ -1956,10 +1956,11 @@ int usb_set_configuration(struct usb_device *dev, int configuration)
> intf->dev.groups = usb_interface_groups;
> /*
> * Please refer to usb_alloc_dev() to see why we set
> - * dma_mask and dma_pfn_offset.
> + * dma_mask and dma_range_map.
> */
> intf->dev.dma_mask = dev->dev.dma_mask;
> - intf->dev.dma_pfn_offset = dev->dev.dma_pfn_offset;
> + if (dma_direct_copy_range_map(&intf->dev, &dev->dev))
> + dev_err(&dev->dev, "failed to copy DMA map\n");
We tell the user, but then just keep on running? Is there anything that
we can do here?
If not, why not have dma_direct_copy_range_map() print out the error?
thanks,
greg k-h
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@lst.de>
Cc: iommu@lists.linux-foundation.org,
Russell King <linux@armlinux.org.uk>,
Santosh Shilimkar <ssantosh@kernel.org>,
Jim Quinlan <james.quinlan@broadcom.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Robin Murphy <robin.murphy@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sh@vger.kernel.org,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
devicetree@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 3/3] dma-mapping: introduce DMA range map, supplanting dma_pfn_offset
Date: Thu, 10 Sep 2020 07:53:51 +0000 [thread overview]
Message-ID: <20200910075351.GA1092435@kroah.com> (raw)
In-Reply-To: <20200910054038.324517-4-hch@lst.de>
On Thu, Sep 10, 2020 at 07:40:38AM +0200, Christoph Hellwig wrote:
> From: Jim Quinlan <james.quinlan@broadcom.com>
>
> The new field 'dma_range_map' in struct device is used to facilitate the
> use of single or multiple offsets between mapping regions of cpu addrs and
> dma addrs. It subsumes the role of "dev->dma_pfn_offset" which was only
> capable of holding a single uniform offset and had no region bounds
> checking.
>
> The function of_dma_get_range() has been modified so that it takes a single
> argument -- the device node -- and returns a map, NULL, or an error code.
> The map is an array that holds the information regarding the DMA regions.
> Each range entry contains the address offset, the cpu_start address, the
> dma_start address, and the size of the region.
>
> of_dma_configure() is the typical manner to set range offsets but there are
> a number of ad hoc assignments to "dev->dma_pfn_offset" in the kernel
> driver code. These cases now invoke the function
> dma_attach_offset_range(dev, cpu_addr, dma_addr, size).
So if an error happens, we don't do anything?
ice_init(dev->dev);
> diff --git a/drivers/usb/core/message.c b/drivers/usb/core/message.c
> index 6197938dcc2d8f..935ee98e049f65 100644
> --- a/drivers/usb/core/message.c
> +++ b/drivers/usb/core/message.c
> @@ -1956,10 +1956,11 @@ int usb_set_configuration(struct usb_device *dev, int configuration)
> intf->dev.groups = usb_interface_groups;
> /*
> * Please refer to usb_alloc_dev() to see why we set
> - * dma_mask and dma_pfn_offset.
> + * dma_mask and dma_range_map.
> */
> intf->dev.dma_mask = dev->dev.dma_mask;
> - intf->dev.dma_pfn_offset = dev->dev.dma_pfn_offset;
> + if (dma_direct_copy_range_map(&intf->dev, &dev->dev))
> + dev_err(&dev->dev, "failed to copy DMA map\n");
We tell the user, but then just keep on running? Is there anything that
we can do here?
If not, why not have dma_direct_copy_range_map() print out the error?
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@lst.de>
Cc: devicetree@vger.kernel.org,
Florian Fainelli <f.fainelli@gmail.com>,
linux-sh@vger.kernel.org, Frank Rowand <frowand.list@gmail.com>,
linux-usb@vger.kernel.org, linux-pci@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
iommu@lists.linux-foundation.org,
Rob Herring <robh+dt@kernel.org>,
Jim Quinlan <james.quinlan@broadcom.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Nathan Chancellor <natechancellor@gmail.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] dma-mapping: introduce DMA range map, supplanting dma_pfn_offset
Date: Thu, 10 Sep 2020 09:53:51 +0200 [thread overview]
Message-ID: <20200910075351.GA1092435@kroah.com> (raw)
In-Reply-To: <20200910054038.324517-4-hch@lst.de>
On Thu, Sep 10, 2020 at 07:40:38AM +0200, Christoph Hellwig wrote:
> From: Jim Quinlan <james.quinlan@broadcom.com>
>
> The new field 'dma_range_map' in struct device is used to facilitate the
> use of single or multiple offsets between mapping regions of cpu addrs and
> dma addrs. It subsumes the role of "dev->dma_pfn_offset" which was only
> capable of holding a single uniform offset and had no region bounds
> checking.
>
> The function of_dma_get_range() has been modified so that it takes a single
> argument -- the device node -- and returns a map, NULL, or an error code.
> The map is an array that holds the information regarding the DMA regions.
> Each range entry contains the address offset, the cpu_start address, the
> dma_start address, and the size of the region.
>
> of_dma_configure() is the typical manner to set range offsets but there are
> a number of ad hoc assignments to "dev->dma_pfn_offset" in the kernel
> driver code. These cases now invoke the function
> dma_attach_offset_range(dev, cpu_addr, dma_addr, size).
So if an error happens, we don't do anything?
ice_init(dev->dev);
> diff --git a/drivers/usb/core/message.c b/drivers/usb/core/message.c
> index 6197938dcc2d8f..935ee98e049f65 100644
> --- a/drivers/usb/core/message.c
> +++ b/drivers/usb/core/message.c
> @@ -1956,10 +1956,11 @@ int usb_set_configuration(struct usb_device *dev, int configuration)
> intf->dev.groups = usb_interface_groups;
> /*
> * Please refer to usb_alloc_dev() to see why we set
> - * dma_mask and dma_pfn_offset.
> + * dma_mask and dma_range_map.
> */
> intf->dev.dma_mask = dev->dev.dma_mask;
> - intf->dev.dma_pfn_offset = dev->dev.dma_pfn_offset;
> + if (dma_direct_copy_range_map(&intf->dev, &dev->dev))
> + dev_err(&dev->dev, "failed to copy DMA map\n");
We tell the user, but then just keep on running? Is there anything that
we can do here?
If not, why not have dma_direct_copy_range_map() print out the error?
thanks,
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-10 7:54 UTC|newest]
Thread overview: 148+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 5:40 support range based offsets in dma-direct Christoph Hellwig
2020-09-10 5:40 ` Christoph Hellwig
2020-09-10 5:40 ` Christoph Hellwig
2020-09-10 5:40 ` Christoph Hellwig
2020-09-10 5:40 ` [PATCH 1/3] ARM/dma-mapping: move various helpers from dma-mapping.h to dma-direct.h Christoph Hellwig
2020-09-10 5:40 ` Christoph Hellwig
2020-09-10 5:40 ` Christoph Hellwig
2020-09-10 5:40 ` Christoph Hellwig
2020-09-10 18:02 ` Robin Murphy
2020-09-10 18:02 ` Robin Murphy
2020-09-10 18:02 ` Robin Murphy
2020-09-10 18:02 ` Robin Murphy
2020-09-11 6:25 ` Christoph Hellwig
2020-09-11 6:25 ` Christoph Hellwig
2020-09-11 6:25 ` Christoph Hellwig
2020-09-11 6:25 ` Christoph Hellwig
2020-09-10 5:40 ` [PATCH 2/3] ARM/keystone: move the DMA offset handling under ifdef CONFIG_ARM_LPAE Christoph Hellwig
2020-09-10 5:40 ` Christoph Hellwig
2020-09-10 5:40 ` Christoph Hellwig
2020-09-10 5:40 ` Christoph Hellwig
2020-09-11 11:12 ` Robin Murphy
2020-09-11 11:12 ` Robin Murphy
2020-09-11 11:12 ` Robin Murphy
2020-09-11 11:12 ` Robin Murphy
2020-09-11 11:15 ` Russell King - ARM Linux admin
2020-09-11 11:15 ` Russell King - ARM Linux admin
2020-09-11 11:15 ` Russell King - ARM Linux admin
2020-09-11 11:15 ` Russell King - ARM Linux admin
2020-09-11 11:27 ` Robin Murphy
2020-09-11 11:27 ` Robin Murphy
2020-09-11 11:27 ` Robin Murphy
2020-09-11 11:27 ` Robin Murphy
2020-09-11 18:00 ` santosh.shilimkar
2020-09-11 18:00 ` santosh.shilimkar
2020-09-11 18:00 ` santosh.shilimkar
2020-09-11 18:00 ` santosh.shilimkar
2020-09-10 5:40 ` [PATCH 3/3] dma-mapping: introduce DMA range map, supplanting dma_pfn_offset Christoph Hellwig
2020-09-10 5:40 ` Christoph Hellwig
2020-09-10 5:40 ` Christoph Hellwig
2020-09-10 5:40 ` Christoph Hellwig
2020-09-10 7:53 ` Greg KH [this message]
2020-09-10 7:53 ` Greg KH
2020-09-10 7:53 ` Greg KH
2020-09-10 7:53 ` Greg KH
2020-09-10 9:13 ` Christoph Hellwig
2020-09-10 9:13 ` Christoph Hellwig
2020-09-10 9:13 ` Christoph Hellwig
2020-09-10 9:13 ` Christoph Hellwig
2020-09-10 16:12 ` Greg KH
2020-09-10 16:12 ` Greg KH
2020-09-10 16:12 ` Greg KH
2020-09-10 16:12 ` Greg KH
2020-09-11 16:12 ` Robin Murphy
2020-09-11 16:12 ` Robin Murphy
2020-09-11 16:12 ` Robin Murphy
2020-09-11 16:12 ` Robin Murphy
2020-09-12 6:46 ` Christoph Hellwig
2020-09-12 6:46 ` Christoph Hellwig
2020-09-12 6:46 ` Christoph Hellwig
2020-09-12 6:46 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2020-09-14 7:33 support range based offsets in dma-direct v2 Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` [PATCH 1/6] ARM/dma-mapping: remove a __arch_page_to_dma #error Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` [PATCH 2/6] ARM/dma-mapping: remove dma_to_virt Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` [PATCH 3/6] ARM/dma-mapping: move various helpers from dma-mapping.h to dma-direct.h Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` [PATCH 4/6] ARM/keystone: move the DMA offset handling under ifdef CONFIG_ARM_LPAE Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` [PATCH 5/6] usb: don't inherity DMA properties for USB devices Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:51 ` Greg Kroah-Hartman
2020-09-14 7:51 ` Greg Kroah-Hartman
2020-09-14 7:51 ` Greg Kroah-Hartman
2020-09-14 7:51 ` Greg Kroah-Hartman
2020-09-14 7:33 ` [PATCH 6/6] dma-mapping: introduce DMA range map, supplanting dma_pfn_offset Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 7:33 ` Christoph Hellwig
2020-09-14 23:01 ` Mathieu Poirier
2020-09-14 23:01 ` Mathieu Poirier
2020-09-14 23:01 ` Mathieu Poirier
2020-09-14 23:01 ` Mathieu Poirier
2020-09-15 5:41 ` Christoph Hellwig
2020-09-15 5:41 ` Christoph Hellwig
2020-09-15 5:41 ` Christoph Hellwig
2020-09-15 5:41 ` Christoph Hellwig
2020-09-15 19:55 ` Mathieu Poirier
2020-09-15 19:55 ` Mathieu Poirier
2020-09-15 19:55 ` Mathieu Poirier
2020-09-15 19:55 ` Mathieu Poirier
2020-09-16 6:13 ` Christoph Hellwig
2020-09-16 6:13 ` Christoph Hellwig
2020-09-16 6:13 ` Christoph Hellwig
2020-09-16 6:13 ` Christoph Hellwig
2020-09-16 6:14 support range based offsets in dma-direct v3 Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` [PATCH 1/6] ARM/dma-mapping: remove a __arch_page_to_dma #error Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` [PATCH 2/6] ARM/dma-mapping: remove dma_to_virt Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` [PATCH 3/6] ARM/dma-mapping: move various helpers from dma-mapping.h to dma-direct.h Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` [PATCH 4/6] ARM/keystone: move the DMA offset handling under ifdef CONFIG_ARM_LPAE Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` [PATCH 5/6] usb: don't inherity DMA properties for USB devices Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` [PATCH 6/6] dma-mapping: introduce DMA range map, supplanting dma_pfn_offset Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 6:14 ` Christoph Hellwig
2020-09-16 17:36 ` Mathieu Poirier
2020-09-16 17:36 ` Mathieu Poirier
2020-09-16 17:36 ` Mathieu Poirier
2020-09-16 17:36 ` Mathieu Poirier
2020-10-26 15:33 ` Geert Uytterhoeven
2020-10-26 15:33 ` Geert Uytterhoeven
2020-10-26 15:33 ` Geert Uytterhoeven
2020-10-26 15:33 ` Geert Uytterhoeven
2020-09-17 16:45 ` support range based offsets in dma-direct v3 Christoph Hellwig
2020-09-17 16:45 ` Christoph Hellwig
2020-09-17 16:45 ` Christoph Hellwig
2020-09-17 16:45 ` Christoph Hellwig
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=20200910075351.GA1092435@kroah.com \
--to=greg@kroah.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=frowand.list@gmail.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=james.quinlan@broadcom.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=natechancellor@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=ssantosh@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.