Remove no longer needed big.LITTLE switcher support from
arm_big_little CPUfreq driver.
The arm_big_little CPUfreq driver itself may also be removed
at later time (after converting platforms using it to use
cpufreq-dt CPUfreq driver instead).
Cc: Sudeep Holla
Cc: Sudeep KarkadaNagesha
Signed-of
On Mon, 2016-06-27 at 12:20 +0200, Matthias Brugger wrote:
>
> On 06/24/2016 09:27 AM, Bibby Hsieh wrote:
> > Hi Dave,
> >
> > Please consider merging this tag, which contains the v2 MT8173 gamma &
> > dither function patches I sent on 2016-06-17, rebased onto v4.7-rc1. There
> > have been no fu
On Mon, Jun 27, 2016 at 12:55:26PM +0200, Hans de Goede wrote:
> Hi Russel,
>
> On 27-06-16 11:45, Russell King - ARM Linux wrote:
> >On Mon, Jun 27, 2016 at 10:13:05AM +0100, Marc Zyngier wrote:
> >>I'm wondering if that's not an effect of this patch:
> >>
> >>https://lkml.org/lkml/2015/9/24/138
On Mon, 2016-06-27 at 21:20 +1000, Michael Ellerman wrote:
> On Mon, 2016-06-27 at 03:51 -0700, Joe Perches wrote:
> >
> > On Mon, 2016-06-27 at 11:38 +0100, Colin Ian King wrote:
> > >
> > > On 26/06/16 05:19, Michael Ellerman wrote:
> > > >
> > > > On Fri, 2016-24-06 at 17:43:00 UTC, Colin Kin
On Fri, Jun 10, 2016 at 4:27 PM, Daniel Vetter wrote:
> On Thu, Jun 09, 2016 at 03:32:55PM +0200, Andrea Merello wrote:
>> This driver supports the VGA/LCD core available from OpenCores:
>> http://opencores.org/project,vga_lcd
>>
>> It's intended as a replacement for the "ocfb" framebuffer driver
On 06/27/2016 01:02 PM, Arnd Bergmann wrote:
> The change to simplify of_platform_populate() had an unintended
> side-effect of introducing a build warning on s3c64xx:
>
> In file included from arch/arm/mach-s3c64xx/mach-s3c64xx-dt.c:18:0:
> arch/arm/mach-s3c64xx/common.h:27:30: error: 'struct dev
This patch moves the struct extcon_cable because that should
be only handled by extcon core. There are no reason to publish
the internal structure.
Signed-off-by: Chanwoo Choi
---
drivers/extcon/extcon.c | 20
include/linux/extcon.h | 20
2 files change
This patch split out the resource-managed related functions
from extcon core driver.
Signed-off-by: Chanwoo Choi
---
drivers/extcon/Makefile | 2 +-
drivers/extcon/devres.c | 143
drivers/extcon/extcon.c | 117 ---
This patch-set are refactoring the extcon core without the modification
of operation. The struct extcon_cabe moves from header file to extcon core
and make the new devres.c driver which only handles the resource-managed
functions. Lastly, this patch-set add resource-managed functions for extcon
reg
On 27/06/16 12:20, Michael Ellerman wrote:
> On Mon, 2016-06-27 at 03:51 -0700, Joe Perches wrote:
>> On Mon, 2016-06-27 at 11:38 +0100, Colin Ian King wrote:
>>> On 26/06/16 05:19, Michael Ellerman wrote:
On Fri, 2016-24-06 at 17:43:00 UTC, Colin King wrote:
> trivial fix to spelling mist
On Friday, June 24, 2016 2:28:59 PM CEST kernelci. org bot wrote:
>
> Errors summary:
>
> 3 arch/arm/include/asm/jump_label.h:13:7: error: impossible constraint
> in 'asm'
> 66 arch/arm/include/asm/jump_label.h:13:7: warning: asm operand 0
> probably doesn't match constraints
I've
This patch adds the resource-managed functions for register/unregister
the extcon notifier with the id of each external connector. This function
will make it easy to handle the extcon notifier.
- int devm_extcon_register_notifier(struct device *dev,
struct extcon_de
On Mon, 27 Jun 2016, Pavel Machek wrote:
> I believe you want "whenever source of function A influenced code in
> function B, I want to be notified", and I believe it should be
> documented as such.
Well, exactly. IPA is a group of optimizations that are, by definition,
intra-prodcedural.
--
On Sat 25-06-16 09:20:06, Chenjie (K) wrote:
>
>
> On 2016/6/23 20:42, Michal Hocko wrote:
> > On Fri 24-06-16 01:30:10, chenj...@huawei.com wrote:
> > > From: chenjie
> > >
> > > cat /dev/kmem and echo > /dev/kmem will lead panic
> >
> > Writing to /dev/kmem without being extremely careful is
This is to avoid cpufreq update callbacks for for !root cgroups when
!CONFIG_SMP
Signed-off-by: Jisheng Zhang
---
Since v1:
-fix commit msg, now I really know what the check is for, thank Peter
kernel/sched/fair.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/s
Check for valid regulator information data before
configuring FPS source and FPS power up/down
period to avoid NULL pointer exception if entries for
PMIC regulators not provided through device tree.
SD4 regulator is not supported by MAX77620 PMIC, removing
SD4 entry from regulator information list.
Hi Ulf and Adrian,
On 6/27/16, 12:08 PM, "Ulf Hansson" wrote:
>[...]
>
If I am not wrong, in current implementation of runtime suspend,
the driver stops BKOPS (send HPI) just before sending sleep command,
see _mmc_suspend(), depends on “MMC_CAP_AGGRESSIVE_PM” flag.
In this c
On Mon, Jun 27, 2016 at 12:31:43PM +0100, Russell King - ARM Linux wrote:
> On Mon, Jun 27, 2016 at 12:55:26PM +0200, Hans de Goede wrote:
> > Hi Russel,
Btw, please take note of how my name is spelt. Thanks.
> Only if we accept that pm_power_off() should be called with IRQs
> enabled, which we
On Mon, 2016-06-27 at 17:54 +0800, Yisen Zhuang wrote:
> From: Daode Huang
>
> There are two approaches to assign data, one does 2 loops, another
> does 1 loop. This patch normalize the different methods to 1 loop.
[]
> diff --git a/drivers/net/ethernet/hisilicon/hns/hns_dsaf_main.c
> b/drivers/
Hi,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.7-rc5 next-20160624]
[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/Keerthy/mfd-regulator-tps65218-Clean-ups/20160627
From: Randy Dunlap
Fix build errors when ACPI is not enabled by adding function stubs:
../drivers/gpu/drm/i915/i915_drv.c: In function 'i915_drm_suspend':
../drivers/gpu/drm/i915/i915_drv.c:635:2: error: implicit declaration of
function 'intel_opregion_unregister' [-Werror=implicit-function-dec
Hi Hans-
Thanks for reviewing this again in such detail.
On 27/06/2016 12:26, Hans Verkuil wrote:
> On 06/23/2016 12:08 AM, Nick Dyer wrote:
>> This is a series of patches to add output of raw touch diagnostic data via
>> V4L2
>> to the Atmel maXTouch and Synaptics RMI4 drivers.
>>
>> It's a rew
The Samsung serial driver registered for CPU frequency transitions to
recalculate its clock when ARM clock frequency changes. This is needed
only on S3C24xx platform so limit the ifdef to respective cpufreq
driver.
On S3C24xx the ratio ratio between frequencies of UART's parent clock
(pclk) and A
On Mon, 2016-06-27 at 04:49 -0700, Joe Perches wrote:
> On Mon, 2016-06-27 at 17:54 +0800, Yisen Zhuang wrote:
> > From: Daode Huang
> >
> > There are two approaches to assign data, one does 2 loops, another
> > does 1 loop. This patch normalize the different methods to 1 loop.
> []
> > diff --gi
On Mon, 2016-06-27 at 15:00 +0300, Andy Shevchenko wrote:
> On Mon, 2016-06-27 at 04:49 -0700, Joe Perches wrote:
> >
> > On Mon, 2016-06-27 at 17:54 +0800, Yisen Zhuang wrote:
> > >
> > > From: Daode Huang
> > >
> > > There are two approaches to assign data, one does 2 loops, another
> > > doe
Hi,
On Mon, Jun 27, 2016 at 03:51:08PM +0530, Rajaram R wrote:
> May be I am missing user or usage of the driver.. I see this driver is
> providing limited information of the Type-C connectors or the port
> partner
Yes, this interface can't provide directly information received from
PD commands l
On Mon, 2016-06-27 at 05:08 -0700, Joe Perches wrote:
> On Mon, 2016-06-27 at 15:00 +0300, Andy Shevchenko wrote:
> > On Mon, 2016-06-27 at 04:49 -0700, Joe Perches wrote:
> > >
> > > On Mon, 2016-06-27 at 17:54 +0800, Yisen Zhuang wrote:
> > > >
> > > > From: Daode Huang
> > > >
> > > > There
From: Michal Hocko
c0ff7453bb5c ("cpuset,mm: fix no node to alloc memory when changing
cpuset's mems") has added TIF_MEMDIE and PF_EXITING check but it is
checking the flag on the current task rather than the given one.
This doesn't make much sense and it is actually wrong. If the current
task wh
Hi,
while I was looking to move TIF_MEMDIE out of the thread info for other purpose
I have noticed these two usages which are not correct. I do not think any of
them
warrant a stable backport because it is highly unlikely they would ever hit but
it is better to have them fixed.
I would route them
From: Michal Hocko
freezing_slow_path is checking TIF_MEMDIE to skip OOM killed
tasks. It is, however, checking the flag on the current task rather than
the given one. This is really confusing because freezing() can be called
also on !current tasks. It would end up working correctly for its main
On 26/06/16 19:29, Greg Kroah-Hartman wrote:
> On Mon, Jun 20, 2016 at 03:40:27PM +0100, Colin King wrote:
>> From: Colin Ian King
>>
>> An ENOMEM when creating a pair tty in tty_ldisc_setup causes a null
>> pointer dereference in devpts_kill_index because tty->link->driver_data
>> is NULL. The o
Hi,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.7-rc5 next-20160624]
[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/Keerthy/mfd-regulator-tps65218-Clean-ups/20160627
On Mon, 27 Jun 2016, Keerthy wrote:
> Currently read directly calls the repmap read function. Hence
> remove the redundant wrapper and use regmap read wherever
> needed.
>
> Signed-off-by: Keerthy
> ---
> drivers/mfd/tps65218.c | 16 +---
> drivers/regulator/tps65218
On Mon, 27 Jun 2016, Keerthy wrote:
> mfd_add_devices enables parsing device tree nodes without compatibles
> for child nodes. Replace of_platform_populate with mfd_add_devices.
> mfd_cell currently is populated with only regulators.
>
> Signed-off-by: Keerthy
> ---
>
> Changes in v2:
>
> *
On 06/27/2016 01:57 PM, Nick Dyer wrote:
> Hi Hans-
>
> Thanks for reviewing this again in such detail.
>
> On 27/06/2016 12:26, Hans Verkuil wrote:
>> On 06/23/2016 12:08 AM, Nick Dyer wrote:
>>> This is a series of patches to add output of raw touch diagnostic data via
>>> V4L2
>>> to the Atme
On Wed, Jun 15, 2016 at 08:25:07AM +0100, Juri Lelli wrote:
> I guess it's not that likely, but yes it could potentially happen that a
> waiter is optimistically spinning, depletes its runtime, gets throttled
> and then replenished when still spinning. Maybe it doesn't really make
> sense continuin
IDE subsystem has been deprecated since 2009 and the majority
(if not all) of Linux distributions have switched to use
libata for ATA support exclusively. However there are still
some users (mostly old or/and embedded non-x86 systems) that
have not converted from using IDE subsystem to libata PATA
On Wed, Jun 22, 2016 at 10:25:47PM -0400, r...@redhat.com wrote:
> From: Rik van Riel
>
> Currently, if there was any irq or softirq time during 'ticks'
> jiffies, the entire period will be accounted as irq or softirq
> time.
>
> This is inaccurate if only a subset of 'ticks' jiffies was
> actua
On Mon, Jun 27, 2016 at 09:36:46AM +1000, Stephen Rothwell wrote:
> Hi Jarkko,
>
> I noticed that a large number of the patches in the tpmdd tree appear
> twice (and some three times). They appear to have been rebased on top
> of the security tree before being remerged. Please clean this all up.
Hi all,
+ Marcin,
According to Marcin's series of patches
"mtd: spi-nor: DUAL/QUAD I/O read modes implementation"
and the Spansion/Cypress S25FS512S datasheet, new Cypress QSPI memories
no longer supports Fast Read 1-1-2 or Fast Read 1-1-4 but only Fast Read x-2-2
and Fast Read x-4-4.
Hence one
On Mon, 27 Jun 2016, Peter Zijlstra wrote:
> On Wed, Jun 15, 2016 at 08:25:07AM +0100, Juri Lelli wrote:
> > I guess it's not that likely, but yes it could potentially happen that a
> > waiter is optimistically spinning, depletes its runtime, gets throttled
> > and then replenished when still spin
On 24/06/16 17:50, Mel Gorman wrote:
> On Fri, Jun 24, 2016 at 04:35:45PM +1000, Balbir Singh wrote:
>>> 1. The residency of a page partially depends on what zone the page was
>>>allocated from. This is partially combatted by the fair zone allocation
>>>policy but that is a partial solut
Hi,
On Tuesday 10 May 2016 05:09 AM, David Lechner wrote:
> The initial use for this is for PHYs that have a mode related to USB OTG.
> There are several SoCs (e.g. TI OMAP and DA8xx) that have a mode setting
> in the USB PHY to override OTG VBUS and ID signals.
>
> Of course, the enum can be exp
On Tuesday 10 May 2016 05:09 AM, David Lechner wrote:
> v5 changes:
>
> Functionally, nothing has really changed. Just some cleanups based on
> feedback.
>
> * Renamed "usbphy" to "usb_phy" or "usb-phy" as appropriate
> * License header matches MODULE_LICENSE in new phy driver
applied all the
On Mon, 2016-06-27 at 14:25 +0200, Frederic Weisbecker wrote:
> On Wed, Jun 22, 2016 at 10:25:47PM -0400, r...@redhat.com wrote:
> >
> > From: Rik van Riel
> >
> > Currently, if there was any irq or softirq time during 'ticks'
> > jiffies, the entire period will be accounted as irq or softirq
>
On Sun, Jun 26, 2016 at 09:41:35AM +0200, Micha?? K??pie?? wrote:
> Haswell-based Fujitsu laptops (Lifebook E734/E744/E754) have a touchpad
> toggle hotkey (Fn+F4) which is handled transparently to the operating
> system: while an ACPI notification is sent to FUJ02B1 when Fn+F4 is
> pressed, touchp
The driver registered for CPU frequency transitions to recalculate its
clock when ARM clock frequency changes (ratio between frequencies of
ARM's parent clock (fclk) and clock for peripherals remains fixed).
This is needed only on S3C24xx platform when cpufreq driver is enabled
so limit the ifdef
On 27/06/2016 13:22, Hans Verkuil wrote:
> On 06/27/2016 01:57 PM, Nick Dyer wrote:
> 2) Alternatively, if we want to keep using BUF_TYPE_VIDEO_CAPTURE, then:
>
> - we keep V4L2_CAP_TOUCH which is combined with CAP_VIDEO_CAPTURE (and perhaps
> VIDEO_OUTPUT in the future). The CAP_TOUCH just says
Hi Russell,
On 27-06-16 13:31, Russell King - ARM Linux wrote:
On Mon, Jun 27, 2016 at 12:55:26PM +0200, Hans de Goede wrote:
Hi Russel,
On 27-06-16 11:45, Russell King - ARM Linux wrote:
On Mon, Jun 27, 2016 at 10:13:05AM +0100, Marc Zyngier wrote:
I'm wondering if that's not an effect of t
The driver registered for CPU frequency transitions to recalculate its
clock when ARM clock frequency changes (ratio between frequencies of
ARM's parent clock (fclk) and clock for peripherals remains fixed).
This is needed only on S3C24xx platform when cpufreq driver is enabled
so limit the ifdef
The driver registered for CPU frequency transitions to recalculate its
clock when ARM clock frequency changes (ratio between frequencies of
ARM's parent clock (fclk) and clock for peripherals remains fixed).
This is needed only on S3C24xx platform when cpufreq driver is enabled
so limit the ifdef
Commit-ID: f09509b9398b23ca53360ca57106555698ec2e93
Gitweb: http://git.kernel.org/tip/f09509b9398b23ca53360ca57106555698ec2e93
Author: David Carrillo-Cisneros
AuthorDate: Tue, 21 Jun 2016 11:31:10 -0700
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 11:34:18 +0200
perf/x86/intel:
> > Haswell-based Fujitsu laptops (Lifebook E734/E744/E754) have a touchpad
> > toggle hotkey (Fn+F4) which is handled transparently to the operating
> > system: while an ACPI notification is sent to FUJ02B1 when Fn+F4 is
> > pressed, touchpad state is properly toggled without any explicit support
Commit-ID: 3812bba84f3d721ff7dc3bb90360bc5ed6771994
Gitweb: http://git.kernel.org/tip/3812bba84f3d721ff7dc3bb90360bc5ed6771994
Author: David Carrillo-Cisneros
AuthorDate: Tue, 21 Jun 2016 11:31:12 -0700
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 11:34:19 +0200
perf/x86/intel:
Commit-ID: 19fc9ddd61e059cc45464bdf6e8fa304bb94080f
Gitweb: http://git.kernel.org/tip/19fc9ddd61e059cc45464bdf6e8fa304bb94080f
Author: David Carrillo-Cisneros
AuthorDate: Tue, 21 Jun 2016 11:31:11 -0700
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 11:34:19 +0200
perf/x86/intel:
Commit-ID: 71adae99ed187de9fcf988cc8873ee2c3af3385f
Gitweb: http://git.kernel.org/tip/71adae99ed187de9fcf988cc8873ee2c3af3385f
Author: David Carrillo-Cisneros
AuthorDate: Tue, 21 Jun 2016 11:31:13 -0700
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 11:34:20 +0200
perf/x86/intel:
Commit-ID: 0dceeaf599e6d9b8bd908ba4bd3dfee84aa26be2
Gitweb: http://git.kernel.org/tip/0dceeaf599e6d9b8bd908ba4bd3dfee84aa26be2
Author: Pan Xinhui
AuthorDate: Tue, 14 Jun 2016 14:37:27 +0800
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 11:37:41 +0200
locking/qspinlock: Use __this
On Fri, Jun 24, 2016 at 10:13:25AM +0800, Shunqian Zheng wrote:
> drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 100 +++--
> drivers/gpu/drm/rockchip/rockchip_drm_drv.h | 3 +
> drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 221
> ++--
> drivers/gpu/drm/rockchip/
Commit-ID: 599b4840b0ea453c7d11e1798dcc8f494dcfd58a
Gitweb: http://git.kernel.org/tip/599b4840b0ea453c7d11e1798dcc8f494dcfd58a
Author: Zev Weiss
AuthorDate: Sun, 26 Jun 2016 16:13:23 -0500
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 12:53:12 +0200
sched/core: Fix sched_getaffin
Commit-ID: dbf984d825935f61965bcfacfd8e8dfdaf3e8051
Gitweb: http://git.kernel.org/tip/dbf984d825935f61965bcfacfd8e8dfdaf3e8051
Author: Borislav Petkov
AuthorDate: Sat, 25 Jun 2016 13:24:57 +0200
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 12:20:31 +0200
x86/boot/64: Add forgott
We can just ignore the return value from debugfs_create_dir() and
debugfs_create_file(). The second one already interanlly checks the dentry
created by the first before creating the file.
debugfs was written so it would be easy to use, no need for error checking.
Signed-off-by: Luis de Bethencour
Commit-ID: 54fd11fee59e7d05287bc4eebccc8ec9742f2745
Gitweb: http://git.kernel.org/tip/54fd11fee59e7d05287bc4eebccc8ec9742f2745
Author: Peter Jones
AuthorDate: Sat, 25 Jun 2016 08:20:25 +0100
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 13:06:55 +0200
efi: Document #define FOO_PR
Commit-ID: 5356c32742bd51c8c57065d2389a2c4bc036adcd
Gitweb: http://git.kernel.org/tip/5356c32742bd51c8c57065d2389a2c4bc036adcd
Author: Compostella, Jeremy
AuthorDate: Sat, 25 Jun 2016 08:20:24 +0100
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 13:06:54 +0200
efibc: Report more i
Commit-ID: f6d1747f898cfe1fe52e3d18f5c77e5bd21fed9a
Gitweb: http://git.kernel.org/tip/f6d1747f898cfe1fe52e3d18f5c77e5bd21fed9a
Author: Colin Ian King
AuthorDate: Sat, 25 Jun 2016 08:20:26 +0100
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 13:06:55 +0200
x86/efi: Remove unused va
On 25/06/16 23:16, Greg KH wrote:
> On Sat, Jun 25, 2016 at 10:43:33PM +0100, Luis de Bethencourt wrote:
>> On 25/06/16 22:36, Greg KH wrote:
>>> On Thu, Jun 23, 2016 at 01:36:17PM +0100, Luis de Bethencourt wrote:
The common format to check if a function returned an error pointer is to
u
Commit-ID: 21f866257c7027f8f49bfde83f559f9e58f9ee93
Gitweb: http://git.kernel.org/tip/21f866257c7027f8f49bfde83f559f9e58f9ee93
Author: Alex Thorlton
AuthorDate: Sat, 25 Jun 2016 08:20:29 +0100
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 13:06:57 +0200
x86/efi: Update efi_thunk(
The CLK_IGNORE_UNUSED flag has to be avoided whenever possible.
Use the CLK_IS_CRITICAL flag instead, which enables the clock line
during boot time.
While none of the SCLK_SPI need to be alive all the time as that
clock is handled by the SPI driver as a busclk whenever needed.
Suggested-by: Tomas
enable SPI3 iosclk by using the CLK_IS_CRITICAL flag.
There is no device which is supposed to enable this clock when
needed, therefore, the only way to use the SPI bus is to enable
it in boot time.
Suggested-by: Tomasz Figa
Signed-off-by: Andi Shyti
Signed-off-by: Jaehoon Chung
---
Hi,
V1 ->
Commit-ID: d1be84a232e359ca9456c63e72cb0082d68311b6
Gitweb: http://git.kernel.org/tip/d1be84a232e359ca9456c63e72cb0082d68311b6
Author: Alex Thorlton
AuthorDate: Sat, 25 Jun 2016 08:20:28 +0100
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 13:06:56 +0200
x86/uv: Update uv_bios_cal
Commit-ID: 80e75596079f0a41f905836ad0ccaac68ba33612
Gitweb: http://git.kernel.org/tip/80e75596079f0a41f905836ad0ccaac68ba33612
Author: Alex Thorlton
AuthorDate: Sat, 25 Jun 2016 08:20:27 +0100
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 13:06:56 +0200
efi: Convert efi_call_virt
Ping!!
> -Original Message-
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: Friday, June 03, 2016 4:28 AM
> To: Nava kishore Manne
> Cc: pawel.m...@arm.com; mark.rutl...@arm.com;
> ijc+devicet...@hellion.org.uk; ga...@codeaurora.org; Michal Simek
> ; Soren Brinkmann ;
> ba...@ti.com;
On (06/27/16 11:26), Petr Mladek wrote:
> On Sat 2016-06-25 14:22:37, Sergey Senozhatsky wrote:
> > On (06/24/16 18:05), Petr Mladek wrote:
> > [..]
> > > > +static bool should_ignore_loglevel(int level)
> > > > +{
> > > > + return (level >= console_loglevel && !ignore_loglevel);
> > >
> > >
Commit-ID: b684e9bc750b6349ff59f1b1ab4397cae255765f
Gitweb: http://git.kernel.org/tip/b684e9bc750b6349ff59f1b1ab4397cae255765f
Author: Arnd Bergmann
AuthorDate: Sat, 25 Jun 2016 08:20:30 +0100
Committer: Ingo Molnar
CommitDate: Mon, 27 Jun 2016 13:06:58 +0200
x86/efi: Remove the unused
Hi All,
Currently I'm doing some tunings on the speed of suspend/resume,
it looks like my serio driver tooks a 200ms to finish, which is
too long:
[ 1120.255783] calling serio0+ @ 2764, parent: i8042
[ 1120.452976] call serio0+ returned 0 after 192472 usecs
So further investigation shows that th
[Sorry for a late reply]
On Fri 24-06-16 13:51:01, Johannes Weiner wrote:
> This is a rebased version on top of mmots sans the nodelru stuff.
>
> ---
>
> 23047a96d7cf ("mm: workingset: per-cgroup cache thrash detection")
> added a page->mem_cgroup lookup to the cache eviction, refault, and
> act
On Mon, Jun 27, 2016 at 04:22:18AM -0400, ok...@codeaurora.org wrote:
> > However, an earlier try on my Inspiron 510m did not work.
> > I'll do a clean retry later today, just to make sure.
>
>
> Ok, let me know. I can post a clean patch series. I was trying to get
> you something to test before
On Sat, Jun 25, 2016 at 10:38:21PM -0700, Stephen Boyd wrote:
> Let's follow other driver registration functions and
> automatically set the driver's owner member to THIS_MODULE when
> ulpi_driver_register() is called. This allows ulpi driver writers
> to forget about this boiler plate detail and a
On Mon, Jun 27, 2016 at 07:57:16PM +0900, Andi Shyti wrote:
> What I meant is that if we do not like num-cs = <0>, the
> unlinked CS line can be handled only this way (case of the
> s3c64xx driver):
> +- broken-cs: the CS line is disconnected, therefore the device should not
> wait
> + for the
If the TSC deadline timer is programmed really close to the deadline or
even in the past, the computation in vmx_set_hv_timer can underflow and
cause delta_tsc to be set to a huge value. This generally results
in vmx_set_hv_timer returning -ERANGE, but we can fix it by limiting
delta_tsc to be pos
Hi, all.
How about exchanging the assignments of `MEMORYs' and `CFGs/IOs'?
In other words, assign MEMEORYs to iatu0, CFGs and IOs to iatu1.
Once the iatu0 is initialized to MEMORY accesses, its BASE_ADDR,
LIMIT and TYPE is fixed. MEMORYs match with iatu0 at first, so
they will never being treated
On Sat, 25 Jun 2016, Vegard Nossum wrote:
> On 27 November 2015 at 05:30, Sasha Levin wrote:
> > (active state 0) object type: timer_list hint:
> > delayed_work_timer_fn+0x0/0x90
> > [ 1167.394563] Workqueue: events kobject_delayed_cleanup
> > [ 1167.410301] [] kfree+0x1fc/0x2f0
> > [ 1167.41
When sending an email regarding a patch to wilc1000, you get the following
automatic replies:
"Sung_hoon Cho is no longer with Atmel Corporation."
"Kang_hee Park is no longer with Atmel Corporation."
"Dong_ho Shin is no longer with Atmel Corporation."
"Bo_moon Kim is no longer with Atmel Corporatio
On 06/27/2016 03:11 AM, Peter Rosin wrote:
Fill the gap for this pre-existing driver.
Signed-off-by: Peter Rosin
---
.../devicetree/bindings/i2c/i2c-arb-pca9541.txt| 33 ++
MAINTAINERS| 1 +
2 files changed, 34 insertions(+)
Haswell-based Fujitsu laptops (Lifebook E734/E744/E754) have a touchpad
toggle hotkey (Fn+F4) which is handled transparently to the operating
system: while an ACPI notification is sent to FUJ02B1 when Fn+F4 is
pressed, touchpad state is properly toggled without any explicit support
for this operati
Hi Peter
On 05/11/2016 06:40 PM, Peter Griffin wrote:
This string is used by dump_stack and as we now support
more SoC's than just STiH415/6 it is misleading to have
the current string in the stack trace.
This patch updates it to be more generic for the STi
family of SoCs.
So instead of lookin
On Mon, Jun 27, 2016 at 11:26 AM, Heikki Krogerus
wrote:
> Whoa! Hold on!
>
> On Thu, Jun 23, 2016 at 05:52:53PM -0700, Bin Gao wrote:
>> Broxton platform firmware has defined new customized operation regions
>> called regs for PMIC chip - regs op region is used to handle the
>> PMIC gpio mainly i
On 06/27/2016 04:33 PM, Bob Liu wrote:
> Uncompleted reqs used to be 'saved and resubmitted' in blkfront_recover()
> during
> migration, but that's too later after multi-queue introduced.
>
> After a migrate to another host (which may not have multiqueue support), the
> number of rings (block ha
Changed the configuration to support 64bit instead of 32bit
this in order to offload the driver from handling a wraparound.
Signed-off-by: Yaniv Machani
---
V2 - Update the interface parameters type to le16 from u16.
drivers/net/wireless/ti/wl18xx/event.c | 26 +-
driver
This is to fix some bad issues on an over-committed guest.
test-caes:
perf record -a perf bench sched messaging -g 400 -p && perf report
18.09% sched-messaging [kernel.vmlinux] [k] osq_lock
12.28% sched-messaging [kernel.vmlinux] [k] rwsem_spin_on_owner
5.27% sched-messaging [kernel.vmli
This is to fix some holder preemption issues. Spinning at one
vcpu which is preempted is meaningless.
Kernel need such interfaces, So lets support it.
We also should suooprt both the shared and dedicated mode.
So add lppaca_dedicated_proc macro in lppaca.h
Suggested-by: Boqun Feng
Signed-off-by
this supports to fix lock holder preempted issue which run as a guest
for kernel users, we could use bool vcpu_is_preempted(int cpu) to detech
if one vcpu is preempted or not.
The default implementation is a macrodefined by false. So compiler can
wrap it out if arch dose not support such vcpu pte
An over-committed guest with more vCPUs than pCPUs has a heavy overload
in osq_lock().
This is because vCPU A hold the osq lock and yield out, vCPU B wait
per_cpu node->locked to be set. IOW, vCPU B wait vCPU A to run and
unlock the osq lock. Such spinning is meaningless.
So lets use vcpu_is_pree
Dan Williams writes:
> When it was first introduced CONFIG_ZONE_DEVICE depended on disabling
> CONFIG_ZONE_DMA, a configuration choice reserved for "experts".
> However, now that the ZONE_DMA conflict has been eliminated it no longer
> makes sense to require CONFIG_EXPERT.
>
> Reported-by: Eric S
On 06/27/2016 05:13 AM, Heikki Krogerus wrote:
Hi,
On Mon, Jun 27, 2016 at 03:51:08PM +0530, Rajaram R wrote:
May be I am missing user or usage of the driver.. I see this driver is
providing limited information of the Type-C connectors or the port
partner
Yes, this interface can't provide dir
This patch fixes "Alignment should match open parantheses" check
thrown by checkpatch.pl
Signed-off-by: Rithvik Patibandla
---
drivers/staging/vt6656/dpc.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/vt6656/dpc.c b/drivers/staging/vt6656/dpc.c
inde
If have got the following kmemleak report when I enabled the ftrace self
test:
unreferenced object 0xa000a000 (size 179):
comm "swapper/0", pid 1, jiffies 4294892507 (age 82553.780s)
hex dump (first 32 bytes):
55 ff 74 24 10 55 48 89 e5 ff 74 24 18 55 48 89 U.t$.UH...t$.UH.
e5
Ftrace modifies the code on many locations. It is paranoid
and avoid a kernel crash using probe_kernel_read() and
probe_kernel_write(). The only exception is update_ftrace_func()
where where we read the old code using memcpy().
It is true that this function is used only to modify well
defined func
1st patch adds one more paranoid check of the modified function on x86.
Plus there are 3 small changes that appeared when hunting down
the 1st patch.
Petr Mladek (4):
ftrace/x86: Make sure to modify 5-bite instructions
ftrace/x86: Do not crash when reading wrong ftrace func
ftrace: Always d
I was hunting a memory leak related to trace_selftest_ops() and found
two small mistakes there.
First, the dynamic trace must be freed in case of error. There was
one wrong goto target. It was even in the original commit
95950c2ecb31314ef ("ftrace: Add self-tests for multiple function
trace users"
Messages' levels and console log level are inspected when the
actual printing occurs, which may provoke console_unlock() and
console_cont_flush() to waste CPU cycles on every message that
has loglevel above the current console_loglevel.
Schematically, console_unlock() does the following:
console_
201 - 300 of 813 matches
Mail list logo
