Hello, Linus.
cgroup changes for v4.11. Several noteworthy changes.
* Parav's rdma controller is finally merged. It is very straight
forward and can limit the abosolute numbers of common rdma
constructs used by different cgroups.
* kernel/cgroup.c got too chubby and disorganized. Created
On Tue, Feb 28, 2017 at 1:01 AM, Joe Perches wrote:
> On Mon, 2017-02-27 at 23:44 +0530, simran singhal wrote:
>> This patch fixes the checkpatch warning that else is not generally
>> useful after a break or return.
> []
>> diff --git a/drivers/staging/sm750fb/ddk750_swi2c.c
>>
On Tue, Feb 28, 2017 at 1:01 AM, Joe Perches wrote:
> On Mon, 2017-02-27 at 23:44 +0530, simran singhal wrote:
>> This patch fixes the checkpatch warning that else is not generally
>> useful after a break or return.
> []
>> diff --git a/drivers/staging/sm750fb/ddk750_swi2c.c
>>
Hello, Linus.
cgroup changes for v4.11. Several noteworthy changes.
* Parav's rdma controller is finally merged. It is very straight
forward and can limit the abosolute numbers of common rdma
constructs used by different cgroups.
* kernel/cgroup.c got too chubby and disorganized. Created
From: Alban Bedel
Signed-off-by: Alban Bedel
---
drivers/mtd/Kconfig | 9 +++
drivers/mtd/Makefile | 1 +
drivers/mtd/devdata.c | 70 +++
3 files changed, 80 insertions(+)
create mode 100644
From: Alban Bedel
Signed-off-by: Alban Bedel
---
drivers/mtd/Kconfig | 9 +++
drivers/mtd/Makefile | 1 +
drivers/mtd/devdata.c | 70 +++
3 files changed, 80 insertions(+)
create mode 100644 drivers/mtd/devdata.c
diff --git
From: Alban Bedel
Some device need configuration data that is specific to this
particular device instance, for example some calibration results,
or a MAC address. Most often this data is stored in some EEPROM
or MTD device.
This API follow the usual provider/consumer pattern to
From: Alban Bedel
Some device need configuration data that is specific to this
particular device instance, for example some calibration results,
or a MAC address. Most often this data is stored in some EEPROM
or MTD device.
This API follow the usual provider/consumer pattern to give device
This makes for more sensible documentation of the whole module than
jumping straight into the details of display.
Signed-off-by: Eric Anholt
---
Documentation/gpu/vc4.rst | 3 +++
drivers/gpu/drm/vc4/vc4_drv.c | 16
2 files changed, 19 insertions(+)
diff
On Mon, Feb 27, 2017 at 04:07:27PM +0100, Julia Lawall wrote:
>
>
> On Mon, 27 Feb 2017, Arushi Singhal wrote:
>
> >
> >
> > On Mon, Feb 27, 2017 at 8:18 PM, Greg KH wrote:
> > On Sun, Feb 26, 2017 at 09:38:20PM +0530, Arushi Singhal wrote:
> > >
On Mon, Feb 27, 2017 at 04:07:27PM +0100, Julia Lawall wrote:
>
>
> On Mon, 27 Feb 2017, Arushi Singhal wrote:
>
> >
> >
> > On Mon, Feb 27, 2017 at 8:18 PM, Greg KH wrote:
> > On Sun, Feb 26, 2017 at 09:38:20PM +0530, Arushi Singhal wrote:
> > > Commenting Code Is a Bad Idea.
> >
This makes for more sensible documentation of the whole module than
jumping straight into the details of display.
Signed-off-by: Eric Anholt
---
Documentation/gpu/vc4.rst | 3 +++
drivers/gpu/drm/vc4/vc4_drv.c | 16
2 files changed, 19 insertions(+)
diff --git
Hi all,
while looking at adding OF support for the ath9k driver I had the problem of
reading the EEPROM data. On the SoC platforms this data is stored in an SPI
flash along with a few other things. In OpenWRT/LEDE this data is read from
the board init code using the fact that the flash is
Hi all,
while looking at adding OF support for the ath9k driver I had the problem of
reading the EEPROM data. On the SoC platforms this data is stored in an SPI
flash along with a few other things. In OpenWRT/LEDE this data is read from
the board init code using the fact that the flash is
The HDMI encoder IP embeds all needed blocks to output audio, with a
custom DAI called MAI moving audio between the two parts of the HDMI
core. This driver now exposes a sound card to let users stream audio
to their display.
Using the hdmi-codec driver has been considered here, but MAI meant
From: Boris Brezillon
Add the dmas and dma-names properties to support HDMI audio.
Signed-off-by: Boris Brezillon
Signed-off-by: Eric Anholt
---
v2: no changes
arch/arm/boot/dts/bcm283x.dtsi | 2 ++
1
The HDMI encoder IP embeds all needed blocks to output audio, with a
custom DAI called MAI moving audio between the two parts of the HDMI
core. This driver now exposes a sound card to let users stream audio
to their display.
Using the hdmi-codec driver has been considered here, but MAI meant
From: Boris Brezillon
Add the dmas and dma-names properties to support HDMI audio.
Signed-off-by: Boris Brezillon
Signed-off-by: Eric Anholt
---
v2: no changes
arch/arm/boot/dts/bcm283x.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/bcm283x.dtsi
From: Boris Brezillon
These are optional, but necessary for HDMI audio support.
Signed-off-by: Boris Brezillon
Signed-off-by: Eric Anholt
Acked-by: Rob Herring
---
v2: no changes
From: Boris Brezillon
These are optional, but necessary for HDMI audio support.
Signed-off-by: Boris Brezillon
Signed-off-by: Eric Anholt
Acked-by: Rob Herring
---
v2: no changes
Documentation/devicetree/bindings/display/brcm,bcm-vc4.txt | 3 +++
1 file changed, 3 insertions(+)
diff
On Tue, Feb 28, 2017 at 12:55 AM, Joe Perches wrote:
> On Mon, 2017-02-27 at 23:44 +0530, simran singhal wrote:
>> This patch fixes the checkpatch warning that else is not generally
>> useful after a break or return.
>
> checkpatch doesn't actually warn for this style
>
>
On Tue, Feb 28, 2017 at 12:55 AM, Joe Perches wrote:
> On Mon, 2017-02-27 at 23:44 +0530, simran singhal wrote:
>> This patch fixes the checkpatch warning that else is not generally
>> useful after a break or return.
>
> checkpatch doesn't actually warn for this style
>
> if (foo)
>
Hi Tejun,
On Mon, Feb 27, 2017 at 11:51 AM, Tejun Heo wrote:
>> __vmalloc+0x45/0x50
>> pcpu_mem_zalloc+0x50/0x80
>> pcpu_populate_chunk+0x3b/0x380
>> pcpu_alloc+0x588/0x6e0
>> __alloc_percpu_gfp+0xd/0x10
>> __percpu_counter_init+0x55/0xc0
>> blkg_alloc+0x76/0x230
>>
Hi Tejun,
On Mon, Feb 27, 2017 at 11:51 AM, Tejun Heo wrote:
>> __vmalloc+0x45/0x50
>> pcpu_mem_zalloc+0x50/0x80
>> pcpu_populate_chunk+0x3b/0x380
>> pcpu_alloc+0x588/0x6e0
>> __alloc_percpu_gfp+0xd/0x10
>> __percpu_counter_init+0x55/0xc0
>> blkg_alloc+0x76/0x230
>> blkg_create+0x489/0x670
>>
Greg Kroah-Hartman writes:
> On Fri, Feb 24, 2017 at 10:09:22AM -0800, kernelci.org bot wrote:
>> stable-rc boot: 191 boots: 2 failed, 181 passed with 8 offline
>> (v4.10-22-g0b3f6c4ba776)
>>
>> Full Boot Summary:
>>
On Mon, Feb 20, 2017 at 04:18:54PM +0100, Enric Balletbo i Serra wrote:
> From: Benson Leung
>
> This patch add documentation for binding of USB Type C cable detection
> mechanism is using EXTCON subsystem. The device can detect the presence
> of display out but it may also
Greg Kroah-Hartman writes:
> On Fri, Feb 24, 2017 at 10:09:22AM -0800, kernelci.org bot wrote:
>> stable-rc boot: 191 boots: 2 failed, 181 passed with 8 offline
>> (v4.10-22-g0b3f6c4ba776)
>>
>> Full Boot Summary:
>> https://kernelci.org/boot/all/job/stable-rc/kernel/v4.10-22-g0b3f6c4ba776/
On Mon, Feb 20, 2017 at 04:18:54PM +0100, Enric Balletbo i Serra wrote:
> From: Benson Leung
>
> This patch add documentation for binding of USB Type C cable detection
> mechanism is using EXTCON subsystem. The device can detect the presence
> of display out but it may also detect other external
From: Matthew Gerlach
This patch separates the core Freeze Bridge
driver code from the platform driver code.
The intent is to allow the core driver code
to be used without requiring platform driver support.
Signed-off-by: Matthew Gerlach
From: Matthew Gerlach
This patch separates the core Freeze Bridge
driver code from the platform driver code.
The intent is to allow the core driver code
to be used without requiring platform driver support.
Signed-off-by: Matthew Gerlach
---
drivers/fpga/Kconfig | 7
On Mon, Feb 20, 2017 at 08:08:57AM -0800, Andrey Smirnov wrote:
> Add various bits of code needed to support i.MX7D variant of the IP.
>
> Cc: yurov...@gmail.com
> Cc: Lucas Stach
> Cc: Bjorn Helgaas
> Cc: Rob Herring
> Cc: Mark
On Mon, Feb 20, 2017 at 08:08:57AM -0800, Andrey Smirnov wrote:
> Add various bits of code needed to support i.MX7D variant of the IP.
>
> Cc: yurov...@gmail.com
> Cc: Lucas Stach
> Cc: Bjorn Helgaas
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: Lee Jones
> Cc: Fabio Estevam
> Cc:
The contents of the header file are used only by this single
source file. Move content into .c and remove .h.
Signed-off-by: simran singhal
---
drivers/staging/iio/accel/adis16201.h | 144
drivers/staging/iio/accel/adis16201_core.c |
Hi!
> > > On Mon 2017-02-20 15:56:36, Sakari Ailus wrote:
> > > > On Mon, Feb 20, 2017 at 03:09:13PM +0200, Sakari Ailus wrote:
> > > > > I've tested ACPI, will test DT soon...
> > > >
> > > > DT case works, too (Nokia N9).
> > >
> > > Hmm. Good to know. Now to figure out how to get N900 case
The contents of the header file are used only by this single
source file. Move content into .c and remove .h.
Signed-off-by: simran singhal
---
drivers/staging/iio/accel/adis16201.h | 144
drivers/staging/iio/accel/adis16201_core.c | 145
Hi!
> > > On Mon 2017-02-20 15:56:36, Sakari Ailus wrote:
> > > > On Mon, Feb 20, 2017 at 03:09:13PM +0200, Sakari Ailus wrote:
> > > > > I've tested ACPI, will test DT soon...
> > > >
> > > > DT case works, too (Nokia N9).
> > >
> > > Hmm. Good to know. Now to figure out how to get N900 case
On Mon, 2017-02-27 at 23:44 +0530, simran singhal wrote:
> This patch fixes the checkpatch warning that else is not generally
> useful after a break or return.
> This was done using Coccinelle:
> @@
> expression e2;
> statement s1;
> @@
> if(e2) { ... return ...; }
> -else
> s1
[]
> diff
On Mon, 2017-02-27 at 23:44 +0530, simran singhal wrote:
> This patch fixes the checkpatch warning that else is not generally
> useful after a break or return.
> This was done using Coccinelle:
> @@
> expression e2;
> statement s1;
> @@
> if(e2) { ... return ...; }
> -else
> s1
[]
> diff
On Mon, Feb 27, 2017 at 8:59 PM, David Ahern wrote:
> On 2/27/17 10:11 AM, Cong Wang wrote:
>> The attached patch fixes this crash, but I am not sure if it is the
>> best way to fix this bug yet...
>
> I'll take a look. I can not reproduce this using route or ip, so the
On Mon, Feb 27, 2017 at 8:59 PM, David Ahern wrote:
> On 2/27/17 10:11 AM, Cong Wang wrote:
>> The attached patch fixes this crash, but I am not sure if it is the
>> best way to fix this bug yet...
>
> I'll take a look. I can not reproduce this using route or ip, so the
> fuzzer is doing
On Tue, Feb 21, 2017 at 09:56:17AM +0100, Richard Leitner wrote:
> Remove the max_{power,current}_{sp,bp} properties of the usb251xb driver
> from devicetree. This is done to simplify the dt bindings as requested
> by Rob Herring in https://lkml.org/lkml/2017/2/15/1283. If those
> properties are
On Tue, Feb 21, 2017 at 09:56:17AM +0100, Richard Leitner wrote:
> Remove the max_{power,current}_{sp,bp} properties of the usb251xb driver
> from devicetree. This is done to simplify the dt bindings as requested
> by Rob Herring in https://lkml.org/lkml/2017/2/15/1283. If those
> properties are
On Sun, Feb 19, 2017 at 10:27:59PM +0200, Priit Laes wrote:
> Kontron AG is a German-based company designing and manufacturing
> embedded modules, computers and systems.
>
> Signed-off-by: Priit Laes
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 3 ++-
> 1
On Sun, Feb 19, 2017 at 10:27:59PM +0200, Priit Laes wrote:
> Kontron AG is a German-based company designing and manufacturing
> embedded modules, computers and systems.
>
> Signed-off-by: Priit Laes
> ---
> Documentation/devicetree/bindings/vendor-prefixes.txt | 3 ++-
> 1 file changed, 2
On Mon 27-02-17 12:06:34, Johannes Weiner wrote:
> On Mon, Feb 27, 2017 at 09:50:24AM +0100, Michal Hocko wrote:
> > On Fri 24-02-17 11:51:05, Johannes Weiner wrote:
> > [...]
> > > >From 29fefdca148e28830e0934d4e6cceb95ed2ee36e Mon Sep 17 00:00:00 2001
> > > From: Johannes Weiner
On Sunday 26 February 2017 21:28:32 Pavel Machek wrote:
> Hi!
>
> v4.10 works quite nicely on N900, but I still have problems with
> audio. Even GSM calls would be usable, if I had reasonable volume on
> microphone and speaker... but I don't.
>
> Both speaker and microphone are too quiet. I can
On Mon 27-02-17 12:06:34, Johannes Weiner wrote:
> On Mon, Feb 27, 2017 at 09:50:24AM +0100, Michal Hocko wrote:
> > On Fri 24-02-17 11:51:05, Johannes Weiner wrote:
> > [...]
> > > >From 29fefdca148e28830e0934d4e6cceb95ed2ee36e Mon Sep 17 00:00:00 2001
> > > From: Johannes Weiner
> > > Date:
On Sunday 26 February 2017 21:28:32 Pavel Machek wrote:
> Hi!
>
> v4.10 works quite nicely on N900, but I still have problems with
> audio. Even GSM calls would be usable, if I had reasonable volume on
> microphone and speaker... but I don't.
>
> Both speaker and microphone are too quiet. I can
On Mon, 2017-02-27 at 23:44 +0530, simran singhal wrote:
> This patch fixes the checkpatch warning that else is not generally
> useful after a break or return.
checkpatch doesn't actually warn for this style
if (foo)
return bar;
else
return baz;
>
On Mon, 2017-02-27 at 23:44 +0530, simran singhal wrote:
> This patch fixes the checkpatch warning that else is not generally
> useful after a break or return.
checkpatch doesn't actually warn for this style
if (foo)
return bar;
else
return baz;
>
On Sat, Feb 25, 2017 at 01:35:51AM +0300, Dmitry V. Levin wrote:
> On Fri, Feb 24, 2017 at 05:35:33PM +0300, Alexey Dobriyan wrote:
> > On Thu, Feb 23, 2017 at 02:44:31PM -0800, a...@linux-foundation.org wrote:
> > > /usr/include/linux/sysctl.h:38:2: error: unknown type name 'size_t'
> > >
On Sat, Feb 25, 2017 at 01:35:51AM +0300, Dmitry V. Levin wrote:
> On Fri, Feb 24, 2017 at 05:35:33PM +0300, Alexey Dobriyan wrote:
> > On Thu, Feb 23, 2017 at 02:44:31PM -0800, a...@linux-foundation.org wrote:
> > > /usr/include/linux/sysctl.h:38:2: error: unknown type name 'size_t'
> > >
On 02/27/2017 12:29 PM, Boris Ostrovsky wrote:
>> On 02/15/2017 12:31 PM, Dave Jiang wrote:
>>> The fix introduced by e4decc90 to fix the UP case for 32bit x86, however
>>> that broke the SMP case that was working previously. Add ifdef so the dummy
>>> function only show up for 32bit UP case
On 02/20/2017 02:37 AM, Heiko Schocher wrote:
From: Guan Ben
extend the pwm-beeper driver to support customized frequency
for SND_BELL from device tree.
Signed-off-by: Guan Ben
Signed-off-by: Mark Jonas
[h...@denx.de:
On 02/27/2017 12:29 PM, Boris Ostrovsky wrote:
>> On 02/15/2017 12:31 PM, Dave Jiang wrote:
>>> The fix introduced by e4decc90 to fix the UP case for 32bit x86, however
>>> that broke the SMP case that was working previously. Add ifdef so the dummy
>>> function only show up for 32bit UP case
On 02/20/2017 02:37 AM, Heiko Schocher wrote:
From: Guan Ben
extend the pwm-beeper driver to support customized frequency
for SND_BELL from device tree.
Signed-off-by: Guan Ben
Signed-off-by: Mark Jonas
[h...@denx.de: adapted to 4.10-rc7]
Signed-off-by: Heiko Schocher
---
Changes in v2:
-
On Mon 27-02-17 11:32:50, Tahsin Erdogan wrote:
> >> >
> >> > Yes, this prevents adding more pcpu chunks and so cause "atomic"
> >> > allocations
> >> > to fail more easily.
> >>
> >> Then I fail to see what is the problem you are trying to fix.
> >
> > To be more specific. Could you describe
On Mon 27-02-17 11:32:50, Tahsin Erdogan wrote:
> >> >
> >> > Yes, this prevents adding more pcpu chunks and so cause "atomic"
> >> > allocations
> >> > to fail more easily.
> >>
> >> Then I fail to see what is the problem you are trying to fix.
> >
> > To be more specific. Could you describe
[adding linux-nvme to Cc as the patch changes the nvme driver, despite
the subject line]
On Sat, Feb 25, 2017 at 08:16:04PM +0100, Matias Bjørling wrote:
On 02/25/2017 07:21 PM, Christoph Hellwig wrote:
On Fri, Feb 24, 2017 at 06:16:48PM +0100, Matias Bjørling wrote:
More implementations of
[adding linux-nvme to Cc as the patch changes the nvme driver, despite
the subject line]
On Sat, Feb 25, 2017 at 08:16:04PM +0100, Matias Bjørling wrote:
On 02/25/2017 07:21 PM, Christoph Hellwig wrote:
On Fri, Feb 24, 2017 at 06:16:48PM +0100, Matias Bjørling wrote:
More implementations of
Mark Brown writes:
> On Fri, Feb 24, 2017 at 12:22:37AM +0100, Harald Geyer wrote:
> > Mark Brown writes:
>
> > > detail. I'd expect to see some words describing the situations where it
> > > can be used or something, both the name and the lack of any information
> > > about issues suggest it's
Mark Brown writes:
> On Fri, Feb 24, 2017 at 12:22:37AM +0100, Harald Geyer wrote:
> > Mark Brown writes:
>
> > > detail. I'd expect to see some words describing the situations where it
> > > can be used or something, both the name and the lack of any information
> > > about issues suggest it's
On Thu, 2017-02-23 at 19:01 -0500, Paul Moore wrote:
> On Thu, Feb 23, 2017 at 1:43 PM, John Stultz
> wrote:
> >
> > Hey folks,
> > I've not been able to figure out why yet, but I wanted to raise
> > the
> > issue that last night I found I couldn't boot Android on my
On Thu, 2017-02-23 at 19:01 -0500, Paul Moore wrote:
> On Thu, Feb 23, 2017 at 1:43 PM, John Stultz
> wrote:
> >
> > Hey folks,
> > I've not been able to figure out why yet, but I wanted to raise
> > the
> > issue that last night I found I couldn't boot Android on my Hikey
> > board with
On Mon, Feb 20, 2017 at 07:27:27AM -0800, Andrey Smirnov wrote:
> Add code allowing for control of various power domains managed by GPCv2
> IP block found in i.MX7 series of SoCs. Power domains covered by this
> patch are:
>
> - PCIE PHY
> - MIPI PHY
> - USB HSIC PHY
> - USB
On Mon, Feb 20, 2017 at 07:27:27AM -0800, Andrey Smirnov wrote:
> Add code allowing for control of various power domains managed by GPCv2
> IP block found in i.MX7 series of SoCs. Power domains covered by this
> patch are:
>
> - PCIE PHY
> - MIPI PHY
> - USB HSIC PHY
> - USB
>> >
>> > Yes, this prevents adding more pcpu chunks and so cause "atomic"
>> > allocations
>> > to fail more easily.
>>
>> Then I fail to see what is the problem you are trying to fix.
>
> To be more specific. Could you describe what more can we do in the
> vmalloc layer for GFP_NOWAIT
On Mon, Feb 27, 2017 at 08:01:51PM +0530, Ganesh Goudar wrote:
> Hi,
>
> Kindly ignore my previous firmware pull-request for revision 1.16.26.0,
> As we have some critical issues fixed in revision 1.16.33.0, please pull
> from the following URL
> git://git.chelsio.net/pub/git/linux-firmware.git
On Mon, Feb 27, 2017 at 08:01:51PM +0530, Ganesh Goudar wrote:
> Hi,
>
> Kindly ignore my previous firmware pull-request for revision 1.16.26.0,
> As we have some critical issues fixed in revision 1.16.33.0, please pull
> from the following URL
> git://git.chelsio.net/pub/git/linux-firmware.git
>> >
>> > Yes, this prevents adding more pcpu chunks and so cause "atomic"
>> > allocations
>> > to fail more easily.
>>
>> Then I fail to see what is the problem you are trying to fix.
>
> To be more specific. Could you describe what more can we do in the
> vmalloc layer for GFP_NOWAIT
On 02/26/2017 09:59 PM, Xiubo Li wrote:
>> But, We likely don't want to release memory from the data area anyways
>> while active, in any case. How about if we set a timer when active
>> commands go to zero, and then reduce data area to some minimum if no new
>> cmds come in before timer expires?
On 02/26/2017 09:59 PM, Xiubo Li wrote:
>> But, We likely don't want to release memory from the data area anyways
>> while active, in any case. How about if we set a timer when active
>> commands go to zero, and then reduce data area to some minimum if no new
>> cmds come in before timer expires?
On Mon, 2017-02-27 at 23:44 +0530, simran singhal wrote:
> This patch fixes the checkpatch warning that else is not generally
> useful after a break or return.
[]
> diff --git a/drivers/staging/sm750fb/ddk750_swi2c.c
> b/drivers/staging/sm750fb/ddk750_swi2c.c
[]
> @@ -295,8 +294,7 @@ static long
On Mon, 2017-02-27 at 23:44 +0530, simran singhal wrote:
> This patch fixes the checkpatch warning that else is not generally
> useful after a break or return.
[]
> diff --git a/drivers/staging/sm750fb/ddk750_swi2c.c
> b/drivers/staging/sm750fb/ddk750_swi2c.c
[]
> @@ -295,8 +294,7 @@ static long
On 02/23/2017 02:23 AM, Linus Walleij wrote:
> Hi Florian, a big sorry for not looking into this earlier, I've been
> having a mess in my inbox... and too much fun with the Gemini
> hehe :)
>
> On Wed, Feb 8, 2017 at 2:17 AM, Florian Fainelli wrote:
>
>> In case a platform
On 02/23/2017 02:23 AM, Linus Walleij wrote:
> Hi Florian, a big sorry for not looking into this earlier, I've been
> having a mess in my inbox... and too much fun with the Gemini
> hehe :)
>
> On Wed, Feb 8, 2017 at 2:17 AM, Florian Fainelli wrote:
>
>> In case a platform only defaults a
On Mon, Feb 20, 2017 at 01:28:37PM +0100, Boris Brezillon wrote:
> The old NAND bindings were not exactly describing the hardware topology
> and were preventing definitions of several NAND chips under the same
> NAND controller.
>
> New bindings address these limitations and should be preferred
On Mon, Feb 20, 2017 at 01:28:37PM +0100, Boris Brezillon wrote:
> The old NAND bindings were not exactly describing the hardware topology
> and were preventing definitions of several NAND chips under the same
> NAND controller.
>
> New bindings address these limitations and should be preferred
On 02/27/2017 01:57 PM, David Daney wrote:
On 02/27/2017 10:49 AM, Jason Baron wrote:
The core jump_label code makes use of the 2 lower bits of the
static_key::[type|entries|next] field. Thus, ensure that the jump_entry
table is at least 4-byte aligned.
[...]
diff --git
On 02/27/2017 01:57 PM, David Daney wrote:
On 02/27/2017 10:49 AM, Jason Baron wrote:
The core jump_label code makes use of the 2 lower bits of the
static_key::[type|entries|next] field. Thus, ensure that the jump_entry
table is at least 4-byte aligned.
[...]
diff --git
On Mon, 2017-02-27 at 11:13 -0600, Steve Magnani wrote:
> On 02/27/2017 10:13 AM, Bart Van Assche wrote:
> > Why are the two checks slightly different? Could the same code be used for
> > both checks?
>
> The checks are different because with READ CAPACITY(16) a _really_ huge
> device could
On Mon, 2017-02-27 at 11:13 -0600, Steve Magnani wrote:
> On 02/27/2017 10:13 AM, Bart Van Assche wrote:
> > Why are the two checks slightly different? Could the same code be used for
> > both checks?
>
> The checks are different because with READ CAPACITY(16) a _really_ huge
> device could
The location of the ERROR and BUSY status bits depends on the descriptor
index, i.e. the CPU, of the message. Since this index does not change,
there is no need to calculate the mmr and index location during message
processing. The less work we do in the hot path the better.
Add stats_mmr and
sparse is unhappy about this code in hlist_add_tail_rcu:
struct hlist_node *i, *last = NULL;
for (i = hlist_first_rcu(h); i; i = hlist_next_rcu(i))
last = i;
This is because hlist_next_rcu and hlist_next_rcu return
__rcu pointers.
It's a false positive - it's a
The location of the ERROR and BUSY status bits depends on the descriptor
index, i.e. the CPU, of the message. Since this index does not change,
there is no need to calculate the mmr and index location during message
processing. The less work we do in the hot path the better.
Add stats_mmr and
sparse is unhappy about this code in hlist_add_tail_rcu:
struct hlist_node *i, *last = NULL;
for (i = hlist_first_rcu(h); i; i = hlist_next_rcu(i))
last = i;
This is because hlist_next_rcu and hlist_next_rcu return
__rcu pointers.
It's a false positive - it's a
The above patch has a conflict in wait_completion with the enumerated UV_BAU
symbol because I let an old version of the patch creep into the set. Following
is the correct version.
Sorry about that!
Andrew
The above patch has a conflict in wait_completion with the enumerated UV_BAU
symbol because I let an old version of the patch creep into the set. Following
is the correct version.
Sorry about that!
Andrew
Hi,
> >> > Rather than trying small and smaller transfers, would it not be better
> >> > to get the i2c core to expose the quirk info about transfer limits?
> >> >
> >>
> >> Sounds a good idea to me, I guess the quirk info can be accessed with
> >>
> >>
Hi,
> >> > Rather than trying small and smaller transfers, would it not be better
> >> > to get the i2c core to expose the quirk info about transfer limits?
> >> >
> >>
> >> Sounds a good idea to me, I guess the quirk info can be accessed with
> >>
> >>
On Mon, Feb 20, 2017 at 01:33:09PM +0530, Ritesh Harjani wrote:
> mmc-sleep-awake enables CMD5 awake feature
> & partial_init which can help reduce resume
> latency on emmc.
>
> Signed-off-by: Ritesh Harjani
> ---
> Documentation/devicetree/bindings/mmc/mmc.txt | 2 ++
>
On Mon, Feb 20, 2017 at 01:33:09PM +0530, Ritesh Harjani wrote:
> mmc-sleep-awake enables CMD5 awake feature
> & partial_init which can help reduce resume
> latency on emmc.
>
> Signed-off-by: Ritesh Harjani
> ---
> Documentation/devicetree/bindings/mmc/mmc.txt | 2 ++
> 1 file changed, 2
On 02/14/2017 07:07 AM, Bjorn Helgaas wrote:
On Mon, Feb 13, 2017 at 09:44:57PM -0700, Alex Williamson wrote:
On Sat, 30 Jan 2016 01:33:58 +0530
Manish Jaggi wrote:
Cavium devices matching this quirk do not perform
peer-to-peer with other functions, allowing
On 02/14/2017 07:07 AM, Bjorn Helgaas wrote:
On Mon, Feb 13, 2017 at 09:44:57PM -0700, Alex Williamson wrote:
On Sat, 30 Jan 2016 01:33:58 +0530
Manish Jaggi wrote:
Cavium devices matching this quirk do not perform
peer-to-peer with other functions, allowing masking out
these bits as if they
On 2/27/17, 11:02 AM, "David Daney" wrote:
On 02/14/2017 07:07 AM, Bjorn Helgaas wrote:
> On Mon, Feb 13, 2017 at 09:44:57PM -0700, Alex Williamson wrote:
>> On Sat, 30 Jan 2016 01:33:58 +0530
>> Manish Jaggi wrote:
>>
On 2/27/17, 11:02 AM, "David Daney" wrote:
On 02/14/2017 07:07 AM, Bjorn Helgaas wrote:
> On Mon, Feb 13, 2017 at 09:44:57PM -0700, Alex Williamson wrote:
>> On Sat, 30 Jan 2016 01:33:58 +0530
>> Manish Jaggi wrote:
>>
>>> Cavium devices matching this quirk do not
- Original Message -
> From: "Thomas Gleixner"
> To: "Paolo Bonzini"
> Cc: "Peter Zijlstra" , "Wanpeng Li"
> , "Mike Galbraith" ,
> "LKML" , "Ingo Molnar"
- Original Message -
> From: "Thomas Gleixner"
> To: "Paolo Bonzini"
> Cc: "Peter Zijlstra" , "Wanpeng Li"
> , "Mike Galbraith" ,
> "LKML" , "Ingo Molnar" ,
> "Borislav Petkov"
> Sent: Monday, February 27, 2017 6:40:46 PM
> Subject: Re: tip.today - scheduler bam boom crash (cpu
Arnaldo Carvalho de Melo writes:
> Em Wed, Feb 22, 2017 at 07:23:38PM +0530, Naveen N. Rao escreveu:
>> With ABIv2, we offset 8 bytes into a function to get at the local entry
>> point.
>
> So, I think I can carry the first one via Ingo, etc, what about this
> one?
>
> Is it ok
On Sun, Feb 19, 2017 at 01:50:21PM -0500, Anurup M wrote:
> 1) Device tree bindings for Hisilicon SoC PMU.
> 2) Add example for Hisilicon L3 cache and MN PMU.
> 3) Add child nodes of L3C and MN in djtag bindings example.
>
> Signed-off-by: Anurup M
> Signed-off-by: Shaokun
701 - 800 of 1502 matches
Mail list logo