On Fri, May 16, 2014 at 02:22:19PM +0200, Peter Zijlstra wrote:
> On Tue, May 13, 2014 at 12:48:12PM -0400, Don Zickus wrote:
> > From: Peter Zijlstra
> >
> > The mmap2 interface was missing the protection and flags bits needed to
> > accurately determine if a mmap memory area was shared or
Commit-ID: 59b47ddc0b4d7ea8a625512e802832730c1feeb4
Gitweb: http://git.kernel.org/tip/59b47ddc0b4d7ea8a625512e802832730c1feeb4
Author: Thomas Gleixner
AuthorDate: Wed, 7 May 2014 15:44:08 +
Committer: Thomas Gleixner
CommitDate: Fri, 16 May 2014 14:05:19 +0200
x86: htirq: Use
Commit-ID: 499c2b75e9c695b57faaf6a63fde391ff9e523a3
Gitweb: http://git.kernel.org/tip/499c2b75e9c695b57faaf6a63fde391ff9e523a3
Author: Thomas Gleixner
AuthorDate: Wed, 7 May 2014 15:44:07 +
Committer: Thomas Gleixner
CommitDate: Fri, 16 May 2014 14:05:18 +0200
x86: hpet: Use
Commit-ID: 465665f78a7f47d46d7fe18195f3548b4911547f
Gitweb: http://git.kernel.org/tip/465665f78a7f47d46d7fe18195f3548b4911547f
Author: Thomas Gleixner
AuthorDate: Wed, 7 May 2014 15:44:05 +
Committer: Thomas Gleixner
CommitDate: Fri, 16 May 2014 14:05:18 +0200
mips: Kill pointless
On Fri, May 16, 2014 at 01:47:57PM +0200, Jiri Olsa wrote:
> On Tue, May 13, 2014 at 12:48:17PM -0400, Don Zickus wrote:
> > In perf's 'mem-mode', one can get access to a whole bunch of details
> > specific to a
> > particular sample instruction. A bunch of those details relate to the data
> >
On Fri, May 16, 2014 at 01:25:14PM +0200, Jiri Olsa wrote:
> On Tue, May 13, 2014 at 12:48:13PM -0400, Don Zickus wrote:
>
> SNIP
>
> > - /*
> > -* Anon maps don't have the execname.
> > -*/
> > - if (n < 4)
> > + n = sscanf(bf,
Hi Sunil,
On Fri, May 16, 2014 at 11:33:04AM +0100, Sunil Kovvuri wrote:
> Hi Liviu,
>
> I am using your ARM64 PCIe patches to write a PCIe host controller
> driver for our SOC. I am facing an issue with SR-IOV capable device.
>
> Consider an PCI Express endpoint connected to a PCI Express
>
On Fri, May 16, 2014 at 12:13:32AM -0400, Rik van Riel wrote:
> Affine wakeups have the potential to interfere with NUMA placement.
> If a task wakes up too many other tasks, affine wakeups will get
> disabled.
>
> However, regardless of how many other tasks it wakes up, it gets
> re-enabled once
On Thu, May 15, 2014 at 10:16:39AM -0500, Christoph Lameter wrote:
> On Thu, 15 May 2014, Vladimir Davydov wrote:
>
> > I admit that's far not perfect, because kfree is really a hot path,
> > where every byte of code matters, but unfortunately I don't see how we
> > can avoid this in case we want
On Fri, 16 May 2014, Richard Lee wrote:
> On Fri, May 16, 2014 at 1:28 AM, Nicolas Pitre
> wrote:
> > On Thu, 15 May 2014, Richard Lee wrote:
> >
> >> Static vm area boundary check:
> >>
> >> paddr1 --->| |
> >> | |
> >> |---| <-\---
On 05/16/2014 01:46 PM, ching wrote:
> Hi Tomas,
>
> Although in http://www.makelinux.net/ldd3/chp-7-sect-6, there said to flush
> the shared workqueue requires calling function
> flush_scheduled_work.
>
> But in kernel workqueue.c, there are comment of flush_scheduled_work said
> that
> "In
From: Heiko Stuebner
When no channel was found the driver currently always returns -ENODEV. This
hides the actual error which is available in ret from the kernel and disables
for example -EPROBE_DEFER handling.
Signed-off-by: Heiko Stuebner
---
drivers/power/generic-adc-battery.c | 4 +---
1
From: Heiko Stuebner
This reduces the amount of code spent on initialization and cleanup
of the properties memory and also simplifies the error handling a bit.
Signed-off-by: Heiko Stuebner
---
drivers/power/generic-adc-battery.c | 14 --
1 file changed, 4 insertions(+), 10
(I'm not subscribed to linux-kernel, pls copy me on the anwsers)
Hi there,
# uname -a
Linux zafu 3.14.4-1-ARCH #1 SMP PREEMPT Tue May 13 16:41:39 CEST 2014 x86_64
GNU/Linux
I've seen the same thing happen several times in the last couple of months (so
with said kernel version + at least 3.13)
On Thu, May 15, 2014 at 10:15:10AM -0500, Christoph Lameter wrote:
> On Thu, 15 May 2014, Vladimir Davydov wrote:
>
> > > That will significantly impact the fastpaths for alloc and free.
> > >
> > > Also a pretty significant change the logic of the fastpaths since they
> > > were not designed to
From: Roger Quadros
As clocks might be named differently on multiple platforms, use a generic
name in the driver and allow device tree node to specify the platform
specific clock name.
Reviewed-by: Felipe Balbi
Signed-off-by: Roger Quadros
Signed-off-by: Kishon Vijay Abraham I
---
From: Arnd Bergmann
If the license string doesn't match exactly, the module refuses to load.
Signed-off-by: Arnd Bergmann
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-exynos5250-sata.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Arnd Bergmann
All other phy drivers use 'select', while this one is
the only one to use 'depends on'. This is not a bug, just
slightly inconsistent, so let's change it to do things the
same way as everyone else.
We may also want to turn GENERIC_PHY into a silent option
that only ever gets
From: Antoine Ténart
The phys array is of size EXYNOS_MIPI_PHYS_NUM. Trying to access the
index EXYNOS_MIPI_PHYS_NUM should return an error.
Fixes: 069d2e26e9d6 "phy: Add driver for Exynos MIPI CSIS/DSIM DPHYs"
Signed-off-by: Antoine Ténart
Signed-off-by: Kishon Vijay Abraham I
---
From: Maxime Ripard
Move the phy initialization and variables declaration to the loop itself, since
it is where it really belongs. Also remove all the temporary variables, we can
use the structure members directly.
Signed-off-by: Maxime Ripard
Reviewed-by: Hans de Goede
Signed-off-by: Kishon
From: Vivek Gautam
Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
The new driver uses the generic PHY framework and will interact
with DWC3 controller present on Exynos5 series of SoCs.
Also, created a new header file in linux/mfd/syscon/ for
Exynos5 SoCs and put the required
From: Vivek Gautam
Add necessary binding documentation for USB 3.0 DRD PHY present on
Exynos5 SoC series.
Signed-off-by: Vivek Gautam
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/phy/samsung-phy.txt| 47
1 file changed, 47 insertions(+)
From: Vivek Gautam
Adding support to enable/disable VBUS controlled by a
regulator, to enable vbus supply on the port.
Signed-off-by: Vivek Gautam
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-exynos5-usbdrd.c | 32
1 file changed, 32
From: Maxime Ripard
The USB phy controller in the A31 differs mostly from the older controllers
because it has a clock dedicated for each phy, while the older ones were having
a single clock for all the phys.
Signed-off-by: Maxime Ripard
Reviewed-by: Hans de Goede
Signed-off-by: Kishon Vijay
From: Roger Quadros
Add "wkupclk" and "refclk" information to DT binding information.
Reviewed-by: Felipe Balbi
Signed-off-by: Roger Quadros
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/phy/ti-phy.txt |7 +++
1 file changed, 7 insertions(+)
diff --git
From: Maxime Ripard
Document the freshly introduced compatible for the USB phy in use in the
Allwinner A31 SoC.
Signed-off-by: Maxime Ripard
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/phy/sun4i-usb-phy.txt | 23 +++-
1 file changed, 17
Hi Greg,
Here's the pull request for 3.16. It contains mostly bug fixes and cleanup
apart from one new driver for exynos5 usb3 PHY. Please consider merging them
to your usb tree.
Let me know if I have to change anything.
Cheers
Kishon
The following changes since commit
On 04/29/2014 04:18 AM, Xiubo Li wrote:
The Freescale FlexTimer Module time reference is a 16-bit counter
that can be used as an unsigned or signed increase counter.
CNTIN defines the starting value of the count and MOD defines the
final value of the count. The value of CNTIN is loaded into the
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Kazuya Mio
commit 4adb6ab3e0fa71363a5ef229544b2d17de6600d7 upstream.
When we try to get 2^32-1 block of the file which has the extent
(ee_block=2^32-2, ee_len=1) with FIBMAP ioctl, it causes
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Tristan Bruns
commit 72b3007951010ce1bbf950e23b19d9839fa905a5 upstream.
Signed-off-by: Tristan Bruns
Signed-off-by: Johan Hovold
Signed-off-by: Greg Kroah-Hartman
Signed-off-by: Ben
On Fri, May 16, 2014 at 11:29:58AM +0200, Paul Bolle wrote:
> Support for ARM710 CPUs was removed in v3.5. But a few lines of ARM710
> specific assembler code were left in the tree. Remove these too.
>
> Signed-off-by: Paul Bolle
> ---
> This minor cleanup was suggested by Arnd. This patch is
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
commit 3758cf7e14b753838fe754ede3862af10b35fdac upstream.
...otherwise the logic in the timeout handling doesn't work correctly.
Spotted-by: Trond Myklebust
Signed-off-by: Jeff
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Larry Finger
commit f764cd68d9036498f08fe8834deb6a367b5c2542 upstream.
Zero-initializing ether_type masked that the ether type would never be
obtained for 8021x packets and the comparison
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dan Williams
commit 8a4aeec8d2d6a3edeffbdfae451cdf05cbf0fefd upstream.
The AHCI spec allows implementations to issue commands in tag order
rather than FIFO order:
5.3.2.12 P:SelectCmd
This is the start of the stable review cycle for the 3.2.59 release.
There are 34 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun May 18 12:47:20 UTC 2014.
Anything
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Julius Werner
commit 1f81b6d22a5980955b01e08cf27fb745dc9b686f upstream.
We have observed a rare cycle state desync bug after Set TR Dequeue
Pointer commands on Intel LynxPoint xHCs (resulting
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 10164c2ad6d2c16809f6c09e278f946e47801b3a upstream.
Fix driver new_id sysfs-attribute removal deadlock by making sure to
not hold any locks that the attribute operations
On 05/15/2014 04:57 PM, Sören Brinkmann wrote:
> ping? Any comments?
>
> Thanks,
> Sören
>
> On Fri, 2014-05-02 at 02:07PM -0700, Soren Brinkmann wrote:
>> To silence the warning
>> cpufreq_cpu0: failed to get cpu0 regulator: -19
>> from the cpufreq driver regarding a missing
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Michele Baldessari
commit efe26e16b1d93ac0085e69178cc18811629e8fc5 upstream.
Custom VID/PIDs for Brainboxes cards as reported in
https://bugzilla.redhat.com/show_bug.cgi?id=1071914
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 1b17844b29ae042576bea588164f2f1e9590a8bc upstream.
fixup_user_fault() is used by the futex code when the direct user access
fails, and the futex code wants it to either
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Matthew Daley
commit ef87dbe7614341c2e7bfe8d32fcb7028cc97442c upstream.
Always clear out these floppy_raw_cmd struct members after copying the
entire structure from userspace so that the
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Matthew Wilcox
commit 9503c67c93ed0b95ba62d12d1fd09da6245dbdd6 upstream.
ext4_end_bio() currently throws away the error that it receives. Chances
are this is part of a spate of errors, one of
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Michael Ulbricht
commit 895d240d1db0b2736d779200788e4c4aea28a0c6 upstream.
By specifying NO_UNION_NORMAL the ACM driver does only use the first two
USB interfaces (modem data & control). The
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit 46a2986ebbe18757c2d8c352f8fb6e0f4f0754e3 upstream.
We expect that all the Haswell series will need such quirks, sigh.
The T431s seems to be T430 hardware in a T440s case,
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: David Cohen
commit 01bb59ebffdec314da8da66266edf29529372f9b upstream.
When CONFIG_PCI and CONFIG_PM are not selected, xhci.c gets this
warning:
drivers/usb/host/xhci.c:409:13: warning:
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit c4bedb77ec4cb42f37cae4cbfddda8283161f7c8 upstream.
Signed-off-by: Hans de Goede
Signed-off-by: Sarah Sharp
[bwh: Backported to 3.2: adjust context]
Signed-off-by: Ben
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Aaron Sanders
commit b16c02fbfb963fa2941b7517ebf1f8a21946775e upstream.
Add device ids to pl2303 for the Hewlett-Packard HP POS pole displays:
LD960: 03f0:0B39
LCM220: 03f0:3139
LCM960:
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Miao Xie
commit 1c70d8fb4dfa95bee491816b2a6767b5ca1080e7 upstream.
Currently, with inode cache enabled, we will reuse its inode id immediately
after unlinking file, we may hit something like
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit 34f972d6156fe9eea2ab7bb418c71f9d1d5c8e7b upstream.
A number of older CMOTech modems are based on Qualcomm
chips. The blacklisted interfaces are QMI/wwan.
Reported-by: Lars
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jani Nikula
commit 5017b2851373ee15c7035151853bb1448800cae2 upstream.
dmi_match() considers a substring match to be a successful match. This is
not always sufficient to distinguish between
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit dd6b48ecec2ea7d15f28d5e5474388681899a5e1 upstream.
Device interface layout:
0: ff/ff/ff - serial
1: ff/00/00 - serial AT+PPP
2: ff/ff/ff - QMI/wwan
3: 08/06/50 - storage
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 5509076d1b4485ce9fb07705fcbcd2695907ab5b upstream.
During firmware download the device expects memory addresses in
big-endian byte order. As the wIndex parameter which hold
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit 533b3994610f316e5cd61b56d0c4daa15c830f89 upstream.
Device interface layout:
0: ff/ff/ff - serial
1: ff/ff/ff - serial AT+PPP
2: 08/06/50 - storage
3: ff/ff/ff - serial
4:
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
Dmitry Semyonov reported that after upgrading from 3.2.54 to
3.2.57 the rtl8192ce driver will crash when its interface is brought
up. The oops message shows:
[ 1833.611397] BUG:
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Stefan Behrens
commit ff76b0565523319d7c1c0b51d5a5a8915d33efab upstream.
Due to an off-by-one error, it is possible to reproduce a bug
when the inode cache is used.
The same inode number is
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Chris Mason
commit c98235cb8584a72e95786e17d695a8e5fafcd766 upstream.
The mlx4 driver is triggering schedules while atomic inside
mlx4_en_netpoll:
spin_lock_irqsave(>lock, flags);
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Xiangyu Lu
commit 80bb3ef109ff40a7593d9481c17de9bbc4d7c0e2 upstream.
In big-endian systems, "%1" get the most significant part of the value, cause
the instruction to get the wrong result.
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Matthew Daley
commit 2145e15e0557a01b9195d1c7199a1b92cb9be81f upstream.
Do not leak kernel-only floppy_raw_cmd structure members to userspace.
This includes the linked-list pointer and the
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 2e01280d2801c72878cf3a7119eac30077b463d5 upstream.
This reverts commit 1ebca9dad5abe8b2ed4dbd186cd657fb47c1f321.
This device was erroneously added to the sierra driver
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Mizuma, Masayoshi"
commit 7848a4bf51b34f41fcc9bd77e837126d99ae84e3 upstream.
soft lockup in freeing gigantic hugepage fixed in commit 55f67141a892 "mm:
hugetlb: fix softlockup when a large
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jeff Layton
commit f1c6bb2cb8b81013e8979806f8e15e3d53efb96d upstream.
A fl->fl_break_time of 0 has a special meaning to the lease break code
that basically means "never break the lease". knfsd
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Peter Hurley
commit 4291086b1f081b869c6d79e5b7441633dc3ace00 upstream.
The tty atomic_write_lock does not provide an exclusion guarantee for
the tty driver if the termios settings are LECHO &
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Helge Deller
commit ab3e55b119c9653b19ea4edffb86f04db867ac98 upstream.
This bug was detected with the libio-epoll-perl debian package where the
test case IO-Ppoll-compat.t failed.
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Theodore Ts'o
commit 6e6358fc3c3c862bfe9a5bc029d3f8ce43dc9765 upstream.
We haven't taken i_mutex yet, so we need to use i_size_read().
Signed-off-by: "Theodore Ts'o"
Signed-off-by: Ben
3.2.59-rc1 review patch. If anyone has any objections, please let me know.
--
From: Daniele Palmas
commit d6de486bc22255779bd54b0fceb4c240962bf146 upstream.
option driver, added VID/PID for Telit UE910v2 modem
Signed-off-by: Daniele Palmas
Signed-off-by: Johan Hovold
On Mon, May 5, 2014 at 7:27 AM, Antoine Ténart
wrote:
> This series adds support for the Marvell Berlin pin-controller, allowing
> to configure the pin muxing from the device tree.
OK looking good!
I've applied patches 1,2,3,4 and 6 to the pin control tree.
Please carry patches 5 and 7 in the
Hi,
On Fri, May 16, 2014 at 11:50:13PM +0800, Zhuang Jin Can wrote:
> > On Fri, May 16, 2014 at 05:57:57AM +0800, Zhuang Jin Can wrote:
> > > In ISOC transfers, when free_slot points to the last TRB (i.e. Link
> > > TRB), and all queued requests meet Missed Interval Isoc error, busy_slot
> > >
Export of symbols statement must be placed right after the definition to meet
kernel coding style guidelines. This issue was reported by checkpatch.
A simplified version of the semantic patch that makes this change is as
follows (http://coccinelle.lip6.fr/):
//
@ r @ identifier f; @@
-
Since v2.6.34 there are two checks for CONFIG_SND_SOC_SMDK2443_WM9710.
But a Kconfig symbol SND_SOC_SMDK2443_WM9710 has never been part of the
tree. However, in v2.6.38 a symbol SND_SOC_SAMSUNG_SMDK2443_WM9710 was
added, so it seems these checks should be for its macro.
But the second check is a
On 05/16/2014 12:18 PM, Mika Westerberg wrote:
> In case of resolving power management or similar issues it might be useful
> to have these properties included in the debugfs output.
>
> Signed-off-by: Mika Westerberg
Looks good to me
Acked-by: Mathias Nyman
-Mathias
> ---
>
From: Thierry Reding
This commit introduces a generic device tree binding for IOMMU devices.
Only a very minimal subset is described here, but it is enough to cover
the requirements of both the Exynos System MMU and Tegra SMMU as
discussed here:
https://lkml.org/lkml/2014/4/27/346
More
It is no longer in use by the driver or board files.
Signed-off-by: Peter Ujfalusi
---
include/linux/platform_data/edma.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/platform_data/edma.h
b/include/linux/platform_data/edma.h
index 12f134b1493c..633e196ebdf2 100644
---
Hi,
Changes since v2:
- Comments from Sekhar and Arnd has been addressed best as I could.
- Use the CCCFG information in all cases instead of pdata provided information
- To achieve this I needed to do a bit more cleanup in this series
- In the documentation patch, retrain the old properties for
The pdata has been just allocated with devm_kzalloc() in
edma_setup_info_from_dt() and passed to this function.
Signed-off-by: Peter Ujfalusi
---
arch/arm/common/edma.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/arm/common/edma.c b/arch/arm/common/edma.c
index
On Tue, May 13, 2014 at 12:48:12PM -0400, Don Zickus wrote:
> From: Peter Zijlstra
>
> The mmap2 interface was missing the protection and flags bits needed to
> accurately determine if a mmap memory area was shared or private and
> if it was readable or not.
>
> [tweaked patch to compile and
There is no need to change the default TC -> Queue mapping. By default the
mapping is: TC0 -> Q0, TC1 -> Q1, etc.
Changing this has no benefits at all and all the board files are just setting
the same mapping back to the HW.
Signed-off-by: Peter Ujfalusi
---
arch/arm/common/edma.c | 28
The struct edma is allocated per CC bases so the member num_cc does not make
any sense. One CC is one CC, it does not have sub CCs.
Signed-off-by: Peter Ujfalusi
---
arch/arm/common/edma.c | 4
1 file changed, 4 deletions(-)
diff --git a/arch/arm/common/edma.c b/arch/arm/common/edma.c
>From CCCFG register of eDMA3 we can get all the needed information for the
driver about the IP:
Number of channels: NUM_DMACH
Number of regions: NUM_REGN
Number of slots (PaRAM sets): NUM_PAENTRY
Number of TC/EQ: NUM_EVQUE
The ti,edma-regions; ti,edma-slots and dma-channels in DT are
redundant
>From CCCFG register of eDMA3 we can get all the needed information for the
driver about the IP:
Number of channels: NUM_DMACH
Number of regions: NUM_REGN
Number of slots (PaRAM sets): NUM_PAENTRY
Number of TC/EQ: NUM_EVQUE
In case when booted with DT or the queue_priority_mapping is not provided
Hello.
On 16-05-2014 1:56, Rickard Strandqvist wrote:
There is otherwise a risk of a possible null pointer dereference.
Was largely found by using a static code analysis program called cppcheck.
Signed-off-by: Rickard Strandqvist
---
net/sunrpc/auth.c | 10 +++---
1 fil ändrad,
dma-channels, ti,edma-regions and ti,edma-slots no longer needed in DT since
the the same information is available in the IP's CCCFG register.
Signed-off-by: Peter Ujfalusi
---
arch/arm/boot/dts/am33xx.dtsi | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/arm/boot/dts/am33xx.dtsi
The following parameters are no longer needed by the edma driver since the
information can be obtained from the IP's CCCFG register:
n_channel, n_region, n_slot and n_tc.
Remove the n_cc as well since in this context it has no meaning. We have
separate edma_soc_info struct/eDMA3_CC instance so
To be consistent in the code that we take parameters from edma_cc[j] struct
and not randomly from info[j] as well.
Signed-off-by: Peter Ujfalusi
---
arch/arm/common/edma.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/common/edma.c b/arch/arm/common/edma.c
index
The following parameters are no longer needed by the edma driver since the
information can be obtained from the IP's CCCFG register:
n_channel, n_region, n_slot and n_tc.
Remove the initialization of n_cc as well since in this context it has no
meaning. We have separate edma_soc_info
dma-channels, ti,edma-regions and ti,edma-slots no longer needed in DT since
the the same information is available in the IP's CCCFG register.
Signed-off-by: Peter Ujfalusi
---
arch/arm/boot/dts/am4372.dtsi | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/arm/boot/dts/am4372.dtsi
It is ignored by the edma driver since we are just setting back the default
mapping of TC -> Queue.
Signed-off-by: Peter Ujfalusi
---
arch/arm/mach-davinci/devices-da8xx.c | 16
arch/arm/mach-davinci/dm355.c | 9 -
arch/arm/mach-davinci/dm365.c | 11
Instead of saving the for loop length, take the num_tc value from the pdata.
In case of DT boot set the n_tc to 3 as it is hardwired in edma_of_parse_dt()
This is a temporary state since upcoming patch(es) will change how we are
dealing with these parameters.
Signed-off-by: Peter Ujfalusi
---
On Fri, May 16, 2014 at 02:14:05PM +0200, Thomas Gleixner wrote:
> On Fri, 16 May 2014, Tejun Heo wrote:
> > On Fri, May 16, 2014 at 01:57:37PM +0200, Peter Zijlstra wrote:
> > > This of course leaves the question how the workqueue code manages to
> > > call set_cpu_allowed_ptr() on a cpu _before_
On Fri, 16 May 2014, Tejun Heo wrote:
> On Fri, May 16, 2014 at 01:57:37PM +0200, Peter Zijlstra wrote:
> > This of course leaves the question how the workqueue code manages to
> > call set_cpu_allowed_ptr() on a cpu _before_ its online.
> >
> > That too sounds fishy.. with the proposed patch the
Hello, Peter.
On Fri, May 16, 2014 at 01:57:37PM +0200, Peter Zijlstra wrote:
> This of course leaves the question how the workqueue code manages to
> call set_cpu_allowed_ptr() on a cpu _before_ its online.
>
> That too sounds fishy.. with the proposed patch the
> set_cpus_allowed_ptr() will
On 13.05.14 16:58, Michael Mueller wrote:
This patch enables cpu model support in kvm/s390 via the vm attribute
interface.
During KVM initialization, the host properties cpuid, IBC value and the
facility list are stored in the architecture specific cpu model structure.
During vcpu setup,
Hello,
Xiangliang Yu wrote:
: > Ben Hutchings already submitted a patch for this twice, which I cc'd you
: > on:
: >
: > http://marc.info/?t=13927720393
: >
: > will you ack it?
: I can't find this mail in my mail box.
any news with this patch? Will it be acked by you and
On Fri, May 16, 2014 at 02:10:47PM +0200, Rafael J. Wysocki wrote:
> On Thursday, May 15, 2014 06:28:46 PM Mika Westerberg wrote:
> > From: Jin Yao
> >
> > Now that the x86 dynamic IRQ allocation problem has been resolved with
> > commmit 62a08ae2a576 (genirq: x86: Ensure that dynamic irq
Before IMA appraisal was introduced, IMA was using own integrity cache
lock along with i_mutex. process_measurement and ima_file_free took
the iint->mutex first and then the i_mutex, while setxattr, chmod and
chown took the locks in reverse order. To resolve the potential deadlock,
i_mutex was
There are a number of checks for CONFIG_CPU_S3C2413. But there's no
Kconfig symbol CPU_S3C2413. That symbol is not needed, as CPU_S3C2412 is
documented to support both the S3C2412 and the S3C2413 SoCs.
Luckily, all these checks for CONFIG_CPU_S3C2413 are in places were we
also checks for
> -Original Message-
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of Joe Perches
> Sent: Friday, May 16, 2014 9:52 AM
> To: Ariel Elior; Dmitry Kravkov
> Cc: netdev; linux-kernel
> Subject: [PATCH] bnx2x: Convert return 0 to return rc
>
> These
On Fri, May 16, 2014 at 11:50:42AM +0800, Lai Jiangshan wrote:
> Hi, Peter and other scheduler Gurus:
>
> When I was trying to test wq-VS-hotplug, I always hit a problem in scheduler
> with the following WARNING:
>
> [ 74.765519] WARNING: CPU: 1 PID: 13 at arch/x86/kernel/smp.c:124
>
On 13.05.14 16:58, Michael Mueller wrote:
The patch introduces facilities and cpu_ids per virtual machine.
Different virtual machines may want to expose different facilities and
cpu ids to the guest, so let's make them per-vm instead of global.
In addition this patch renames all ocurrences of
On Tue, May 13, 2014 at 06:38:32PM +0200, Daniel Vetter wrote:
> On Tue, May 13, 2014 at 05:21:49PM +0200, Jörg Otte wrote:
> > 2014-05-13 15:22 GMT+02:00 Daniel Vetter :
> > > On Tue, May 13, 2014 at 12:38:41PM +0200, Daniel Vetter wrote:
> > >> On Tue, May 13, 2014 at 12:29 PM, Jörg Otte wrote:
On Thursday, May 15, 2014 06:28:46 PM Mika Westerberg wrote:
> From: Jin Yao
>
> Now that the x86 dynamic IRQ allocation problem has been resolved with
> commmit 62a08ae2a576 (genirq: x86: Ensure that dynamic irq allocation does
> not conflict), we can add back Baytrail-T ACPI ID to the pinctrl
501 - 600 of 1590 matches
Mail list logo
