Commit-ID: d49597fd3bc7d9534de55e9256767f073be1b33a
Gitweb: http://git.kernel.org/tip/d49597fd3bc7d9534de55e9256767f073be1b33a
Author: Thomas Gleixner
AuthorDate: Wed, 9 Nov 2016 16:35:51 +0100
Committer: Thomas Gleixner
CommitDate: Wed, 9 Nov 2016 21:05:01 +0100
x86/cpu: Deal with bro
Hi!
> > Thanks for the analysis. Either way, this patch, with the modification
> > I mentioned in my previous message is required to assure proper
> > LED sysfs locking.
> >
> > Regarding the races between user and atomic context, I think that
> > it should be system root's responsibility to defi
Em Wed, 9 Nov 2016 19:57:58 +
Malcolm Priestley escreveu:
> > Yeah, I avoided serializing the logic that detects if the firmware is
> > loaded, but forgot that the power control had the same issue. The
> > newer dvb usb drivers use the dvb-usb-v2, so I didn't touch this
> > code for a while.
On Wed, Nov 09, 2016 at 02:47:24PM -0500, J. Bruce Fields wrote:
> For now I wish we could just like to continue assuming the workqueue
> processes only one item at a time. Do we have that now, or do we need
> to switch to (looking at workqueue.h...) alloc_ordered workqueue()?
Oh, wait, I missed
Em Wed, 9 Nov 2016 11:07:35 -0800
Linus Torvalds escreveu:
> On Wed, Nov 9, 2016 at 3:09 AM, Jörg Otte wrote:
> >
> > Tried patch with no success. Again a NULL ptr dereferece.
>
> That patch was pure garbage, I think. Pretty much all the other
> drivers that use the same approach will have th
Stephen Boyd writes:
> This function is passed an __iomem pointer but we use a u32
> pointer instead which makes checkers like spare complain.
> Furthermore, "lock" is a pretty poor variable name for a string
> that will go into lockdep reports and the symbol isn't marked
> static. Cleanup all th
On Wed, Nov 09, 2016 at 06:12:50PM -0200, Marcelo Tosatti wrote:
> On Wed, Nov 09, 2016 at 05:48:15PM +0100, Paolo Bonzini wrote:
> > Userspace can read the exact value of kvmclock by reading the TSC
> > and fetching the timekeeping parameters out of guest memory. This
> > however is brittle and n
Arnd Bergmann writes:
> The newly added pxa glue driver for 8250 supports console output, but
> fails to build if the 8250 console is disabled:
>
> drivers/tty/serial/8250/8250_pxa.o: In function `early_serial_pxa_setup':
> 8250_pxa.c:(.init.text+0x50): undefined reference to `early_serial8250_se
On Wed, Nov 09, 2016 at 12:12:55PM -0600, Rob Herring wrote:
On Mon, Nov 7, 2016 at 5:44 PM, Reza Arbab wrote:
+ hotpluggable = of_get_flat_dt_prop(node, "linux,hotpluggable", NULL);
Memory being hotpluggable doesn't seem like a linux property to me.
I'd drop the linux prefix. Also, thi
On Wed, Nov 09, 2016 at 05:48:15PM +0100, Paolo Bonzini wrote:
> Userspace can read the exact value of kvmclock by reading the TSC
> and fetching the timekeeping parameters out of guest memory. This
> however is brittle and not necessary anymore with KVM 4.11.
Hi Paolo,
Can you point to commit
On 9 November 2016 at 12:02, Bjorn Andersson wrote:
> The correct include file for getting errno constants and ERR_PTR() is
> linux/err.h, rather than linux/errno.h, so fix the include.
>
> Fixes: e8b123e60084 ("soc: qcom: smem_state: Add stubs for disabled
> smem_state")
> Signed-off-by: Bjorn A
On 09/11/16 18:59, Don Dutile wrote:
> On 11/09/2016 12:03 PM, Will Deacon wrote:
>> On Tue, Nov 08, 2016 at 09:52:33PM -0500, Don Dutile wrote:
>>> On 11/08/2016 06:35 PM, Alex Williamson wrote:
On Tue, 8 Nov 2016 21:29:22 +0100
Christoffer Dall wrote:
> Is my understanding correct,
On Mon, Nov 07, 2016 at 09:38:15AM +0900, Jaehoon Chung wrote:
> On 11/05/2016 12:04 AM, Krzysztof Kozlowski wrote:
> > On Fri, Nov 04, 2016 at 12:19:49PM +0100, Heiko Stuebner wrote:
> >> Hi Jaehoon,
> >>
> >> Am Freitag, 4. November 2016, 19:21:30 CET schrieb Jaehoon Chung:
> >>> On 11/04/2016 03
On Wed, Nov 09, 2016 at 02:25:56PM -0500, Christopher Covington wrote:
> Hi Bjorn,
>
> On 11/02/2016 12:08 PM, Bjorn Helgaas wrote:
> > On Tue, Nov 01, 2016 at 07:06:31AM -0600, c...@codeaurora.org wrote:
> >> Hi Bjorn,
> >>
> >> On 2016-10-31 15:48, Bjorn Helgaas wrote:
> >>> On Wed, Sep 21, 2016
On Wed, Nov 09, 2016 at 03:38:33PM +0800, Jason Wang wrote:
> This patch tries to utilize tuntap rx batching by peeking the tx
> virtqueue during transmission, if there's more available buffers in
> the virtqueue, set MSG_MORE flag for a hint for tuntap to batch the
> packets. The maximum number of
On 11/08, Arnd Bergmann wrote:
> The new pxa2xx_determine_rate() function seems lacking in a few
> regards:
>
> - For an exact match or no match at all, the rate is uninitialized
> as reported by gcc -Wmaybe-unintialized:
>drivers/clk/pxa/clk-pxa.c: In function 'pxa2xx_determine_rate':
>
On Wed, 9 Nov 2016 20:23:03 +0100
Christoffer Dall wrote:
> On Wed, Nov 09, 2016 at 01:59:07PM -0500, Don Dutile wrote:
> > On 11/09/2016 12:03 PM, Will Deacon wrote:
> > >On Tue, Nov 08, 2016 at 09:52:33PM -0500, Don Dutile wrote:
> > >>On 11/08/2016 06:35 PM, Alex Williamson wrote:
> > >>
This patch moves ARMv8-related perf event definitions from perf_event.c
to asm/perf_event.h; so KVM code can use them directly. This also help
remove a duplicated definition of SW_INCR in perf_event.h.
Signed-off-by: Wei Huang
---
arch/arm64/include/asm/perf_event.h | 161 +++
KVM calls kvm_pmu_set_counter_event_type() when PMCCFILTR is configured.
But this function can't deals with PMCCFILTR correctly because the evtCount
bit of PMCCFILTR, which is reserved 0, conflits with the SW_INCR event
type of other PMXEVTYPER registers. To fix it, when eventsel == 0, this
functio
On 08/11/16 21:38, Mauro Carvalho Chehab wrote:
Em Tue, 8 Nov 2016 22:15:24 +0100
Benjamin Larsson escreveu:
On 11/08/2016 09:22 PM, Mauro Carvalho Chehab wrote:
Em Tue, 8 Nov 2016 10:42:03 -0800
Linus Torvalds escreveu:
On Sun, Nov 6, 2016 at 7:40 AM, Jörg Otte wrote:
Since v4.9-rc4 I g
On Wed, Nov 09, 2016 at 03:38:32PM +0800, Jason Wang wrote:
> We should use vq->last_avail_idx instead of vq->avail_idx in the
> checking of vhost_vq_avail_empty() since latter is the cached avail
> index from guest but we want to know if there's pending available
> buffers in the virtqueue.
>
> S
Will,
On 07.11.16 21:05:14, Will Deacon wrote:
> Just to reiterate here, but your patch as it stands will break other parts
> of the kernel. For example, acpi_os_ioremap relies on being able to ioremap
> these regions afaict.
>
> I think any solution involving pfn_valid is just going to move the
On 11/09/2016 09:07 AM, Jens Axboe wrote:
On 11/09/2016 01:40 AM, Jan Kara wrote:
So for devices with write cache, you will completely drain the device
before waking anybody waiting to issue new requests. Isn't it too
strict?
In particular may_queue() will allow new writers to issue new writes
o
On 11/09/2016 09:09 AM, Jens Axboe wrote:
On 11/09/2016 02:01 AM, Jan Kara wrote:
On Tue 08-11-16 08:25:52, Jens Axboe wrote:
On 11/08/2016 06:30 AM, Jan Kara wrote:
On Tue 01-11-16 15:08:49, Jens Axboe wrote:
For legacy block, we simply track them in the request queue. For
blk-mq, we track t
On Wed, Nov 09, 2016 at 12:33:35PM -0500, Jeff Layton wrote:
> On Wed, 2016-11-09 at 11:27 -0500, J. Bruce Fields wrote:
> > On Wed, Nov 09, 2016 at 08:18:08AM -0500, Jeff Layton wrote:
> > >
> > > On Tue, 2016-11-08 at 20:27 -0500, J. Bruce Fields wrote:
> > > >
> > > > On Tue, Nov 08, 2016 at 0
Hi Florian,
On Wed, Nov 9, 2016 at 8:17 PM, Florian Fainelli wrote:
> On 11/08/2016 11:50 AM, Geert Uytterhoeven wrote:
>> On Tue, Nov 8, 2016 at 8:42 PM, Florian Fainelli
>> wrote:
>>> On 11/08/2016 11:35 AM, Geert Uytterhoeven wrote:
Currently the renesas-irqc driver uses postcore_initca
On 11/08/2016 10:37 PM, Andrey Konovalov wrote:
> Right now print_stack_trace prints timestamp twice, the first time
> it's done by printk when printing spaces, the second - by print_ip_sym.
> As a result, stack traces in KASAN reports have double timestamps:
> [ 18.822232] Allocated by task 3838
On Wed, Nov 09, 2016 at 11:44:43AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.8.7 release.
> There are 138 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Wed, Nov 09, 2016 at 11:43:38AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.31 release.
> There are 69 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Wed, Nov 09, 2016 at 06:16:13PM +0100, Clemens Gruber wrote:
> Support setting the reference voltage from the device tree.
>
> Signed-off-by: Clemens Gruber
> ---
> drivers/hwmon/mcp3021.c | 46 --
> 1 file changed, 36 insertions(+), 10 deletions(-)
Hi Bjorn,
On 11/02/2016 12:08 PM, Bjorn Helgaas wrote:
> On Tue, Nov 01, 2016 at 07:06:31AM -0600, c...@codeaurora.org wrote:
>> Hi Bjorn,
>>
>> On 2016-10-31 15:48, Bjorn Helgaas wrote:
>>> On Wed, Sep 21, 2016 at 06:38:05PM -0400, Christopher Covington wrote:
The Qualcomm Technologies QDF24
On Wed, Nov 9, 2016 at 4:32 AM, Xin Long wrote:
> this fix may break TYPE_SCTP_PRIMITIVE_SHUTDOWN statetable,
> could you give the following one a try ? thanks.
This one also works.
Thanks.
>
> --- a/net/sctp/socket.c
> +++ b/net/sctp/socket.c
> @@ -4288,9 +4288,9 @@ static void sctp_shutdown(s
Hi,
Looks like commit 883d32ce3385 ("leds: core: Add support for poll()ing
the sysfs brightness attr for changes.") breaks runtime PM for me.
On my omap dm3730 based test system, idle power consumption is over 70
times higher now with this patch! It goes from about 6mW for the core
system to over
On Wed, Nov 09, 2016 at 01:59:07PM -0500, Don Dutile wrote:
> On 11/09/2016 12:03 PM, Will Deacon wrote:
> >On Tue, Nov 08, 2016 at 09:52:33PM -0500, Don Dutile wrote:
> >>On 11/08/2016 06:35 PM, Alex Williamson wrote:
> >>>On Tue, 8 Nov 2016 21:29:22 +0100
> >>>Christoffer Dall wrote:
> Is my
On 11/08/2016 11:50 AM, Geert Uytterhoeven wrote:
> Hi Florian,
>
> On Tue, Nov 8, 2016 at 8:42 PM, Florian Fainelli wrote:
>> On 11/08/2016 11:35 AM, Geert Uytterhoeven wrote:
>>> Currently the renesas-irqc driver uses postcore_initcall().
>>>
>>> However, the new CPG/MSSR driver uses subsys_ini
On Wed, 2016-11-09 at 15:19 +1100, Stephen Rothwell wrote:
> Hi Andrew,
>
> Today's linux-next merge of the akpm tree got a conflict in:
>
> Documentation/admin-guide/kernel-parameters.rst
>
> between commit:
>
> e52347bd66f6 ("Documentation/admin-guide: split the kernel parameter list
> t
On Wed, Nov 09, 2016 at 06:57:43PM +, Will Deacon wrote:
> Hi Paul,
>
> Just a couple of comments, but they be more suited to Andy.
>
> On Wed, Nov 09, 2016 at 09:38:08AM -0800, Paul E. McKenney wrote:
> > @@ -355,10 +373,33 @@ static bool rcu_dynticks_in_eqs_since(struct
> > rcu_dynticks *r
On 2016-11-09 17:27, Peter Rosin wrote:
> On 2016-11-09 14:38, Mark Brown wrote:
>> On Tue, Nov 08, 2016 at 05:20:57PM +0100, Peter Rosin wrote:
>>> + struct snd_soc_pcm_runtime *rtd = substream->private_data;
>>> + struct device *dev = rtd->dev;
>>> + struct snd_soc_dai *cpu_dai = rtd->cpu_d
On Wed, Nov 9, 2016 at 9:36 AM, John Garry wrote:
> On 09/11/2016 12:28, John Garry wrote:
>>
>> On 03/11/2016 14:58, John Garry wrote:
>>>
>>> The following patch introduces an annoying WARN
>>> when a device is removed from the SAS topology:
>>> [SCSI] libsas: prevent domain rediscovery competin
On 11/08/2016 10:37 PM, Andrey Konovalov wrote:
> 1. Change header format.
> 2. Unify header format between different kinds of bad accesses.
> 3. Add empty lines between parts of the report to improve readability.
> 4. Improve slab object description.
> 5. Improve mm/kasan/report.c readability.
>
On Wed, Nov 9, 2016 at 3:09 AM, Jörg Otte wrote:
>
> Tried patch with no success. Again a NULL ptr dereferece.
That patch was pure garbage, I think. Pretty much all the other
drivers that use the same approach will have the same issue. Adding
that init function just for the semaphore is crazy.
I
Idle injection drivers today use RT threads to run idle loop. There are
efficiency and accounting issues with the current intel_powerclamp.c
and acpi_pad.c. A while ago, I posted CFS based idle injection patch trying
to address them:
https://lkml.org/lkml/2015/11/13/576
Peter proposed another appr
With the introduction of play_idle(), idle injection kthread can
go through the normal idle task processing to get correct accounting
and turn off scheduler tick when possible.
Hrtimer is used to wake up since timeout is most likely to occur
during idle injection.
Signed-off-by: Jacob Pan
---
d
When idle injection is used to cap power, we need to override
governor's choice of idle states. This patch allows caller to select
the deepest idle state on a CPU therefore achieve the maximum
potential power saving.
Signed-off-by: Jacob Pan
---
drivers/cpuidle/cpuidle.c | 12
inclu
From: Peter Zijlstra
Idle injection drivers such as Intel powerclamp and ACPI PAD drivers use
realtime tasks to take control of CPU then inject idle. There are two issues
with this approach:
1. Low efficiency: injected idle task is treated as busy so sched ticks do
not stop during injected i
On 11/09/2016 06:06 PM, Brenden Blanco wrote:
On Wed, Nov 09, 2016 at 10:57:32AM +0100, Daniel Borkmann wrote:
On 11/09/2016 10:45 AM, Zhiyi Sun wrote:
On Wed, Nov 09, 2016 at 10:05:31AM +0100, Daniel Borkmann wrote:
On 11/09/2016 08:35 AM, Zhiyi Sun wrote:
There are rx_ring_num queues. Each
From: Kan Liang
The perf per-process monitoring overhead increases rapidly with the
increasing of events# and CPU#.
Here is some data from the overhead test on Skylake server which has 64
logical CPU. Elapsed time of AIM7 is used to measure the overhead.
perf record -e $event_list -p $pi
Linus,
please pull sound fixes for v4.9-rc5 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-4.9-rc5
The topmost commit is 6809cd682b82dfff47943850d1a8c714f971b5ca
sound fixes for 4.9-rc5
this be
On 11/09/2016 12:03 PM, Will Deacon wrote:
On Tue, Nov 08, 2016 at 09:52:33PM -0500, Don Dutile wrote:
On 11/08/2016 06:35 PM, Alex Williamson wrote:
On Tue, 8 Nov 2016 21:29:22 +0100
Christoffer Dall wrote:
Is my understanding correct, that you need to tell userspace about the
location of th
On Wed, Nov 09, 2016 at 08:36:31PM +0900, Tetsuo Handa wrote:
> Hello.
>
> When I build
>
> -- test/test.c --
> #include
>
> static int __init test_init(void)
> {
> DEFINE_SRCU(srcu);
> int idx = srcu_read_lock(&srcu);
> void *ptr = srcu_dereference(ptr,
Hi Paul,
Just a couple of comments, but they be more suited to Andy.
On Wed, Nov 09, 2016 at 09:38:08AM -0800, Paul E. McKenney wrote:
> @@ -355,10 +373,33 @@ static bool rcu_dynticks_in_eqs_since(struct
> rcu_dynticks *rdtp, int snap)
> static void rcu_dynticks_momentary_idle(void)
> {
>
Am Donnerstag, 3. November 2016, 15:21:22 CET schrieb Jaehoon Chung:
> This patchset is modified the some minor fixing and cleaning code.
> If needs to split the patches, i will re-send the patches.
>
> * Major changes
> - Use the cookie enum values like sdhci controller.
> - Remove the unnecessar
On 09/11/16 11:39, Marek Vasut wrote:
On 11/09/2016 07:37 PM, Joel Holdsworth wrote:
On 09/11/16 05:01, Marek Vasut wrote:
On 11/08/2016 06:30 PM, Joel Holdsworth wrote:
On the whole, I don't think the zero-length transfers are too
egregiously bad, and all the alternatives seem worse to me.
On 09/11/16 18:39, Lorenzo Pieralisi wrote:
On Wed, Nov 09, 2016 at 05:43:30PM +, Sudeep Holla wrote:
enter_freeze() callback is expected atleast to do the same as enter()
but it has to guarantee that interrupts aren't enabled at any point
in its execution, as the tick is frozen.
CPUs exe
On Wed, Nov 9, 2016 at 10:30 AM, Mark Rutland wrote:
>> >> I've seen the same iteration slowness problem on x86 with
>> >> CONFIG_DEBUG_RODATA which walks all pages. The is about 1 minute, but
>> >> it is enough to trigger rcu stall warning.
>> >
>> > Interesting; do you know where that happens? I
On 11/09/2016 07:37 PM, Joel Holdsworth wrote:
> On 09/11/16 05:01, Marek Vasut wrote:
>> On 11/08/2016 06:30 PM, Joel Holdsworth wrote:
>> On the whole, I don't think the zero-length transfers are too
>> egregiously bad, and all the alternatives seem worse to me.
>
> So why not tur
2016-11-10 02:42+0800, kbuild test robot:
> Hi Radim,
And I even replied to the series, so this would happen ...
Btw. would the tool recognize it if the header was [PATCH v4 4/4]?
> [auto build test ERROR on kvm/linux-next]
> [also build test ERROR on v4.9-rc4 next-20161109]
> [if y
Hi Adrian/Ulf,
Please ignore my comments in last email I sent out. The v2 patch
documentation matches the code and is good. I am confusing myself
between internal versions and external upstream versions of this code.
On 16-11-09 10:38 AM, Scott Branden wrote:
Hi Adrian/Ulf,
On 16-11-08 01
Hi Radim,
[auto build test ERROR on kvm/linux-next]
[also build test ERROR on v4.9-rc4 next-20161109]
[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/Radim-Kr-m/KVM-x86-emulate-FXSAVE-and
On 11/09/2016 12:04 PM, Sudip Mukherjee wrote:
> Hi Joe,
>
> On 09/11/16 16:00, Joe Lawrence wrote:
>> Hi Sudip,
>>
>> I hit a sysfs_warn_dup inside QEMU running 4.9.0-rc4 (I suspect earlier
>> versions as well, but this is the first upstream I've run in a while).
>> This warning looks like someth
On Wed, 9 Nov 2016, Charles (Chas) Williams wrote:
> On 11/09/2016 11:03 AM, Peter Zijlstra wrote:
> > On Wed, Nov 09, 2016 at 04:35:51PM +0100, Thomas Gleixner wrote:
> > > Both ACPI and MP specifications require that the APIC id in the respective
> > > tables must be the same as the APIC id in CP
On 11/08/16 20:40, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20161108:
>
> The drm-misc tree gained a build failure, so I used the version from
> next-20161108.
>
> The sound-asoc tree still had its build failure, so I used the version
> from next-20161028.
(similar to yesterday, ipv6
Hi Adrian/Ulf,
On 16-11-08 01:55 AM, Adrian Hunter wrote:
On 01/11/16 18:37, Scott Branden wrote:
Add bytewise register accesses support for newer versions of IPROC
SDHCI controllers.
Previous sdhci-iproc versions of SDIO controllers
(such as Raspberry Pi and Cygnus) only allowed for 32-bit reg
On Wed, Nov 09, 2016 at 05:43:30PM +, Sudeep Holla wrote:
> enter_freeze() callback is expected atleast to do the same as enter()
> but it has to guarantee that interrupts aren't enabled at any point
> in its execution, as the tick is frozen.
>
> CPUs execute ->enter_freeze with the local tick
> That's why the hotplug callback mce_disable_cpu() doesn't fiddle with
> CR4 - it only clears the bits in MCi_CTL. And I think we should remain
> that way.
N.B. See vendor_disable_error_reporting() ... on Intel we don't clear MCi_CTL.
-Tony
On 09/11/16 05:01, Marek Vasut wrote:
On 11/08/2016 06:30 PM, Joel Holdsworth wrote:
On the whole, I don't think the zero-length transfers are too
egregiously bad, and all the alternatives seem worse to me.
So why not turn the CS line into GPIO and just toggle the GPIO?
Does that work with *
On Mon, Oct 31, 2016 at 03:45:34PM +0100, Bartosz Golaszewski wrote:
> Create a new driver for the da8xx DDR2/mDDR controller and implement
> support for writing to the Peripheral Bus Burst Priority Register.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> .../memory-controllers/ti-da8xx-ddrctl.t
On Mon, Oct 31, 2016 at 12:30:53PM +0100, Geert Uytterhoeven wrote:
> Add device tree binding documentation for the Common Chip Code Register
> and Product Register, which provide SoC product and revision
> information.
>
> Signed-off-by: Geert Uytterhoeven
> ---
> v2:
> - New.
> ---
> Documen
On Mon, Oct 31, 2016 at 11:49:41AM +0900, Jaehoon Chung wrote:
> Add reset-names property for binding dw-mmc controller.
> It might be used together with "reset" property.
> - Note: It must be "reset" as name.
>
> Fixes: d6786fefe816 ("mmc: dw_mmc: add reset support to dwmmc host
> controller")
On Mon, Oct 31, 2016 at 04:02:03PM +, Steve Twiss wrote:
> From: Steve Twiss
>
> Extend existing DA9062 binding information to include the DA9061 PMIC for
> MFD core and regulators.
>
> Add a da9062-onkey link to the existing onkey binding file.
>
> Add a da9062-thermal link to the new temp
On Wed, Nov 02, 2016 at 09:32:55AM -0500, ttha...@opensource.altera.com wrote:
> From: Thor Thayer
>
> Add the Arria10 DevKit System Resource Chip register and state
> monitoring module to the MFD.
>
> Signed-off-by: Thor Thayer
> ---
> Note: This needs to be applied to the bindings document th
On Wed, Nov 09, 2016 at 10:16:03AM -0800, Dmitry Vyukov wrote:
> On Wed, Nov 9, 2016 at 2:56 AM, Mark Rutland wrote:
> > On Tue, Nov 08, 2016 at 02:09:27PM -0800, Dmitry Vyukov wrote:
> >> On Tue, Nov 8, 2016 at 11:03 AM, Mark Rutland wrote:
> >> I've seen the same iteration slowness problem on x
On Wed, Nov 9, 2016 at 1:10 PM, Jan Kara wrote:
> On Sun 06-11-16 08:45:54, Amir Goldstein wrote:
>> On Sat, Nov 5, 2016 at 11:34 PM, Jan Kara wrote:
>> > On Wed 02-11-16 23:09:26, Miklos Szeredi wrote:
>> >> We've got a report where a fanotify daemon that implements permission
>> >> checks
>> >
On Mon, Oct 31, 2016 at 04:55:26PM +0200, Georgi Djakov wrote:
> Add a driver for the A53 Clock Controller. It is a hardware block that
> implements a combined mux and half integer divider functionality. It can
> choose between a fixed-rate clock or the dedicated A53 PLL. The source
> and the divid
- i2c-list
On 9 November 2016 at 04:14, Yangbo Lu wrote:
> This patchset is used to fix a host version register bug in the
> T4240-R1.0-R2.0
> eSDHC controller. To match the SoC version and revision, 15 previous version
> patchsets had tried many methods but all of them were rejected by reviewer
On Tue, Nov 01, 2016 at 09:37:56AM -0700, Scott Branden wrote:
> Adds brcm,sdhci-iproc compat string to DT bindings document for
> the iProc SDHCI driver.
>
> Signed-off-by: Anup Patel
> Signed-off-by: Scott Branden
> ---
> Documentation/devicetree/bindings/mmc/brcm,sdhci-iproc.txt | 9
On 09/11/2016 07:55 πμ, Viresh Kumar wrote:
> On 08-11-16, 21:25, Stratos Karafotis wrote:
>> But this is the supposed behaviour of conservative governor. We want
>> the CPU to increase the frequency in steps. The patch just resets
>> the frequency to a lower frequency in case of idle.
>>
>> For
From: Philippe Reynes
Date: Sat, 5 Nov 2016 16:17:54 +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.
On Tue, Nov 01, 2016 at 07:52:00PM +0800, Youlin Pei wrote:
> This commit adds the device tree binding document for
> the mediatek cirq.
>
> Signed-off-by: Youlin Pei
> ---
> .../interrupt-controller/mediatek,cirq.txt | 30
>
> 1 file changed, 30 insertions(+)
>
On Mon, Oct 31, 2016 at 05:56:23PM +0100, Neil Armstrong wrote:
> In order to support PHY switching on Amlogic GXL SoCs, add support for
> 16bit and 32bit registers sizes.
>
> Signed-off-by: Neil Armstrong
> ---
> .../devicetree/bindings/net/mdio-mux-mmioreg.txt | 4 +-
> drivers/net/phy/mdio
On Tue, Nov 01, 2016 at 11:58:39AM +0100, Paul Cercueil wrote:
> This document gives information about how to write a devicetree
> node that corresponds to the rfkill-regulator driver.
>
> Signed-off-by: Paul Cercueil
> ---
> .../devicetree/bindings/net/rfkill-regulator.txt | 18
> +++
On Wed, Nov 02, 2016 at 05:56:56PM +0200, Georgi Djakov wrote:
> This adds initial support for clocks controlled by the Resource
> Power Manager (RPM) processor on some Qualcomm SoCs, which use
> the qcom_smd_rpm driver to communicate with RPM.
> Such platforms are msm8916, apq8084 and msm8974.
>
From: Philippe Reynes
Date: Sun, 6 Nov 2016 00:26:41 +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.
From: Philippe Reynes
Date: Sun, 6 Nov 2016 15:02:32 +0100
> When moving from typhoon_get_settings to typhoon_getlink_ksettings
> in the commit f7a5537cd2a5 ("net: 3com: typhoon: use new api
> ethtool_{get|set}_link_ksettings"), we use a local variable supported
> but we forgot to update the str
On Thu, Nov 03, 2016 at 11:39:21AM +0100, Jacek Anaszewski wrote:
> On 11/03/2016 11:10 AM, Andi Shyti wrote:
> > Hi Jacek,
> >
> > > Only DT bindings of LED class drivers should be placed in
> > > Documentation/devicetree/bindings/leds. Please move it to the
> > > media bindings.
> >
> > that's
On Thu, Nov 03, 2016 at 01:07:57AM +1030, Andrew Jeffery wrote:
> The Aspeed SoC Display Controller is presented as a syscon device to
> arbitrate access by display and pinmux drivers. Video pinmux
> configuration on fifth generation SoCs depends on bits in both the
> System Control Unit and the Di
On Thu, Nov 03, 2016 at 01:07:59AM +1030, Andrew Jeffery wrote:
> The System Control Unit IP block in the Aspeed SoCs is typically where
> the pinmux configuration is found, but not always. A number of pins
> depend on state in one of LPC Host Control (LPCHC) or SoC Display
> Controller (GFX) IP bl
On Wed, Nov 02, 2016 at 05:56:57PM +0200, Georgi Djakov wrote:
> This adds initial support for clocks controlled by the Resource
> Power Manager (RPM) processor on some Qualcomm SoCs, which use
> the qcom_rpm driver to communicate with RPM.
> Such platforms are apq8064 and msm8960.
>
> Signed-off-
On Wed, Nov 02, 2016 at 03:02:37PM +0100, Neil Armstrong wrote:
> Signed-off-by: Neil Armstrong
> ---
> .../devicetree/bindings/net/oxnas-dwmac.txt| 39
> ++
> 1 file changed, 39 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/oxnas-dwmac.txt
From: Philippe Reynes
Date: Sun, 6 Nov 2016 14:57:04 +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.
From: Philippe Reynes
Date: Sat, 5 Nov 2016 20:17:03 +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.
On Mon, Oct 31, 2016 at 04:02:03PM +, Steve Twiss wrote:
> From: Steve Twiss
>
> Device tree binding information for DA9062 and DA9061 thermal junction
> temperature monitor.
>
> Binding descriptions for the DA9061 and DA9062 thermal TJUNC supervisor
> device driver, using a single THERMAL_T
On Mon, Oct 31, 2016 at 04:55:24PM +0200, Georgi Djakov wrote:
> Add support for the PLL, which generates the higher range of CPU
> frequencies on MSM8916 platforms.
>
> Signed-off-by: Georgi Djakov
> ---
> .../devicetree/bindings/clock/qcom,a53pll.txt | 20 +
> drivers/clk/qcom/Kconfig
From: Philippe Reynes
Date: Sat, 5 Nov 2016 14:05:39 +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.
On Mon, Oct 31, 2016 at 04:02:03PM +, Steve Twiss wrote:
> From: Steve Twiss
>
> Add binding information for DA9062 and DA9061 watchdog.
>
> Example bindings for both DA9062 and DA9061 devices are added. For
> the DA9061 device, a fallback compatible line is added as a valid
> combination of
On Mon, Oct 31, 2016 at 12:09:54PM +0100, Gregory CLEMENT wrote:
> From: Ziji Hu
>
> Marvell Xenon SDHC can support eMMC/SD/SDIO.
> Add Xenon-specific properties.
> Also add properties for Xenon PHY setting.
>
> Signed-off-by: Hu Ziji
> Signed-off-by: Gregory CLEMENT
> ---
> Documentation/dev
On Mon, Oct 31, 2016 at 03:45:35PM +0100, Bartosz Golaszewski wrote:
> Create the driver for the da8xx master peripheral priority
> configuration and implement support for writing to the three
> Master Priority registers on da850 SoCs.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> .../devicetre
On Mon, Oct 31, 2016 at 04:02:02PM +, Steve Twiss wrote:
> From: Steve Twiss
>
> Add binding information for DA9061 onkey.
>
> This patch updates the compatible string "dlg,da9061-onkey" to support
> DA9061, removes the reference to KEY_SLEEP (which the driver no longer
> supports) and fixes
On 11/09/2016 03:43 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.31 release.
> There are 69 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sh
On 11/09/2016 03:44 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.8.7 release.
> There are 138 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sh
301 - 400 of 965 matches
Mail list logo
