From: Saheed Bolarinwa <refactormyself@gmail.com>
To: Borislav Petkov <bp@alien8.de>, trix@redhat.com
Cc: helgaas@kernel.org, Kalle Valo <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Wolfgang Grandegger <wg@grandegger.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Joerg Roedel <joro@8bytes.org>,
bjorn@helgaas.com, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-mtd@lists.infradead.org, iommu@lists.linux-foundation.org,
linux-rdma@vger.kernel.org, linux-ide@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-hwmon@vger.kernel.org,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
linux-gpio@vger.kernel.org, linux-fpga@vger.kernel.org,
linux-edac@vger.kernel.org, dmaengine@vger.kernel.org,
linux-crypto@vger.kernel.org,
linux-atm-general@lists.sourceforge.net
Subject: Re: [RFC PATCH 00/17] Drop uses of pci_read_config_*() return value
Date: Sun, 2 Aug 2020 19:28:00 +0200 [thread overview]
Message-ID: <b720aa44-895a-203b-e220-ecdb3acd9278@gmail.com> (raw)
In-Reply-To: <20200801125657.GA25391@nazgul.tnic>
On 8/1/20 2:56 PM, Borislav Petkov wrote:
> On Sat, Aug 01, 2020 at 01:24:29PM +0200, Saheed O. Bolarinwa wrote:
>> The return value of pci_read_config_*() may not indicate a device error.
>> However, the value read by these functions is more likely to indicate
>> this kind of error. This presents two overlapping ways of reporting
>> errors and complicates error checking.
> So why isn't the *value check done in the pci_read_config_* functions
> instead of touching gazillion callers?
Because the value ~0 has a meaning to some drivers and only
drivers have this knowledge. For those cases more checks will
be needed to ensure that it is an error that has actually
happened.
> For example, pci_conf{1,2}_read() could check whether the u32 *value it
> just read depending on the access method, whether that value is ~0 and
> return proper PCIBIOS_ error in that case.
The primary goal is to make pci_config_read*() return void, so
that there is *only* one way to check for error i.e. through the
obtained value.
Again, only the drivers can determine if ~0 is a valid value. This
information is not available inside pci_config_read*().
- Saheed
WARNING: multiple messages have this Message-ID (diff)
From: Saheed Bolarinwa <refactormyself@gmail.com>
To: Borislav Petkov <bp@alien8.de>, trix@redhat.com
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
linux-pci@vger.kernel.org, linux-fpga@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-ide@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-i2c@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-rdma@vger.kernel.org, Richard Weinberger <richard@nod.at>,
Joerg Roedel <joro@8bytes.org>,
linux-atm-general@lists.sourceforge.net, helgaas@kernel.org,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org,
Wolfgang Grandegger <wg@grandegger.com>,
intel-gfx@lists.freedesktop.org, linux-gpio@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
skhan@linuxfoundation.org, bjorn@helgaas.com,
Kalle Valo <kvalo@codeaurora.org>,
linux-edac@vger.kernel.org, linux-hwmon@vger.kernel.org,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH 00/17] Drop uses of pci_read_config_*() return value
Date: Sun, 2 Aug 2020 19:28:00 +0200 [thread overview]
Message-ID: <b720aa44-895a-203b-e220-ecdb3acd9278@gmail.com> (raw)
In-Reply-To: <20200801125657.GA25391@nazgul.tnic>
On 8/1/20 2:56 PM, Borislav Petkov wrote:
> On Sat, Aug 01, 2020 at 01:24:29PM +0200, Saheed O. Bolarinwa wrote:
>> The return value of pci_read_config_*() may not indicate a device error.
>> However, the value read by these functions is more likely to indicate
>> this kind of error. This presents two overlapping ways of reporting
>> errors and complicates error checking.
> So why isn't the *value check done in the pci_read_config_* functions
> instead of touching gazillion callers?
Because the value ~0 has a meaning to some drivers and only
drivers have this knowledge. For those cases more checks will
be needed to ensure that it is an error that has actually
happened.
> For example, pci_conf{1,2}_read() could check whether the u32 *value it
> just read depending on the access method, whether that value is ~0 and
> return proper PCIBIOS_ error in that case.
The primary goal is to make pci_config_read*() return void, so
that there is *only* one way to check for error i.e. through the
obtained value.
Again, only the drivers can determine if ~0 is a valid value. This
information is not available inside pci_config_read*().
- Saheed
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Saheed Bolarinwa <refactormyself@gmail.com>
To: Borislav Petkov <bp@alien8.de>, trix@redhat.com
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
linux-pci@vger.kernel.org, linux-fpga@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-ide@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-i2c@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-rdma@vger.kernel.org, Richard Weinberger <richard@nod.at>,
linux-atm-general@lists.sourceforge.net, helgaas@kernel.org,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org,
Wolfgang Grandegger <wg@grandegger.com>,
intel-gfx@lists.freedesktop.org, linux-gpio@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
skhan@linuxfoundation.org, bjorn@helgaas.com,
Kalle Valo <kvalo@codeaurora.org>,
linux-edac@vger.kernel.org, linux-hwmon@vger.kernel.org,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH 00/17] Drop uses of pci_read_config_*() return value
Date: Sun, 2 Aug 2020 19:28:00 +0200 [thread overview]
Message-ID: <b720aa44-895a-203b-e220-ecdb3acd9278@gmail.com> (raw)
In-Reply-To: <20200801125657.GA25391@nazgul.tnic>
On 8/1/20 2:56 PM, Borislav Petkov wrote:
> On Sat, Aug 01, 2020 at 01:24:29PM +0200, Saheed O. Bolarinwa wrote:
>> The return value of pci_read_config_*() may not indicate a device error.
>> However, the value read by these functions is more likely to indicate
>> this kind of error. This presents two overlapping ways of reporting
>> errors and complicates error checking.
> So why isn't the *value check done in the pci_read_config_* functions
> instead of touching gazillion callers?
Because the value ~0 has a meaning to some drivers and only
drivers have this knowledge. For those cases more checks will
be needed to ensure that it is an error that has actually
happened.
> For example, pci_conf{1,2}_read() could check whether the u32 *value it
> just read depending on the access method, whether that value is ~0 and
> return proper PCIBIOS_ error in that case.
The primary goal is to make pci_config_read*() return void, so
that there is *only* one way to check for error i.e. through the
obtained value.
Again, only the drivers can determine if ~0 is a valid value. This
information is not available inside pci_config_read*().
- Saheed
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Saheed Bolarinwa <refactormyself@gmail.com>
To: Borislav Petkov <bp@alien8.de>, trix@redhat.com
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
linux-pci@vger.kernel.org, linux-fpga@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-ide@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-i2c@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-rdma@vger.kernel.org, Richard Weinberger <richard@nod.at>,
Joerg Roedel <joro@8bytes.org>,
linux-atm-general@lists.sourceforge.net, helgaas@kernel.org,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org,
Wolfgang Grandegger <wg@grandegger.com>,
intel-gfx@lists.freedesktop.org, linux-gpio@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
Kalle Valo <kvalo@codeaurora.org>,
linux-edac@vger.kernel.org, linux-hwmon@vger.kernel.org,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Linux-kernel-mentees] [RFC PATCH 00/17] Drop uses of pci_read_config_*() return value
Date: Sun, 2 Aug 2020 19:28:00 +0200 [thread overview]
Message-ID: <b720aa44-895a-203b-e220-ecdb3acd9278@gmail.com> (raw)
In-Reply-To: <20200801125657.GA25391@nazgul.tnic>
On 8/1/20 2:56 PM, Borislav Petkov wrote:
> On Sat, Aug 01, 2020 at 01:24:29PM +0200, Saheed O. Bolarinwa wrote:
>> The return value of pci_read_config_*() may not indicate a device error.
>> However, the value read by these functions is more likely to indicate
>> this kind of error. This presents two overlapping ways of reporting
>> errors and complicates error checking.
> So why isn't the *value check done in the pci_read_config_* functions
> instead of touching gazillion callers?
Because the value ~0 has a meaning to some drivers and only
drivers have this knowledge. For those cases more checks will
be needed to ensure that it is an error that has actually
happened.
> For example, pci_conf{1,2}_read() could check whether the u32 *value it
> just read depending on the access method, whether that value is ~0 and
> return proper PCIBIOS_ error in that case.
The primary goal is to make pci_config_read*() return void, so
that there is *only* one way to check for error i.e. through the
obtained value.
Again, only the drivers can determine if ~0 is a valid value. This
information is not available inside pci_config_read*().
- Saheed
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
WARNING: multiple messages have this Message-ID (diff)
From: Saheed Bolarinwa <refactormyself@gmail.com>
To: Borislav Petkov <bp@alien8.de>, trix@redhat.com
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
linux-pci@vger.kernel.org, linux-fpga@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-ide@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-i2c@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-rdma@vger.kernel.org, Richard Weinberger <richard@nod.at>,
Joerg Roedel <joro@8bytes.org>,
linux-atm-general@lists.sourceforge.net, helgaas@kernel.org,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org,
Wolfgang Grandegger <wg@grandegger.com>,
intel-gfx@lists.freedesktop.org, linux-gpio@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
skhan@linuxfoundation.org, bjorn@helgaas.com,
Kalle Valo <kvalo@codeaurora.org>,
linux-edac@vger.kernel.org, linux-hwmon@vger.kernel.org,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFC PATCH 00/17] Drop uses of pci_read_config_*() return value
Date: Sun, 2 Aug 2020 19:28:00 +0200 [thread overview]
Message-ID: <b720aa44-895a-203b-e220-ecdb3acd9278@gmail.com> (raw)
In-Reply-To: <20200801125657.GA25391@nazgul.tnic>
On 8/1/20 2:56 PM, Borislav Petkov wrote:
> On Sat, Aug 01, 2020 at 01:24:29PM +0200, Saheed O. Bolarinwa wrote:
>> The return value of pci_read_config_*() may not indicate a device error.
>> However, the value read by these functions is more likely to indicate
>> this kind of error. This presents two overlapping ways of reporting
>> errors and complicates error checking.
> So why isn't the *value check done in the pci_read_config_* functions
> instead of touching gazillion callers?
Because the value ~0 has a meaning to some drivers and only
drivers have this knowledge. For those cases more checks will
be needed to ensure that it is an error that has actually
happened.
> For example, pci_conf{1,2}_read() could check whether the u32 *value it
> just read depending on the access method, whether that value is ~0 and
> return proper PCIBIOS_ error in that case.
The primary goal is to make pci_config_read*() return void, so
that there is *only* one way to check for error i.e. through the
obtained value.
Again, only the drivers can determine if ~0 is a valid value. This
information is not available inside pci_config_read*().
- Saheed
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Saheed Bolarinwa <refactormyself@gmail.com>
To: Borislav Petkov <bp@alien8.de>, trix@redhat.com
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
linux-pci@vger.kernel.org, linux-fpga@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-ide@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-i2c@vger.kernel.org,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-rdma@vger.kernel.org, Richard Weinberger <richard@nod.at>,
Joerg Roedel <joro@8bytes.org>,
linux-atm-general@lists.sourceforge.net, helgaas@kernel.org,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel-mentees@lists.linuxfoundation.org,
Wolfgang Grandegger <wg@grandegger.com>,
intel-gfx@lists.freedesktop.org, linux-gpio@vger.kernel.org,
Marc Kleine-Budde <mkl@pengutronix.de>,
skhan@linuxfoundation.org, bjorn@helgaas.com,
Kalle Valo <kvalo@codeaurora.org>,
linux-edac@vger.kernel.org, linux-hwmon@vger.kernel.org,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-gfx] [RFC PATCH 00/17] Drop uses of pci_read_config_*() return value
Date: Sun, 2 Aug 2020 19:28:00 +0200 [thread overview]
Message-ID: <b720aa44-895a-203b-e220-ecdb3acd9278@gmail.com> (raw)
In-Reply-To: <20200801125657.GA25391@nazgul.tnic>
On 8/1/20 2:56 PM, Borislav Petkov wrote:
> On Sat, Aug 01, 2020 at 01:24:29PM +0200, Saheed O. Bolarinwa wrote:
>> The return value of pci_read_config_*() may not indicate a device error.
>> However, the value read by these functions is more likely to indicate
>> this kind of error. This presents two overlapping ways of reporting
>> errors and complicates error checking.
> So why isn't the *value check done in the pci_read_config_* functions
> instead of touching gazillion callers?
Because the value ~0 has a meaning to some drivers and only
drivers have this knowledge. For those cases more checks will
be needed to ensure that it is an error that has actually
happened.
> For example, pci_conf{1,2}_read() could check whether the u32 *value it
> just read depending on the access method, whether that value is ~0 and
> return proper PCIBIOS_ error in that case.
The primary goal is to make pci_config_read*() return void, so
that there is *only* one way to check for error i.e. through the
obtained value.
Again, only the drivers can determine if ~0 is a valid value. This
information is not available inside pci_config_read*().
- Saheed
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-08-02 18:27 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 11:24 [RFC PATCH 00/17] Drop uses of pci_read_config_*() return value Saheed O. Bolarinwa
2020-08-01 11:24 ` [Intel-gfx] " Saheed O. Bolarinwa
2020-08-01 11:24 ` Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 11:24 ` Saheed O. Bolarinwa
2020-08-01 11:24 ` Saheed O. Bolarinwa
2020-08-01 11:24 ` [RFC PATCH 01/17] ata: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 11:24 ` [RFC PATCH 02/17] atm: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-05 10:51 ` kernel test robot
2020-08-01 11:24 ` [RFC PATCH 03/17] bcma: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 11:24 ` [RFC PATCH 04/17] hwrng: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 11:24 ` [RFC PATCH 05/17] dmaengine: ioat: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 11:24 ` [RFC PATCH 06/17] edac: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 21:38 ` kernel test robot
2020-08-01 11:24 ` [RFC PATCH 07/17] fpga: altera-cvp: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 22:32 ` kernel test robot
2020-08-05 12:31 ` kernel test robot
2020-08-01 11:24 ` [RFC PATCH 08/17] gpio: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-18 19:59 ` Bartosz Golaszewski
2020-08-18 19:59 ` [Linux-kernel-mentees] " Bartosz Golaszewski
2020-08-19 2:21 ` Bjorn Helgaas
2020-08-19 2:21 ` [Linux-kernel-mentees] " Bjorn Helgaas
2020-08-01 11:24 ` [RFC PATCH 09/17] drm/i915/vga: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Intel-gfx] " Saheed O. Bolarinwa
2020-08-01 11:24 ` Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 11:24 ` [RFC PATCH 10/17] hwmon: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-04 21:26 ` Guenter Roeck
2020-08-04 21:26 ` [Linux-kernel-mentees] " Guenter Roeck
2020-08-01 11:24 ` [RFC PATCH 11/17] intel_th: pci: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 11:24 ` [RFC PATCH 12/17] i2c: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 11:24 ` [RFC PATCH 13/17] ide: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 11:24 ` [RFC PATCH 14/17] IB: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 14:18 ` kernel test robot
2020-08-01 11:24 ` [RFC PATCH 15/17] iommu/vt-d: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 11:24 ` Saheed O. Bolarinwa
2020-08-01 11:24 ` [RFC PATCH 16/17] mtd: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 11:24 ` Saheed O. Bolarinwa
2020-08-01 11:24 ` [RFC PATCH 17/17] net: " Saheed O. Bolarinwa
2020-08-01 11:24 ` [Linux-kernel-mentees] " Saheed O. Bolarinwa
2020-08-01 14:58 ` kernel test robot
2020-08-01 12:56 ` [RFC PATCH 00/17] " Borislav Petkov
2020-08-01 12:56 ` [Intel-gfx] " Borislav Petkov
2020-08-01 12:56 ` Borislav Petkov
2020-08-01 12:56 ` [Linux-kernel-mentees] " Borislav Petkov
2020-08-01 12:56 ` Borislav Petkov
2020-08-01 12:56 ` Borislav Petkov
2020-08-02 14:53 ` Tom Rix
2020-08-02 14:53 ` [Intel-gfx] " Tom Rix
2020-08-02 14:53 ` Tom Rix
2020-08-02 14:53 ` [Linux-kernel-mentees] " Tom Rix
2020-08-02 14:53 ` Tom Rix
2020-08-02 14:53 ` Tom Rix
2020-08-02 17:28 ` Saheed Bolarinwa [this message]
2020-08-02 17:28 ` [Intel-gfx] " Saheed Bolarinwa
2020-08-02 17:28 ` Saheed Bolarinwa
2020-08-02 17:28 ` [Linux-kernel-mentees] " Saheed Bolarinwa
2020-08-02 17:28 ` Saheed Bolarinwa
2020-08-02 17:28 ` Saheed Bolarinwa
2020-08-02 18:46 ` Borislav Petkov
2020-08-02 18:46 ` [Intel-gfx] " Borislav Petkov
2020-08-02 18:46 ` Borislav Petkov
2020-08-02 18:46 ` [Linux-kernel-mentees] " Borislav Petkov
2020-08-02 18:46 ` Borislav Petkov
2020-08-02 18:46 ` Borislav Petkov
2020-08-02 19:14 ` Bjorn Helgaas
2020-08-02 19:14 ` [Intel-gfx] " Bjorn Helgaas
2020-08-02 19:14 ` Bjorn Helgaas
2020-08-02 19:14 ` [Linux-kernel-mentees] " Bjorn Helgaas
2020-08-02 19:14 ` Bjorn Helgaas
2020-08-02 19:14 ` Bjorn Helgaas
2020-08-02 20:18 ` Borislav Petkov
2020-08-02 20:18 ` [Intel-gfx] " Borislav Petkov
2020-08-02 20:18 ` Borislav Petkov
2020-08-02 20:18 ` [Linux-kernel-mentees] " Borislav Petkov
2020-08-02 20:18 ` Borislav Petkov
2020-08-02 20:18 ` Borislav Petkov
2020-08-03 6:56 ` Christoph Hellwig
2020-08-03 6:56 ` [Intel-gfx] " Christoph Hellwig
2020-08-03 6:56 ` [Linux-kernel-mentees] " Christoph Hellwig
2020-08-03 6:56 ` Christoph Hellwig
2020-08-03 6:56 ` 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=b720aa44-895a-203b-e220-ecdb3acd9278@gmail.com \
--to=refactormyself@gmail.com \
--cc=bjorn@helgaas.com \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=helgaas@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=richard@nod.at \
--cc=skhan@linuxfoundation.org \
--cc=trix@redhat.com \
--cc=vigneshr@ti.com \
--cc=wg@grandegger.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.