On 03/13/18 22:23, Andy Shevchenko wrote:
> On Tue, Mar 13, 2018 at 9:34 PM, Kirill Marinushkin
> wrote:
>> In the current implementation, `rmmod snd_bcm2835` does not release
>> resources properly. It causes an oops when trying to list sound devices.
>>
>> This commit
On 03/13/18 22:23, Andy Shevchenko wrote:
> On Tue, Mar 13, 2018 at 9:34 PM, Kirill Marinushkin
> wrote:
>> In the current implementation, `rmmod snd_bcm2835` does not release
>> resources properly. It causes an oops when trying to list sound devices.
>>
>> This commit fixes it.
> Nice catch!
>
>
2018-03-13 11:30 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Each of 'make {menu,n,g,x}config' uses (needs) pkg-config to make sure
> that other required files are present, but none of these check that
> pkg-config itself is present. Add a
2018-03-13 11:30 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Each of 'make {menu,n,g,x}config' uses (needs) pkg-config to make sure
> that other required files are present, but none of these check that
> pkg-config itself is present. Add a check for all 4 of these targets.
>
> Fixes kernel
Hi Masami,
On 03/08/2018 02:20 PM, Masami Hiramatsu wrote:
> Add array type support for probe events.
> This allows user to get arraied types from memory address.
> The array type syntax is
>
> TYPE[N]
>
> Where TYPE is one of types (u8/16/32/64,s8/16/32/64,
> x8/16/32/64, symbol, string)
On Tue, Mar 13, 2018 at 3:20 AM, Peter Zijlstra wrote:
> On Sun, Mar 11, 2018 at 10:15:55AM -0700, Dan Williams wrote:
>> On Sun, Mar 11, 2018 at 4:27 AM, Peter Zijlstra wrote:
>> > On Fri, Mar 09, 2018 at 10:55:32PM -0800, Dan Williams wrote:
>> >>
Hi Masami,
On 03/08/2018 02:20 PM, Masami Hiramatsu wrote:
> Add array type support for probe events.
> This allows user to get arraied types from memory address.
> The array type syntax is
>
> TYPE[N]
>
> Where TYPE is one of types (u8/16/32/64,s8/16/32/64,
> x8/16/32/64, symbol, string)
On Tue, Mar 13, 2018 at 3:20 AM, Peter Zijlstra wrote:
> On Sun, Mar 11, 2018 at 10:15:55AM -0700, Dan Williams wrote:
>> On Sun, Mar 11, 2018 at 4:27 AM, Peter Zijlstra wrote:
>> > On Fri, Mar 09, 2018 at 10:55:32PM -0800, Dan Williams wrote:
>> >> Add a generic facility for awaiting an
Hi Arnd,
On Wed, 14 Mar 2018 16:35:13 +0100
Arnd Bergmann wrote:
> Hi driver maintainers,
>
> I just posted one series with the removal of eight architectures,
> see https://lkml.org/lkml/2018/3/14/505 for details, or
> https://lwn.net/Articles/748074/ for more background.
>
>
Hi Arnd,
On Wed, 14 Mar 2018 16:35:13 +0100
Arnd Bergmann wrote:
> Hi driver maintainers,
>
> I just posted one series with the removal of eight architectures,
> see https://lkml.org/lkml/2018/3/14/505 for details, or
> https://lwn.net/Articles/748074/ for more background.
>
> These are the
Hi Marc,
Today's linux-next merge of the irqchip tree got a conflict in:
drivers/irqchip/Makefile
between commit:
abe45fd9f1b0 ("irqchip: Andestech Internal Vector Interrupt Controller
driver")
from the nds32 tree and commit:
f55c73aef890 ("irqchip/pdc: Add PDC interrupt controller
Hi Marc,
Today's linux-next merge of the irqchip tree got a conflict in:
drivers/irqchip/Makefile
between commit:
abe45fd9f1b0 ("irqchip: Andestech Internal Vector Interrupt Controller
driver")
from the nds32 tree and commit:
f55c73aef890 ("irqchip/pdc: Add PDC interrupt controller
On Wed, Mar 14, 2018 at 09:40:28PM +0100, Arnd Bergmann wrote:
> On Wed, Mar 14, 2018 at 9:31 PM, Dominik Brodowski
> wrote:
> > On Wed, Mar 14, 2018 at 03:43:47PM +0100, Arnd Bergmann wrote:
> >> The frv, tile and blackfin architectures are being removed, so
> >> we
On Wed, Mar 14, 2018 at 09:40:28PM +0100, Arnd Bergmann wrote:
> On Wed, Mar 14, 2018 at 9:31 PM, Dominik Brodowski
> wrote:
> > On Wed, Mar 14, 2018 at 03:43:47PM +0100, Arnd Bergmann wrote:
> >> The frv, tile and blackfin architectures are being removed, so
> >> we can clean up this header by
On Tue, Mar 13, 2018 at 04:46:38PM +, Craig Tatlor wrote:
> The compatible string was mistakenly pulled from the downstream tree and the
> startup delay property is needed to prevent io errors on initial page select.
>
> Signed-off-by: Craig Tatlor
Thanks for the patch.
On Tue, Mar 13, 2018 at 04:46:38PM +, Craig Tatlor wrote:
> The compatible string was mistakenly pulled from the downstream tree and the
> startup delay property is needed to prevent io errors on initial page select.
>
> Signed-off-by: Craig Tatlor
Thanks for the patch. I'll add Bjorn's
On Sat, Mar 10, 2018 at 10:17:45AM -0800, Andiry Xu wrote:
> From: Andiry Xu
>
> inode.h defines the non-volatile and volatile NOVA inode data structures.
>
> The non-volatile NOVA inode (nova_inode) is aligned to 128 bytes and contains
> file/directory metadata information.
On Sat, Mar 10, 2018 at 10:17:45AM -0800, Andiry Xu wrote:
> From: Andiry Xu
>
> inode.h defines the non-volatile and volatile NOVA inode data structures.
>
> The non-volatile NOVA inode (nova_inode) is aligned to 128 bytes and contains
> file/directory metadata information. The most important
Hi Mark,
Today's linux-next merge of the spi tree got a conflict in:
drivers/spi/Kconfig
between commit:
588020dcb92a ("treewide: simplify Kconfig dependencies for removed archs")
from the asm-generic tree and commit:
e3d001a0c29d ("spi: kconfig: Remove AVR32 dep. from SPI_ATMEL")
Hi Mark,
Today's linux-next merge of the spi tree got a conflict in:
drivers/spi/Kconfig
between commit:
588020dcb92a ("treewide: simplify Kconfig dependencies for removed archs")
from the asm-generic tree and commit:
e3d001a0c29d ("spi: kconfig: Remove AVR32 dep. from SPI_ATMEL")
On Sat, Mar 10, 2018 at 10:17:44AM -0800, Andiry Xu wrote:
> From: Andiry Xu
>
> This header file defines NOVA persistent and volatile superblock
> data structures.
>
> It also defines NOVA block layout:
>
> Page 0: Superblock
> Page 1: Reserved inodes
> Page 2 - 15:
On Sat, Mar 10, 2018 at 10:17:44AM -0800, Andiry Xu wrote:
> From: Andiry Xu
>
> This header file defines NOVA persistent and volatile superblock
> data structures.
>
> It also defines NOVA block layout:
>
> Page 0: Superblock
> Page 1: Reserved inodes
> Page 2 - 15: Reserved
> Page 16 - 31:
On Wed, 14 Mar 2018, Nicolas Pitre wrote:
> On Wed, 14 Mar 2018, Arnd Bergmann wrote:
>
> > The m32r architecture is getting removed, so this part can be
> > cleaned up as well.
> >
> > Signed-off-by: Arnd Bergmann
>
> Acked-by: Nicolas Pitre
>
> > ---
> >
On Wed, 14 Mar 2018, Nicolas Pitre wrote:
> On Wed, 14 Mar 2018, Arnd Bergmann wrote:
>
> > The m32r architecture is getting removed, so this part can be
> > cleaned up as well.
> >
> > Signed-off-by: Arnd Bergmann
>
> Acked-by: Nicolas Pitre
>
> > ---
> > drivers/net/ethernet/smsc/Kconfig
Stephen,
> In preparation to enabling -Wvla, remove VLAs and replace them with
> fixed-length arrays instead.
>
> The arrays fixed here, using the number of constant sections, aren't
> really VLAs, but they appear so to the compiler. Replace the array
> sizes with a pre-processor-level constant
Stephen,
> In preparation to enabling -Wvla, remove VLAs and replace them with
> fixed-length arrays instead.
>
> The arrays fixed here, using the number of constant sections, aren't
> really VLAs, but they appear so to the compiler. Replace the array
> sizes with a pre-processor-level constant
Hi,
I have a ASUS AIO V222GA and another Acer Desktop XC-830 both
have Intel CPU J5005 and they both hit the same problem. The XHCI
connected USB keyboard/mouse can never wakeup the system from suspend.
It reminds me that similiar thing happens on ApolloLake too which
needs the
Hi,
I have a ASUS AIO V222GA and another Acer Desktop XC-830 both
have Intel CPU J5005 and they both hit the same problem. The XHCI
connected USB keyboard/mouse can never wakeup the system from suspend.
It reminds me that similiar thing happens on ApolloLake too which
needs the
Stephen,
> bfad_bsg.c uses a variable-length array declaration to measure the
> size of a putative array; this can be replaced by the product of the
> size of an element and the number of elements, avoiding the VLA
> altogether.
>
> - sizeof(wwn_t[iocmd->nports])) != BFA_STATUS_OK) {
Stephen,
> bfad_bsg.c uses a variable-length array declaration to measure the
> size of a putative array; this can be replaced by the product of the
> size of an element and the number of elements, avoiding the VLA
> altogether.
>
> - sizeof(wwn_t[iocmd->nports])) != BFA_STATUS_OK) {
On Wed, Mar 14, 2018 at 12:34 PM, Stephen Bates wrote:
>> P2P over PCI/PCI-X is quite common in devices like raid controllers.
>
> Hi Dan
>
> Do you mean between PCIe devices below the RAID controller? Isn't it pretty
> novel to be able to support PCIe EPs below a RAID
On Wed, Mar 14, 2018 at 12:34 PM, Stephen Bates wrote:
>> P2P over PCI/PCI-X is quite common in devices like raid controllers.
>
> Hi Dan
>
> Do you mean between PCIe devices below the RAID controller? Isn't it pretty
> novel to be able to support PCIe EPs below a RAID controller (as opposed to
On Wed, Mar 14, 2018 at 05:32:13PM -0500, Eddie James wrote:
> From: Christopher Bostic
>
> Add a struct gpio_chip and define some methods so that this device's
> I/O can be accessed via /sys/class/gpio.
>
> Signed-off-by: Christopher Bostic
On Wed, Mar 14, 2018 at 05:32:13PM -0500, Eddie James wrote:
> From: Christopher Bostic
>
> Add a struct gpio_chip and define some methods so that this device's
> I/O can be accessed via /sys/class/gpio.
>
> Signed-off-by: Christopher Bostic
> Signed-off-by: Andrew Jeffery
> Signed-off-by:
On Wed, Mar 14, 2018 at 05:32:14PM -0500, Eddie James wrote:
> From: Christopher Bostic
>
> Expose the gpiN_fault fields of mfr_status as individual debugfs
> attributes. This provides a way for users to be easily notified of gpi
> faults. Also provide the whole
On Wed, Mar 14, 2018 at 05:32:14PM -0500, Eddie James wrote:
> From: Christopher Bostic
>
> Expose the gpiN_fault fields of mfr_status as individual debugfs
> attributes. This provides a way for users to be easily notified of gpi
> faults. Also provide the whole mfr_status register in debugfs.
>
bumping for review
On Sat, Mar 3, 2018 at 10:50 PM, Nick Desaulniers
wrote:
> Fixes commit 2be04df5668d ("certs/blacklist_nohashes.c: fix const confusion
> in certs blacklist")
>
> Signed-off-by: Nick Desaulniers
> ---
> certs/blacklist.h
bumping for review
On Sat, Mar 3, 2018 at 10:50 PM, Nick Desaulniers
wrote:
> Fixes commit 2be04df5668d ("certs/blacklist_nohashes.c: fix const confusion
> in certs blacklist")
>
> Signed-off-by: Nick Desaulniers
> ---
> certs/blacklist.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> iscsi tcp will first send out data, then calculate and send data
> digest. If we don't have BDI_CAP_STABLE_WRITES, the page cache will
> be written in spite of the on going writeback. Consequently, wrong
> digest will be got and sent to target.
>
> To fix this, set BDI_CAP_STABLE_WRITES when
> iscsi tcp will first send out data, then calculate and send data
> digest. If we don't have BDI_CAP_STABLE_WRITES, the page cache will
> be written in spite of the on going writeback. Consequently, wrong
> digest will be got and sent to target.
>
> To fix this, set BDI_CAP_STABLE_WRITES when
> Never directly free @dev after calling device_register(), even
> if it returned an error! Always use put_device() to give up the
> reference initialized.
Lee, Chris: Please review!
--
Martin K. Petersen Oracle Linux Engineering
> Never directly free @dev after calling device_register(), even
> if it returned an error! Always use put_device() to give up the
> reference initialized.
Lee, Chris: Please review!
--
Martin K. Petersen Oracle Linux Engineering
Hi Wolfgang,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0aa3fdb8b3a6df3c2e3b61dbfe079db9d30e03cd
commit: 6cdeaed3b1420bd2569891be0c4123ff59628e9e media: dvb_usb_pctv452e:
module refcount changes were
Hi Wolfgang,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 0aa3fdb8b3a6df3c2e3b61dbfe079db9d30e03cd
commit: 6cdeaed3b1420bd2569891be0c4123ff59628e9e media: dvb_usb_pctv452e:
module refcount changes were
On Thu, 15 Mar 2018, Borislav Petkov wrote:
> On Wed, Mar 14, 2018 at 10:00:14PM -0300, Henrique de Moraes Holschuh wrote:
> > Intel takes anything from twenty thousand cycles to several *million*
> > cycles per core, proportional to microcode update size.
>
> Got any hard data to back that claim
On Thu, 15 Mar 2018, Borislav Petkov wrote:
> On Wed, Mar 14, 2018 at 10:00:14PM -0300, Henrique de Moraes Holschuh wrote:
> > Intel takes anything from twenty thousand cycles to several *million*
> > cycles per core, proportional to microcode update size.
>
> Got any hard data to back that claim
Stephen,
>> It would be useful if those configurations were not left behind so
>> that Linux could feasibly deploy offload code to a controller in the
>> PCI domain.
>
> Agreed. I think this would be great. Kind of like the XCOPY framework
> that was proposed a while back for SCSI devices
Stephen,
>> It would be useful if those configurations were not left behind so
>> that Linux could feasibly deploy offload code to a controller in the
>> PCI domain.
>
> Agreed. I think this would be great. Kind of like the XCOPY framework
> that was proposed a while back for SCSI devices
Colin,
> There are several unions that are local to the source and do not need
> to be in global scope, so make them static. Also add in a missing void
> parameter to functions lpfc_nvme_cmd_template and
> lpfc_nvmet_cmd_template to clean up non-ANSI warning.
Applied to 4.17/scsi-queue. Thanks!
Colin,
> There are several unions that are local to the source and do not need
> to be in global scope, so make them static. Also add in a missing void
> parameter to functions lpfc_nvme_cmd_template and
> lpfc_nvmet_cmd_template to clean up non-ANSI warning.
Applied to 4.17/scsi-queue. Thanks!
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
sound/pci/hda/hda_intel.c
between commits:
1ba8f9d30817 ("ALSA: hda: Add a power_save blacklist")
40088dc4e1ea ("ALSA: hda - Revert power_save option default value")
from Linus' tree and commit:
07f4f97d7b4b
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
sound/pci/hda/hda_intel.c
between commits:
1ba8f9d30817 ("ALSA: hda: Add a power_save blacklist")
40088dc4e1ea ("ALSA: hda - Revert power_save option default value")
from Linus' tree and commit:
07f4f97d7b4b
On 3/14/2018 9:54 PM, Arnaldo Carvalho de Melo wrote:
Em Wed, Mar 14, 2018 at 10:04:49AM +0800, Jin, Yao escreveu:
On 3/13/2018 11:20 PM, Arnaldo Carvalho de Melo wrote:
Em Tue, Mar 13, 2018 at 10:16:50PM +0800, Jin Yao escreveu:
There is a requirement to let perf annotate support
On 3/14/2018 9:54 PM, Arnaldo Carvalho de Melo wrote:
Em Wed, Mar 14, 2018 at 10:04:49AM +0800, Jin, Yao escreveu:
On 3/13/2018 11:20 PM, Arnaldo Carvalho de Melo wrote:
Em Tue, Mar 13, 2018 at 10:16:50PM +0800, Jin Yao escreveu:
There is a requirement to let perf annotate support
On Thu, Feb 08, 2018 at 02:47:10PM +0800, Shawn Guo wrote:
> On Mon, Jan 22, 2018 at 07:07:47AM -0800, Andrey Smirnov wrote:
> > Platform device core assumes the ownership of dev.platform_data as
> > well as that it is dynamically allocated and it will try to kfree it
> > as a part of
On Thu, Feb 08, 2018 at 02:47:10PM +0800, Shawn Guo wrote:
> On Mon, Jan 22, 2018 at 07:07:47AM -0800, Andrey Smirnov wrote:
> > Platform device core assumes the ownership of dev.platform_data as
> > well as that it is dynamically allocated and it will try to kfree it
> > as a part of
xenbus_command_reply() did not actually copy the response string and
leaked stack content instead.
Fixes: 9a6161fe73bd ("xen: return xenstore command failures via response
instead of rc")
Signed-off-by: Simon Gaiser
---
PS: AFAICS this is not a security issue
xenbus_command_reply() did not actually copy the response string and
leaked stack content instead.
Fixes: 9a6161fe73bd ("xen: return xenstore command failures via response
instead of rc")
Signed-off-by: Simon Gaiser
---
PS: AFAICS this is not a security issue since /dev/xen/xenbus is
normally
Rafael J told me in order for the ACPI-based physical CPU hotplug to work,
there have to be objects in the ACPI namespace corresponding to all of the
processors in question. If they are not present, there is no way to signal
insertion and eject the processors safely.
But, Kernel calculates the
Rafael J told me in order for the ACPI-based physical CPU hotplug to work,
there have to be objects in the ACPI namespace corresponding to all of the
processors in question. If they are not present, there is no way to signal
insertion and eject the processors safely.
But, Kernel calculates the
On Wed, Mar 14, 2018 at 2:44 PM, dbasehore . wrote:
> On Wed, Mar 14, 2018 at 3:22 AM, Marc Zyngier wrote:
>> On 02/03/18 02:08, dbasehore . wrote:
>>> On Thu, Mar 1, 2018 at 4:29 AM, Marc Zyngier wrote:
Hi Mark,
On Wed, Mar 14, 2018 at 2:44 PM, dbasehore . wrote:
> On Wed, Mar 14, 2018 at 3:22 AM, Marc Zyngier wrote:
>> On 02/03/18 02:08, dbasehore . wrote:
>>> On Thu, Mar 1, 2018 at 4:29 AM, Marc Zyngier wrote:
Hi Mark,
On 01/03/18 11:41, Mark Rutland wrote:
> On Wed, Feb 28, 2018
Hi Andy,
At 03/15/2018 01:24 AM, Andy Shevchenko wrote:
On Wed, Mar 14, 2018 at 12:28 PM, Dou Liyang wrote:
+static void __init acpi_update_possible_map(void)
+{
+ unsigned int cpu, nr = 0;
+
+ if (nr_cpu_ids <= nr_unique_ids)
+ return;
Hi Andy,
At 03/15/2018 01:24 AM, Andy Shevchenko wrote:
On Wed, Mar 14, 2018 at 12:28 PM, Dou Liyang wrote:
+static void __init acpi_update_possible_map(void)
+{
+ unsigned int cpu, nr = 0;
+
+ if (nr_cpu_ids <= nr_unique_ids)
+ return;
+
+
Genuine offer
How are you today and your family, I am a citizen of Sudan but
currently staying in Burkina Faso. My name is Miss Mariam Dim Deng,
25years old originated from Sudan.
My late father Dr. Dominic Dim Deng was the former Minister for SPLA
Affair and Special Adviser to President Salva
Genuine offer
How are you today and your family, I am a citizen of Sudan but
currently staying in Burkina Faso. My name is Miss Mariam Dim Deng,
25years old originated from Sudan.
My late father Dr. Dominic Dim Deng was the former Minister for SPLA
Affair and Special Adviser to President Salva
Hi Herbert,
Today's linux-next merge of the crypto tree got a conflict in:
drivers/crypto/bfin_crc.c
between commit:
1d77094897bc ("crypto: remove blackfin CRC driver")
from the asm-generic tree and commits:
f1b298103e14 ("crypto: bfin_crc - Add empty hash export and import")
Hi Herbert,
Today's linux-next merge of the crypto tree got a conflict in:
drivers/crypto/bfin_crc.c
between commit:
1d77094897bc ("crypto: remove blackfin CRC driver")
from the asm-generic tree and commits:
f1b298103e14 ("crypto: bfin_crc - Add empty hash export and import")
On Wed, Mar 14, 2018 at 1:52 PM, Arnd Bergmann wrote:
> On Wed, Mar 14, 2018 at 4:50 AM, Deepa Dinamani
> wrote:
>> The file arch/arm64/kernel/process.c needs asm/compat.h also to be
>> included directly since this is included conditionally from
>>
On Wed, Mar 14, 2018 at 1:52 PM, Arnd Bergmann wrote:
> On Wed, Mar 14, 2018 at 4:50 AM, Deepa Dinamani
> wrote:
>> The file arch/arm64/kernel/process.c needs asm/compat.h also to be
>> included directly since this is included conditionally from
>> include/compat.h. This does seem to be typical
On Wed, 2018-03-14 at 12:57 -0700, Tejun Heo wrote:
> Hello,
>
> On Sat, Mar 10, 2018 at 04:47:28AM +0100, Mike Galbraith wrote:
> > Some form of cpu_exclusive (preferably exactly that, but something else
> > could replace it) is needed to define sets that must not overlap any
> > other set at
On Wed, 2018-03-14 at 12:57 -0700, Tejun Heo wrote:
> Hello,
>
> On Sat, Mar 10, 2018 at 04:47:28AM +0100, Mike Galbraith wrote:
> > Some form of cpu_exclusive (preferably exactly that, but something else
> > could replace it) is needed to define sets that must not overlap any
> > other set at
Hi Boris,
Today's linux-next merge of the nand tree got a conflict in:
drivers/mtd/nand/Kconfig
(mostly moved to drivers/mtd/nand/raw/Kconfig)
drivers/mtd/nand/Makefile
(mostly moved to drivers/mtd/nand/raw/Makefile)
drivers/mtd/nand/bf5xx_nand.c
(renamed to
On 14-03-18, 16:35, Arnd Bergmann wrote:
> The blackfin architecture is getting removed, so this driver is
> now obsolete.
>
> Signed-off-by: Arnd Bergmann
> ---
> drivers/cpufreq/Makefile | 1 -
> drivers/cpufreq/blackfin-cpufreq.c | 217
>
Hi Boris,
Today's linux-next merge of the nand tree got a conflict in:
drivers/mtd/nand/Kconfig
(mostly moved to drivers/mtd/nand/raw/Kconfig)
drivers/mtd/nand/Makefile
(mostly moved to drivers/mtd/nand/raw/Makefile)
drivers/mtd/nand/bf5xx_nand.c
(renamed to
On 14-03-18, 16:35, Arnd Bergmann wrote:
> The blackfin architecture is getting removed, so this driver is
> now obsolete.
>
> Signed-off-by: Arnd Bergmann
> ---
> drivers/cpufreq/Makefile | 1 -
> drivers/cpufreq/blackfin-cpufreq.c | 217
> -
>
This adds the algorithm to maintain a system wide PASID name space
for the PASID allocation. Previously we maintained a per IOMMU unit
PASID name space which is not suitable for some use cases. For an
example, one application (associated with one PASID) might talk to
two physical devices
This adds the algorithm to maintain a system wide PASID name space
for the PASID allocation. Previously we maintained a per IOMMU unit
PASID name space which is not suitable for some use cases. For an
example, one application (associated with one PASID) might talk to
two physical devices
On 14-03-18, 16:35, Arnd Bergmann wrote:
> The cris architecture is getting removed, including the artpec3
> and etraxfs SoCs, so these cpufreq drivers are now unused.
>
> Signed-off-by: Arnd Bergmann
> ---
> drivers/cpufreq/Makefile | 2 -
>
On 14-03-18, 16:35, Arnd Bergmann wrote:
> The cris architecture is getting removed, including the artpec3
> and etraxfs SoCs, so these cpufreq drivers are now unused.
>
> Signed-off-by: Arnd Bergmann
> ---
> drivers/cpufreq/Makefile | 2 -
>
This patch switches PASID management for SVM from SVM specific
idr to the global idr.
Cc: Ashok Raj
Cc: Jacob Pan
Cc: Kevin Tian
Cc: Liu Yi L
Signed-off-by: Lu Baolu
By guaranteeing that the argument of XS_TRANSACTION_END is valid we can
assume that the transaction has been closed when we get an XS_ERROR
response from xenstore (Note that we already verify that it's a valid
transaction id).
Signed-off-by: Simon Gaiser
---
This patch switches PASID management for SVM from SVM specific
idr to the global idr.
Cc: Ashok Raj
Cc: Jacob Pan
Cc: Kevin Tian
Cc: Liu Yi L
Signed-off-by: Lu Baolu
Reviewed-by: Kevin Tian
---
drivers/iommu/intel-svm.c | 20 +---
include/linux/intel-iommu.h | 1 -
2
By guaranteeing that the argument of XS_TRANSACTION_END is valid we can
assume that the transaction has been closed when we get an XS_ERROR
response from xenstore (Note that we already verify that it's a valid
transaction id).
Signed-off-by: Simon Gaiser
---
As we move the PASID idr out of SVM code and make it serving
as a global PASID name space, the consumer can specify a ptr
to bind it with a PASID. We shouldn't assume that each PASID
will be bond with a ptr of struct intel_svm anymore.
This patch cleans up a idr_for_each_entry() usage in the SVM
As we move the PASID idr out of SVM code and make it serving
as a global PASID name space, the consumer can specify a ptr
to bind it with a PASID. We shouldn't assume that each PASID
will be bond with a ptr of struct intel_svm anymore.
This patch cleans up a idr_for_each_entry() usage in the SVM
Hi,
This patch series is trying to change the scope of PASID management
used in Intel IOMMU driver from per IOMMU to driver global. This is
required for some cases where current per-IOMMU PASID name space
doesn't work. For an example, one application (associated with one
PASID) might talk to two
Hi,
This patch series is trying to change the scope of PASID management
used in Intel IOMMU driver from per IOMMU to driver global. This is
required for some cases where current per-IOMMU PASID name space
doesn't work. For an example, one application (associated with one
PASID) might talk to two
Users of the xenbus functions should never close a non existent
transaction (for example by trying to closing the same transaction
twice) but better catch it in xs_request_exit() than to corrupt the
reference counter.
Signed-off-by: Simon Gaiser
---
Users of the xenbus functions should never close a non existent
transaction (for example by trying to closing the same transaction
twice) but better catch it in xs_request_exit() than to corrupt the
reference counter.
Signed-off-by: Simon Gaiser
---
drivers/xen/xenbus/xenbus_xs.c | 4 +++-
1
Commit fd8aa9095a95 ("xen: optimize xenbus driver for multiple
concurrent xenstore accesses") made a subtle change to the semantic of
xenbus_dev_request_and_reply() and xenbus_transaction_end().
Before on an error response to XS_TRANSACTION_END
xenbus_dev_request_and_reply() would not decrement
Commit fd8aa9095a95 ("xen: optimize xenbus driver for multiple
concurrent xenstore accesses") made a subtle change to the semantic of
xenbus_dev_request_and_reply() and xenbus_transaction_end().
Before on an error response to XS_TRANSACTION_END
xenbus_dev_request_and_reply() would not decrement
Hi Emil,
On Wednesday, March 14, 2018 08:02 PM, Emil Velikov wrote:
Hi Lin,
On 14 March 2018 at 09:12, Lin Huang wrote:
From: huang lin
Refactor Innolux P079ZCA panel driver, let it support
multi panel.
Change-Id:
Hi Emil,
On Wednesday, March 14, 2018 08:02 PM, Emil Velikov wrote:
Hi Lin,
On 14 March 2018 at 09:12, Lin Huang wrote:
From: huang lin
Refactor Innolux P079ZCA panel driver, let it support
multi panel.
Change-Id: If89be5e56dba8cb498e2d50c1bbeb0e8016123a2
Signed-off-by: Lin Huang
---
On 03/14/2018 06:48 PM, Daniel Kurtz wrote:
> Commit 470ca0de69fe ("serial: earlycon: Enable earlycon without command
> line param") added EARLYCON_TABLE().
>
> Commit 99492c39f39f ("earlycon: Fix __earlycon_table stride") referenced
> commit 07fca0e57fca92 ("tracing: Properly align linker
On 03/14/2018 06:48 PM, Daniel Kurtz wrote:
> Commit 470ca0de69fe ("serial: earlycon: Enable earlycon without command
> line param") added EARLYCON_TABLE().
>
> Commit 99492c39f39f ("earlycon: Fix __earlycon_table stride") referenced
> commit 07fca0e57fca92 ("tracing: Properly align linker
On Wed, Mar 14, 2018 at 6:36 PM, Ard Biesheuvel
wrote:
> On 14 March 2018 at 16:41, Ard Biesheuvel wrote:
>> On 14 March 2018 at 15:54, Ard Biesheuvel wrote:
>>> On 14 March 2018 at 14:54, Michal Hocko
Linus,
> I've pulled it, but I don't see why (and how) this kind of garbage got
> reviewed and acked by multiple people.
My bad. I actually did notice the superfluous ifs and meant to nuke them
when I committed the patch.
However, I had a freak accident with my fixes branch that day that
On Wed, Mar 14, 2018 at 6:36 PM, Ard Biesheuvel
wrote:
> On 14 March 2018 at 16:41, Ard Biesheuvel wrote:
>> On 14 March 2018 at 15:54, Ard Biesheuvel wrote:
>>> On 14 March 2018 at 14:54, Michal Hocko wrote:
On Wed 14-03-18 14:35:12, Ard Biesheuvel wrote:
> On 14 March 2018 at 14:13,
Linus,
> I've pulled it, but I don't see why (and how) this kind of garbage got
> reviewed and acked by multiple people.
My bad. I actually did notice the superfluous ifs and meant to nuke them
when I committed the patch.
However, I had a freak accident with my fixes branch that day that
1 - 100 of 2500 matches
Mail list logo