On Tue, Nov 15, 2016 at 1:47 PM, John Stultz wrote:
> I suspect that some of these issues may be due to the phy driver
> on hikey being somewhat minimal:
> https://git.linaro.org/people/john.stultz/android-dev.git/plain/drivers/phy/phy-hi6220-usb.c?h=dev/hikey-mainline-WIP
Whoops. Sorry, that lin
Hey folks,
I wanted to send out these patches again for comment.
These three patches are basically required to get otg/gadget
mode working reliably on HiKey.
I admit they do feel a bit hackish, but without them we run
into a number of problems related to autosuspend and incorrect
connection stat
I've found when booting HiKey with the usb gadget cable attached
if I then try to connect via adb, I get an infinite spew of:
dwc2 f72c.usb: dwc2_hsotg_ep_sethalt(ep ffc0790ecb18 ep1out, 0)
dwc2 f72c.usb: dwc2_hsotg_ep_sethalt(ep ffc0790eca18 ep1in, 0)
It seems that the usb autosu
I had seen some odd behavior with HiKey's usb-gadget interface
that I finally seemed to have chased down. Basically every other
time I pluged in the OTG port, the gadget interface would
properly initialize. The other times, I'd get a big WARN_ON
in dwc2_hsotg_init_fifo() about the fifo_map not bein
On Mon, 14 Nov 2016, John Stultz wrote:
> On Mon, Nov 14, 2016 at 11:42 AM, Chris Metcalf wrote:
> > This bugfix was originally made in commit 35a4933a8959 ("time:
> > Avoid signed overflow in timekeeping_get_ns()"). When the code was
> > refactored in commit 6bd58f09e1d8 ("time: Add cycles to n
What's with people sending out replies without subjects?
On Tue, 15 Nov 2016 14:29:16 -0600 (CST)
Christoph Lameter wrote:
> > > There is a deadlock, Peter!!!
> >
> > Describe please? Also, have you tried disabling RT_RUNTIME_SHARE ?
> >
>
>
> The description was given earlier in the the
> The link state is retrieved by a command to the application processor that is
> running
> on the network card. Also the register to set the phy configuration is
> write-only, so
> it is not even possible to do the usual mdio bit-banging in the Phy read()
> and write()
> functions (however the
On 11/15/2016 3:33 PM, Borislav Petkov wrote:
> On Tue, Nov 15, 2016 at 03:22:45PM -0600, Tom Lendacky wrote:
>> Hmmm... I still need the ebx value from the CPUID instruction to
>> calculate the proper reduction in physical bits, so I'll still need
>> to make the CPUID call.
>
> if (c->ext
On Tue, Nov 15, 2016 at 1:53 PM, Thomas Gleixner wrote:
> On Mon, 14 Nov 2016, John Stultz wrote:
>
>> On Mon, Nov 14, 2016 at 11:42 AM, Chris Metcalf
>> wrote:
>> > This bugfix was originally made in commit 35a4933a8959 ("time:
>> > Avoid signed overflow in timekeeping_get_ns()"). When the cod
From: Philippe Reynes
Date: Sun, 13 Nov 2016 23:33:46 +0100
> The ethtool api {get|set}_settings is deprecated.
> We move this driver to new api {get|set}_link_ksettings.
>
> Signed-off-by: Philippe Reynes
Applied.
Hi Kees,
On Tue, Nov 15, 2016 at 1:36 PM, Kees Cook wrote:
> On Tue, Nov 15, 2016 at 11:55 AM, Joel Fernandes wrote:
>> Hi Kees,
>>
>> On Fri, Nov 11, 2016 at 2:21 PM, Kees Cook wrote:
>>> Hi Joel,
>>>
>>> I've reorganized a bunch of the logic here. Since pstore is going to need
>>> the init_pr
On Wed, Nov 09, 2016 at 09:50:09PM -0800, Bjorn Andersson wrote:
> This document defines the binding for a component that loads firmware
> and control the life cycle of the Qualcomm ADSP Hexagon core.
>
> Cc: Sarangdhar Joshi
> Signed-off-by: Bjorn Andersson
> ---
>
> Changes since v2:
> - Adde
NOT FOR MERGE!
Introduce a test version of a 'ti-opp-domain' driver that will use new
multiple regulator support introduced to the OPP core by Viresh [1].
Tested on v4.9-rc1 with that series applied. This is needed on TI
platforms like DRA7/AM57 in order to control both CPU regulator and
Adaptive
你好
有打算开发国外客户吗？
不参加展会也不上B2B平台，但照样可以开发优质海外客户。方法很简单，一天帮您做出效果
您只需要提供一个产品关键词，花费十分钟时间，就可以体验客户开发搜索软件带给您的惊喜。 咨询qq: 1286754208
Hi,
On 11/15/2016 12:56 PM, Stephen Boyd wrote:
On 11/15, Viresh Kumar wrote:
On 14-11-16, 18:13, Stephen Boyd wrote:
On 11/14, Rob Herring wrote:
On Fri, Nov 11, 2016 at 08:41:20AM +0530, Viresh Kumar wrote:
On 10-11-16, 14:51, Stephen Boyd wrote:
No. The supply names (and also clock names
On Tue, Nov 15, 2016 at 2:06 PM, Joel Fernandes wrote:
> Hi Kees,
>
> On Tue, Nov 15, 2016 at 1:36 PM, Kees Cook wrote:
>> On Tue, Nov 15, 2016 at 11:55 AM, Joel Fernandes wrote:
>>> Hi Kees,
>>>
>>> On Fri, Nov 11, 2016 at 2:21 PM, Kees Cook wrote:
Hi Joel,
I've reorganized a bu
On Fri, Nov 11, 2016 at 08:02:04PM +0100, H. Nikolaus Schaller wrote:
> Signed-off-by: H. Nikolaus Schaller
> ---
> Documentation/devicetree/bindings/input/{ => touchscreen}/ads7846.txt | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename Documentation/devicetree/bindings/input/{ => t
Hi all,
Fetching the amlogic tree
(git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git#for-next)
produces this error:
fatal: Couldn't find remote ref refs/heads/for-next
I will continue to use te previously fetched version of this tree.
--
Cheers,
Stephen Rothwell
On Tue, 15 Nov 2016 20:59:54 +0530
Kirti Wankhede wrote:
> Added blocking notifier to IOMMU TYPE1 driver to notify vendor drivers
> about DMA_UNMAP.
> Exported two APIs vfio_register_notifier() and vfio_unregister_notifier().
> Notifier should be registered, if external user wants to use
> vfio_p
On Sat, Nov 12, 2016 at 02:46:39PM +0800, Chen-Yu Tsai wrote:
> The internal codec on A23/A33/H3 is split into 2 parts. The
> analog path controls are routed through an embedded custom register
> bus accessed through the PRCM block.
>
> The SoCs share a common set of inputs, outputs, and audio pat
On Sat, Nov 12, 2016 at 02:46:42PM +0800, Chen-Yu Tsai wrote:
> The codec in the A23 is similar to the one found on the A31. One key
> difference is the analog path controls are routed through the PRCM
> block. This is supported by the sun8i-codec-analog driver, and tied
> into this codec driver wi
On Sat, Nov 12, 2016 at 02:46:46PM +0800, Chen-Yu Tsai wrote:
> The codec on the H3 is similar to the one found on the A31. One key
> difference is the analog path controls are routed through the PRCM
> block. This is supported by the sun8i-codec-analog driver, and tied
> into this codec driver wit
Hi Jens,
On Thu, Nov 10, 2016 at 10:00:37AM -0700, Jens Axboe wrote:
> Hi,
>
> We ran into a funky issue, where someone doing 256K buffered reads saw
> 128K requests at the device level. Turns out it is read-ahead capping
> the request size, since we use 128K as the default setting. This doesn't
On Wed, Nov 9, 2016 at 9:06 AM, Denys Vlasenko wrote:
> On 32-bit powerpc the ELF PLT sections of binaries (built with --bss-plt,
> or with a toolchain which defaults to it) look like this:
>
> [17] .sbss NOBITS 0002aff8 01aff8 14 00 WA 0 0
> 4
> [18] .plt
Hi Michael,
[auto build test ERROR on char-misc/char-misc-testing]
[also build test ERROR on v4.9-rc5]
[cannot apply to next-20161115]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Michael
On 15.11.2016 22:59, Andrew Lunn wrote:
>> The link state is retrieved by a command to the application processor that
>> is running
>> on the network card. Also the register to set the phy configuration is
>> write-only, so
>> it is not even possible to do the usual mdio bit-banging in the Phy r
On Tue, Nov 15, 2016 at 6:05 PM, Doug Smythies wrote:
> On 2016.11.13 16:08 Rafael J. Wysocki wrote:
>
>> Rebased on top of my linux-next branch, which in turn is based on 4.9-rc5
>> now.
>>
>> I'm running this on my IVB laptop w/ the schedutil governor, no problems so
>> far (fingers crossed).
>
On Mon, Nov 14, 2016 at 09:39:38PM -0800, Guenter Roeck wrote:
> F54 diagnostics report functions provide data based on the number of
> enabled rx and tx electrodes, which is not identical to the number of
> electrodes reported with F54:Query0 and F54:Query1. Those values report
> the number of sup
On Mon, Nov 14, 2016 at 09:39:37PM -0800, Guenter Roeck wrote:
> Sensor tuning support is needed to determine the number of enabled
> tx and rx electrodes for use in F54 functions.
>
> The number of enabled electrodes is not identical to the total number
> of electrodes as reported with F55:Query0
This option was added in 6a89a314ab107a12af08c71420c19a37a30fc2d3 to allow use
of the devm_gpio_* functions without CONFIG_GPIOLIB. However, only a few months
later in b69ac52449c658b7ac40034dc3c5f5f4a71a723d, CONFIG_GPIOLIB, was added
as a dependency, defeating the original purpose of this option.
On 11/15/2016 02:34 PM, Lino Sanfilippo wrote:
> On 15.11.2016 22:59, Andrew Lunn wrote:
>>> The link state is retrieved by a command to the application processor that
>>> is running
>>> on the network card. Also the register to set the phy configuration is
>>> write-only, so
>>> it is not even
On 11/15/2016 03:27 PM, Johannes Weiner wrote:
Hi Jens,
On Thu, Nov 10, 2016 at 10:00:37AM -0700, Jens Axboe wrote:
Hi,
We ran into a funky issue, where someone doing 256K buffered reads saw
128K requests at the device level. Turns out it is read-ahead capping
the request size, since we use 12
Per the original author, the proposed document was never deemed
necessary, and the important bits got merged into completion.txt. Let's
just stop confusing readers by pointing at a nonexistent doc.
Signed-off-by: Brian Norris
---
On Wed, Oct 26, 2016 at 10:11:26AM +, Nicholas Mc Guire wrote:
On Wed, 2016-11-16 at 05:20 +0800, kernel test robot wrote:
> FYI, we noticed the following commit:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 34fad54c2537f7c99d07375e50cb30aa3c23bd83 ("net: __skb_flow_dissect()
> must cap its return value")
>
> in tes
On Tue, 15 Nov 2016, Christoph Hellwig wrote:
> Adjust the exit condition for assigning the affinity vectors to take the
> pre_vectors into account. Otherwise the last vector will get a cpu mask
> for all CPUs by accidentally hitting the post_vectors case.
>
> Signed-off-by: Christoph Hellwig
>
On 15.11.2016 23:39, Florian Fainelli wrote:
> On 11/15/2016 02:34 PM, Lino Sanfilippo wrote:
>> On 15.11.2016 22:59, Andrew Lunn wrote:
The link state is retrieved by a command to the application processor that
is running
on the network card. Also the register to set the phy confi
Hi Pavel,
On Tue, Nov 15, 2016 at 11:54:25AM +0100, Pavel Machek wrote:
> Hi!
>
> > On Tue, Nov 01, 2016 at 12:54:08AM +0200, Sakari Ailus wrote:
> > > > > Thanks, this answered half of my questions already. ;-)
> > > > :-).
> > > >
> > > > I'll have to go through the patches, et8ek8 driver is p
This change allows user to provide hints to P-State selection algorithm
to be more more performance centric or more energy centric.
Even if this change only impacts intel_pstate driver, this change is
submitted as RFC to check if we need a generic method in cpufreq to
support such configuration.
It is possible to provide hints to the HWP algorithms in the processor
to be more performance centric to more energy centric.
The scope of these settings is per logical processor, which means that
each of the logical processors in the package can be programmed with a
different value. One of the us
> > + val = MII_BMCR << 16 | SLIC_PCR_AUTONEG |
> > +SLIC_PCR_AUTONEG_RST;
> > + slic_write(sdev, SLIC_REG_WPHY, val);
> Thats essentially what I meant by setting a flag in the irq handler. The mdio
> function
From: Christian Lamparter
This patch adds support for the "amcc,usb-otg" device
which is found in the PowerPC Canyonlands' dts.
The device definition was added by:
commit c89b3458d8cc ("powerpc/44x: Add USB DWC DTS entry to Canyonlands
board")
but without any driver support as the dwc2 driver
debugfs_create_dir() and debugfs_create_file() returns NULL on error or
a pointer on success. They do not return the error value with ERR_PTR.
So we should not check the return with IS_ERR_OR_NULL, instead we
should just check for NULL.
Signed-off-by: Sudip Mukherjee
---
drivers/mtd/nand/nandsim
Hi Linus,
After merging the pinctrl tree, today's linux-next build
(arm_multi_v7_defconfig) produced these warnings:
drivers/pinctrl/sunxi/pinctrl-sunxi.c: In function 'sunxi_pinctrl_init':
drivers/pinctrl/sunxi/pinctrl-sunxi.c:1191:8: warning: 'best_div' may be used
uninitialized in this functi
On 16.11.2016 00:03, Andrew Lunn wrote:
>> > + val = MII_BMCR << 16 | SLIC_PCR_AUTONEG |
>> > + SLIC_PCR_AUTONEG_RST;
>> > + slic_write(sdev, SLIC_REG_WPHY, val);
>
>> Thats essentially what I meant by setting a fl
On Tue, Oct 18, 2016 at 6:23 PM, Namhyung Kim wrote:
> When update_ms is set, pstore_get_records() will be called when there's
> a new entry. But unlink can be called at the same time and might
> contend with the open-read-close loop. Depending on the implementation
> of platform driver, it may
On Tue, Oct 18, 2016 at 6:23 PM, Namhyung Kim wrote:
> Maybe I'm missing something, but I don't know why it needs to copy the
> input buffer to psinfo->buf and then write. Instead we can write the
> input buffer directly. The only implementation that supports console
> message (i.e. ramoops) alr
On Thu, Nov 3, 2016 at 8:49 AM, Kees Cook wrote:
> On Thu, Nov 3, 2016 at 9:30 AM, Lafcadio Wluiki wrote:
>> (Third, rebased submission, since first two submissions yielded no replies.)
>
> Hm, I didn't see this series before, for some reason.
>
>> Previously, the hidepid parameter was checked by
On Tue, 15 Nov 2016 17:07:25 +0100 Dmitry Vyukov wrote:
> Gcc revision 241896 implements use-after-scope detection.
> Will be available in gcc 7. Support it in KASAN.
>
> Gcc emits 2 new callbacks to poison/unpoison large stack
> objects when they go in/out of scope.
> Implement the callbacks an
On 11/16/2016 12:09 AM, Sudip Mukherjee wrote:
> debugfs_create_dir() and debugfs_create_file() returns NULL on error or
> a pointer on success. They do not return the error value with ERR_PTR.
> So we should not check the return with IS_ERR_OR_NULL, instead we
> should just check for NULL.
>
> Si
On 11/15/2016 03:17 AM, Benjamin Gaignard wrote:
> version 2:
> - rebased on kernel 4.9-rc5
> - change heap bindings to use definitions of
> drivers/staging/android/ion/devicetree.txt
>
> version 1:
> - initial patch
>
> It is more or less a copy of Hisilicon driver but with a heap definition
>
Andrew,
It seems like there are no objections to this patch series so far.
Can you help us get this patch series to be code reviewed in more
depth so it can be considered for inclusion to 4.10?
Will appreciate if Mel, Johannes, Rik or others can take a look.
We appreciate feedback about this pa
Add new functions that free unused swap slots in batches without
the need to reacquire swap info lock. This improves scalability
and reduce lock contention.
Signed-off-by: Tim Chen
Co-developed-by: "Huang, Ying"
---
include/linux/swap.h | 1 +
mm/swapfile.c| 155 +
Currently, the swap slots are allocated one page at a time,
causing contention to the swap_info lock protecting the swap partition
on every page being swapped.
This patch adds new functions get_swap_pages and scan_swap_map_slots
to request multiple swap slots at once. This will reduces the lock
co
Initialize swap slots cache and enable it on swap on.
Drain all swap slots on swap off.
Signed-off-by: Tim Chen
---
mm/swapfile.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/mm/swapfile.c b/mm/swapfile.c
index 0bd105d..9cbdbfc 100644
--- a/mm/swapfile.c
+++ b/mm/swapfile.c
@@ -218
From: "Huang, Ying"
swap_info_get() is used not only in swap free code path but also in
page_swapcount(), etc. So the original kernel message in
swap_info_get() is not correct now. Fix it via replacing "swap_free" to
"swap_info_get" in the message.
Signed-off-by: "Huang, Ying"
Signed-off-by:
From: "Huang, Ying"
This patch is to reduce the lock contention of swap_info_struct->lock
via using a more fine grained lock in swap_cluster_info for some swap
operations. swap_info_struct->lock is heavily contended if multiple
processes reclaim pages simultaneously. Because there is only one l
We add per cpu caches for swap slots that can be allocated and freed
quickly without the need to touch the swap info lock.
Two separate caches are maintained for swap slots allocated and
swap slots returned. This is to allow the swap slots to be returned
to the global pool in a batch so they will
From: "Huang, Ying"
The patch is to improve the scalability of the swap out/in via using
fine grained locks for the swap cache. In current kernel, one address
space will be used for each swap device. And in the common
configuration, the number of the swap device is very small (one is
typical).
We can avoid needlessly allocating page for swap slots that
are not used by anyone. No pages have to be read in for
these slots.
Signed-off-by: Tim Chen
Co-developed-by: "Huang, Ying"
---
include/linux/swap.h | 6 ++
mm/swap_state.c | 4
mm/swapfile.c| 47 +++
Kees Cook writes:
> On Tue, Nov 15, 2016 at 2:57 AM, Michael Ellerman wrote:
>> POISON_POINTER_DELTA is defined in poison.h, and is intended to be used
>> to shift poison values so that they don't alias userspace.
>>
>> We should add it to ZERO_SIZE_PTR so that attackers can't use
>> ZERO_SIZE_P
On 11/15, Ard Biesheuvel wrote:
> On 15 November 2016 at 19:18, Stephen Boyd wrote:
> > On 11/15, Ard Biesheuvel wrote:
> >> On 19 October 2016 at 00:42, Stephen Boyd wrote:
> >> >
> >> > +static unsigned char ideal_nop4_arm_le[4] = { 0x00, 0x00, 0xa0, 0xe1 };
> >> > /* mov r0, r0 */
> >> > +sta
On Thu, 10 Nov 2016 14:11:57 -0800 Dan Williams
wrote:
> ZONE_DEVICE pages are mapped into a process via the filesystem-dax and
> device-dax mechanisms. There are also proposals to use ZONE_DEVICE
> pages for other usages outside of dax. Add statistics to smaps so
> applications can debug that
On Mon, Nov 14, 2016 at 10:56:54AM +0530, Sriram Dash wrote:
> Adds qoriq usb 3.0 phy driver support for LS1043A platform.
> Describes the qoriq usb 2.0 phy driver binding, currently used
> for LS1043A platform.
>
> Signed-off-by: Sriram Dash
> ---
> .../devicetree/bindings/phy/phy-qoriq-usb3.tx
On Tue, Nov 15, 2016 at 3:50 PM, Michael Ellerman wrote:
> Kees Cook writes:
>
>> On Tue, Nov 15, 2016 at 2:57 AM, Michael Ellerman
>> wrote:
>>> POISON_POINTER_DELTA is defined in poison.h, and is intended to be used
>>> to shift poison values so that they don't alias userspace.
>>>
>>> We sho
On 11/15/2016 10:35 AM, Catalin Marinas wrote:
> On Mon, Nov 14, 2016 at 10:41:29AM -0800, Laura Abbott wrote:
>> On 11/14/2016 10:19 AM, Catalin Marinas wrote:
>>> On Thu, Nov 03, 2016 at 03:51:07PM +, Mark Rutland wrote:
On Wed, Nov 02, 2016 at 05:56:42PM -0600, Laura Abbott wrote:
>
Fix RK3368_CLKSEL_CON to RK3399_CLKSEL_CON for rk3399 clock
driver.
Signed-off-by: Jianqun Xu
---
drivers/clk/rockchip/clk-rk3399.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/clk/rockchip/clk-rk3399.c
b/drivers/clk/rockchip/clk-rk3399.c
index 2c7cba7..2bde6c
Reference from drm_dp_aux description (about transfer):
Upon success, the implementation should return the number of payload bytes
that were transferred, or a negative error-code on failure. Helpers
propagate errors from the .transfer() function, with the exception of
the -EBUSY error, which causes
On Mon, Nov 14, 2016 at 10:44:11AM +0100, Neil Armstrong wrote:
> Following the Amlogic Linux kernel, it seem the only differences
> between the GXL and GXM SoCs are the CPU Clusters.
>
> Simply add a meson-gxm dtsi and reproduce the P23x to Q20x boards
> dts files since the S905D and S912 SoCs sh
On 11/10/2016 02:11 PM, Dan Williams wrote:
> @@ -774,6 +778,8 @@ static int show_smap(struct seq_file *m, void *v, int
> is_pid)
> "ShmemPmdMapped: %8lu kB\n"
> "Shared_Hugetlb: %8lu kB\n"
> "Private_Hugetlb: %7lu kB\n"
> +"Device
There is a disagreement between drivers/tty/vt/keyboard.c and
drivers/input/input-leds.c with regard to what is a Scroll Lock LED
trigger name: input calls it "kbd-scrolllock", but vt calls it
"kbd-scrollock" (two l's).
This prevents Scroll Lock LED trigger from binding to this LED by default.
Sin
Hi,
At present I am using the uevent in the userspace to infer
the Presence of a port on the remote end through the
appearance of usbc*-partner.
Userspace uses this info to decide on when to show a USB
notification on the screen and what should be the options
provided in the dialog.
I was assumi
Fix RK3368_* to RK3399_* for rk3399 clk_test clock.
Signed-off-by: Jianqun Xu
---
drivers/clk/rockchip/clk-rk3399.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/clk/rockchip/clk-rk3399.c
b/drivers/clk/rockchip/clk-rk3399.c
index 2c7cba7..ccbf558b 100644
--- a/
On Wed, Aug 17, 2016 at 1:00 PM, Bjorn Helgaas wrote:
> From: Joao Pinto
>
> Add support for the new iATU Unroll mechanism that will be used from Core
> version 4.80. The new Cores can support either iATU Unroll or the "old"
> iATU method, now called Legacy Mode. The driver is perfectly capable
Hi Kees,
After merging the pstore tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from include/linux/rcupdate.h:38:0,
from include/linux/idr.h:18,
from include/linux/kernfs.h:14,
from include/linux/sys
Maciej S. Szmigiero, on Wed 16 Nov 2016 00:55:57 +0100, wrote:
> There is a disagreement between drivers/tty/vt/keyboard.c and
> drivers/input/input-leds.c with regard to what is a Scroll Lock LED
> trigger name: input calls it "kbd-scrolllock", but vt calls it
> "kbd-scrollock" (two l's).
> This p
Hi Tim,
On Tue, Nov 15, 2016 at 10:22 PM, Tim Harvey wrote:
> Bjorn / Joao,
>
> This patch (from commit a0601a47053714eecec726aea5ebcd829f817497) is
> causing a kernel regression in 4.9. I can no longer boot the kernel on
> boards that have a PCIe switch downstream from the IMX6 (ie many of
> th
On Thu, Sep 29, 2016 at 3:05 AM, Geliang Tang wrote:
> On Wed, Sep 28, 2016 at 12:45:13PM -0700, Kees Cook wrote:
>> On Wed, Sep 28, 2016 at 3:32 AM, Geliang Tang wrote:
>> > When the pdata is NULL, ramoops_probe() segfaults. So this patch adds
>> > a NULL check to it.
>>
>> While I don't mind th
On 15/11/16 21:57, Michael Ellerman wrote:
> POISON_POINTER_DELTA is defined in poison.h, and is intended to be used
> to shift poison values so that they don't alias userspace.
>
> We should add it to ZERO_SIZE_PTR so that attackers can't use
> ZERO_SIZE_PTR as a way to get a pointer to userspa
On Tue, Nov 15, 2016 at 4:27 PM, Stephen Rothwell wrote:
> Hi Kees,
>
> After merging the pstore tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from include/linux/rcupdate.h:38:0,
> from include/linux/idr.h:18,
>
Hi all,
After merging the net-next tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
kernel/bpf/bpf_lru_list.c: In function '__bpf_lru_list_rotate_inactive.isra.3':
kernel/bpf/bpf_lru_list.c:201:28: warning: 'next' may be used uninitialized in
this function [-Wmaybe-uni
On 2016/11/15 17:41, Heiko Stuebner wrote:
Am Montag, 14. November 2016, 20:04:52 CET schrieb Andy Yan:
From: Shawn Lin
Add the dt-bindings header for the rk1108, that gets shared
between the clock controller and the clock references in the dts.
Signed-off-by: Shawn Lin
Signed-off-by: Andy Y
On 2016/11/15 17:35, Heiko Stuebner wrote:
Hi Andy,
Am Montag, 14. November 2016, 20:03:01 CET schrieb Andy Yan:
From: Shawn Lin
This adds the dt-binding documentation for the clock and reset unit
found on Rockchip rk1108 SoCs.
Signed-off-by: Shawn Lin
Signed-off-by: Andy Yan
---
Changes
On Thu, Nov 10, 2016 at 9:10 PM, Nicolas Pitre wrote:
> Some embedded systems have no use for them. This removes about
> 25KB from the kernel binary size when configured out.
>
> Corresponding syscalls are routed to a stub logging the attempt to
> use those syscalls which should be enough of a cl
On Tue, Nov 15, 2016 at 4:15 PM, Dave Hansen wrote:
> On 11/10/2016 02:11 PM, Dan Williams wrote:
>> @@ -774,6 +778,8 @@ static int show_smap(struct seq_file *m, void *v, int
>> is_pid)
>> "ShmemPmdMapped: %8lu kB\n"
>> "Shared_Hugetlb: %8lu kB\n"
>>
On Wed, Nov 9, 2016 at 3:19 PM, Lorenzo Pieralisi
wrote:
> On DT based systems, the of_dma_configure() API implements DMA
> configuration for a given device. On ACPI systems an API equivalent to
> of_dma_configure() is missing which implies that it is currently not
> possible to set-up DMA operati
On Wed, Nov 16, 2016 at 11:36:47AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the net-next tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> kernel/bpf/bpf_lru_list.c: In function
> '__bpf_lru_list_rotate_inactive.isra.3':
> kernel/bpf/bpf_lru_list.c
From: Giuseppe Cavallaro
Date: Mon, 14 Nov 2016 09:27:27 +0100
> This subset of patches aim to fix the PTP support
> for the stmmac and especially for 4.x chip series.
> While setting PTP on an ST box with 4.00a Ethernet
> core, the kernel panics due to a broken settings
> of the descriptors. The
On Wed, Nov 9, 2016 at 3:19 PM, Lorenzo Pieralisi
wrote:
> DT based systems have a generic kernel API to configure IOMMUs
> for devices (ie of_iommu_configure()).
>
> On ARM based ACPI systems, the of_iommu_configure() equivalent can
> be implemented atop ACPI IORT kernel API, with the correspondi
On Sat, Nov 12, 2016 at 09:02:24PM -0500, David Miller wrote:
> From: Kast Bernd
> Date: Fri, 4 Nov 2016 00:33:06 +0100
>
> > This patch adds a module parameter in order to activate ASPM. By that
> > the CPU can enter deep sleep modes (PC6) and power consumption can be
> > reduced (for example fr
On Tue, Nov 15, 2016 at 2:03 PM, John Stultz wrote:
> On Tue, Nov 15, 2016 at 1:53 PM, Thomas Gleixner wrote:
>> On Mon, 14 Nov 2016, John Stultz wrote:
>>
>>> On Mon, Nov 14, 2016 at 11:42 AM, Chris Metcalf
>>> wrote:
>>> > This bugfix was originally made in commit 35a4933a8959 ("time:
>>> > A
Vicente Jiménez wrote:
> I agree that both patches try to solve the same problem in a very similar way.
> Florian Westphal's patch do two more things:
> 1- add warning with pr_warn_ratelimited. I like this idea. I also
> though about adding some message but I have no kernel experience and I
> pref
Add SCM DT bindings for Qualcomm's MSM8996 platform.
Acked-by: Rob Herring
Signed-off-by: Sarangdhar Joshi
---
Documentation/devicetree/bindings/firmware/qcom,scm.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/firmware/qcom,scm.txt
b/Documentation/d
On earlier chiptsets (APQ8064, MSM8660, MSM8690, MSM8916,
APQ8084, MSM8974) crypto operations of TZ were depends on crypto
clocks controlled by users/clients. However on MSM8996 crypto clocks
control is handled internally in TZ itself. The current series of
patches handle this clock dependency in S
When devm_clk_get fails for core clock, the failure was ignored
and the core_clk was explicitly set to NULL so that other
remaining clocks can be queried. However, now that we have a
cleaner way of expressing the clock dependency, return failure
when devm_clk_get fails for core clock.
Signed-off-b
Core, iface and bus clocks are not required to be voted from SCM
driver for some of the Qualcomm chipsets. Remove dependency on
these clocks from driver.
Suggested-by: Bjorn Andersson
Signed-off-by: Sarangdhar Joshi
---
drivers/firmware/qcom_scm.c | 49 ++
Hi Dave,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.9-rc5]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Dave-Gerlach/WIP-Test-OPP-multi-regulator-support-with-ti-opp
On Mon, Nov 7, 2016 at 8:48 PM, John Garry wrote:
> From: Xiang Chen
>
> Currently slots are allocated from queues in a round-robin fashion.
> This causes a problem for internal commands in device mode. For this
> mode, we should ensure that the internal abort command is the last
> command seen i
On Mon, Nov 7, 2016 at 8:48 PM, John Garry wrote:
> From: Xiang Chen
>
> When we form a wideport, we should use hardware PHY port_id instead
> of sas_phy->id.
>
> Signed-off-by: Xiang Chen
> Signed-off-by: John Garry
Reviewed-by: Zhangfei Gao
On Mon, Nov 7, 2016 at 8:48 PM, John Garry wrote:
> From: Xiang Chen
>
> Delete repeated configuration items for hisi_sas_device() when
> we free a device. These items are now only set in
> hisi_sas_dev_gone().
>
> Signed-off-by: Xiang Chen
> Signed-off-by: John Garry
Reviewed-by: Zhangfei Gao
On Mon, Nov 7, 2016 at 8:48 PM, John Garry wrote:
> Sometimes the value of hisi_sas_device.running_req
> would go negative unless we have the check for
> running_req >= 0 before trying to decrement.
>
> This is because using running_req is not thread-safe.
>
> As such, the value for running_req ma
801 - 900 of 939 matches
Mail list logo
