On 09/20/2016 10:12 AM, Hanjun Guo wrote:
> On 09/20/2016 09:38 PM, Robert Richter wrote:
>> On 20.09.16 19:32:34, Hanjun Guo wrote:
>>> On 09/20/2016 06:43 PM, Robert Richter wrote:
>>
Instead we need to make sure the set_*numa_node() functions are called
earlier before secondary cpus
On 09/20/2016 10:12 AM, Hanjun Guo wrote:
> On 09/20/2016 09:38 PM, Robert Richter wrote:
>> On 20.09.16 19:32:34, Hanjun Guo wrote:
>>> On 09/20/2016 06:43 PM, Robert Richter wrote:
>>
Instead we need to make sure the set_*numa_node() functions are called
earlier before secondary cpus
From: Markus Elfring
Date: Wed, 21 Sep 2016 13:31:45 +0200
The local variable "map" will be set to an appropriate pointer a bit later.
Thus omit the explicit initialisation at the beginning.
Signed-off-by: Markus Elfring
---
From: Markus Elfring
Date: Wed, 21 Sep 2016 13:31:45 +0200
The local variable "map" will be set to an appropriate pointer a bit later.
Thus omit the explicit initialisation at the beginning.
Signed-off-by: Markus Elfring
---
drivers/gpu/drm/omapdrm/omap_dmm_tiler.c | 2 +-
1 file changed, 1
On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote:
> in sysfs.
Google pointed me to /sys/bus/usb/drivers/usb/*
where I find all kinds of 'bConfigurationValue'.
Now is the problem to find which one you could mean.
Under /sys/bus/usb/drivers/usb/7-1 I find
manufacturer which reads
On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote:
> in sysfs.
Google pointed me to /sys/bus/usb/drivers/usb/*
where I find all kinds of 'bConfigurationValue'.
Now is the problem to find which one you could mean.
Under /sys/bus/usb/drivers/usb/7-1 I find
manufacturer which reads
From: Markus Elfring
Date: Wed, 21 Sep 2016 13:16:20 +0200
The kfree() function was called in up to two cases
by the tiler_map_show() function during error handling even if
the passed variable contained a null pointer.
* Adjust jump targets according to the Linux
From: Markus Elfring
Date: Wed, 21 Sep 2016 13:16:20 +0200
The kfree() function was called in up to two cases
by the tiler_map_show() function during error handling even if
the passed variable contained a null pointer.
* Adjust jump targets according to the Linux coding style convention.
*
From: Markus Elfring
Date: Wed, 21 Sep 2016 12:54:07 +0200
A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array" at another place.
From: Markus Elfring
Date: Wed, 21 Sep 2016 12:54:07 +0200
A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array" at another place.
Signed-off-by: Markus Elfring
---
On Wed, Sep 21, 2016 at 11:19:35AM -0500, Timur Tabi wrote:
> On Wed, Sep 21, 2016 at 5:37 AM, Greg Kroah-Hartman
> wrote:
> >
> > I thought you asked Rafael to take them, they are not in my queue
> > anymore because of that. Don't try to shop-around for maintainers
>
On Wed, Sep 21, 2016 at 11:19:35AM -0500, Timur Tabi wrote:
> On Wed, Sep 21, 2016 at 5:37 AM, Greg Kroah-Hartman
> wrote:
> >
> > I thought you asked Rafael to take them, they are not in my queue
> > anymore because of that. Don't try to shop-around for maintainers
> > please, that's kind of
From: Markus Elfring
Date: Wed, 21 Sep 2016 12:23:46 +0200
A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was detected
From: Markus Elfring
Date: Wed, 21 Sep 2016 12:23:46 +0200
A multiplication for the size determination of a memory allocation
indicated that an array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was detected by using the Coccinelle
From: Markus Elfring
Date: Wed, 21 Sep 2016 18:28:38 +0200
Several update suggestions were taken into account
from static source code analysis.
Markus Elfring (14):
Use kmalloc_array() in tiler_map_show()
Replace another kmalloc() call by kmalloc_array() in
From: Markus Elfring
Date: Wed, 21 Sep 2016 18:28:38 +0200
Several update suggestions were taken into account
from static source code analysis.
Markus Elfring (14):
Use kmalloc_array() in tiler_map_show()
Replace another kmalloc() call by kmalloc_array() in tiler_map_show()
Less function
2016-09-21 10:14+0800, Wanpeng Li:
> From: Wanpeng Li
>
> I observed that kvmvapic(to optimize flexpriority=N or AMD) is used
> to boost TPR access when testing kvm-unit-test/eventinj.flat tpr case
> on my haswell desktop (w/ flexpriority, w/o APICv). Commit
2016-09-21 10:14+0800, Wanpeng Li:
> From: Wanpeng Li
>
> I observed that kvmvapic(to optimize flexpriority=N or AMD) is used
> to boost TPR access when testing kvm-unit-test/eventinj.flat tpr case
> on my haswell desktop (w/ flexpriority, w/o APICv). Commit (8d14695f9542
> x86, apicv: add
Thanks, I've got this one, too.
-corey
On 09/21/2016 05:24 AM, Cédric Le Goater wrote:
Signed-off-by: Cédric Le Goater
---
drivers/char/ipmi/Kconfig |1 +
1 file changed, 1 insertion(+)
Index: linux.git/drivers/char/ipmi/Kconfig
On Wed, Sep 21, 2016 at 12:37:53PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 20, 2016 at 06:29:59PM -0700, Stephane Eranian escreveu:
> > Hi Arnaldo,
> >
> > I ran into an issue trying to use the --pid filtering option of perf report.
> >
> > I do a system-wide collection and then I
Thanks, I've got this one, too.
-corey
On 09/21/2016 05:24 AM, Cédric Le Goater wrote:
Signed-off-by: Cédric Le Goater
---
drivers/char/ipmi/Kconfig |1 +
1 file changed, 1 insertion(+)
Index: linux.git/drivers/char/ipmi/Kconfig
On Wed, Sep 21, 2016 at 12:37:53PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Sep 20, 2016 at 06:29:59PM -0700, Stephane Eranian escreveu:
> > Hi Arnaldo,
> >
> > I ran into an issue trying to use the --pid filtering option of perf report.
> >
> > I do a system-wide collection and then I
On 09/21/2016 05:17 AM, Cédric Le Goater wrote:
On 09/21/2016 12:05 PM, Joel Stanley wrote:
devm_ioremap_resource returns ERR_PTR so we can't check for NULL.
Thanks for spotting this.
Acked-by: Cédric Le Goater
Thanks, I've pull this into my tree.
-corey
C.
On 09/21/2016 05:17 AM, Cédric Le Goater wrote:
On 09/21/2016 12:05 PM, Joel Stanley wrote:
devm_ioremap_resource returns ERR_PTR so we can't check for NULL.
Thanks for spotting this.
Acked-by: Cédric Le Goater
Thanks, I've pull this into my tree.
-corey
C.
Signed-off-by: Joel Stanley
On 09/21/2016 09:27 AM, Michal Hocko wrote:
> That was not my point. I wasn't very clear probably. Offlining can fail
> which shouldn't be really surprising. There might be a kernel allocation
> in the particular block which cannot be migrated so failures are to be
> expected. I just do not see
On 09/21/2016 09:27 AM, Michal Hocko wrote:
> That was not my point. I wasn't very clear probably. Offlining can fail
> which shouldn't be really surprising. There might be a kernel allocation
> in the particular block which cannot be migrated so failures are to be
> expected. I just do not see
On Wednesday, September 21, 2016 12:13:25 PM CEST Greg KH wrote:
> On Sat, Sep 17, 2016 at 09:43:02PM +0200, Christian Lamparter wrote:
> > Ben Greear reported:
> > > I see lots of instability as soon as I load up the carl9710 NIC.
> > > My application is going to be poking at it's debugfs
On Wednesday, September 21, 2016 12:13:25 PM CEST Greg KH wrote:
> On Sat, Sep 17, 2016 at 09:43:02PM +0200, Christian Lamparter wrote:
> > Ben Greear reported:
> > > I see lots of instability as soon as I load up the carl9710 NIC.
> > > My application is going to be poking at it's debugfs
On Wed, Sep 21, 2016 at 09:57:38AM +0100, Brian Starkey wrote:
> Hi Russell,
>
> Are you in a position to be able to test this now?
Normally, I'd say no, because I'd normally wait for 4.8 to be out before
moving the cubox tree up. However, as we're close to 4.8, I've merged
4.8-rc7 in (and
On Wed, Sep 21, 2016 at 09:57:38AM +0100, Brian Starkey wrote:
> Hi Russell,
>
> Are you in a position to be able to test this now?
Normally, I'd say no, because I'd normally wait for 4.8 to be out before
moving the cubox tree up. However, as we're close to 4.8, I've merged
4.8-rc7 in (and
On Mon, Sep 19, 2016 at 07:09:51PM +0100, James wrote:
> From: Greg Kroah-Hartman
>
> This patch fixes a NULL pointer dereference caused by a race codition in the
> probe function of the legousbtower driver. It re-structures the probe
> function to only register the
On Mon, Sep 19, 2016 at 07:09:51PM +0100, James wrote:
> From: Greg Kroah-Hartman
>
> This patch fixes a NULL pointer dereference caused by a race codition in the
> probe function of the legousbtower driver. It re-structures the probe
> function to only register the interface after successfully
On Wed 21-09-16 09:04:31, Dave Hansen wrote:
> On 09/21/2016 05:05 AM, Michal Hocko wrote:
> > On Tue 20-09-16 10:43:13, Dave Hansen wrote:
> >> On 09/20/2016 08:52 AM, Rui Teng wrote:
> >>> On 9/20/16 10:53 PM, Dave Hansen wrote:
> >> ...
> That's good, but aren't we still left with a
On Wed 21-09-16 09:04:31, Dave Hansen wrote:
> On 09/21/2016 05:05 AM, Michal Hocko wrote:
> > On Tue 20-09-16 10:43:13, Dave Hansen wrote:
> >> On 09/20/2016 08:52 AM, Rui Teng wrote:
> >>> On 9/20/16 10:53 PM, Dave Hansen wrote:
> >> ...
> That's good, but aren't we still left with a
On Wed, Sep 21, 2016 at 5:37 AM, Greg Kroah-Hartman
wrote:
>
> I thought you asked Rafael to take them, they are not in my queue
> anymore because of that. Don't try to shop-around for maintainers
> please, that's kind of rude...
In Aleksey's defense, these patches
On Wed, Sep 21, 2016 at 5:37 AM, Greg Kroah-Hartman
wrote:
>
> I thought you asked Rafael to take them, they are not in my queue
> anymore because of that. Don't try to shop-around for maintainers
> please, that's kind of rude...
In Aleksey's defense, these patches have been floating around for
Commit-ID: 1827822902cf659d60d3413fd42c7e6cbd18df4d
Gitweb: http://git.kernel.org/tip/1827822902cf659d60d3413fd42c7e6cbd18df4d
Author: Denys Vlasenko
AuthorDate: Sun, 18 Sep 2016 20:21:25 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Sep 2016
Commit-ID: 475339684ef19e46f4702e2d185a869a5c454688
Gitweb: http://git.kernel.org/tip/475339684ef19e46f4702e2d185a869a5c454688
Author: Denys Vlasenko
AuthorDate: Sat, 17 Sep 2016 23:39:26 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Sep 2016
Commit-ID: 1827822902cf659d60d3413fd42c7e6cbd18df4d
Gitweb: http://git.kernel.org/tip/1827822902cf659d60d3413fd42c7e6cbd18df4d
Author: Denys Vlasenko
AuthorDate: Sun, 18 Sep 2016 20:21:25 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Sep 2016 15:02:12 +0200
x86/e820: Use much less
Commit-ID: 475339684ef19e46f4702e2d185a869a5c454688
Gitweb: http://git.kernel.org/tip/475339684ef19e46f4702e2d185a869a5c454688
Author: Denys Vlasenko
AuthorDate: Sat, 17 Sep 2016 23:39:26 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Sep 2016 15:02:12 +0200
x86/e820: Prepare e280
Commit-ID: 8c2103f224216a45c1a4d7aebbc13f3e007cde34
Gitweb: http://git.kernel.org/tip/8c2103f224216a45c1a4d7aebbc13f3e007cde34
Author: Denys Vlasenko
AuthorDate: Sat, 17 Sep 2016 23:39:25 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Sep 2016
Commit-ID: 8c2103f224216a45c1a4d7aebbc13f3e007cde34
Gitweb: http://git.kernel.org/tip/8c2103f224216a45c1a4d7aebbc13f3e007cde34
Author: Denys Vlasenko
AuthorDate: Sat, 17 Sep 2016 23:39:25 +0200
Committer: Ingo Molnar
CommitDate: Wed, 21 Sep 2016 15:02:11 +0200
x86/e820: Mark some
Hi Zhichang
> -Original Message-
> From: zhichang [mailto:zhichang.yua...@gmail.com]
> Sent: 21 September 2016 11:09
> To: Arnd Bergmann; linux-arm-ker...@lists.infradead.org
> Cc: Gabriele Paoloni; devicet...@vger.kernel.org;
> lorenzo.pieral...@arm.com; miny...@acm.org;
Hi Zhichang
> -Original Message-
> From: zhichang [mailto:zhichang.yua...@gmail.com]
> Sent: 21 September 2016 11:09
> To: Arnd Bergmann; linux-arm-ker...@lists.infradead.org
> Cc: Gabriele Paoloni; devicet...@vger.kernel.org;
> lorenzo.pieral...@arm.com; miny...@acm.org;
On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote:
> On Tue, 2016-09-20 at 17:45 +0200, Wim Osterholt wrote:
>
> Anyway, which of its configurations is used?
> Please look up the bConfigurationValue for your device
> in sysfs.
And what might that be?
'locate sysfs' gives one hit at
On Wed, Sep 21, 2016 at 02:21:17PM +0200, Oliver Neukum wrote:
> On Tue, 2016-09-20 at 17:45 +0200, Wim Osterholt wrote:
>
> Anyway, which of its configurations is used?
> Please look up the bConfigurationValue for your device
> in sysfs.
And what might that be?
'locate sysfs' gives one hit at
On Wed, Sep 21, 2016 at 11:45:02AM +0300, Mika Westerberg wrote:
> On Wed, Sep 21, 2016 at 07:48:35AM +0200, Wolfram Sang wrote:
> > On Tue, Sep 20, 2016 at 04:59:25PM +0300, Mika Westerberg wrote:
> > > When enumerating I2C devices connected to an I2C adapter we scan the whole
> > > namespace (as
On Wed, Sep 21, 2016 at 11:45:02AM +0300, Mika Westerberg wrote:
> On Wed, Sep 21, 2016 at 07:48:35AM +0200, Wolfram Sang wrote:
> > On Tue, Sep 20, 2016 at 04:59:25PM +0300, Mika Westerberg wrote:
> > > When enumerating I2C devices connected to an I2C adapter we scan the whole
> > > namespace (as
store the physical address of the device in its priv to use it
for DMA addressing in the client drivers.
Signed-off-by: Mugunthan V N
---
drivers/mfd/ti_am335x_tscadc.c | 1 +
include/linux/mfd/ti_am335x_tscadc.h | 1 +
2 files changed, 2 insertions(+)
diff --git
The ADC has a 64 work depth fifo length which holds the ADC data
till the CPU reads. So when a user program needs a large ADC data
to operate on, then it has to do multiple reads to get its
buffer. Currently if the application asks for 4 samples per
channel with all 8 channels are enabled, kernel
store the physical address of the device in its priv to use it
for DMA addressing in the client drivers.
Signed-off-by: Mugunthan V N
---
drivers/mfd/ti_am335x_tscadc.c | 1 +
include/linux/mfd/ti_am335x_tscadc.h | 1 +
2 files changed, 2 insertions(+)
diff --git
The ADC has a 64 work depth fifo length which holds the ADC data
till the CPU reads. So when a user program needs a large ADC data
to operate on, then it has to do multiple reads to get its
buffer. Currently if the application asks for 4 samples per
channel with all 8 channels are enabled, kernel
Add DMA properties for tscadc
Signed-off-by: Mugunthan V N
---
arch/arm/boot/dts/am33xx.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 98748c6..6d607b8 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
BugLink: https://bugs.launchpad.net/bugs/1535802
T: Bus=01 Lev=02 Prnt=02 Port=04 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=04ca ProdID=3011 Rev=00.01
C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon)
BugLink: https://bugs.launchpad.net/bugs/1535802
T: Bus=01 Lev=02 Prnt=02 Port=04 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=04ca ProdID=3011 Rev=00.01
C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon)
Add DMA properties for tscadc
Signed-off-by: Mugunthan V N
---
arch/arm/boot/dts/am33xx.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi
index 98748c6..6d607b8 100644
--- a/arch/arm/boot/dts/am33xx.dtsi
+++
Add DMA properties for tscadc
Signed-off-by: Mugunthan V N
---
arch/arm/boot/dts/am4372.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi
index 0fadae5..6094d17 100644
--- a/arch/arm/boot/dts/am4372.dtsi
This patch adds the required pieces to ti_am335x_adc driver for
DMA support
Signed-off-by: Mugunthan V N
---
drivers/iio/adc/ti_am335x_adc.c | 160 ++-
include/linux/mfd/ti_am335x_tscadc.h | 7 ++
2 files changed, 164 insertions(+), 3
This patch adds the required pieces to ti_am335x_adc driver for
DMA support
Signed-off-by: Mugunthan V N
---
drivers/iio/adc/ti_am335x_adc.c | 160 ++-
include/linux/mfd/ti_am335x_tscadc.h | 7 ++
2 files changed, 164 insertions(+), 3 deletions(-)
diff
Add DMA properties for tscadc
Signed-off-by: Mugunthan V N
---
arch/arm/boot/dts/am4372.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi
index 0fadae5..6094d17 100644
--- a/arch/arm/boot/dts/am4372.dtsi
+++
On Wed, Sep 21, 2016 at 03:56:41PM +, David Laight wrote:
> From: Neil Horman
> > Sent: 21 September 2016 16:43
> > On Wed, Sep 21, 2016 at 09:44:30PM +0800, Sun Paul wrote:
> > > Hi
> > >
> > > we have an SCTP application running in JAVA. and we found that there
> > > is a problem when we as
On Wed, Sep 21, 2016 at 03:56:41PM +, David Laight wrote:
> From: Neil Horman
> > Sent: 21 September 2016 16:43
> > On Wed, Sep 21, 2016 at 09:44:30PM +0800, Sun Paul wrote:
> > > Hi
> > >
> > > we have an SCTP application running in JAVA. and we found that there
> > > is a problem when we as
On 09/21/2016 05:05 AM, Michal Hocko wrote:
> On Tue 20-09-16 10:43:13, Dave Hansen wrote:
>> On 09/20/2016 08:52 AM, Rui Teng wrote:
>>> On 9/20/16 10:53 PM, Dave Hansen wrote:
>> ...
That's good, but aren't we still left with a situation where we've
offlined and dissolved the _middle_
On 09/21/2016 05:05 AM, Michal Hocko wrote:
> On Tue 20-09-16 10:43:13, Dave Hansen wrote:
>> On 09/20/2016 08:52 AM, Rui Teng wrote:
>>> On 9/20/16 10:53 PM, Dave Hansen wrote:
>> ...
That's good, but aren't we still left with a situation where we've
offlined and dissolved the _middle_
Convert the use of UV version-specific functions to their abstracted
counterparts.
Signed-off-by: Andrew Banman
Acked-by: Mike Travis
Acked-by: Dimitri Sivanich
Acked-by: Thomas Gleixner
---
arch/x86/platform/uv/tlb_uv.c
Convert the use of UV version-specific functions to their abstracted
counterparts.
Signed-off-by: Andrew Banman
Acked-by: Mike Travis
Acked-by: Dimitri Sivanich
Acked-by: Thomas Gleixner
---
arch/x86/platform/uv/tlb_uv.c | 26 +-
1 file changed, 13 insertions(+), 13
The BAU on UV4 does not need to maintain the payload queue tail pointer. Do
not initialize the tail pointer MMR on UV4.
Note that write_payload_tail is not an abstracted BAU function since it is
an operation specific to pre-UV4 versions. Then we must switch on the UV
version to control its usage,
Many BAU functions have different implementations depending on the UV
version. Rather than switching on the uvhub_version throughout the driver,
we can define a set of operations for each version. This is especially
beneficial for UV4, which will require many new MMR read/write functions.
The payload queue first MMR requires the physical memory address and hub
GNODE of where the payload queue resides in memory, but the associated
variables are named as if the PNODE were used. Rename gnode-related
variables and clarify the definitions of the payload queue head, last, and
tail
Many BAU functions have different implementations depending on the UV
version. Rather than switching on the uvhub_version throughout the driver,
we can define a set of operations for each version. This is especially
beneficial for UV4, which will require many new MMR read/write functions.
The payload queue first MMR requires the physical memory address and hub
GNODE of where the payload queue resides in memory, but the associated
variables are named as if the PNODE were used. Rename gnode-related
variables and clarify the definitions of the payload queue head, last, and
tail
The BAU on UV4 does not need to maintain the payload queue tail pointer. Do
not initialize the tail pointer MMR on UV4.
Note that write_payload_tail is not an abstracted BAU function since it is
an operation specific to pre-UV4 versions. Then we must switch on the UV
version to control its usage,
Software timeouts are not currently supported on BAU for UV4. Instead, the
BAU will rely on hardware-level fairness protocols to determine broadcast
timeouts.
Do not call enable_timeouts or calculate_destination_timeout on UV4. These
functions write to pre-UV4 MMRs so they generate error messages
The BAU driver should use the functions provided by uv_hub.h rather than
its own implementations. uv_physnodeaddr converts vaddrs to paddrs for
BAU MMR fields, but this is done better by uv_gpa_to_offset.
Signed-off-by: Andrew Banman
Acked-by: Mike Travis
Add the UV4-specific function definitions and define an operations struct
to implement them in the BAU driver.
Many BAU MMRs, although functionally the same, have new addresses on UV4
due to hardware changes. Each MMR requires new read/write functions, but
their implementation in the driver does
Fix whitespace on blocks of code to be vertically aligned.
Signed-off-by: Andrew Banman
Acked-by: Mike Travis
Acked-by: Dimitri Sivanich
Acked-by: Thomas Gleixner
---
arch/x86/platform/uv/tlb_uv.c | 64
Software timeouts are not currently supported on BAU for UV4. Instead, the
BAU will rely on hardware-level fairness protocols to determine broadcast
timeouts.
Do not call enable_timeouts or calculate_destination_timeout on UV4. These
functions write to pre-UV4 MMRs so they generate error messages
The BAU driver should use the functions provided by uv_hub.h rather than
its own implementations. uv_physnodeaddr converts vaddrs to paddrs for
BAU MMR fields, but this is done better by uv_gpa_to_offset.
Signed-off-by: Andrew Banman
Acked-by: Mike Travis
Acked-by: Dimitri Sivanich
Acked-by:
Add the UV4-specific function definitions and define an operations struct
to implement them in the BAU driver.
Many BAU MMRs, although functionally the same, have new addresses on UV4
due to hardware changes. Each MMR requires new read/write functions, but
their implementation in the driver does
Fix whitespace on blocks of code to be vertically aligned.
Signed-off-by: Andrew Banman
Acked-by: Mike Travis
Acked-by: Dimitri Sivanich
Acked-by: Thomas Gleixner
---
arch/x86/platform/uv/tlb_uv.c | 64 +--
1 file changed, 32 insertions(+), 32
Replace all uses of printk with the appropriate pr_* function.
Signed-off-by: Andrew Banman
Acked-by: Mike Travis
Acked-by: Dimitri Sivanich
Acked-by: Thomas Gleixner
---
arch/x86/platform/uv/tlb_uv.c | 26
This is version 2 of a patch set to add UV4 support to the BAU. The only
changes from the the original version are whitespace sytle fixes (PATCH 1).
The following patch set adds support for UV4 architecture to the Broadcast
Assist Unit (BAU). Major hardware changes to the BAU require these fixes
Signed-off-by: Andrew Banman
Acked-by: Mike Travis
Acked-by: Dimitri Sivanich
Acked-by: Thomas Gleixner
---
arch/x86/platform/uv/tlb_uv.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Replace all uses of printk with the appropriate pr_* function.
Signed-off-by: Andrew Banman
Acked-by: Mike Travis
Acked-by: Dimitri Sivanich
Acked-by: Thomas Gleixner
---
arch/x86/platform/uv/tlb_uv.c | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff
This is version 2 of a patch set to add UV4 support to the BAU. The only
changes from the the original version are whitespace sytle fixes (PATCH 1).
The following patch set adds support for UV4 architecture to the Broadcast
Assist Unit (BAU). Major hardware changes to the BAU require these fixes
Signed-off-by: Andrew Banman
Acked-by: Mike Travis
Acked-by: Dimitri Sivanich
Acked-by: Thomas Gleixner
---
arch/x86/platform/uv/tlb_uv.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/x86/platform/uv/tlb_uv.c b/arch/x86/platform/uv/tlb_uv.c
index 030d452..ddbeb16
Memdup_user encapsulates a memory allocation with the flag GFP_KERNEL, so
only allow this flag in the original code.
Signed-off-by: Julia Lawall
---
scripts/coccinelle/api/memdup_user.cocci |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Memdup_user encapsulates a memory allocation with the flag GFP_KERNEL, so
only allow this flag in the original code.
Signed-off-by: Julia Lawall
---
scripts/coccinelle/api/memdup_user.cocci |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
Hi Tejun,
On Wed, Sep 21, 2016 at 7:56 PM, Tejun Heo wrote:
> Hello, Parav.
>
> On Wed, Sep 21, 2016 at 10:13:38AM +0530, Parav Pandit wrote:
>> We have completed review from Tejun, Christoph.
>> HFI driver folks also provided feedback for Intel drivers.
>> Matan's also doesn't
Hi Tejun,
On Wed, Sep 21, 2016 at 7:56 PM, Tejun Heo wrote:
> Hello, Parav.
>
> On Wed, Sep 21, 2016 at 10:13:38AM +0530, Parav Pandit wrote:
>> We have completed review from Tejun, Christoph.
>> HFI driver folks also provided feedback for Intel drivers.
>> Matan's also doesn't have any more
From: Rafał Miłecki
This driver should initialize controller only, PHY initialization should
be handled by separated PHY driver. We already have phy-bcm-ns-usb2 in
place so let it makes its duty.
Signed-off-by: Rafał Miłecki
---
drivers/usb/host/bcma-hcd.c
From: Rafał Miłecki
This driver should initialize controller only, PHY initialization should
be handled by separated PHY driver. We already have phy-bcm-ns-usb2 in
place so let it makes its duty.
Signed-off-by: Rafał Miłecki
---
drivers/usb/host/bcma-hcd.c | 80
Date: Wed, 21 Sep 2016 16:17:20 +0200, Andrew Lunn wrote:
>On Wed, Sep 21, 2016 at 02:16:30PM +0800, Sean Wang wrote:
>> Date: Tue, 20 Sep 2016 21:37:58 +0200, Andrew Lunn wrote:
>> >On Tue, Sep 20, 2016 at 03:59:20PM +0800, sean.w...@mediatek.com wrote:
>> >>
Date: Wed, 21 Sep 2016 16:17:20 +0200, Andrew Lunn wrote:
>On Wed, Sep 21, 2016 at 02:16:30PM +0800, Sean Wang wrote:
>> Date: Tue, 20 Sep 2016 21:37:58 +0200, Andrew Lunn wrote:
>> >On Tue, Sep 20, 2016 at 03:59:20PM +0800, sean.w...@mediatek.com wrote:
>> >> From: Sean Wang
>> >>
>> >> Add
On Tue, Sep 20, 2016 at 10:33:57AM +0800, Chao Yu wrote:
> register_shrinker can fail after commit 1d3d4437eae1 ("vmscan: per-node
> deferred work"), we should detect the failure of it, otherwise we may
> fail to register shrinker after raid5 configuration was setup successfully.
>
>
On Tue, Sep 20, 2016 at 10:33:57AM +0800, Chao Yu wrote:
> register_shrinker can fail after commit 1d3d4437eae1 ("vmscan: per-node
> deferred work"), we should detect the failure of it, otherwise we may
> fail to register shrinker after raid5 configuration was setup successfully.
>
>
On Wed, 21 Sep 2016, Binoy Jayan wrote:
> On 20 September 2016 at 19:49, Thomas Gleixner wrote:
> > You still fail to explain why this get_time() magic is required.
>
> Sorry, I missed to address this comment from you. From what I understand
> why the get_time() is needed is
On Wed, 21 Sep 2016, Binoy Jayan wrote:
> On 20 September 2016 at 19:49, Thomas Gleixner wrote:
> > You still fail to explain why this get_time() magic is required.
>
> Sorry, I missed to address this comment from you. From what I understand
> why the get_time() is needed is to get the more
Free memory mapping, if tegra20_init_timer is not successful.
Signed-off-by: Arvind Yadav
---
drivers/clocksource/tegra20_timer.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/clocksource/tegra20_timer.c
b/drivers/clocksource/tegra20_timer.c
index
Free memory mapping, if tegra20_init_timer is not successful.
Signed-off-by: Arvind Yadav
---
drivers/clocksource/tegra20_timer.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/clocksource/tegra20_timer.c
b/drivers/clocksource/tegra20_timer.c
index f960891..adcd7f4 100644
---
601 - 700 of 1514 matches
Mail list logo