There are multiple places where arrays or otherwise variable sized
buffer are allocated through V4L2 core code, including things like
controls, memory pages, staging buffers for ioctls and so on. Such
allocations can potentially require an order > 0 allocation from the
page allocator, which is not
clk_prepare_enable() can fail here and we must check its return value.
Signed-off-by: Arvind Yadav
---
drivers/i2c/busses/i2c-at91.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/i2c-at91.c b/drivers/i2c/busses/i2c-at91.c
index fabbb9e..2525cd9 10
On Tue, 30 May 2017, Sathyanarayanan Kuppuswamy Natarajan wrote:
> Hi All,
>
> On Tue, May 30, 2017 at 8:38 PM, Stephen Rothwell
> wrote:
> > Hi all,
> >
> > On Tue, 30 May 2017 09:53:06 +0100 Lee Jones wrote:
> >>
> >> Dear fellow Maintainers,
> >>
> >> Enjoy!
> >>
> >> The following changes
On Wed 31-05-17 14:30:33, kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> commit: beeeccca9bebcec386cc31c250cff8a06cf27034 ("btrfs: Use kvzalloc
> instead of kzalloc/vmalloc in alloc_bitmap")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
I have
Hi Thomas,
On 05/30/2017 03:21 PM, Thomas Gleixner wrote:
> While trying to address the longstanding FIXME in the posix timer code
> related to ignored signals, I stumbled over the following issue:
>
> I blocked the signal of the timer, then installed the SIG_IGN handler,
> created and started th
On Wed, 31 May 2017, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 30 May 2017 09:53:06 +0100 Lee Jones wrote:
> >
> > Dear fellow Maintainers,
> >
> > Enjoy!
> >
> > The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
> >
> > Linux 4.12-rc1 (2017-05-13 13:19:49 -07
>-Original Message-
>From: Zhenyu Wang [mailto:zhen...@linux.intel.com]
>Sent: Wednesday, May 31, 2017 1:12 PM
>To: Chen, Xiaoguang
>Cc: alex.william...@redhat.com; kra...@redhat.com; ch...@chris-wilson.co.uk;
>intel-...@lists.freedesktop.org; linux-kernel@vger.kernel.org;
>zhen...@linux
>-Original Message-
>From: Zhenyu Wang [mailto:zhen...@linux.intel.com]
>Sent: Wednesday, May 31, 2017 2:30 PM
>To: Chen, Xiaoguang
>Cc: Tian, Kevin ; intel-...@lists.freedesktop.org; linux-
>ker...@vger.kernel.org; ch...@chris-wilson.co.uk; alex.william...@redhat.com;
>kra...@redhat.com
On Tue, May 30, 2017 at 8:03 PM, Matt Mullins wrote:
> On Tue, May 30, 2017 at 02:54:21PM +0200, Radim Krčmář wrote:
>> 2017-05-29 15:24+0200, Gioh Kim:
>> > If so, why type is checked when setting segment registers?
>>
>> No idea. 19bca6ab75d8 ("KVM: SVM: Fix cross vendor migration issue with
>>
From: Michal Hocko
We have seen an early OOM killer invocation on ppc64 systems with
crashkernel=4096M
kthreadd invoked oom-killer:
gfp_mask=0x16040c0(GFP_KERNEL|__GFP_COMP|__GFP_NOTRACK), nodemask=7, order=0,
oom_score_adj=0
kthreadd cpuset=/ mems_allowed=7
CPU: 0 PID:
Hello Petr,
thanks for taking a look.
On (05/30/17 11:55), Petr Mladek wrote:
[..]
> My understanding is that notifiers should return NOTIFY_OK
> when they handled it and NOTIFY_DONE when they did nothing.
> For example, see cpu_hotplug_pm_callback().
>
> In reality, there does not seem to be a
Hello there, I sent you an email yesterday with a proposal that is going to be
very beneficial to both yourself and I but I did not receive a response from
you so I am sending you this follow up to confirm if you actually did get my
email yesterday. Kindly let me know if you are interested in th
Hi Daniel,
On Thu, May 25, 2017 at 10:54:55PM +0200, Daniel Lezcano wrote:
> On Sat, May 13, 2017 at 03:29:35PM +0800, Dong Aisheng wrote:
> > IMX Timer/PWM Module (TPM) supports both timer and pwm function while
> > this patch only adds the timer support. PWM would be added later.
> >
> > The TP
On 2017.05.31 06:22:28 +, Chen, Xiaoguang wrote:
> >> @@ -467,6 +555,15 @@ static int intel_vgpu_create(struct kobject *kobj,
> >struct mdev_device *mdev)
> >>vgpu->vdev.mdev = mdev;
> >>mdev_set_drvdata(mdev, vgpu);
> >>
> >> + ret = intel_vgpu_reg_init_opregion(vgpu);
> >> + if (ret
On 2017-05-30 23:50, Alexandre Belloni wrote:
> Hi,
>
> This series reworks the Atmel Timer counter Block drivers. Those blocks
> each have 3 counters with 2 channels each and can be used for
> multiple functions:
> - timers
> - PWMs
> - Quadrature decoders
> - Stepper motor counters
I'd like
Hi Arnd,
On Thu, May 25, 2017 at 11:02:22PM +0200, Arnd Bergmann wrote:
> On Sat, May 13, 2017 at 9:29 AM, Dong Aisheng wrote:
>
> > diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
> > index 3356ab8..03dfd6a 100644
> > --- a/drivers/clocksource/Kconfig
> > +++ b/drivers/cl
FYI, we noticed the following commit:
commit: aefd950b83d2d8cf4d3c270546c8725f866da191 ("mm: make kswapd try harder
to keep active pages in cache")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -smp 2 -
FYI, we noticed the following commit:
commit: beeeccca9bebcec386cc31c250cff8a06cf27034 ("btrfs: Use kvzalloc instead
of kzalloc/vmalloc in alloc_bitmap")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -c
On 05/30/2017 06:06 PM, Andrea Arcangeli wrote:
>
> I'm not sure if it should be considered a bug, the prctl is intended
> to use normally by wrappers so it looks optimal as implemented this
> way: affecting future vmas only, which will all be created after
> execve executed by the wrapper.
>
> W
On 2017-05-30 19:47, sathyanarayanan kuppuswamy wrote:
> Hi Peter,
>
> Thanks for your comments.
>
> On 05/30/2017 06:40 AM, Peter Rosin wrote:
>> On 2017-05-30 02:47, sathyanarayanan.kuppusw...@linux.intel.com wrote:
>>> From: Kuppuswamy Sathyanarayanan
>>>
>>>
>>> In some Intel SOCs, a single
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
rcu/next
head: 8995eb05b8c6f9bde96bc2713ec9b7bb9072093f
commit: 32bc295e22be3b484ee3324f6aeeaae93234c429 [96/97] srcu: Move
rcu_scheduler_starting() from Tiny RCU to Tiny SRCU
config: sparc64-allnoconfig (attached as
Hi Philippe,
Le Tue, 30 May 2017 16:55:42 +,
Philippe CORNU a écrit :
> Hi Eric,
>
> I took your patch for the panel-bridge and it works perfectly in both
> DPI mode (panel RGB //) and DSI mode (bridge dw mipi dsi), bravo :-)
I still don't understand how it can work without a call to
drm_
From: Michal Hocko
Heiko Carstens has noticed that he can generate overlapping zones for
ZONE_DMA and ZONE_NORMAL:
DMA [mem 0x-0x7fff]
Normal [mem 0x8000-0x00017fff]
$ cat /sys/devices/system/memory/block_size_bytes
1000
$ cat /sys/devic
From: Michal Hocko
Heiko Carstens has noticed that the MMOP_ONLINE_KEEP is broken currently
$ grep . memory3?/valid_zones
memory34/valid_zones:Normal Movable
memory35/valid_zones:Normal Movable
memory36/valid_zones:Normal Movable
memory37/valid_zones:Normal Movable
$ echo online_movable > memory
On Wed, 31 May 2017 11:27:19 +0800
Lu Baolu wrote:
> >> +
> >> +#define XDBC_TRACE
> >> +#ifdef XDBC_TRACE
> >> +#define xdbc_trace trace_printk
> > Did you forget to remove the #define XDBC_TRACE?
> >
> > Enabling this driver brings the "trace_printk() being used.
> > Allocating extr
On Tue 30-05-17 16:55:01, Heiko Carstens wrote:
> On Tue, May 30, 2017 at 04:32:47PM +0200, Michal Hocko wrote:
> > On Tue 30-05-17 14:37:24, Heiko Carstens wrote:
> > > On Tue, May 30, 2017 at 02:18:06PM +0200, Michal Hocko wrote:
> > > > > So ZONE_DMA ends within ZONE_NORMAL. This shouldn't be po
Hi
>-Original Message-
>From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
>Behalf Of Zhenyu Wang
>Sent: Wednesday, May 31, 2017 12:47 PM
>To: Chen, Xiaoguang
>Cc: Tian, Kevin ; intel-...@lists.freedesktop.org; linux-
>ker...@vger.kernel.org; zhen...@linux.intel.
From: Fenglin Wu
Add pwm_chip to support QTI LPG module and export LPG channels as
PWM devices for consumer drivers' usage.
Signed-off-by: Fenglin Wu
---
.../devicetree/bindings/pwm/pwm-qti-lpg.txt| 39 ++
drivers/pwm/Kconfig| 10 +
drivers/pwm/Makefil
gsm_cleanup_mux() is called in the line discipline close path which
is called at tty_release() time. At this stage the tty is no longer
operational enough to send any frames. Sending close frames is
therefore not possible and waiting for their answers always times
out.
This patch removes sending c
Hi,
>-Original Message-
>From: Gerd Hoffmann [mailto:kra...@redhat.com]
>Sent: Monday, May 29, 2017 3:20 PM
>To: Chen, Xiaoguang ;
>alex.william...@redhat.com; ch...@chris-wilson.co.uk; intel-
>g...@lists.freedesktop.org; linux-kernel@vger.kernel.org;
>zhen...@linux.intel.com; Lv, Zhiyuan
From: Fenglin Wu
QTI TRI_LED module has 3 current sinks for LED driver and each is
controlled by a PWM channel used for LED dimming or blinking. Add
the driver to support it.
Signed-off-by: Fenglin Wu
---
.../devicetree/bindings/leds/leds-qti-rgb.txt | 66 +++
drivers/leds/Kconfig
From: Fenglin Wu
QTI TRI_LED module and LPG modules are existing in some Qualcomm PMICs
like PMI8998, PM660, etc. TRI_LED module has 3 LED drivers and each is
controlled by a PWM channel used for LED dimming or blinking. LPG (Light
Pulse Generator) module can be configured to operate in PWM mode
One of the Freescale recommended sequences for power off with external
PMIC is the following:
...
3. SoC is programming PMIC for power off when standby is asserted.
4. In CCM STOP mode, Standby is asserted, PMIC gates SoC supplies.
See:
http://www.nxp.com/assets/documents/data/en/reference-manua
Signed-off-by: Oleksij Rempel
Cc: ker...@pengutronix.de
Cc: linux-arm-ker...@lists.infradead.org
Cc: Michael Turquette
Cc: Stephen Boyd
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-...@vger.kernel.org
Cc: devicet...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
Documentation/devicetree/b
This board, as well as some other boards with i.MX6 and a PMIC, uses a
"MPIC_STBY_REQ" line to notify the PMIC about a state change.
The PMIC is programmed for a specific state change before triggering the
line.
In this case, PMIC_STBY_REQ can be used for Stand by, Sleep
and Power off modes.
Signe
v2:
- export pm_power_off_prepare to fix pfuze100-regulator as module compilation.
Oleksij Rempel (6):
ARM: imx6q: provide documentation for new fsl,pmic_stby_poweroff
property
ARM: imx6: register pm_power_off handler if "fsl,pmic_stby_poweroff"
is set
kernel/reboot.c: export pm_pow
we need it to preconfigure PMIC to properly power off the system.
Signed-off-by: Oleksij Rempel
Cc: Andrew Morton
Cc: ker...@pengutronix.de
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
---
kernel/reboot.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/re
Document the new optional "fsl,pmic_stby_poweroff" property.
Signed-off-by: Oleksij Rempel
Cc: ker...@pengutronix.de
Cc: linux-arm-ker...@lists.infradead.org
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Rob Herring
Cc: Mark Rutland
Cc: linux-kernel@vger.kernel.org
Cc: devicet...@vger.kernel.org
---
On some boards the SoC can use one pin "PMIC_STBY_REQ" to notify th PMIC
about state changes. In this case internal state of PMIC must be
preconfigured for upcomming state change.
It works fine with the current regulator framework, except with the
power-off case.
This patch is providing an optiona
Hi Marc/Robin/Will,
I did a little more digging myself and I think I now understand what you
meant by identity mapping, i.e., configuring the MMU-500 with 1:1
mapping between the DMA address and the IOVA address.
I think that should work. In the end, due to this MSI write parsing
issue in ou
On Tue, May 30, 2017 at 09:32:06PM +0200, Alexandre Belloni wrote:
> Switch to atomic PWM. The main goal is to properly wait for a period before
> disabling a channel to ensure the correct level is set on the output.
>
> Changes in v2:
> - fixed remaining checkpatch warnings
> - split the series
On Wed, May 31, 2017 at 7:54 AM, Daniel Vetter wrote:
> On Wed, May 31, 2017 at 1:06 AM, Dave Airlie wrote:
>> On 31 May 2017 at 08:10, David Miller wrote:
>>> From: Daniel Vetter
>>> Date: Tue, 30 May 2017 22:15:42 +0200
>>>
If the e1000e maintainer wants to coalesce or not return stateme
On Tue, May 30, 2017 at 05:16:56PM +0300, Andrey Ryabinin wrote:
> On 05/29/2017 06:29 PM, Dmitry Vyukov wrote:
> > Joonsoo,
> >
> > I guess mine (and Andrey's) main concern is the amount of additional
> > complexity (I am still struggling to understand how it all works) and
> > more arch-dependen
es e.g. at line 1477.
The regmap patch removes member client from struct ds1307.
Rgds, Heiner
>
> Caused by commit
>
> 345b89453dda ("rtc: rtc-ds1307: enable support for mcp794xx as a wakeup
> source without IRQ")
>
> interacting with commit
>
> 11e5890b5342 ("rtc: ds1307: convert driver to regmap")
>
> I have used the rtc tree from next-20170530 for today.
>
From: Colin Ian King
Trivial fix to spelling mistake in dev_err message
Signed-off-by: Colin Ian King
---
drivers/pci/dwc/pcie-qcom.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/dwc/pcie-qcom.c b/drivers/pci/dwc/pcie-qcom.c
index 289cda1b4897..fbc79a5274c6 1
From: Colin Ian King
Trivial fix to spelling mistake in dev_err message
Signed-off-by: Colin Ian King
---
drivers/pci/dwc/pcie-qcom.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/dwc/pcie-qcom.c b/drivers/pci/dwc/pcie-qcom.c
index 289cda1b4897..fbc79a5274c6 1
Hi all,
Changes since 20170530:
The mfd tree gained a build failure so I used the version from
next-20170530.
The drivers-x86 tree gained the same build failure as the mfd tree so
I used the version from next-20170530.
The rtc tree gained a build failure so I used the version from
next
From: Kuppuswamy Sathyanarayanan
TMU interrupts are registered as a separate interrupt chip, and
hence it should start its interrupt index(BXTWC_TMU_IRQ) number
from 0. But currently, BXTWC_TMU_IRQ is defined as part of enum
bxtwc_irqs_level2 and its index value is 11. Since this index
value is u
From: Kuppuswamy Sathyanarayanan
Cleanup the resource allocation/free code in probe function by using
devm_* calls.
Signed-off-by: Kuppuswamy Sathyanarayanan
Acked-for-MFD-by: Lee Jones
---
drivers/mfd/intel_soc_pmic_bxtwc.c | 54 +-
1 file changed, 18 ins
From: Kuppuswamy Sathyanarayanan
Since all second level thermal irqs are consumed by the same
device(bxt_wcove_thermal), there is no need to expose them as separate
interrupts. We can just export only the first level irqs for thermal and
let the device(bxt_wcove_thermal) driver handle the second
From: Kuppuswamy Sathyanarayanan
Following patch set fixes the chained IRQ issue observed in WCOVE PMIC driver.
Changes since v3:
* Added fix for typec wcove driver.
Kuppuswamy Sathyanarayanan (9):
mfd: intel_soc_pmic_bxtwc: fix TMU interrupt index
mfd: intel_soc_pmic_bxtwc: remove thermal
From: Kuppuswamy Sathyanarayanan
Currently, in Whiskey cove PMIC driver, USBC IRQ is moved under charger
level2 irq chip. So use irq_chip_data_chgr to get the USBC virtual IRQ
number.
Signed-off-by: Kuppuswamy Sathyanarayanan
---
drivers/usb/typec/typec_wcove.c | 2 +-
1 file changed, 1 inser
From: Kuppuswamy Sathyanarayanan
Currently all PMIC GPIO domain irqs are consumed by the same
device(bxt_wcove_gpio), so there is no need to export them as
separate interrupts. We can just export only the first level
GPIO irq(BXTWC_GPIO_LVL1_IRQ) as an irq resource and let the
GPIO device driver(
From: Kuppuswamy Sathyanarayanan
PMIC mfd driver only exports first level irq for GPIO device.
But currently we are reading the irqs from the second level irq
chip, So this patch fixes this issue by adding support to use
first level PMIC GPIO irq.
Signed-off-by: Kuppuswamy Sathyanarayanan
Acke
From: Kuppuswamy Sathyanarayanan
PMIC mfd driver only exports first level irq for thermal device.
But currently we are reading the irqs from the second level irq
chip, So this patch fixes this issue by adding support to use
first level PMIC thermal irq.
Signed-off-by: Kuppuswamy Sathyanarayanan
From: Kuppuswamy Sathyanarayanan
Whishkey cove PMIC has support to mask/unmask interrupts at two levels.
At first level we can mask/unmask interrupt domains like TMU, GPIO, ADC,
CHGR, BCU THERMAL and PWRBTN and at second level, it provides facility
to mask/unmask individual interrupts belong each
From: Kuppuswamy Sathyanarayanan
Currently in WCOVE PMIC mfd driver, all second level irq chips
are chained to the respective first level irqs. So there is no
need for explicitly unmasking the first level irq in this
driver. This patches removes this level 1 irq unmask support.
Signed-off-by: Ku
On 2017.05.27 16:38:49 +0800, Xiaoguang Chen wrote:
> decode frambuffer attributes of primary, cursor and sprite plane
>
> Signed-off-by: Xiaoguang Chen
> ---
> drivers/gpu/drm/i915/gvt/Makefile | 3 +-
> drivers/gpu/drm/i915/gvt/display.c| 2 +-
> drivers/gpu/drm/i915/gvt/display.h
Hi André, Jan, Andrew,
On 26/05/17 20:28, Jan Kiszka wrote:
> On 2017-05-26 13:22, André Draszik wrote:
>> lx-dmesg needs access to the log_buf symbol from printk.c.
>> Unfortunately, the symbol log_buf also exists in BPF's
>> verifier.c and hence gdb can pick one or the other. If it
>> happens to
Hey MNC,
On Fri, 2017-05-26 at 22:14 -0500, Mike Christie wrote:
> Thanks for the patch.
>
Btw, after running DATERA's internal longevity and scale tests across
~20 racks on v4.1.y with this patch over the long weekend, there haven't
been any additional regressions.
> On 05/26/2017 12:32 AM, Ni
On 2017.05.27 16:38:48 +0800, Xiaoguang Chen wrote:
> OpRegion is needed to support display related operation for
> intel vgpu.
>
> A vfio device region is added to intel vgpu to deliver the
> host OpRegion information to user space so user space can
> construct the OpRegion for vgpu.
>
> Signed-
On Tue, May 30, 2017 at 08:06:38PM +0300, Andy Shevchenko wrote:
> On Tue, May 30, 2017 at 7:51 PM, Douglas Anderson
> wrote:
> > In commit 9a075265c6dc ("ASoC: Intel: sst: Remove unused function
> > sst_restore_shim64()"), we deleted the sst_restore_shim64() since it
> > was never used. ...but
Hi Tim,
Thanks for comment!
On 2017/5/31 8:56, Tim Chen wrote:
> On 05/19/2017 11:47 PM, Yisheng Xie wrote:
>> When ioremap a 67112960 bytes vm_area with the vmallocinfo:
>> [..]
>> 0xec79b000-0xec7fa000 389120 ftl_add_mtd+0x4d0/0x754 pages=94 vmalloc
>> 0xec80-0xecbe1000 4067328 kbox_proc
chip->alarm && (ds1307->client->irq > 0 ||
^
Caused by commit
345b89453dda ("rtc: rtc-ds1307: enable support for mcp794xx as a wakeup
source without IRQ")
interacting with commit
11e5890b5342 ("rtc: ds1307: convert dri
Hi All,
On Tue, May 30, 2017 at 8:38 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 30 May 2017 09:53:06 +0100 Lee Jones wrote:
>>
>> Dear fellow Maintainers,
>>
>> Enjoy!
>>
>> The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
>>
>> Linux 4.12-rc1 (2017-05-13 13:
Sorry, its a mistake from my end. It looks like typec wcove driver got
merged recently and I missed to add it to my cleanup patch set.
Lee,
I have created a patch to fix this issue.
Do you want me to send the entire series again with this fix or just
send the fix alone.
On Tue, May 30, 2017 at
On Tue, May 30, 2017 at 02:56:18PM +0200, Michal Suchánek wrote:
> > > > I concede userspace doesn't have the feature, but you should
> > > > really have a look at libinput (i.e. open a bug on
> > > > bugs.freedesktop.org) and request the feature here.
> > > >
> > > > >
> > > > > >
> >
Maxime Ripard writes:
> Hi Kevin,
>
> On Thu, May 18, 2017 at 11:59:50AM -0700, Kevin Hilman wrote:
>> On Fri, Mar 17, 2017 at 10:39 AM, Kevin Hilman wrote:
>> > On Fri, Feb 10, 2017 at 12:42 AM, Maxime Ripard
>> > wrote:
>> >> On Wed, Feb 08, 2017 at 11:09:31PM +0100, Rask Ingemann Lambertsen
On 05/30/2017 10:48 PM, James Morris wrote:
On Mon, 29 May 2017, Boris Lukashev wrote:
With all due respect sir, i believe your review falls short of the
purpose of this effort - to harden the kernel against flaws in
userspace.
Which effort? Kernel self protection is about protecting against
On Wed, 24 May 2017 13:20:23 -0400
Jérôme Glisse wrote:
> Allow to unmap and restore special swap entry of un-addressable
> ZONE_DEVICE memory.
>
> Changed since v1:
> - s/device unaddressable/device private/
>
> Signed-off-by: Jérôme Glisse
> Cc: Kirill A. Shutemov
> ---
> include/linux/m
On Tue, May 30, 2017 at 2:34 PM, Leonard Crestez
wrote:
> Right now mach-imx6ul registers a fixup for the ksz8081 phy. The same
> register values can be set through the micrel phy driver by using dts
> properties.
>
> This seems preferable and allows cleanly fixing suspend/resume.
>
> Signed-off-b
On Tue, May 30, 2017 at 12:57 PM, Leonard Crestez
wrote:
> From: Octavian Purdila
>
> This fixes an issue with imx6ull where setting the frequency to 528Mhz
> would actually set the ARM clock to 324Mhz.
>
> Signed-off-by: Octavian Purdila
> Signed-off-by: Leonard Crestez
Reviewed-by: Fabio Est
On Wed, 2017-05-31 at 12:28 +0900, Hirokazu Honda wrote:
> If I understand a bitmap correctly, it is necessary to change the log level
> for each message.
> I didn't mean a bitmap will take a long CPU time.
> I mean the work to change so takes a long time.
No, none of the messages or levels need c
On 5/27/2017 9:56 AM, Andy Lutomirski wrote:
On Sat, May 27, 2017 at 9:00 AM, Andy Lutomirski wrote:
On Sat, May 27, 2017 at 6:31 AM, kernel test robot
wrote:
FYI, we noticed the following commit:
commit: e2a7dcce31f10bd7471b4245a6d1f2de344e7adf ("x86/mm: Rework lazy TLB to track
the actua
Nathan Fontenot writes:
> On 05/30/2017 06:41 AM, Michael Ellerman wrote:
>> Michael Bringmann writes:
>>> When adding or removing memory, the aa_index (affinity value) for the
>>> memblock must also be converted to match the endianness of the rest
>>> of the 'ibm,dynamic-memory' property. Other
On Wed, 24 May 2017 13:20:21 -0400
Jérôme Glisse wrote:
> This patch add a new memory migration helpers, which migrate memory
> backing a range of virtual address of a process to different memory
> (which can be allocated through special allocator). It differs from
> numa migration by working on
On 30-05-17, 18:57, Leonard Crestez wrote:
> From: Octavian Purdila
>
> This fixes an issue with imx6ull where setting the frequency to 528Mhz
> would actually set the ARM clock to 324Mhz.
>
> Signed-off-by: Octavian Purdila
> Signed-off-by: Leonard Crestez
> ---
> drivers/cpufreq/imx6q-cpufr
On Sun 28 May 23:23 PDT 2017, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in dev_err message
>
Thanks Colin,
Regards,
Bjorn
From: "leilei.lin"
locklessly and integrally copy dentry name. It will be used later for
bugfix
Signed-off-by: leilei.lin
---
fs/dcache.c| 38 ++
include/linux/dcache.h | 2 ++
2 files changed, 40 insertions(+)
diff --git a/fs/dcache.c b/fs/dca
From: "leilei.lin"
Slub alloced mem overwritten ocurrs when fsnotify thread was copying the
dentry name and another rename thread change the dentry name at same
time.
These patches do the following:
1. A new copy_dname method was created which copy file_name to new alloc mem.
The later patch
From: "leilei.lin"
Kernel got panicked in inotify_handle_event, while running the rename
operation against the same file. The root cause is that the race between
fsnotify thread and file rename thread. When fsnotify thread was
copying the dentry name, another rename thread could change the dentr
On 2017/5/31 11:30, Jessica Yu wrote:
> +++ Wanlong Gao [31/05/17 10:23 +0800]:
>> Hi Jessica,
>>
>> On 2017/5/29 17:10, Jessica Yu wrote:
>>> +++ Xie XiuQi [20/05/17 15:46 +0800]:
From: Wanlong Gao
Module name has a limited length, but currently the build system
allows the b
4.12.0-rc3-next-20170530 #489
[ 1844.182078] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[ 1844.182085] kworker/u8:3D11008 129 2 0x
[ 1844.182109] Workqueue: events_unbound flush_to_ldisc
[ 1844.182118] Call Trace:
[ 1844.182136
Hi Jessica,
On 2017/5/31 11:30, Jessica Yu wrote:
> +++ Wanlong Gao [31/05/17 10:23 +0800]:
>> Hi Jessica,
>>
>> On 2017/5/29 17:10, Jessica Yu wrote:
>>> +++ Xie XiuQi [20/05/17 15:46 +0800]:
From: Wanlong Gao
Module name has a limited length, but currently the build system
a
On Sat, May 27, 2017 at 04:23:34PM -0700, Bjorn Andersson wrote:
> Add device tree binding documentation for the Qualcomm GLINK RPM, used
> for communication with the Resource Power Management subsystem in
> various Qualcomm SoCs.
>
> Acked-by: Rob Herring
> Signed-off-by: Bjorn Andersson
> ---
Hi all,
On Tue, 30 May 2017 09:53:06 +0100 Lee Jones wrote:
>
> Dear fellow Maintainers,
>
> Enjoy!
>
> The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
>
> Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
>
> are available in the git repository at:
>
> git://git.ke
On Tue, May 30, 2017 at 11:47:59PM +0200, Thomas Gleixner wrote:
> On Fri, 26 May 2017, Octavian Purdila wrote:
> > On Vi, 2017-05-26 at 14:55 +0200, Frederic Weisbecker wrote:
> >
> > Nice, it is less expensive and deletes some code :-) Thanks for the
> > quick fix Frederic, I confirm it solves m
tel_soc_pmic_bxtwc: Use chained irqs for second level
> irq chips")
>
> interacting with commit
>
> d2061f9cc32d ("usb: typec: add driver for Intel Whiskey Cove PMIC USB
> Type-C PHY")
>
> from Linus' tree (v4.12-rc1). grep is your friend. :-)
>
Hi Marcel,
Quoting "Gustavo A. R. Silva" :
Hi Marcel,
Quoting Marcel Holtmann :
Hi Gustavo,
While looking into Coverity ID 1357456 I ran into the following
piece of code at net/bluetooth/smp.c:166
166/* The following functions map to the LE SC SMP crypto functions
167 * AES-CMAC, f4, f5
The driver may sleep under a write spin lock, the function call path is:
qla4_82xx_wr_32 (acquire the lock)
qla4_82xx_crb_win_lock
schedule or cpu_relax
To fix it, the lock is released before "schedule" and "cpu_relax",
and the lock is acquired again after "schedule" and "cpu_relax".
Sign
On Wed, May 31, 2017 at 3:32 AM, Alexandre Belloni
wrote:
> Implement .get_state instead of only reading the polarity at probe time.
> This allows to get the proper state, period and duty cycle.
>
> Signed-off-by: Alexandre Belloni
> ---
> drivers/pwm/pwm-sun4i.c | 65
>
+++ Wanlong Gao [31/05/17 10:23 +0800]:
Hi Jessica,
On 2017/5/29 17:10, Jessica Yu wrote:
+++ Xie XiuQi [20/05/17 15:46 +0800]:
From: Wanlong Gao
Module name has a limited length, but currently the build system
allows the build finishing even if the module name is too long.
CC
/root/
Hi Marcel,
Quoting Marcel Holtmann :
Hi Gustavo,
While looking into Coverity ID 1357456 I ran into the following
piece of code at net/bluetooth/smp.c:166
166/* The following functions map to the LE SC SMP crypto functions
167 * AES-CMAC, f4, f5, f6, g2 and h6.
168 */
169
170static int aes_
Hi,
On 05/30/2017 09:46 PM, Vlastimil Babka wrote:
> On 03/21/2017 09:01 AM, Lu Baolu wrote:
>> XHCI debug capability (DbC) is an optional but standalone
>> functionality provided by an xHCI host controller. Software
>> learns this capability by walking through the extended
>> capability list of t
The driver may sleep under a spin lock, and the function call path is:
iscsit_tpg_enable_portal_group (acquire the lock by spin_lock)
iscsi_update_param_value
kstrdup(GFP_KERNEL) --> may sleep
To fix it, the "GFP_KERNEL" is replaced with "GFP_ATOMIC".
Signed-off-by: Jia-Ju Bai
---
drivers
Hi Jia-Ju,
[auto build test ERROR on scsi/for-next]
[also build test ERROR on v4.12-rc3 next-20170530]
[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/Jia-Ju-Bai/qla4xxx-Fix-a-sleep-in-atomic
The driver may sleep under a spin lock, and the function call path is:
ffs_epfile_io (acquire the lock by spin_lock_irq)
usb_ep_alloc_request(GFP_KERNEL) --> may sleep
To fix it, the "GFP_KERNEL" is replaced with "GFP_ATOMIC".
Signed-off-by: Jia-Ju Bai
---
drivers/usb/gadget/function/f_fs.c |
em_fxstor previously called fxstor_fixup. Both created instances of
struct fxregs_state on the stack, which triggered the warning:
arch/x86/kvm/emulate.c:4018:12: warning: stack frame size of 1080 bytes
in function
'em_fxrstor' [-Wframe-larger-than=]
static int em_fxrstor(struct x86_emulate
2017-05-26 20:55 GMT+08:00 Frederic Weisbecker :
> On Wed, May 24, 2017 at 03:39:24PM +0300, Octavian Purdila wrote:
>> Currently, when detecting expired timers in tick_nohz_stop_sched_tick
>> we just schedule a new hrtimer and let its handler to schedule
>> TIMER_SOFITRQ.
>>
>> This can lead to in
The driver may sleep under a spin lock, and the function call path is:
mraid_mm_attach_buf (acquire the lock by spin_lock_irqsave)
pci_pool_alloc(GFP_KERNEL) --> may sleep
To fix it, the "GFP_KERNEL" is replaced with "GFP_ATOMIC".
Signed-off-by: Jia-Ju Bai
---
drivers/scsi/megaraid/megaraid_m
1 - 100 of 1077 matches
Mail list logo
