On 12/05/2016 10:10 AM, Niklas Cassel wrote:
> From: Niklas Cassel
>
> commit 64c3b252e9fc ("net: stmmac: fixed the pbl setting with DT")
> changed the parsing of the DT binding.
>
> Before 64c3b252e9fc, snps,fixed-burst and snps,mixed-burst were parsed
> regardless if the
On 12/05/2016 10:10 AM, Niklas Cassel wrote:
> From: Niklas Cassel
>
> commit 64c3b252e9fc ("net: stmmac: fixed the pbl setting with DT")
> changed the parsing of the DT binding.
>
> Before 64c3b252e9fc, snps,fixed-burst and snps,mixed-burst were parsed
> regardless if the property snps,pbl
Hi,
On 12/02/2016 02:22 PM, Lee Jones wrote:
On Fri, 02 Dec 2016, Benjamin Gaignard wrote:
Add general purpose timers and it sub-nodes into DT for stm32f4.
Define and enable pwm1 and pwm3 for stm32f469 discovery board
version 3:
- use "st,stm32-timer-trigger" in DT
version 2:
- use
Hi,
On 12/02/2016 02:22 PM, Lee Jones wrote:
On Fri, 02 Dec 2016, Benjamin Gaignard wrote:
Add general purpose timers and it sub-nodes into DT for stm32f4.
Define and enable pwm1 and pwm3 for stm32f469 discovery board
version 3:
- use "st,stm32-timer-trigger" in DT
version 2:
- use
On 12/05/2016 12:27 PM, Mika Westerberg wrote:
> On Mon, Nov 28, 2016 at 03:06:23PM +0300, Mika Westerberg wrote:
>> This is 6th iteration of the series. You can find the previous versions
>> archived on:
>>
>> v5: https://lwn.net/Articles/706363/
>> v4: https://lwn.net/Articles/703773/
>>
On 12/05/2016 12:27 PM, Mika Westerberg wrote:
> On Mon, Nov 28, 2016 at 03:06:23PM +0300, Mika Westerberg wrote:
>> This is 6th iteration of the series. You can find the previous versions
>> archived on:
>>
>> v5: https://lwn.net/Articles/706363/
>> v4: https://lwn.net/Articles/703773/
>>
> -Original Message-
> From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
> Sent: Monday, December 5, 2016 2:01 AM
> To: KY Srinivasan
> Cc: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; o...@aepfle.de;
> -Original Message-
> From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
> Sent: Monday, December 5, 2016 2:01 AM
> To: KY Srinivasan
> Cc: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
>
2016-12-05 15:41+0100, David Hildenbrand:
> Am 02.12.2016 um 20:43 schrieb Radim Krčmář:
>> Interrupt to self can sent without knowing the APIC ID.
>
> can _be_ sent?
Yes, thanks, I'll fix it in v2 or when applying your r-b.
2016-12-05 15:41+0100, David Hildenbrand:
> Am 02.12.2016 um 20:43 schrieb Radim Krčmář:
>> Interrupt to self can sent without knowing the APIC ID.
>
> can _be_ sent?
Yes, thanks, I'll fix it in v2 or when applying your r-b.
2016-12-05 15:37+0100, David Hildenbrand:
> Am 02.12.2016 um 20:44 schrieb Radim Krčmář:
>> LAPIC after reset is in xAPIC mode, which poses a problem for hotplug of
>> VCPUs with high APIC ID, because reset VCPU is waiting for INIT/SIPI,
>> but there is no way to uniquely address it using xAPIC.
2016-12-05 15:37+0100, David Hildenbrand:
> Am 02.12.2016 um 20:44 schrieb Radim Krčmář:
>> LAPIC after reset is in xAPIC mode, which poses a problem for hotplug of
>> VCPUs with high APIC ID, because reset VCPU is waiting for INIT/SIPI,
>> but there is no way to uniquely address it using xAPIC.
For jump instructions that does not include target address as direct
operand, show the original disassembled line for them. This is needed
for certain powerpc jump instructions that use target address in a
register (such as bctr, btar, ...).
Before:
ld r12,32088(r12)
mtctr r12
v
For jump instructions that does not include target address as direct
operand, show the original disassembled line for them. This is needed
for certain powerpc jump instructions that use target address in a
register (such as bctr, btar, ...).
Before:
ld r12,32088(r12)
mtctr r12
v
zram hot_add sysfs attribute is a very 'special' attribute - reading
from it creates a new uninitialized zram device. This file, by a mistake,
can be read by a 'normal' user at the moment, while only root must be
able to create a new zram device, therefore hot_add attribute must have
S_IRUSR mode,
zram hot_add sysfs attribute is a very 'special' attribute - reading
from it creates a new uninitialized zram device. This file, by a mistake,
can be read by a 'normal' user at the moment, while only root must be
able to create a new zram device, therefore hot_add attribute must have
S_IRUSR mode,
Arch like powerpc has jump instructions that includes target address
as second operand. For example, 'bne cr7,0xc00f6154'. Add
support for such instruction in perf annotate.
objdump o/p:
c00f6140: ld r9,1032(r31)
c00f6144: cmpdi cr7,r9,0
c00f6148:
If jump target is outside of function range, perf is not handling it
correctly. Especially when target address is lesser than function start
address, target offset will be negative. But, target address declared
to be unsigned, converts negative number into 2's complement. See below
example. Here
Arch like powerpc has jump instructions that includes target address
as second operand. For example, 'bne cr7,0xc00f6154'. Add
support for such instruction in perf annotate.
objdump o/p:
c00f6140: ld r9,1032(r31)
c00f6144: cmpdi cr7,r9,0
c00f6148:
If jump target is outside of function range, perf is not handling it
correctly. Especially when target address is lesser than function start
address, target offset will be negative. But, target address declared
to be unsigned, converts negative number into 2's complement. See below
example. Here
On (12/05/16 13:57), Greg KH wrote:
> > +/*
> > + * NOTE: hot_add attribute is not the usual read-only sysfs
> > + * attribute. In a sence that reading from this file does alter
> > + * the state of your system -- it creates a new un-initialized
> > + * zram device and returns back this device's
On (12/05/16 13:57), Greg KH wrote:
> > +/*
> > + * NOTE: hot_add attribute is not the usual read-only sysfs
> > + * attribute. In a sence that reading from this file does alter
> > + * the state of your system -- it creates a new un-initialized
> > + * zram device and returns back this device's
On Mon, 2016-12-05 at 23:47 +0800, Icenowy Zheng wrote:
> 2016年12月5日 19:49于 Lubomir Rintel 写道:
> >
> > On Sun, 2016-12-04 at 22:59 +0800, Icenowy Zheng wrote:
> > >
> > > 04.12.2016, 22:00, "Icenowy Zheng" :
> > > > A new usbid of UTV007 is found in a newly
On Mon, 2016-12-05 at 23:47 +0800, Icenowy Zheng wrote:
> 2016年12月5日 19:49于 Lubomir Rintel 写道:
> >
> > On Sun, 2016-12-04 at 22:59 +0800, Icenowy Zheng wrote:
> > >
> > > 04.12.2016, 22:00, "Icenowy Zheng" :
> > > > A new usbid of UTV007 is found in a newly bought device.
> > > >
> > > > The
Hello.
On 05/12/16 16:34, Ozgur Karatas wrote:
Hello all,
I will solve a checkpatch errors.
Signed-off-by: Ozgur Karatas
The patch itself looks good, but please have a read about having a good
commit message. I would suggest reading Documentation/SubmittingPatches
On Fri, Dec 02, 2016 at 02:59:22PM +, David Howells wrote:
> Greg KH wrote:
>
> > > If root is able to modify the behaviour of verified code after it was
> > > verified, then the value of that verification is reduced. Ensuring that
> > > the code remains
Hello.
On 05/12/16 16:34, Ozgur Karatas wrote:
Hello all,
I will solve a checkpatch errors.
Signed-off-by: Ozgur Karatas
The patch itself looks good, but please have a read about having a good
commit message. I would suggest reading Documentation/SubmittingPatches
section 14: The
On Fri, Dec 02, 2016 at 02:59:22PM +, David Howells wrote:
> Greg KH wrote:
>
> > > If root is able to modify the behaviour of verified code after it was
> > > verified, then the value of that verification is reduced. Ensuring that
> > > the code remains trustworthy is vital in a number of
In most cases, usleep_range is better than udelay, as the precise wakeup
from udelay is unnecessary.
usleep_range gives a much better chance of coalescing processor wakeups.
Signed-off-by: Shiva Kerdel
---
drivers/staging/dgnc/dgnc_neo.c | 10 +-
1 file changed, 5
In most cases, usleep_range is better than udelay, as the precise wakeup
from udelay is unnecessary.
usleep_range gives a much better chance of coalescing processor wakeups.
Signed-off-by: Shiva Kerdel
---
drivers/staging/dgnc/dgnc_neo.c | 10 +-
1 file changed, 5 insertions(+), 5
In most cases, usleep_range is better than udelay, as the precise wakeup
from udelay is unnecessary.
usleep_range gives a much better chance of coalescing processor wakeups.
Signed-off-by: Shiva Kerdel
---
drivers/staging/dgnc/dgnc_cls.c | 6 +++---
1 file changed, 3
In most cases, usleep_range is better than udelay, as the precise wakeup
from udelay is unnecessary.
usleep_range gives a much better chance of coalescing processor wakeups.
Signed-off-by: Shiva Kerdel
---
drivers/staging/dgnc/dgnc_cls.c | 6 +++---
1 file changed, 3 insertions(+), 3
On Sat, 3 Dec 2016, David Miller wrote:
> From: Arnd Bergmann
> Date: Sat, 3 Dec 2016 00:04:32 +0100
>
> > ptp now depends on the optional POSIX_TIMERS setting and fails to build
> > if we select it without that:
> >
> > warning: (LIQUIDIO_VF && TI_CPTS) selects PTP_1588_CLOCK
On Sat, 3 Dec 2016, David Miller wrote:
> From: Arnd Bergmann
> Date: Sat, 3 Dec 2016 00:04:32 +0100
>
> > ptp now depends on the optional POSIX_TIMERS setting and fails to build
> > if we select it without that:
> >
> > warning: (LIQUIDIO_VF && TI_CPTS) selects PTP_1588_CLOCK which has unmet
+ linux-btrfs
On Mon, Dec 05, 2016 at 09:30:52AM -0600, Gerard Saraber wrote:
> I have a NAS with a mix of 6, 4 and 3 TB drives:
>
> shrapnel zm # btrfs filesystem df /home/exports
> Data, RAID1: total=19.59TiB, used=19.51TiB
> System, RAID1: total=32.00MiB, used=2.75MiB
> Metadata, RAID1:
+ linux-btrfs
On Mon, Dec 05, 2016 at 09:30:52AM -0600, Gerard Saraber wrote:
> I have a NAS with a mix of 6, 4 and 3 TB drives:
>
> shrapnel zm # btrfs filesystem df /home/exports
> Data, RAID1: total=19.59TiB, used=19.51TiB
> System, RAID1: total=32.00MiB, used=2.75MiB
> Metadata, RAID1:
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Saturday, December 03, 2016 8:09 PM
> To: Salil Mehta
> Cc: Zhuangyuzeng (Yisen); mehta.salil@gmail.com;
> net...@vger.kernel.org; linux-kernel@vger.kernel.org; Linuxarm
> Subject: Re: [PATCH V2 net-next]
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Saturday, December 03, 2016 8:09 PM
> To: Salil Mehta
> Cc: Zhuangyuzeng (Yisen); mehta.salil@gmail.com;
> net...@vger.kernel.org; linux-kernel@vger.kernel.org; Linuxarm
> Subject: Re: [PATCH V2 net-next]
Remove 'fixed-link' nodes from DSA ports since they are not needed (they
are not limiting link's speed and the ports will be configured to their
maximux speed as a default)
Suggested-by: Andrew Lunn
Signed-off-by: Andrey Smirnov
---
Changes since v2:
Remove 'fixed-link' nodes from DSA ports since they are not needed (they
are not limiting link's speed and the ports will be configured to their
maximux speed as a default)
Suggested-by: Andrew Lunn
Signed-off-by: Andrey Smirnov
---
Changes since v2:
- None
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Saturday, December 03, 2016 8:25 PM
> To: Salil Mehta
> Cc: Zhuangyuzeng (Yisen); mehta.salil@gmail.com;
> net...@vger.kernel.org; linux-kernel@vger.kernel.org; Linuxarm
> Subject: Re: [PATCH V2 net-next]
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Saturday, December 03, 2016 8:25 PM
> To: Salil Mehta
> Cc: Zhuangyuzeng (Yisen); mehta.salil@gmail.com;
> net...@vger.kernel.org; linux-kernel@vger.kernel.org; Linuxarm
> Subject: Re: [PATCH V2 net-next]
On 05/12/16 16:32, Boris Ostrovsky wrote:
> On 12/02/2016 01:15 AM, Juergen Gross wrote:
>>
>> -static struct vscsiif_request *scsifront_pre_req(struct vscsifrnt_info
>> *info)
>> +static int scsifront_do_request(struct vscsifrnt_info *info,
>> +struct
On 05/12/16 16:32, Boris Ostrovsky wrote:
> On 12/02/2016 01:15 AM, Juergen Gross wrote:
>>
>> -static struct vscsiif_request *scsifront_pre_req(struct vscsifrnt_info
>> *info)
>> +static int scsifront_do_request(struct vscsifrnt_info *info,
>> +struct
Hello all,
I will solve a checkpatch errors.
Signed-off-by: Ozgur Karatas
---
net/8021q/vlan_dev.c | 2 +-
diff --git a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c
index fbfacd5..2edb495 100644
--- a/net/8021q/vlan_dev.c
+++
Hello all,
I will solve a checkpatch errors.
Signed-off-by: Ozgur Karatas
---
net/8021q/vlan_dev.c | 2 +-
diff --git a/net/8021q/vlan_dev.c b/net/8021q/vlan_dev.c
index fbfacd5..2edb495 100644
--- a/net/8021q/vlan_dev.c
+++ b/net/8021q/vlan_dev.c
@@ -738,7
On 2 December 2016 at 14:49, James Morse wrote:
> Patch "arm64: mm: Fix memmap to be initialized for the entire section"
> changes pfn_valid() in a way that breaks hibernate. These patches fix
> hibernate, and provided struct page's are allocated for nomap pages,
> can be
On 2 December 2016 at 14:49, James Morse wrote:
> Patch "arm64: mm: Fix memmap to be initialized for the entire section"
> changes pfn_valid() in a way that breaks hibernate. These patches fix
> hibernate, and provided struct page's are allocated for nomap pages,
> can be applied before [0].
>
>
This patch introduces the RX checksum function to check the
status of the hardware calculated checksum and its error and
appropriately convey status to the upper stack in skb->ip_summed
field.
In hardware, we only support checksum for the following
protocols:
1) IPv4,
2) TCP(over IPv4 or IPv6),
On Fri, Oct 21, 2016 at 11:33:09PM +0300, Yury Norov wrote:
> binfmt_ilp32.c is needed to handle ILP32 binaries
>
> Signed-off-by: Yury Norov
> Signed-off-by: Bamvor Zhang Jian
> ---
> arch/arm64/include/asm/elf.h | 6 +++
>
This patch introduces the RX checksum function to check the
status of the hardware calculated checksum and its error and
appropriately convey status to the upper stack in skb->ip_summed
field.
In hardware, we only support checksum for the following
protocols:
1) IPv4,
2) TCP(over IPv4 or IPv6),
On Fri, Oct 21, 2016 at 11:33:09PM +0300, Yury Norov wrote:
> binfmt_ilp32.c is needed to handle ILP32 binaries
>
> Signed-off-by: Yury Norov
> Signed-off-by: Bamvor Zhang Jian
> ---
> arch/arm64/include/asm/elf.h | 6 +++
> arch/arm64/kernel/Makefile | 1 +
>
> -Original Message-
> From: Ben Hutchings [mailto:b...@decadent.org.uk]
> Sent: Friday, December 02, 2016 9:26 PM
> To: linux-kernel@vger.kernel.org; linux-firmw...@kernel.org
> Cc: Deucher, Alexander
> Subject: [PATCH linux-firmware 1/2] WHENCE: Add new amdgpu firmware
>
> Missed in
> -Original Message-
> From: Ben Hutchings [mailto:b...@decadent.org.uk]
> Sent: Friday, December 02, 2016 9:26 PM
> To: linux-kernel@vger.kernel.org; linux-firmw...@kernel.org
> Cc: Deucher, Alexander
> Subject: [PATCH linux-firmware 1/2] WHENCE: Add new amdgpu firmware
>
> Missed in
On Mon, Nov 28, 2016 at 3:04 PM, David Graziano
wrote:
> On Wed, Nov 9, 2016 at 4:25 PM, Paul Moore wrote:
>> On Wed, Nov 9, 2016 at 11:25 AM, David Graziano
>> wrote:
>>> On Mon, Nov 7, 2016 at 4:23
On Mon, Nov 28, 2016 at 3:04 PM, David Graziano
wrote:
> On Wed, Nov 9, 2016 at 4:25 PM, Paul Moore wrote:
>> On Wed, Nov 9, 2016 at 11:25 AM, David Graziano
>> wrote:
>>> On Mon, Nov 7, 2016 at 4:23 PM, Paul Moore wrote:
On Mon, Nov 7, 2016 at 3:46 PM, David Graziano
wrote:
>
Al Viro wrote:
> > I understand wanting to avoid extra arguments, but you are asking for
> > trouble with that sort of calling conventions. Verifying that all call
> > chains have these fields initialized is bloody unpleasant and it *is*
> > going to break, especially
Al Viro wrote:
> > I understand wanting to avoid extra arguments, but you are asking for
> > trouble with that sort of calling conventions. Verifying that all call
> > chains have these fields initialized is bloody unpleasant and it *is*
> > going to break, especially since the rules are "you
On Mon, Dec 5, 2016 at 4:19 PM, J. Bruce Fields wrote:
>> Can NFS people comment on this? Where does the nfs4_acl come from?
>
> This is the interface the NFS client provides for applications to modify
> NFSv4 ACLs on servers that support them.
Fine, but why are we seeing
On Mon, Dec 5, 2016 at 4:19 PM, J. Bruce Fields wrote:
>> Can NFS people comment on this? Where does the nfs4_acl come from?
>
> This is the interface the NFS client provides for applications to modify
> NFSv4 ACLs on servers that support them.
Fine, but why are we seeing this xattr on exports
On Mon, Dec 05, 2016 at 02:36:07PM +0100, Sebastian Frias wrote:
> + * Equivalent of BIT(x) but for contiguous bitfields
> + * SETBITFIELD(1, 0,0xff) = 0x0003
> + * SETBITFIELD(3, 0,0xff) = 0x000f
> + * SETBITFIELD(15,8,0xff) = 0xff00
> + * SETBITFIELD(6, 6, 1) = 0x0040 == BIT(6)
On Mon, Dec 05, 2016 at 02:36:07PM +0100, Sebastian Frias wrote:
> + * Equivalent of BIT(x) but for contiguous bitfields
> + * SETBITFIELD(1, 0,0xff) = 0x0003
> + * SETBITFIELD(3, 0,0xff) = 0x000f
> + * SETBITFIELD(15,8,0xff) = 0xff00
> + * SETBITFIELD(6, 6, 1) = 0x0040 == BIT(6)
On 12/02/2016 01:15 AM, Juergen Gross wrote:
>
> -static struct vscsiif_request *scsifront_pre_req(struct vscsifrnt_info *info)
> +static int scsifront_do_request(struct vscsifrnt_info *info,
> + struct vscsifrnt_shadow *shadow)
> {
> struct vscsiif_front_ring
I have a NAS with a mix of 6, 4 and 3 TB drives:
shrapnel zm # btrfs filesystem df /home/exports
Data, RAID1: total=19.59TiB, used=19.51TiB
System, RAID1: total=32.00MiB, used=2.75MiB
Metadata, RAID1: total=76.00GiB, used=74.71GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
shrapnel zm #
On 12/02/2016 01:15 AM, Juergen Gross wrote:
>
> -static struct vscsiif_request *scsifront_pre_req(struct vscsifrnt_info *info)
> +static int scsifront_do_request(struct vscsifrnt_info *info,
> + struct vscsifrnt_shadow *shadow)
> {
> struct vscsiif_front_ring
I have a NAS with a mix of 6, 4 and 3 TB drives:
shrapnel zm # btrfs filesystem df /home/exports
Data, RAID1: total=19.59TiB, used=19.51TiB
System, RAID1: total=32.00MiB, used=2.75MiB
Metadata, RAID1: total=76.00GiB, used=74.71GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
shrapnel zm #
On 05/12/2016 at 14:11:53 +0100, Emil Bartczak wrote :
> Change rtc-mcp795.c to use the bcd2bin/bin2bcd functions.
> ---
> drivers/rtc/rtc-mcp795.c | 28 +---
> 1 file changed, 13 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/rtc/rtc-mcp795.c
On 05/12/2016 at 14:11:53 +0100, Emil Bartczak wrote :
> Change rtc-mcp795.c to use the bcd2bin/bin2bcd functions.
> ---
> drivers/rtc/rtc-mcp795.c | 28 +---
> 1 file changed, 13 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/rtc/rtc-mcp795.c
On Mon, Dec 05, 2016 at 08:46:21AM -0600, Rob Herring wrote:
> On Tue, Nov 29, 2016 at 01:38:21AM +0300, Serge Semin wrote:
> > See cover-letter for changelog
> >
> > Signed-off-by: Serge Semin
> >
> > ---
> >
On Mon, Dec 05, 2016 at 08:46:21AM -0600, Rob Herring wrote:
> On Tue, Nov 29, 2016 at 01:38:21AM +0300, Serge Semin wrote:
> > See cover-letter for changelog
> >
> > Signed-off-by: Serge Semin
> >
> > ---
> > .../devicetree/bindings/misc/idt_89hpesx.txt | 41
> > ++
Hi Hans,
On Monday 05 Dec 2016 16:02:55 Hans Verkuil wrote:
> On 12/05/2016 03:45 PM, Laurent Pinchart wrote:
> > On Monday 05 Dec 2016 14:44:55 Hans Verkuil wrote:
> >> On 11/25/2016 03:57 PM, Todor Tomov wrote:
> >>> These files handle the video device nodes of the camss driver.
> >>>
> >>>
Hi Hans,
On Monday 05 Dec 2016 16:02:55 Hans Verkuil wrote:
> On 12/05/2016 03:45 PM, Laurent Pinchart wrote:
> > On Monday 05 Dec 2016 14:44:55 Hans Verkuil wrote:
> >> On 11/25/2016 03:57 PM, Todor Tomov wrote:
> >>> These files handle the video device nodes of the camss driver.
> >>>
> >>>
On 05/12/2016 at 14:11:52 +0100, Emil Bartczak wrote :
> According to Microchip errata some combinations of date and month
> values may result in the date being reset to 1, even if the date
> is also written with the month (for example 31-07 or 31-08).
> As a workaround avoid writing date and
On 05/12/2016 at 14:11:52 +0100, Emil Bartczak wrote :
> According to Microchip errata some combinations of date and month
> values may result in the date being reset to 1, even if the date
> is also written with the month (for example 31-07 or 31-08).
> As a workaround avoid writing date and
On Mon, 2016-12-05 at 06:53 -0800, Nathaniel Quillin wrote:
> Add device-id entry for GW Instek AFG-125, which has a byte swapped
> bInterfaceSubClass (0x20).
>
> Signed-off-by: Nathaniel Quillin
Acked-by: Oliver Neukum
On Mon, 2016-12-05 at 06:53 -0800, Nathaniel Quillin wrote:
> Add device-id entry for GW Instek AFG-125, which has a byte swapped
> bInterfaceSubClass (0x20).
>
> Signed-off-by: Nathaniel Quillin
Acked-by: Oliver Neukum
Hi Todor,
Thank you for the patch.
On Friday 25 Nov 2016 16:57:20 Todor Tomov wrote:
> These files handle the video device nodes of the camss driver.
camss is a quite generic, I'm a bit concerned about claiming that acronym in
the global kernel namespace. Would it be too long if we prefixed
Hi Todor,
Thank you for the patch.
On Friday 25 Nov 2016 16:57:20 Todor Tomov wrote:
> These files handle the video device nodes of the camss driver.
camss is a quite generic, I'm a bit concerned about claiming that acronym in
the global kernel namespace. Would it be too long if we prefixed
On Mon, Dec 05, 2016 at 10:28:18AM +0100, Miklos Szeredi wrote:
> [Added a few more CCs]
>
> On Mon, Dec 5, 2016 at 1:51 AM, Patrick Plagwitz
> wrote:
> > Mounting an overlayfs with an NFSv4 lowerdir and an ext4 upperdir causes
> > copy_up operations, specifically the
On Mon, Dec 05, 2016 at 10:28:18AM +0100, Miklos Szeredi wrote:
> [Added a few more CCs]
>
> On Mon, Dec 5, 2016 at 1:51 AM, Patrick Plagwitz
> wrote:
> > Mounting an overlayfs with an NFSv4 lowerdir and an ext4 upperdir causes
> > copy_up operations, specifically the function
On Mon, Dec 05, 2016 at 03:31:43PM +0100, Dmitry Vyukov wrote:
> On Sat, Dec 3, 2016 at 7:19 PM, Johannes Thumshirn wrote:
> > On Sat, Dec 03, 2016 at 04:22:39PM +0100, Dmitry Vyukov wrote:
> >> On Sat, Dec 3, 2016 at 11:38 AM, Johannes Thumshirn
> >>
On Mon, Dec 05, 2016 at 03:31:43PM +0100, Dmitry Vyukov wrote:
> On Sat, Dec 3, 2016 at 7:19 PM, Johannes Thumshirn wrote:
> > On Sat, Dec 03, 2016 at 04:22:39PM +0100, Dmitry Vyukov wrote:
> >> On Sat, Dec 3, 2016 at 11:38 AM, Johannes Thumshirn
> >> wrote:
> >> > On Fri, Dec 02, 2016 at
The Surface 3 is not following the ACPI spec for PNP0C40, but nearly.
The device is connected to a I2C device that might have some magic
but we don't know about.
Just create the device after the enumeration and use the declared GPIOs
to provide button support.
This driver is just an adaptation of
The Surface 3 is not following the ACPI spec for PNP0C40, but nearly.
The device is connected to a I2C device that might have some magic
but we don't know about.
Just create the device after the enumeration and use the declared GPIOs
to provide button support.
This driver is just an adaptation of
On Fri, Oct 21, 2016 at 11:33:08PM +0300, Yury Norov wrote:
> As we support more than one compat formats, it looks more reasonable
> to not use fs/compat_binfmt.c. Custom binfmt_elf32.c allows to move aarch32
> specific definitions there and make code more maintainable and readable.
Can you
On Fri, Oct 21, 2016 at 11:33:08PM +0300, Yury Norov wrote:
> As we support more than one compat formats, it looks more reasonable
> to not use fs/compat_binfmt.c. Custom binfmt_elf32.c allows to move aarch32
> specific definitions there and make code more maintainable and readable.
Can you
Hi,
On 05/12/2016 at 14:11:50 +0100, Emil Bartczak wrote :
> The 10 month register was always set to value 0 in the RTC hardware.
> Due to the bug month November or December became February.
All your patches are missing your SoB, see Developer's Certificate of
Origin 1.1 in
Hi,
On 05/12/2016 at 14:11:50 +0100, Emil Bartczak wrote :
> The 10 month register was always set to value 0 in the RTC hardware.
> Due to the bug month November or December became February.
All your patches are missing your SoB, see Developer's Certificate of
Origin 1.1 in
On 12/05/2016 03:45 PM, Laurent Pinchart wrote:
> Hello,
>
> On Monday 05 Dec 2016 14:44:55 Hans Verkuil wrote:
>> On 11/25/2016 03:57 PM, Todor Tomov wrote:
>>> These files handle the video device nodes of the camss driver.
>>>
>>> Signed-off-by: Todor Tomov
>>> ---
>>>
On 12/05/2016 03:45 PM, Laurent Pinchart wrote:
> Hello,
>
> On Monday 05 Dec 2016 14:44:55 Hans Verkuil wrote:
>> On 11/25/2016 03:57 PM, Todor Tomov wrote:
>>> These files handle the video device nodes of the camss driver.
>>>
>>> Signed-off-by: Todor Tomov
>>> ---
>>>
>>>
Add watchdog timer specific driver for Loongson1 SoC.
Signed-off-by: Yang Ling
---
V2.4:
Set DEFAULT_HEARTBEAT to 0.
V2.3:
Set DEFAULT_HEARTBEAT value to ls1x_wdt->timeout.
V2.2:
Remove the wide character.
Check the return value for clk_get_rate().
V2.1 from Kelvin
Add watchdog timer specific driver for Loongson1 SoC.
Signed-off-by: Yang Ling
---
V2.4:
Set DEFAULT_HEARTBEAT to 0.
V2.3:
Set DEFAULT_HEARTBEAT value to ls1x_wdt->timeout.
V2.2:
Remove the wide character.
Check the return value for clk_get_rate().
V2.1 from Kelvin Cheung:
Use
Hi!
I've got the following error report while running the syzkaller fuzzer.
On commit 3c49de52d5647cda8b42c4255cf8a29d1e22eff5 (Dec 2).
WARNING: CPU: 0 PID: 5257 at drivers/usb/gadget/udc/dummy_hcd.c:672
dummy_free_request+0x153/0x170
Kernel panic - not syncing: panic_on_warn set ...
usb 2-1:
Hi!
I've got the following error report while running the syzkaller fuzzer.
On commit 3c49de52d5647cda8b42c4255cf8a29d1e22eff5 (Dec 2).
WARNING: CPU: 0 PID: 5257 at drivers/usb/gadget/udc/dummy_hcd.c:672
dummy_free_request+0x153/0x170
Kernel panic - not syncing: panic_on_warn set ...
usb 2-1:
On 12/04/2016 06:56 AM, Nicolai Stange wrote:
> Since commit e73c23ff736e ("block: add async variant of
> blkdev_issue_zeroout") messages like the following show up:
>
> EXT4-fs (dm-1): Delayed block allocation failed for inode 2368848 at
> logical offset 0 with max blocks 1
On 12/04/2016 06:56 AM, Nicolai Stange wrote:
> Since commit e73c23ff736e ("block: add async variant of
> blkdev_issue_zeroout") messages like the following show up:
>
> EXT4-fs (dm-1): Delayed block allocation failed for inode 2368848 at
> logical offset 0 with max blocks 1
On Mon, Dec 05, 2016 at 06:08:16AM -0800, Christoph Hellwig wrote:
> [crazy CC list dropped]
>
> Can someone explain who the hell I ended up the on this stupid
> Cc long list for a reply to a mail I can't see either in my
> inbox or lkml folder?
You were cc'ed on this series but the messages
On Mon, Dec 05, 2016 at 06:08:16AM -0800, Christoph Hellwig wrote:
> [crazy CC list dropped]
>
> Can someone explain who the hell I ended up the on this stupid
> Cc long list for a reply to a mail I can't see either in my
> inbox or lkml folder?
You were cc'ed on this series but the messages
Add device-id entry for GW Instek AFG-125, which has a byte swapped
bInterfaceSubClass (0x20).
Signed-off-by: Nathaniel Quillin
---
drivers/usb/class/cdc-acm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
index
Add device-id entry for GW Instek AFG-125, which has a byte swapped
bInterfaceSubClass (0x20).
Signed-off-by: Nathaniel Quillin
---
drivers/usb/class/cdc-acm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
index fada988..c5ff13f
1101 - 1200 of 1768 matches
Mail list logo