The parameter order mismatches tpm_transmit_cmd().
Fixes: c659af78eb7b ("tpm: Check size of response before accessing data")
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c | 14 +++---
drivers/char/tpm/tpm-sysfs.c | 33
The parameter order mismatches tpm_transmit_cmd().
Fixes: c659af78eb7b ("tpm: Check size of response before accessing data")
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm-interface.c | 14 +++---
drivers/char/tpm/tpm-sysfs.c | 33 -
On Tue, Jan 24, 2017 at 10:38:03AM +0800, Chris Zhong wrote:
> correct the coding style, according the checkpatch scripts
>
Reviewed-by: Sean Paul
> Signed-off-by: Chris Zhong
> ---
>
> Changes in v4: None
> Changes in v3: None
>
>
On Tue, Jan 31, 2017 at 8:59 AM, Matthew Wilcox wrote:
> Hi Dan, Konstantin,
>
> You've been interested in using range entries in the radix tree rather
> than higher-order entries. I've built a range entry interface on top
> of our current radix tree substrate, and it seems
On Tue, Jan 24, 2017 at 10:38:03AM +0800, Chris Zhong wrote:
> correct the coding style, according the checkpatch scripts
>
Reviewed-by: Sean Paul
> Signed-off-by: Chris Zhong
> ---
>
> Changes in v4: None
> Changes in v3: None
>
> drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 33
On Tue, Jan 31, 2017 at 8:59 AM, Matthew Wilcox wrote:
> Hi Dan, Konstantin,
>
> You've been interested in using range entries in the radix tree rather
> than higher-order entries. I've built a range entry interface on top
> of our current radix tree substrate, and it seems to be behaving itself
On Tue, Jan 31, 2017 at 02:16:31PM +0100, Dmitry Vyukov wrote:
> Hello,
>
> I am getting the following reports with low frequency while running
> syzkaller fuzzer. Unfortunately they are not reproducible and happen
> in a background thread, so it is difficult to extract any context on
> my side.
On Tue, Jan 31, 2017 at 02:16:31PM +0100, Dmitry Vyukov wrote:
> Hello,
>
> I am getting the following reports with low frequency while running
> syzkaller fuzzer. Unfortunately they are not reproducible and happen
> in a background thread, so it is difficult to extract any context on
> my side.
On Tue, Jan 24, 2017 at 10:38:02AM +0800, Chris Zhong wrote:
> The vopb/vopl switch register of RK3399 mipi is different from RK3288,
> the default setting for mipi dsi mode is different too, so add a
> of_device_id structure to distinguish them, and make sure set the
> correct mode before mipi
On Tue, Jan 24, 2017 at 10:38:02AM +0800, Chris Zhong wrote:
> The vopb/vopl switch register of RK3399 mipi is different from RK3288,
> the default setting for mipi dsi mode is different too, so add a
> of_device_id structure to distinguish them, and make sure set the
> correct mode before mipi
Hi Steve,
On Fri, Jan 06, 2017 at 06:11:36PM -0800, Steve Longerbeam wrote:
> +/*
> + * Min/Max supported width and heights.
> + *
> + * We allow planar output from the SMFC, so we have to align
> + * output width by 16 pixels to meet IDMAC alignment requirements,
> + * which also means input
On Wed, Feb 01, 2017 at 07:53:47PM +0200, Jarkko Sakkinen wrote:
> There are two type issues associated with tpm_getcap().
>
> You must not do arithmetic with __be32 or __le32 types because sometimes
> it results incorrect results. Calculations must be done only with data
> that is in CPU byte
Hi Steve,
On Fri, Jan 06, 2017 at 06:11:36PM -0800, Steve Longerbeam wrote:
> +/*
> + * Min/Max supported width and heights.
> + *
> + * We allow planar output from the SMFC, so we have to align
> + * output width by 16 pixels to meet IDMAC alignment requirements,
> + * which also means input
On Wed, Feb 01, 2017 at 07:53:47PM +0200, Jarkko Sakkinen wrote:
> There are two type issues associated with tpm_getcap().
>
> You must not do arithmetic with __be32 or __le32 types because sometimes
> it results incorrect results. Calculations must be done only with data
> that is in CPU byte
Given that the naming of pmem devices changes from the pmemX form to the
pmemX.Y form when namespace id is greater than 0, arrange for namespaces
with id-0 to be exempt from deletion. Otherwise a simple reconfiguration
of an existing namespace to a new mode results in a name change of the
Given that the naming of pmem devices changes from the pmemX form to the
pmemX.Y form when namespace id is greater than 0, arrange for namespaces
with id-0 to be exempt from deletion. Otherwise a simple reconfiguration
of an existing namespace to a new mode results in a name change of the
On Wed, Feb 01, 2017 at 06:34:01PM +, Will Deacon wrote:
> On Wed, Feb 01, 2017 at 06:22:44PM +, Catalin Marinas wrote:
> > On Wed, Feb 01, 2017 at 05:59:48PM +, Will Deacon wrote:
> > > On Wed, Feb 01, 2017 at 05:49:34PM +, Catalin Marinas wrote:
> > > > On Wed, Feb 01, 2017 at
On Wed, Feb 01, 2017 at 06:34:01PM +, Will Deacon wrote:
> On Wed, Feb 01, 2017 at 06:22:44PM +, Catalin Marinas wrote:
> > On Wed, Feb 01, 2017 at 05:59:48PM +, Will Deacon wrote:
> > > On Wed, Feb 01, 2017 at 05:49:34PM +, Catalin Marinas wrote:
> > > > On Wed, Feb 01, 2017 at
On Fri, Jan 27, 2017 at 01:30:15PM +, Dan O'Donovan wrote:
> + if (acpi_of_modalias(adev, spi->modalias, sizeof(spi->modalias)))
> + strlcpy(spi->modalias, acpi_device_hid(adev),
> + sizeof(spi->modalias));
I can't help but think that this would be simpler
On Fri, Jan 27, 2017 at 01:30:15PM +, Dan O'Donovan wrote:
> + if (acpi_of_modalias(adev, spi->modalias, sizeof(spi->modalias)))
> + strlcpy(spi->modalias, acpi_device_hid(adev),
> + sizeof(spi->modalias));
I can't help but think that this would be simpler
On Wed, Feb 01, 2017 at 06:22:44PM +, Catalin Marinas wrote:
> On Wed, Feb 01, 2017 at 05:59:48PM +, Will Deacon wrote:
> > On Wed, Feb 01, 2017 at 05:49:34PM +, Catalin Marinas wrote:
> > > On Wed, Feb 01, 2017 at 05:41:05PM +, Will Deacon wrote:
> > > > Maybe
> > > > just select
On Wed, Feb 01, 2017 at 06:22:44PM +, Catalin Marinas wrote:
> On Wed, Feb 01, 2017 at 05:59:48PM +, Will Deacon wrote:
> > On Wed, Feb 01, 2017 at 05:49:34PM +, Catalin Marinas wrote:
> > > On Wed, Feb 01, 2017 at 05:41:05PM +, Will Deacon wrote:
> > > > Maybe
> > > > just select
Thanks Gwendal for adding the resume handling. Glad to have been able to
catch that early.
On 01/30/2017 03:47 PM, Gwendal Grignou wrote:
> Add a kernel driver for GOOG0006, an ACPI driver reporting an event when
> the tablet switch status changes.
>
> On an ACPI based convertible chromebook
Thanks Gwendal for adding the resume handling. Glad to have been able to
catch that early.
On 01/30/2017 03:47 PM, Gwendal Grignou wrote:
> Add a kernel driver for GOOG0006, an ACPI driver reporting an event when
> the tablet switch status changes.
>
> On an ACPI based convertible chromebook
On Wed, Feb 01, 2017 at 08:18:45PM +0200, Jarkko Sakkinen wrote:
> On Wed, Feb 01, 2017 at 07:53:47PM +0200, Jarkko Sakkinen wrote:
> > There are two type issues associated with tpm_getcap().
> >
> > You must not do arithmetic with __be32 or __le32 types because sometimes
> > it results incorrect
On Wed, Feb 01, 2017 at 08:18:45PM +0200, Jarkko Sakkinen wrote:
> On Wed, Feb 01, 2017 at 07:53:47PM +0200, Jarkko Sakkinen wrote:
> > There are two type issues associated with tpm_getcap().
> >
> > You must not do arithmetic with __be32 or __le32 types because sometimes
> > it results incorrect
On Wed, Feb 01, 2017 at 01:01:06PM +0530, Nayna wrote:
>
>
> On 02/01/2017 02:20 AM, Jarkko Sakkinen wrote:
> > On Wed, Feb 01, 2017 at 12:14:12AM +0530, Nayna wrote:
> > > > I already sent my pull request to 4.11 and even today I found something
> > > > fishy. You declared a function local
On Wed, Feb 01, 2017 at 01:01:06PM +0530, Nayna wrote:
>
>
> On 02/01/2017 02:20 AM, Jarkko Sakkinen wrote:
> > On Wed, Feb 01, 2017 at 12:14:12AM +0530, Nayna wrote:
> > > > I already sent my pull request to 4.11 and even today I found something
> > > > fishy. You declared a function local
> -Original Message-
> From: Peter Rosin [mailto:p...@axentia.se]
> Sent: Wednesday, February 1, 2017 2:18 AM
> To: Peter Meerwald-Stadler
> Cc: linux-kernel@vger.kernel.org; Jonathan Cameron; Hartmut Knaack; Lars-
> Peter Clausen; Alison Schofield; Gregor Boirie; Sanchayan Maity;
> -Original Message-
> From: Peter Rosin [mailto:p...@axentia.se]
> Sent: Wednesday, February 1, 2017 2:18 AM
> To: Peter Meerwald-Stadler
> Cc: linux-kernel@vger.kernel.org; Jonathan Cameron; Hartmut Knaack; Lars-
> Peter Clausen; Alison Schofield; Gregor Boirie; Sanchayan Maity;
When the debug spinlock code detects a lockup, it will print out an
error messages as well as the backtraces of all the CPUs. However, if
more than one CPUs are waiting on that lock, multiple lockup messages
will be printed leading to garbled output.
To reduce clutter in the console log, now only
When the debug spinlock code detects a lockup, it will print out an
error messages as well as the backtraces of all the CPUs. However, if
more than one CPUs are waiting on that lock, multiple lockup messages
will be printed leading to garbled output.
To reduce clutter in the console log, now only
The current debug spinlock implementation is a TATAS unfair lock. This
can occasionally lead to system lockup with a debug kernel because
of the unfairness of the lock rather than inherent locking problem.
This patch set changes the debug spinlock implementation to a
mostly fair spinlock based on
The debug spinlock code is a basic TATAS unfair lock irrespective
of what the underlying architecture specific spinlock implementation
is. As a result, it is sometimes possible to trigger a false positive
"lockup suspected" warning with all the cpu backtraces.
This patch re-implements the debug
The current debug spinlock implementation is a TATAS unfair lock. This
can occasionally lead to system lockup with a debug kernel because
of the unfairness of the lock rather than inherent locking problem.
This patch set changes the debug spinlock implementation to a
mostly fair spinlock based on
The debug spinlock code is a basic TATAS unfair lock irrespective
of what the underlying architecture specific spinlock implementation
is. As a result, it is sometimes possible to trigger a false positive
"lockup suspected" warning with all the cpu backtraces.
This patch re-implements the debug
On Wed, Feb 01, 2017 at 08:49:30AM -0500, Mimi Zohar wrote:
> On Wed, 2017-02-01 at 12:30 +0200, Jarkko Sakkinen wrote:
> > On Tue, Jan 31, 2017 at 05:31:50PM -0500, Mimi Zohar wrote:
> > > On Wed, 2017-02-01 at 08:46 +1100, James Morris wrote:
> > > > On Tue, 31 Jan 2017, Jarkko Sakkinen wrote:
>
On Wed, Feb 01, 2017 at 08:49:30AM -0500, Mimi Zohar wrote:
> On Wed, 2017-02-01 at 12:30 +0200, Jarkko Sakkinen wrote:
> > On Tue, Jan 31, 2017 at 05:31:50PM -0500, Mimi Zohar wrote:
> > > On Wed, 2017-02-01 at 08:46 +1100, James Morris wrote:
> > > > On Tue, 31 Jan 2017, Jarkko Sakkinen wrote:
>
Declare a ramoops memory segment to aid debugging for those without UART
access. Verified to carry console log when holding volume down for 15
seconds.
I was unable to find any ramoops-like memory region used in the 8916
downstream kernels, so the picked region is the last MB in System RAM.
No
Declare a ramoops memory segment to aid debugging for those without UART
access. Verified to carry console log when holding volume down for 15
seconds.
I was unable to find any ramoops-like memory region used in the 8916
downstream kernels, so the picked region is the last MB in System RAM.
No
On Wed, Feb 01, 2017 at 05:59:48PM +, Will Deacon wrote:
> On Wed, Feb 01, 2017 at 05:49:34PM +, Catalin Marinas wrote:
> > On Wed, Feb 01, 2017 at 05:41:05PM +, Will Deacon wrote:
> > > On Wed, Feb 01, 2017 at 05:36:09PM +, Catalin Marinas wrote:
> > > > On Wed, Feb 01, 2017 at
On Wed, Feb 01, 2017 at 05:59:48PM +, Will Deacon wrote:
> On Wed, Feb 01, 2017 at 05:49:34PM +, Catalin Marinas wrote:
> > On Wed, Feb 01, 2017 at 05:41:05PM +, Will Deacon wrote:
> > > On Wed, Feb 01, 2017 at 05:36:09PM +, Catalin Marinas wrote:
> > > > On Wed, Feb 01, 2017 at
On 1 February 2017 at 17:36, Ard Biesheuvel wrote:
> On 1 February 2017 at 16:58, Laura Abbott wrote:
>> On 10/19/2016 09:22 AM, Will Deacon wrote:
>>> On Wed, Oct 19, 2016 at 09:01:33AM -0700, Linus Torvalds wrote:
On Wed, Oct 19, 2016 at 8:56
On 1 February 2017 at 17:36, Ard Biesheuvel wrote:
> On 1 February 2017 at 16:58, Laura Abbott wrote:
>> On 10/19/2016 09:22 AM, Will Deacon wrote:
>>> On Wed, Oct 19, 2016 at 09:01:33AM -0700, Linus Torvalds wrote:
On Wed, Oct 19, 2016 at 8:56 AM, Markus Trippelsdorf
wrote:
> On
On Wed, Feb 01, 2017 at 07:53:47PM +0200, Jarkko Sakkinen wrote:
> There are two type issues associated with tpm_getcap().
>
> You must not do arithmetic with __be32 or __le32 types because sometimes
> it results incorrect results. Calculations must be done only with data
> that is in CPU byte
On Wed, Feb 01, 2017 at 07:53:47PM +0200, Jarkko Sakkinen wrote:
> There are two type issues associated with tpm_getcap().
>
> You must not do arithmetic with __be32 or __le32 types because sometimes
> it results incorrect results. Calculations must be done only with data
> that is in CPU byte
On Tue, Jan 31, 2017 at 11:54:17AM -0600, Rob Herring wrote:
> A few bindings snuck into bindings/video/bridge since consolidating
> everything under bindings/display/bridge/. Move them to the correct
> spot.
>
> Cc: Andrzej Hajda
> Cc: Archit Taneja
On Tue, Jan 31, 2017 at 11:54:17AM -0600, Rob Herring wrote:
> A few bindings snuck into bindings/video/bridge since consolidating
> everything under bindings/display/bridge/. Move them to the correct
> spot.
>
> Cc: Andrzej Hajda
> Cc: Archit Taneja
> Cc: Enric Balletbo i Serra
> Cc: Thierry
Looks fine,
Reviewed-by: Christoph Hellwig
Looks fine,
Reviewed-by: Christoph Hellwig
Dear E-mail User
Please follow the link to update your webmail account http://sbjgqmz93.ukit.me
Thank You
Dear E-mail User
Please follow the link to update your webmail account http://sbjgqmz93.ukit.me
Thank You
On Tue, Jan 24, 2017 at 10:27:27AM +0800, Chris Zhong wrote:
> Hi Sean
>
> On 01/24/2017 01:48 AM, Sean Paul wrote:
> >On Fri, Jan 20, 2017 at 06:10:49PM +0800, Chris Zhong wrote:
> >>The MIPI DSI do not need check the validity of resolution, the max
> >>resolution should depend VOP. Hence,
On Tue, Jan 24, 2017 at 10:27:27AM +0800, Chris Zhong wrote:
> Hi Sean
>
> On 01/24/2017 01:48 AM, Sean Paul wrote:
> >On Fri, Jan 20, 2017 at 06:10:49PM +0800, Chris Zhong wrote:
> >>The MIPI DSI do not need check the validity of resolution, the max
> >>resolution should depend VOP. Hence,
Looks good,
Reviewed-by: Christoph Hellwig
Looks good,
Reviewed-by: Christoph Hellwig
On Wed, 2017-02-01 at 18:36 +0200, Martin Karamihov wrote:
>
> On 02/01/2017 12:39 AM, Joe Perches wrote:
> > On Tue, 2017-01-31 at 21:24 +0200, Martin Karamihov wrote:
> > > This is checkpatch fix for hal/bb_cfg.c file:
> > > remove not necessary braces {}
> > >
> > > Signed-off-by: Martin
On Wed, 2017-02-01 at 18:36 +0200, Martin Karamihov wrote:
>
> On 02/01/2017 12:39 AM, Joe Perches wrote:
> > On Tue, 2017-01-31 at 21:24 +0200, Martin Karamihov wrote:
> > > This is checkpatch fix for hal/bb_cfg.c file:
> > > remove not necessary braces {}
> > >
> > > Signed-off-by: Martin
Looks fine,
Reviewed-by: Christoph Hellwig
Looks fine,
Reviewed-by: Christoph Hellwig
Thiago Jung Bauermann [bauer...@linux.vnet.ibm.com] wrote:
> Instead of this method of trying a small RMA size and rebooting to try a
> bigger size, could the "min RMA percentage of total RAM" field of the
> ibm_architecture_vec be used?
We tried that and concluded that even 1% could end up
Thiago Jung Bauermann [bauer...@linux.vnet.ibm.com] wrote:
> Instead of this method of trying a small RMA size and rebooting to try a
> bigger size, could the "min RMA percentage of total RAM" field of the
> ibm_architecture_vec be used?
We tried that and concluded that even 1% could end up
Hi Steve,
On 01/31/2017 07:32 PM, Steven Rostedt wrote:
> On Tue, 31 Jan 2017 17:00:43 -0500
> Jason Baron wrote:
>
>> ---
>> Documentation/static-keys.txt | 4 +-
>> include/linux/jump_label.h| 23 +---
>> kernel/jump_label.c | 126
>>
Hi Steve,
On 01/31/2017 07:32 PM, Steven Rostedt wrote:
> On Tue, 31 Jan 2017 17:00:43 -0500
> Jason Baron wrote:
>
>> ---
>> Documentation/static-keys.txt | 4 +-
>> include/linux/jump_label.h| 23 +---
>> kernel/jump_label.c | 126
>>
On Wed, Feb 01, 2017 at 05:49:34PM +, Catalin Marinas wrote:
> On Wed, Feb 01, 2017 at 05:41:05PM +, Will Deacon wrote:
> > On Wed, Feb 01, 2017 at 05:36:09PM +, Catalin Marinas wrote:
> > > On Wed, Feb 01, 2017 at 04:33:58PM +, Will Deacon wrote:
> > > > On Wed, Feb 01, 2017 at
On Wed, Feb 01, 2017 at 05:49:34PM +, Catalin Marinas wrote:
> On Wed, Feb 01, 2017 at 05:41:05PM +, Will Deacon wrote:
> > On Wed, Feb 01, 2017 at 05:36:09PM +, Catalin Marinas wrote:
> > > On Wed, Feb 01, 2017 at 04:33:58PM +, Will Deacon wrote:
> > > > On Wed, Feb 01, 2017 at
On Wed 01-02-17 12:29:56, Mikulas Patocka wrote:
>
>
> On Mon, 30 Jan 2017, Michal Hocko wrote:
>
> > From: Michal Hocko
> >
> > copy_params uses kmalloc with vmalloc fallback. We already have a helper
> > for that - kvmalloc. This caller requires GFP_NOIO semantic so it
On Wed 01-02-17 12:29:56, Mikulas Patocka wrote:
>
>
> On Mon, 30 Jan 2017, Michal Hocko wrote:
>
> > From: Michal Hocko
> >
> > copy_params uses kmalloc with vmalloc fallback. We already have a helper
> > for that - kvmalloc. This caller requires GFP_NOIO semantic so it hasn't
> > been
Am Mittwoch, den 01.02.2017, 08:55 -0800 schrieb Andrey Smirnov:
> 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
Am Mittwoch, den 01.02.2017, 08:55 -0800 schrieb Andrey Smirnov:
> 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:
On Fri, Jan 27, 2017 at 11:52:35AM +0100, Enric Balletbo i Serra wrote:
> From: Gwendal Grignou
>
> Add switch to report tablet mode.
>
> Signed-off-by: Gwendal Grignou
> Signed-off-by: Enric Balletbo Serra
Acked-by:
On Fri, Jan 27, 2017 at 11:52:35AM +0100, Enric Balletbo i Serra wrote:
> From: Gwendal Grignou
>
> Add switch to report tablet mode.
>
> Signed-off-by: Gwendal Grignou
> Signed-off-by: Enric Balletbo Serra
Acked-by: Dmitry Torokhov
Lee, can you please take it as well?
> ---
>
> I should
There are two type issues associated with tpm_getcap().
You must not do arithmetic with __be32 or __le32 types because sometimes
it results incorrect results. Calculations must be done only with data
that is in CPU byte order. This commit migrates tpm_getcap() to struct
tpm_buf in order to sort
There are two type issues associated with tpm_getcap().
You must not do arithmetic with __be32 or __le32 types because sometimes
it results incorrect results. Calculations must be done only with data
that is in CPU byte order. This commit migrates tpm_getcap() to struct
tpm_buf in order to sort
blk_mq_tags/requests of specific hardware queue are mostly used in
specific cpus, which might not be in the same numa node as disk. For
example, a nvme card is in node 0. half hardware queue will be used by
node 0, the other node 1.
Signed-off-by: Shaohua Li
---
block/blk-mq.c | 21
blk_mq_tags/requests of specific hardware queue are mostly used in
specific cpus, which might not be in the same numa node as disk. For
example, a nvme card is in node 0. half hardware queue will be used by
node 0, the other node 1.
Signed-off-by: Shaohua Li
---
block/blk-mq.c | 21
On Mon, Jan 23, 2017 at 12:13:19PM +, Lee Jones wrote:
> On Fri, 20 Jan 2017, Enric Balletbo i Serra wrote:
>
> > From: Douglas Anderson
> >
> > Add the defines for the new buttons and switches connected to the CrosEC.
> >
> > Signed-off-by: Douglas Anderson
On Mon, Jan 23, 2017 at 12:13:19PM +, Lee Jones wrote:
> On Fri, 20 Jan 2017, Enric Balletbo i Serra wrote:
>
> > From: Douglas Anderson
> >
> > Add the defines for the new buttons and switches connected to the CrosEC.
> >
> > Signed-off-by: Douglas Anderson
> > Signed-off-by: Enric
Next patch will use the API to get the node from vector for nvme device
Signed-off-by: Shaohua Li
---
drivers/pci/msi.c | 16
include/linux/pci.h | 6 ++
2 files changed, 22 insertions(+)
diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
index
Next patch will use the API to get the node from vector for nvme device
Signed-off-by: Shaohua Li
---
drivers/pci/msi.c | 16
include/linux/pci.h | 6 ++
2 files changed, 22 insertions(+)
diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
index 50c5003..ab7aee7 100644
nvme_queue is per-cpu queue (mostly). Allocating it in node where blk-mq
will use it.
Signed-off-by: Shaohua Li
---
drivers/nvme/host/pci.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index
nvme_queue is per-cpu queue (mostly). Allocating it in node where blk-mq
will use it.
Signed-off-by: Shaohua Li
---
drivers/nvme/host/pci.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index 032237c..9733008
Hi Vineet,
On Wed, 2017-02-01 at 09:37 -0800, Vineet Gupta wrote:
> On 02/01/2017 09:14 AM, Alexey Brodkin wrote:
> >
> > >
> > > >
> > > > -# CONFIG_ARC_TIMERS_64BIT is not set
> > >
> > > Are you sure abut this part. Ater the timers driver rework, this would
> > > enable GFRC
> > > for SMP
Hi Vineet,
On Wed, 2017-02-01 at 09:37 -0800, Vineet Gupta wrote:
> On 02/01/2017 09:14 AM, Alexey Brodkin wrote:
> >
> > >
> > > >
> > > > -# CONFIG_ARC_TIMERS_64BIT is not set
> > >
> > > Are you sure abut this part. Ater the timers driver rework, this would
> > > enable GFRC
> > > for SMP
On Wed, Feb 01, 2017 at 05:49:34PM +, Catalin Marinas wrote:
> On Wed, Feb 01, 2017 at 05:41:05PM +, Will Deacon wrote:
> > On Wed, Feb 01, 2017 at 05:36:09PM +, Catalin Marinas wrote:
> > > On Wed, Feb 01, 2017 at 04:33:58PM +, Will Deacon wrote:
> > > > On Wed, Feb 01, 2017 at
On Wed, Feb 01, 2017 at 05:49:34PM +, Catalin Marinas wrote:
> On Wed, Feb 01, 2017 at 05:41:05PM +, Will Deacon wrote:
> > On Wed, Feb 01, 2017 at 05:36:09PM +, Catalin Marinas wrote:
> > > On Wed, Feb 01, 2017 at 04:33:58PM +, Will Deacon wrote:
> > > > On Wed, Feb 01, 2017 at
On Fri, Jan 20, 2017 at 11:14:15AM +0100, Enric Balletbo i Serra wrote:
> From: Douglas Anderson
>
> On some newer boards using mkbp we're hooking up non-matrix buttons and
> switches to the EC but NOT to the main application processor.
>
> Let's add kernel support to
On Fri, Jan 20, 2017 at 11:14:15AM +0100, Enric Balletbo i Serra wrote:
> From: Douglas Anderson
>
> On some newer boards using mkbp we're hooking up non-matrix buttons and
> switches to the EC but NOT to the main application processor.
>
> Let's add kernel support to handle this. Rather than
On Wed, Feb 01, 2017 at 05:41:05PM +, Will Deacon wrote:
> On Wed, Feb 01, 2017 at 05:36:09PM +, Catalin Marinas wrote:
> > On Wed, Feb 01, 2017 at 04:33:58PM +, Will Deacon wrote:
> > > On Wed, Feb 01, 2017 at 11:29:22AM -0500, Christopher Covington wrote:
> > > > On 01/31/2017 12:56
On Wed, Feb 01, 2017 at 05:41:05PM +, Will Deacon wrote:
> On Wed, Feb 01, 2017 at 05:36:09PM +, Catalin Marinas wrote:
> > On Wed, Feb 01, 2017 at 04:33:58PM +, Will Deacon wrote:
> > > On Wed, Feb 01, 2017 at 11:29:22AM -0500, Christopher Covington wrote:
> > > > On 01/31/2017 12:56
On Wed, Feb 01, 2017 at 05:45:02PM +, Ard Biesheuvel wrote:
> Some AArch64 UEFI implementations disable the MMU in ExitBootServices(),
> after which unaligned accesses to RAM are no longer supported.
>
> Commit abfb7b686a3e ("efi/libstub/arm*: Pass latest memory map to the
> kernel") fixed an
On Wed, Feb 01, 2017 at 05:45:02PM +, Ard Biesheuvel wrote:
> Some AArch64 UEFI implementations disable the MMU in ExitBootServices(),
> after which unaligned accesses to RAM are no longer supported.
>
> Commit abfb7b686a3e ("efi/libstub/arm*: Pass latest memory map to the
> kernel") fixed an
Am Mittwoch, den 01.02.2017, 08:55 -0800 schrieb Andrey Smirnov:
> Some designs implement reset GPIO via a GPIO expander connected to a
> peripheral bus. One such example would be i.MX7 Sabre board where said
> GPIO is provided by SPI shift register connected to a bitbanged SPI
> bus. In order to
Am Mittwoch, den 01.02.2017, 08:55 -0800 schrieb Andrey Smirnov:
> Some designs implement reset GPIO via a GPIO expander connected to a
> peripheral bus. One such example would be i.MX7 Sabre board where said
> GPIO is provided by SPI shift register connected to a bitbanged SPI
> bus. In order to
Hello,
Am Mittwoch, 1. Februar 2017, 16:37:58 BRST schrieb Michael Ellerman:
> Sukadev Bhattiprolu writes:
> > Paul Clarke [p...@us.ibm.com] wrote:
> > ---
> >
> > From f9e9e8460206bc3fa7eaa741b9a2bde22870b9e0 Mon Sep 17 00:00:00 2001
>
> I know it's been a while
Hello,
Am Mittwoch, 1. Februar 2017, 16:37:58 BRST schrieb Michael Ellerman:
> Sukadev Bhattiprolu writes:
> > Paul Clarke [p...@us.ibm.com] wrote:
> > ---
> >
> > From f9e9e8460206bc3fa7eaa741b9a2bde22870b9e0 Mon Sep 17 00:00:00 2001
>
> I know it's been a while but I think it would still be
From: Kalle Valo
Date: Wed, 01 Feb 2017 11:37:38 +0200
> here's a pull request to 4.11, more details in the signed tag below.
>
> I forgot to mention in the tag that this includes one small change to
> include/linux/soc/qcom/smem_state.h which was acked by Andy Gross in
>
From: Kalle Valo
Date: Wed, 01 Feb 2017 11:37:38 +0200
> here's a pull request to 4.11, more details in the signed tag below.
>
> I forgot to mention in the tag that this includes one small change to
> include/linux/soc/qcom/smem_state.h which was acked by Andy Gross in
> commit 6c0b2e833f14.
Now that we have a separate structure for timer context, make functions
generic so that they can work with any timer context, not just the
virtual timer context. This does not change the virtual timer
functionality.
Signed-off-by: Jintack Lim
Acked-by: Marc Zyngier
Now that we have a separate structure for timer context, make functions
generic so that they can work with any timer context, not just the
virtual timer context. This does not change the virtual timer
functionality.
Signed-off-by: Jintack Lim
Acked-by: Marc Zyngier
---
arch/arm/kvm/arm.c
601 - 700 of 1862 matches
Mail list logo