This patch adds missing MIX2 path on RX1/2 which take IIR1 and
IIR2 as inputs.
Without this patch sound card fails to intialize with below warning:
ASoC: no sink widget found for RX1 MIX2 INP1
ASoC: Failed to add route IIR1 -> IIR1 -> RX1 MIX2 INP1
ASoC: no sink widget found for RX2 MIX2 INP1
Test virtual server via ipip tunnel.
Tested:
# selftests: netfilter: ipvs.sh
# Testing DR mode...
# Testing NAT mode...
# Testing Tunnel mode...
# ipvs.sh: PASS
ok 6 selftests: netfilter: ipvs.sh
Signed-off-by: Haishuang Yan
---
v2: optimize test script
---
tools/testing/selftests/netfilter/ipv
Test virtual server via NAT.
Tested:
# selftests: netfilter: ipvs.sh
# Testing DR mode...
# Testing NAT mode...
# ipvs.sh: PASS
Signed-off-by: Haishuang Yan
---
tools/testing/selftests/netfilter/ipvs.sh | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/t
Test virutal server via directing routing for IPv4.
Tested:
# selftests: netfilter: ipvs.sh
# Testing DR mode...
# ipvs.sh: PASS
ok 6 selftests: netfilter: ipvs.sh
Signed-off-by: Haishuang Yan
---
v5: use cmp to compare two file contents suggested by Simon Horman
v4: use #!/bin/bash -p suggeste
On 09/10/19 12:42, Vitaly Kuznetsov wrote:
> Paolo Bonzini writes:
>> There is no practical difference with Vitaly's patch. The first
>> _vcpu_run has no pre-/post-conditions on the value of %rbx:
>
> I think what Sean was suggesting is to prevent GCC from inserting
> anything (and thus clobberi
On 2019/10/9 17:48, James Clark wrote:
> Hi Xiaojun,
>
>> By the way, you mentioned before that you want the spe event to be in the
>> form of "event:pp" like pebs. Is that the whole framework should be made
>> similar to pebs? Or is it just a modification to the command format?
>
> We're curr
On 29/09/19 18:43, Julia Lawall wrote:
> From: kbuild test robot
>
> Use BUG_ON instead of a if condition followed by BUG.
>
> Generated by: scripts/coccinelle/misc/bugon.cocci
>
> Fixes: 4b526de50e39 ("KVM: x86: Check kvm_rebooting in kvm_spurious_fault()")
> CC: Sean Christopherson
> Signed-
On 27/09/19 23:45, Sean Christopherson wrote:
> Handle caching CR3 (from VMX's VMCS) into struct kvm_vcpu via the common
> cache_reg() callback and drop the dedicated decache_cr3(). The name
> decache_cr3() is somewhat confusing as the caching behavior of CR3
> follows that of GPRs, RFLAGS and PDP
On 30/09/19 11:32, Vitaly Kuznetsov wrote:
>> +static inline void kvm_register_mark_dirty(struct kvm_vcpu *vcpu,
>> + enum kvm_reg reg)
>> +{
>> +__set_bit(reg, (unsigned long *)&vcpu->arch.regs_avail);
>> +__set_bit(reg, (unsigned long *)&vcpu->arch.re
On 07/10/2019 19:11, Jason Gunthorpe wrote:
> On Mon, Oct 07, 2019 at 05:20:30PM +0100, Steven Price wrote:
>> On 07/10/2019 17:10, Jason Gunthorpe wrote:
>>> On Mon, Oct 07, 2019 at 04:38:14PM +0100, Steven Price wrote:
diff --git a/mm/hmm.c b/mm/hmm.c
index 902f5fa6bf93..34fe904dd417 10
> -Original Message-
> From: Christoph Hellwig
> Sent: Wednesday, October 9, 2019 10:39 AM
> To: Madalin-cristian Bucur
> Cc: da...@davemloft.net; net...@vger.kernel.org; Roy Pledge
> ; Laurentiu Tudor ; linux-
> ker...@vger.kernel.org
> Subject: Re: [PATCH 19/20] dpaa_eth: add dpaa_dma_t
On 2019-10-08 8:52 pm, Rob Herring wrote:
From: Robin Murphy
Since the "dma-ranges" property is only valid for a node representing a
bus, of_dma_get_range() currently assumes the node passed in is a leaf
representing a device, and starts the walk from its parent. In cases
like PCI host controll
On 10/02/19 09:20, Jing-Ting Wu wrote:
> On Thu, 2019-09-19 at 16:11 +0100, Qais Yousef wrote:
> > On 09/19/19 16:37, Vincent Guittot wrote:
> > > On Thu, 19 Sep 2019 at 16:32, Vincent Guittot
> > > wrote:
> > > >
> > > > On Thu, 19 Sep 2019 at 16:23, Qais Yousef wrote:
> > > > >
> > > > > On 09/
Hi Andreas,
On Wed, Oct 9, 2019 at 12:06 PM Andreas Schwab wrote:
> On Okt 09 2019, Geert Uytterhoeven wrote:
> > I believe risc-v is DT-only, so if chosen/stdout-path is set up
>
> If. Currently, it isn't.
IC. So isn't it better to fix that, instead of pointing people to more obscure
legacy s
On 08/10/2019 22:33, Paul Walmsley wrote:
> On Mon, 7 Oct 2019, Steven Price wrote:
>
>> walk_page_range() is going to be allowed to walk page tables other than
>> those of user space. For this it needs to know when it has reached a
>> 'leaf' entry in the page tables. This information is provided
On 30/09/19 11:25, Vitaly Kuznetsov wrote:
>> -enum kvm_reg_ex {
>> VCPU_EXREG_PDPTR = NR_VCPU_REGS,
> (Personally, I would've changed that to NR_VCPU_REGS + 1)
>
Why?
Paolo
On 27/09/19 23:45, Sean Christopherson wrote:
> Open code the RIP and RSP accessors so as to avoid pointless overhead of
> WARN_ON_ONCE().
Is there actually an overhead here? It is effectively WARN_ON_ONCE(0)
which should be compiled out just fine.
Paolo
The driver was accessing its struct usb_interface from its release()
callback without holding a reference. This would lead to a
use-after-free whenever debugging was enabled and the device was
disconnected while its character device was open.
Fixes: 549e83500b80 ("USB: iowarrior: Convert local dbg
This series fixes a use-after-free bug introduced by a recent
disconnect-deadlock fix that was reported by syzbot. Turns out there was
already a related bug in the driver, and the first patch addresses both
issues.
While looking at the code I found two more use-after-free bugs, which
the next two
A recent fix addressing a deadlock on disconnect introduced a new bug
by moving the present flag out of the critical section protected by the
driver-data mutex. This could lead to a racing release() freeing the
driver data before disconnect() is done with it.
Due to insufficient locking a related
Drop the redundant iowarrior mutex introduced by commit 925ce689bb31
("USB: autoconvert trivial BKL users to private mutex") which replaced
an earlier BKL use.
The lock serialised calls to open() against other open() and ioctl(),
but neither is needed.
Signed-off-by: Johan Hovold
---
drivers/us
Drop the redundant disconnect mutex which was introduced after the
open-disconnect race had been addressed generally in USB core by commit
d4ead16f50f9 ("USB: prevent char device open/deregister race").
Specifically, the rw-semaphore in core guarantees that all calls to
open() will have completed
Replace the one remaining printk with pr_err().
Signed-off-by: Johan Hovold
---
drivers/usb/misc/iowarrior.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/misc/iowarrior.c b/drivers/usb/misc/iowarrior.c
index ad29ef51e53f..dce44fbf031f 100644
--- a/drivers/usb/m
Make sure to stop also the asynchronous write URBs on disconnect() to
avoid use-after-free in the completion handler after driver unbind.
Fixes: 946b960d13c1 ("USB: add driver for iowarrior devices.")
Cc: stable # 2.6.21: 51a2f077c44e ("USB: introduce
usb_anchor")
Signed-off-by: Johan Hovold
On Tue, Oct 08, 2019 at 03:00:14PM -0700, Dmitry Torokhov wrote:
> On Mon, Oct 07, 2019 at 10:50:21PM +0200, Stephan Gerhold wrote:
> > MMS345L is another first generation touch screen from Melfas,
> > which uses the same registers as MMS152.
> >
> > However, using I2C_M_NOSTART for it causes erro
On Tue, Sep 24, 2019 at 10:28:48AM -0700, Jeykumar Sankaran wrote:
> Reviving this thread from the context of the below conversion:
>
> https://lore.kernel.org/linux-arm-msm/db26145b-3f64-a334-f698-76f972332...@baylibre.com/T/#u
>
> On 2018-10-05 01:19, Neil Armstrong wrote:
> > On 05/10/2018 09:
Hello,
On Wed, Jul 31, 2019 at 11:24:12AM -0700, Matt Helsley wrote:
> Recordmcount uses setjmp/longjmp to manage control flow as
> it reads and then writes the ELF file. This unusual control
> flow is hard to follow and check in addition to being unlike
> kernel coding style.
>
> So we rewrite t
Capacity Awareness refers to the fact that on heterogeneous systems
(like Arm big.LITTLE), the capacity of the CPUs is not uniform, hence
when placing tasks we need to be aware of this difference of CPU
capacities.
In such scenarios we want to ensure that the selected CPU has enough
capacity to me
From: Sudheer Papothi
For wigdets which have set the suspend ignore flag asoc framework
shouldn't mark them as dirty when ASoC suspend function is called.
This change adds check to skip suspending the widgets with the flag set.
Signed-off-by: Gopikrishnaiah Anandan
Signed-off-by: Sudheer Papoth
On Wed, Oct 09, 2019 at 12:16:37PM +0200, Uwe Kleine-König wrote:
> On Wed, Oct 09, 2019 at 10:56:35AM +0100, Daniel Thompson wrote:
> > On Wed, Oct 09, 2019 at 11:27:13AM +0200, Enric Balletbo i Serra wrote:
> > > Hi Uwe,
> > >
> > > Adding Daniel and Lee to the discussion ...
> >
> > Thanks!
>
Hi,
On 09.10.2019 12:35, Hans de Goede wrote:
> Hi Denis,
>
> On 30-09-2019 13:01, Denis Efremov wrote:
>> memcpy() in phy_ConfigBBWithParaFile() and PHY_ConfigRFWithParaFile() is
>> called with "src == NULL && len == 0". This is an undefined behavior.
>> Moreover this if pre-condition "pBufLen &
Paolo Bonzini writes:
> On 08/10/19 20:36, Sean Christopherson wrote:
>> On Tue, Oct 08, 2019 at 08:08:08PM +0200, Vitaly Kuznetsov wrote:
>>> Commit 204c91eff798a ("KVM: selftests: do not blindly clobber registers in
>>> guest asm") was intended to make test more gcc-proof, however, the result
On 27/09/19 23:45, Sean Christopherson wrote:
> Rework vmx_set_rflags() to avoid the extra code need to handle emulation
> of real mode and invalid state when unrestricted guest is disabled. The
> primary reason for doing so is to avoid the call to vmx_get_rflags(),
> which will incur a VMREAD whe
On Tue, Oct 08, 2019 at 02:05:16PM -0400, Joel Fernandes wrote:
> On Tue, Oct 08, 2019 at 03:01:59PM +0200, Christian Brauner wrote:
> > When a binder transaction is initiated on a binder device coming from a
> > binderfs instance, a pointer to the name of the binder device is stashed
> > in the bi
Hi Jonas,
On 10/1/19 10:52 PM, Jonas Karlman wrote:
> When EDID is refreshed, HDMI cable is unplugged/replugged or
> an AVR is power cycled the CEC phys addr gets invalidated.
>
> This can cause some disruption of CEC communication when
> adapter is being reconfigured.
>
> Add a debounce module
On Tue, 8 Oct 2019, Steven Rostedt wrote:
> On Tue, 8 Oct 2019 15:35:34 -0400
> Joe Lawrence wrote:
>
> >
> > I wonder if the opposite would be more intuitive: when ftrace_enabled is
> > not set, don't allow livepatches to register ftrace filters and
> > likewise, don't allow ftrace_enabled to
Hello Aleksa,
On 10/9/19 12:17 PM, Aleksa Sarai wrote:
> On 2019-10-09, Michael Kerrisk (man-pages) wrote:
>> Hello Aleksa,
>>
>> Thanks for this. It's a great piece of documentation work!
>>
>> I would prefer the path_resolution(7) piece as a separate patch.
>
> Thanks, and will do.
>
>> On 10
Hi Mark,
On 08.10.2019 20:07, Mark Brown wrote:
> On Tue, Oct 08, 2019 at 09:00:29PM +0300, Dmitry Osipenko wrote:
>> Properly handling case of a disabled coupled regulator certainly will be
>> useful, but looks like there are no real users for that feature right
>> now and thus no real testing is
The patch supports slave mode for imx I2C driver
Signed-off-by: Biwen Li
---
Change in v2:
- remove MACRO CONFIG_I2C_SLAVE
drivers/i2c/busses/i2c-imx.c | 180 ---
1 file changed, 166 insertions(+), 14 deletions(-)
diff --git a/drivers/i2c/busses/i2c-imx.
Hi,
Are you in need of a loan of any purpose?, Do you want to pay your bills?, Are
you in a financial problem:, Do you need a financial Solution?. Here is the
solution to all your financial problem. We are offering Non Collateral loans
From Minimum of $50,000 to $3,500,000.00 for project, busin
Hi Jonathan,
Thanks for the review!
On Tue, Oct 08, 2019 at 01:27:44PM +0100, Jonathan Cameron wrote:
> On Mon, 7 Oct 2019 21:09:17 +0530
> Manivannan Sadhasivam wrote:
>
> > Add initial support for Analog Devices ADUX1020 Photometric sensor.
> > Only proximity mode has been enabled for now.
>
Hello Eric,
Thank you. I was hoping you might jump in on this thread.
Please see below.
On 10/9/19 10:46 AM, Eric W. Biederman wrote:
> "Michael Kerrisk (man-pages)" writes:
>
>> Hello Philipp,
>>
>> My apologies that it has taken a while to reply. (I had been hoping
>> and waiting that a few
From: Sudheer Papothi
During sound card registration, dapm adds routes of
codec and other component paths, but the invalidation of
the widgets in these paths will happen only when the
sound card is instantiated. As these routes are added
before sound card instantiation, these widgets are
not inva
On Wed, 2019-10-09 at 15:15 +0530, Manivannan Sadhasivam wrote:
> [External]
>
> Hi Ardelean,
>
> Thanks for the quick review!
>
> On Tue, Oct 08, 2019 at 06:52:50AM +, Ardelean, Alexandru wrote:
> > On Mon, 2019-10-07 at 15:40 +0530, Manivannan Sadhasivam wrote:
> > > [External]
> > >
> >
On 09.10.19 11:37, Michal Hocko wrote:
> On Wed 09-10-19 11:12:04, David Hildenbrand wrote:
>> There are various places where we access uninitialized memmaps, namely:
>> - /proc/kpagecount
>> - /proc/kpageflags
>> - /proc/kpagecgroup
>> - memory_failure() - which reuses stable_page_flags() from fs/
On 9/10/19 12:16, Uwe Kleine-König wrote:
> On Wed, Oct 09, 2019 at 10:56:35AM +0100, Daniel Thompson wrote:
>> On Wed, Oct 09, 2019 at 11:27:13AM +0200, Enric Balletbo i Serra wrote:
>>> Hi Uwe,
>>>
>>> Adding Daniel and Lee to the discussion ...
>>
>> Thanks!
>>
>>> On 8/10/19 22:31, Uwe Klein
On 10/7/19 9:01 PM, Jernej Škrabec wrote:
> Dne ponedeljek, 07. oktober 2019 ob 12:44:24 CEST je Hans Verkuil napisal(a):
>> Hi Jernej,
>>
>> On 9/29/19 10:00 PM, Jernej Skrabec wrote:
>>> This series adds support for decoding multi-slice H264 frames along with
>>> support for V4L2_DEC_CMD_FLUSH an
Hi,
Static analysis with Coverity has detected a potential issue in the
Rockchip AXI PCIe endpoint controller driver. The issue is in
drivers/pci/controller/pcie-rockchip-ep.c, function
rockchip_pcie_ep_write_header:
The coverity report is as follows:
124 static int rockchip_pcie_ep_write_heade
SGI IOC3 ASIC includes support for ethernet, PS2 keyboard/mouse,
NIC (number in a can), GPIO and a byte bus. By attaching a
SuperIO chip to it, it also supports serial lines and a parallel
port. The chip is used on a variety of SGI systems with different
configurations. This patchset moves code ou
Failed to get irq using name is NOT fatal as driver will use index
to get irq instead, use platform_get_irq_byname_optional() instead
of platform_get_irq_byname() to avoid below error message during
probe:
[0.819312] fec 30be.ethernet: IRQ int0 not found
[0.824433] fec 30be.etherne
Use platform_get_irq_byname_optional() and platform_get_irq_optional()
instead of platform_get_irq_byname() and platform_get_irq() for optional
IRQs to avoid below error message during probe:
[0.795803] fec 30be.ethernet: IRQ pps not found
[0.800787] fec 30be.ethernet: IRQ index 3
IOC3 chips in SGI system are conntected to a bridge ASIC, which has
a 1-wire prom attached with part number information. This changeset
uses this information to create PCI subsystem information, which
the MFD driver uses for further platform device setup.
Signed-off-by: Thomas Bogendoerfer
---
a
On 2019-10-09, Michael Kerrisk (man-pages) wrote:
> Hello Aleksa,
>
> Thanks for this. It's a great piece of documentation work!
>
> I would prefer the path_resolution(7) piece as a separate patch.
Thanks, and will do.
> On 10/3/19 4:55 PM, Aleksa Sarai wrote:
> > Rather than trying to merge t
nvmem_device_find provides a way to search for nvmem devices with
the help of a match function simlair to bus_find_device.
Reviewed-by: Srinivas Kandagatla
Acked-by: Srinivas Kandagatla
Signed-off-by: Thomas Bogendoerfer
---
Documentation/driver-api/nvmem.rst | 2 ++
drivers/nvmem/core.c
On Thu, Sep 19, 2019 at 01:37:08PM +0200, Greg KH wrote:
> Why is this being submitted for drivers/staging/ and not the "real" part
> of the kernel tree?
Hi Greg!
I sent v2 of the patchset, but it does not need to be part of the
staging tree. I CC-ed de...@driverdev.osuosl.org for reference.
Tha
Our chosen byte swapping, which is what firmware already uses, is to
do readl/writel by normal lw/sw intructions (data invariance). This
also means we need to mangle addresses for u8 and u16 accesses. The
mangling for 16bit has been done aready, but 8bit one was missing.
Correcting this causes diff
On Wed, Oct 09, 2019 at 10:56:35AM +0100, Daniel Thompson wrote:
> On Wed, Oct 09, 2019 at 11:27:13AM +0200, Enric Balletbo i Serra wrote:
> > Hi Uwe,
> >
> > Adding Daniel and Lee to the discussion ...
>
> Thanks!
>
> > On 8/10/19 22:31, Uwe Kleine-König wrote:
> > > On Tue, Oct 08, 2019 at 06:
This is sample implementation of a driver that uses "avalon-dma"
driver interface to perform data transfers between on-chip and
system memory in devices using Avalon-MM DMA Interface for PCIe
design. Companion user-level tool could be found at
https://github.com/a-gordeev/avalon-tool.git
CC: Micha
This series is against v5.4-rc2
Changes since v1:
- "avalon-dma" converted to "dmaengine" model;
- "avalon-drv" renamed to "avalon-test";
The Avalon-MM DMA Interface for PCIe is a design used in hard IPs for
Intel Arria, Cyclone or Stratix FPGAs. It transfers data between on-chip
memory and syste
Support Avalon-MM DMA Interface for PCIe used in hard IPs for
Intel Arria, Cyclone or Stratix FPGAs.
CC: Michael Chen
CC: de...@driverdev.osuosl.org
CC: dmaeng...@vger.kernel.org
Signed-off-by: Alexander Gordeev
---
drivers/dma/Kconfig | 2 +
drivers/dma/Makefile |
On Thu, Oct 03, 2019 at 07:32:40PM +0200, Christian Kellner wrote:
> From: Christian Kellner
>
> The Thunderbolt standard went through several major iterations, here
> called generation. USB4, which will be based on Thunderbolt, will be
> generation 4. Let userspace know the generation of the con
Hello Grygorri,
On 10/9/19 11:43 AM, Grygorii Strashko wrote:
>
>
>>> Grygorii doesn't suggest to add a fixes tag, just to change the
>>> referenced
>>> commit to another. Obviously I would like to understand why another
>>> commit
>>> should be referenced. And then I should read and parse the r
On 03/10/19 23:17, Lendacky, Thomas wrote:
> From: Tom Lendacky
>
> This patch series provides fixes in the area of ASID assignment and VM
> deactivation.
>
> Additionally, it provides some performance enhancements by reducing the
> number of WBINVD/DF_FLUSH invocations that are made.
>
> Note:
On 09.10.2019 10:39, Christoph Hellwig wrote:
> On Tue, Oct 08, 2019 at 03:10:40PM +0300, Madalin Bucur wrote:
>> Centralize the phys_to_virt() calls.
>
> You don't need to centralize those, you need to fix them. Calling
> phys_to_virt on a dma_addr is completely bogus.
>
Yeah, that's on my TOD
Commit ac7c3e4ff401 ("compiler: enable CONFIG_OPTIMIZE_INLINING
forcibly") allows compiler to uninline functions marked as 'inline'.
In cace of __xchg this would cause to reference function
__xchg_called_with_bad_pointer, which is an error case
for catching bugs and will not happen for correct code
Hi Stefan,
I'm thinking about dividing this test into single applications, one
for each test, do you think it makes sense?
Or is it just a useless complication?
Thanks,
Stefano
On Thu, Aug 1, 2019 at 5:27 PM Stefano Garzarella wrote:
>
> From: Stefan Hajnoczi
>
> The vsock_test.c program runs a
On 2019-10-08 10:03 pm, Ard Biesheuvel wrote:
On Tue, 8 Oct 2019 at 18:19, Robin Murphy wrote:
On 08/10/2019 16:22, Sami Tolvanen wrote:
On Mon, Oct 7, 2019 at 2:46 PM 'Nick Desaulniers' via Clang Built
Linux wrote:
I'm worried that one of these might lower to LSE atomics without
ALTERNATIV
On 2019-10-09, Michael Kerrisk (man-pages) wrote:
> Hello Aleksa,
>
> You write "5.FOO" in these patches. When do you expect these changes to
> land in the kernel?
Probably 5.6 (I'd hope for 5.5, but I don't know how the v14 review will
go). I'm not too sure though, and the magic-link changes (
On 2019/10/7 23:46, Will Deacon wrote:
> Hi all,
>
> This is version three of the patches I previously posted here:
>
> v1: https://lkml.kernel.org/r/20190802101000.12958-1-w...@kernel.org
> v2: https://lkml.kernel.org/r/20190827163204.29903-1-w...@kernel.org
>
> Changes since v2 include:
>
The patch
ASoC: jz4740: Remove unused match variable
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.5
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sen
Hi David,
On Wed, Oct 09, 2019 at 11:12:04AM +0200, David Hildenbrand wrote:
> There are various places where we access uninitialized memmaps, namely:
> - /proc/kpagecount
> - /proc/kpageflags
> - /proc/kpagecgroup
> - memory_failure() - which reuses stable_page_flags() from fs/proc/page.c
Ah rig
From: Peng Fan
According Architecture definition guide, SYS_PLL1 is fixed at
800MHz, SYS_PLL2 is fixed at 1000MHz, so let's use imx_clk_fixed
to register the clocks and drop code that could change the rate.
Signed-off-by: Peng Fan
---
drivers/clk/imx/clk-imx8mm.c | 14 --
1 file ch
From: Peng Fan
According Architecture definition guide, SYS_PLL1 is fixed at
800MHz, SYS_PLL2 is fixed at 1000MHz, so let's use imx_clk_fixed
to register the clocks and drop code that could change the rate.
Signed-off-by: Peng Fan
---
drivers/clk/imx/clk-imx8mn.c | 14 --
1 file ch
From: Peng Fan
According Architecture definition guide, SYS1_PLL is fixed at
800MHz, SYS2_PLL is fixed at 1000MHz, so let's use imx_clk_fixed
to register the clocks and drop code that could change the rate.
Signed-off-by: Peng Fan
---
drivers/clk/imx/clk-imx8mq.c | 8 ++--
1 file changed,
On 2019-10-09, Michael Kerrisk (man-pages) wrote:
> On 10/3/19 4:55 PM, Aleksa Sarai wrote:
> > Traditionally, magic-links have not been a well-understood topic in
> > Linux. Given the new changes in their semantics (related to the link
> > mode of trailing magic-links), it seems like a good oppor
On Wed, Oct 09, 2019 at 11:27:13AM +0200, Enric Balletbo i Serra wrote:
> Hi Uwe,
>
> Adding Daniel and Lee to the discussion ...
Thanks!
> On 8/10/19 22:31, Uwe Kleine-König wrote:
> > On Tue, Oct 08, 2019 at 06:33:15PM +0200, Enric Balletbo i Serra wrote:
> >>> A few thoughts to your approach
Hi,
On 19/09/19 9:02 PM, Faiz Abbas wrote:
> The following are dts patches to add MMC/SD Support on TI's J721e base
> board.
>
> Patches depend on Lokesh's gpio patches[1] and device exclusivity patches[2].
>
> [1] https://patchwork.kernel.org/cover/11085643/
> [2] https://patchwork.kernel.org/c
On Wed, Oct 09, 2019 at 11:21:41AM +0200, Paolo Bonzini wrote:
> On 13/09/19 21:01, Suthikulpanit, Suravee wrote:
> > /*
> > +* In case APICv accelerate EOI write and do not trap,
> > +* in-kernel IOAPIC will not be able to receive the EOI.
> > +* In this case, we do lazy update of
On Tue, Oct 08, 2019 at 10:41:42PM +, Dexuan Cui wrote:
> > From: Vitaly Kuznetsov
> > Sent: Tuesday, October 8, 2019 6:00 AM
> > ...
> > > Looking at the uses of VERSION_INVAL, I find one remaining occurrence
> > > of this macro in vmbus_bus_resume(), which does:
> > >
> > > if (vmbus_prot
On Tue, Oct 08, 2019 at 10:16:22PM +0200, Marco Felsch wrote:
> On 19-10-08 17:23, Mark Brown wrote:
> > As you'll have seen from the discussion that's a bug, nothing should be
> > taking a reference to the regulator outside of explicit enable calls.
> Okay now we are on the right way :) Is the s
Hello David,
See my previous mails.
There is no fsinfo(2) in the system call in the kernel currently.
Will that call still be added, or was it replaced by fsconfig(2),
which--as far as I can tell--dnot have a man-pages patch?
Thanks,
Michael
On 7/11/18 12:55 AM, David Howells wrote:
> Add a ma
Hello David,
See my previous mail.
With respect to the patch below, would you be willing to review
the content of this man-pages patch to see if it accurately reflects
what was merged into the kernel, and then resubmit please?
Thanks,
Michael
On 7/11/18 12:54 AM, David Howells wrote:
> Add a
Hello David,
Your wrote a series of manual pages patches (of which the mail below is one)
for the new mount API about a year before the code patches were actually
released in the kernel.
I'd like to check that these man-pages patches are up to date before
merging them. I think they may not be, si
All i.MX SoCs except i.MX1 have ONLY one necessary IRQ, use
platform_get_irq_optional() to get second/third IRQ which are
optional to avoid below error message during probe:
[0.726219] imx-uart 3086.serial: IRQ index 1 not found
[0.731329] imx-uart 3086.serial: IRQ index 2 not foun
On 10/8/19 4:45 PM, Uwe Kleine-König wrote:
> On Tue, Oct 08, 2019 at 01:41:27PM +0200, Fabrice Gasnier wrote:
>> Add a comment to better describe the purpose of breakinput feature that
>> can be found on some STM32 timer instances. Briefly comment on the
>> characteristics of this input for PWM, a
Hi Xiaojun,
> By the way, you mentioned before that you want the spe event to be in the
> form of "event:pp" like pebs. Is that the whole framework should be made
> similar to pebs? Or is it just a modification to the command format?
We're currently still investigating if it makes sense to mod
Quoting Colin King (2019-10-09 10:39:35)
> From: Colin Ian King
>
> An earlier commit removed any error assignments to err and we
> are now left with a zero assignment to err and a check that is
> always false. Clean this up by removing the redundant variable
> err and the error check.
Oh, we ad
Hi Andy,
On 9/10/2019 5:40 PM, Andy Shevchenko wrote:
On Wed, Oct 09, 2019 at 09:06:16AM +0800, Ramuthevar, Vadivel MuruganX wrote:
Hi Adrian,
Thank you for the Acked-by, will add *Acked-by* in the next-patch.
Please, stop top-posting.
Besides that, there is no need for next version if
Hello, Daniel.
On Wed, Oct 09, 2019 at 08:05:39AM +0200, Daniel Wagner wrote:
> On Tue, Oct 08, 2019 at 06:04:59PM +0200, Uladzislau Rezki wrote:
> > > so, we do not guarantee, instead we minimize number of allocations
> > > with GFP_NOWAIT flag. For example on my 4xCPUs i am not able to
> > > eve
From: Colin Ian King
The memset appears to have the 2nd and 3rd arguments in the wrong
order, fix this by swapping these around into the correct order.
Addresses-Coverity: ("Memset fill truncated")
Fixes: 4f8b7fabb15d ("staging: wfx: allow to send commands to chip")
Signed-off-by: Colin Ian King
Wed, Oct 09, 2019 at 11:22:00AM CEST,
syzbot+d2a8670576fa63d18...@syzkaller.appspotmail.com wrote:
>syzbot has bisected this bug to:
>
>commit 057af70713445fad2459aa348c9c2c4ecf7db938
>Author: Jiri Pirko
>Date: Sat Oct 5 18:04:39 2019 +
>
>net: tipc: have genetlink code to parse the att
Hi Ardelean,
Thanks for the quick review!
On Tue, Oct 08, 2019 at 06:52:50AM +, Ardelean, Alexandru wrote:
> On Mon, 2019-10-07 at 15:40 +0530, Manivannan Sadhasivam wrote:
> > [External]
> >
>
> Hey,
>
> Comments inline.
>
> I thought I sent an initial review, but seems to have gotten lo
On Fri, Sep 27, 2019 at 01:27:01PM +0200, Stefano Garzarella wrote:
> VMCI transport provides both g2h and h2g behaviors in a single
> transport.
> We are able to set (or not) the g2h behavior, detecting if we
> are in a VMware guest (or not), but the h2g feature is always set.
> This prevents to l
On Mon, Sep 16, 2019 at 10:17:36AM +0800, Xiaowei Bao wrote:
> This patch set are for adding Mobiveil EP driver and adding PCIe Gen4
> EP driver of NXP Layerscape platform.
>
> This patch set depends on:
> https://patchwork.kernel.org/project/linux-pci/list/?series=159139
>
I've not had any feed
On 08/10/2019 20:02, Tony Lindgren wrote:
* Jeroen Hofstee [191008 17:00]:
Hi,
On 10/8/19 6:51 PM, Tony Lindgren wrote:
* Jeroen Hofstee [191008 16:43]:
Hello Tony,
On 10/8/19 6:14 PM, Tony Lindgren wrote:
* Jeroen Hofstee [191008 16:03]:
Hello Tony,
On 10/8/19 4:23 PM, Tony Lindgre
On 08/10/19 20:36, Sean Christopherson wrote:
> On Tue, Oct 08, 2019 at 08:08:08PM +0200, Vitaly Kuznetsov wrote:
>> Commit 204c91eff798a ("KVM: selftests: do not blindly clobber registers in
>> guest asm") was intended to make test more gcc-proof, however, the result
>> is exactly the opposite: o
On Wed, Oct 09, 2019 at 09:06:16AM +0800, Ramuthevar, Vadivel MuruganX wrote:
> Hi Adrian,
>
> Thank you for the Acked-by, will add *Acked-by* in the next-patch.
Please, stop top-posting.
Besides that, there is no need for next version if the only comments you got
are ACKs. Rb:s, etc.
--
W
Hi Hans,
also adding Ingo on Cc.
I tested you patch on s390 and it does what it's supposed to do. The build now
fails with
LD arch/s390/purgatory/purgatory.chk
arch/s390/purgatory/purgatory: In function `sha256_update':
(.text+0x3bc2): undefined reference to `memzero_explicit'
/home/prud
Include to fix the following warnings
from missing declarations:
drivers/gpu/drm/drm_fb_cma_helper.c:38:27: warning: symbol
'drm_fb_cma_get_gem_obj' was not declared. Should it be static?
drivers/gpu/drm/drm_fb_cma_helper.c:62:12: warning: symbol
'drm_fb_cma_get_gem_addr' was not declared. Shou
platform_get_irq_optional is just a wrapper for __platform_get_irq. So
rename __platform_get_irq to platform_get_irq_optional and drop
platform_get_irq_optional's previous implementation. This way there is
one function and one indirection less without loss of functionality.
Signed-off-by: Uwe Klei
901 - 1000 of 1156 matches
Mail list logo
