On Fri, Sep 25, 2015 at 09:47:26AM -0700, Mark Brown wrote:
> On Fri, Sep 25, 2015 at 11:07:24AM +0200, Sascha Hauer wrote:
>
> > Any idea how such a scenario could be implemented? The regulator
> > framework already has some idea of supply regulators, but it only takes
> > care of en/disabling th
On 2015/09/29 08:53AM, Jiri Olsa wrote:
> On Tue, Sep 29, 2015 at 11:06:17AM +0530, Naveen N. Rao wrote:
> > On 2015/09/24 10:15PM, Naveen N Rao wrote:
> > > On 2015/09/24 08:32AM, Stephane Eranian wrote:
> > > > On Thu, Sep 24, 2015 at 5:57 AM, Jiri Olsa wrote:
> > > > >
> > > > > On Thu, Sep 24,
On Mon, 28 Sep 2015 15:50:38 -0700
Frank Rowand wrote:
> On 9/28/2015 9:42 AM, Marc Zyngier wrote:
> > We want to be able to generate "fake" device nodes that can be
> > used as an identifier for irq domains. For that, we reuse the
> > dynamic DT layer in order to generate DT nodes in a detached
On 26 September 2015 at 20:15, Rob Herring wrote:
> On 09/21/2015 09:03 AM, Tomeu Vizoso wrote:
>> Add a field to struct device that instructs the device-driver core to
>> defer the probe of this device until the late_initcall level.
>
> This is true until the next patch with moves deferred probe
> IW_AUTH_ALG_OPEN_SYSTEM is ambiguous in set_auth for WEP as
> wpa_supplicant uses it for both no encryption and WEP open system.
> Cache the last mode set (only of these two) and use it here.
>
> This allows wpa_supplicant to work with unencrypted APs.
>
> Signed-off-by: Ondrej Zary
Thanks,
On 26 September 2015 at 20:17, Rob Herring wrote:
> On 09/21/2015 09:02 AM, Tomeu Vizoso wrote:
>> Hello,
>>
>> I have a problem with the panel on my Tegra Chromebook taking longer
>> than expected to be ready during boot (Stéphane Marchesin reported what
>> is basically the same issue in [0]), an
Commit-ID: 30f2136346cab91e1ffd9ee6370d76809f20487a
Gitweb: http://git.kernel.org/tip/30f2136346cab91e1ffd9ee6370d76809f20487a
Author: Robert Richter
AuthorDate: Mon, 21 Sep 2015 22:58:34 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 29 Sep 2015 10:10:53 +0200
irqchip/gicv3-its: Ad
Commit-ID: c14e36733b8a63894db9ca0b486ce14299ef2fda
Gitweb: http://git.kernel.org/tip/c14e36733b8a63894db9ca0b486ce14299ef2fda
Author: Robert Richter
AuthorDate: Mon, 21 Sep 2015 22:58:36 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 29 Sep 2015 10:10:53 +0200
irqchip/gicv3-its: Re
Commit-ID: 67510ccafb9d69e79079b5cd6c9959025bc02061
Gitweb: http://git.kernel.org/tip/67510ccafb9d69e79079b5cd6c9959025bc02061
Author: Robert Richter
AuthorDate: Mon, 21 Sep 2015 22:58:37 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 29 Sep 2015 10:10:53 +0200
irqchip/gicv3-its: Ad
Commit-ID: 6d4e11c5e2e8cd54a035ba395bf8ccfa7e22cfd8
Gitweb: http://git.kernel.org/tip/6d4e11c5e2e8cd54a035ba395bf8ccfa7e22cfd8
Author: Robert Richter
AuthorDate: Mon, 21 Sep 2015 22:58:35 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 29 Sep 2015 10:10:53 +0200
irqchip/gicv3: Workar
Commit-ID: 8ac2a1704a9f315d490ca1050b8fe8367644e675
Gitweb: http://git.kernel.org/tip/8ac2a1704a9f315d490ca1050b8fe8367644e675
Author: Robert Richter
AuthorDate: Mon, 21 Sep 2015 22:58:39 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 29 Sep 2015 10:10:54 +0200
irqchip/gicv3-its: Us
On 28/09/15 23:08, Arnaldo Carvalho de Melo wrote:
> Em Fri, Sep 25, 2015 at 04:15:48PM +0300, Adrian Hunter escreveu:
>> Adjust the validation to allow for max_stack greater than
>> PERF_MAX_STACK_DEPTH.
>>
>> Signed-off-by: Adrian Hunter
>> ---
>> tools/perf/util/machine.c | 2 +-
>> 1 file cha
Commit-ID: 94100970743365a9f9e186520e77ef56c492058d
Gitweb: http://git.kernel.org/tip/94100970743365a9f9e186520e77ef56c492058d
Author: Robert Richter
AuthorDate: Mon, 21 Sep 2015 22:58:38 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 29 Sep 2015 10:10:54 +0200
irqchip/gicv3-its: Wo
On Mon, 2015-09-28 at 04:17 +0200, Mike Galbraith wrote:
> Hi Peter,
>
> I bumped into an odd futextest regression, and finally bisected it to
> $subject. I haven't poked at it yet, chasing down and confirming the
> little bugger munched the day.
homer:/home/git/futextest/functional # ./futex_re
Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Cheers,
Vinson
Hi.
This build error still occurs with next-20150929.
attached patch should fix it
FYI there
On Mo, 2015-09-28 at 14:36 +0200, Daniel Vetter wrote:
> On Mon, Sep 28, 2015 at 09:39:13AM +0200, Gerd Hoffmann wrote:
> > Hi,
> >
> > > As Daniel mentioned, the connector+encoder+crtc combination is one of
> > > those simplifications that would make sense if more such drivers are
> > > added.
Introduce an optional hardware maximum timeout in the watchdog core.
The hardware maximum timeout can be lower than the maximum timeout.
Drivers can set the maximum hardware timeout value in the watchdog data
structure. If the configured timeout exceeds the maximum hardware timeout,
the watchdog c
Up to now, a new timeout value is only evaluated against min_timeout
if max_timeout is provided. This does not really make sense; a driver
can have a minimum timeout even if it does not have a maximum timeout.
Ensure that it is not smaller than min_timeout, even if max_timeout
is not set.
Signed-o
The watchdog infrastructure is currently purely passive, meaning
it only passes information from user space to drivers and vice versa.
Since watchdog hardware tends to have its own quirks, this can result
in quite complex watchdog drivers. A number of scanarios are especially common.
- A watchdog
For some watchdogs, the hardware timeout is fixed, and the
watchdog driver depends on the watchdog core to handle the
actual timeout. In this situation, the watchdog driver might
only set the 'timeout' variable but do nothing else.
This can as well be handled by the infrastructure, so make
the set_
The current code uses 'wdd', wddev', and 'watchdog' as variable names
for struct watchdog_device. This is confusing and makes it difficult
to enhance the code. Replace it all with 'wdd'.
Cc: Timo Kokkonen
Acked-by: Uwe Kleine-König
Signed-off-by: Guenter Roeck
---
v2: No changes
---
drivers/w
The WDOG_RUNNING flag is expected to be set by watchdog drivers if
the hardware watchdog is running. If the flag is set, the watchdog
subsystem will ping the watchdog even if the watchdog device is closed.
The watchdog driver stop function is now optional and may be omitted
if the watchdog can not
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
Convert the driver to use this infrastructure.
Signed-off-by: Guenter Roeck
---
v3: No changes
v2: No changes
---
drivers/watchdog/imx2_wdt.c | 72
Some watchdogs require a minimum time between heartbeats.
Examples are the watchdogs in DA9062 and AT91SAM9x.
Signed-off-by: Guenter Roeck
---
Documentation/watchdog/watchdog-kernel-api.txt | 4
drivers/watchdog/watchdog_dev.c| 12
include/linux/watchdog.h
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
Convert the driver to use this infrastructure.
Signed-off-by: Guenter Roeck
---
v3: No changes
v2: No changes
---
drivers/watchdog/retu_wdt.c | 78
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
The infrastructure now also supports generating additional heartbeats
if the maximum hardware timeout is smaller than or close to the
configured timeout. Convert the
2015-09-29 15:16 GMT+08:00 Lee Jones :
> On Tue, 29 Sep 2015, Barry Song wrote:
>> >> >> +static int sirfsoc_pwrc_probe(struct platform_device *pdev)
>> >> >> +{
>> >> >> + struct device_node *np = pdev->dev.of_node;
>> >> >> + const struct of_device_id *match;
>> >> >> + struct sirfsoc
Hi Gerd,
On Tuesday 29 September 2015 10:23:23 Gerd Hoffmann wrote:
> On Mo, 2015-09-28 at 14:36 +0200, Daniel Vetter wrote:
> > On Mon, Sep 28, 2015 at 09:39:13AM +0200, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > As Daniel mentioned, the connector+encoder+crtc combination is one of
> > > >
RUC_Soft_Sec writes:
> Current code assigns 0 to variable 'retval', which makes ezusb_probe() to
> return success even if alloc_orinocodev() fails.
>
> The related code snippets in mantis_dma_init() is as following.
>
> 1573 static int ezusb_probe(struct usb_interface *interface,
> 1574
The AD1934 codec has no DAC feature. Hence it register mapping is slightly
different from the register mapping of other members of the AD193x family.
Some ASoC controls and widgets are related to the DAC feature so are not
relevant in the case of an AD1934 codec.
Signed-off-by: Cyrille Pitchen
-
Commit-ID: cfc5acd4c80b875d2f739d6a93562034aee5563f
Gitweb: http://git.kernel.org/tip/cfc5acd4c80b875d2f739d6a93562034aee5563f
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 23 Sep 2015 15:15:54 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 15:50:53 -0300
pe
Commit-ID: 045b80dd03403b8e61a29460987c231317ebfbd4
Gitweb: http://git.kernel.org/tip/045b80dd03403b8e61a29460987c231317ebfbd4
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 23 Sep 2015 15:38:55 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 15:50:54 -0300
pe
On Mon, Sep 28, 2015 at 3:42 PM, Maxime Ripard
wrote:
> Hi Priit,
>
> On Tue, Sep 22, 2015 at 04:26:57PM +0300, Priit Laes wrote:
>> On Sat, 2015-09-12 at 15:26 +0200, Maxime Ripard wrote:
>> > Hi everyone,
>> >
>> > This patch set adds the support for what Allwinner calls the codec on
>> > their
Commit-ID: dc240c5dc2a02e335c5bcb50ad3a1274818c8609
Gitweb: http://git.kernel.org/tip/dc240c5dc2a02e335c5bcb50ad3a1274818c8609
Author: Jiri Olsa
AuthorDate: Sat, 19 Sep 2015 16:47:07 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 15:50:54 -0300
tools lib api fs:
Commit-ID: ab9c2bdc8947482057b81258c0128952763661cb
Gitweb: http://git.kernel.org/tip/ab9c2bdc8947482057b81258c0128952763661cb
Author: Arnaldo Carvalho de Melo
AuthorDate: Wed, 23 Sep 2015 15:45:20 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 15:50:54 -0300
pe
* Andrey Ryabinin wrote:
> In not-instrumented code KASAN replaces instrumented
> memset/memcpy/memmove with not-instrumented analogues
> __memset/__memcpy/__memove.
> However, on x86 the EFI stub is not linked with the kernel.
> It uses not-instrumented mem*() functions from
> arch/x86/boot/com
Commit-ID: 0d44975d1e2791f6df2b84b182f49d815ba3c9e0
Gitweb: http://git.kernel.org/tip/0d44975d1e2791f6df2b84b182f49d815ba3c9e0
Author: Denys Vlasenko
AuthorDate: Sat, 26 Sep 2015 14:47:17 +0200
Committer: Ingo Molnar
CommitDate: Mon, 28 Sep 2015 10:13:31 +0200
x86/kgdb: Replace bool_in
Commit-ID: ab6201d09b1840c7ffcd6606c1d3dae68b8b3048
Gitweb: http://git.kernel.org/tip/ab6201d09b1840c7ffcd6606c1d3dae68b8b3048
Author: Jiri Olsa
AuthorDate: Wed, 23 Sep 2015 12:33:56 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 15:50:54 -0300
tools build: Add
Commit-ID: 0c00c3fb4e4a6ff714b7ad864f58e0fb33b3534c
Gitweb: http://git.kernel.org/tip/0c00c3fb4e4a6ff714b7ad864f58e0fb33b3534c
Author: Jiri Olsa
AuthorDate: Wed, 23 Sep 2015 12:33:57 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 15:50:54 -0300
tools build: Add
Commit-ID: 9f7ef9854e800bc3bab3d9a527e8f8f960eec1a6
Gitweb: http://git.kernel.org/tip/9f7ef9854e800bc3bab3d9a527e8f8f960eec1a6
Author: Jiri Olsa
AuthorDate: Wed, 23 Sep 2015 12:33:58 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 15:50:55 -0300
tools build: Add
Commit-ID: 9fb81323eb3085b6a47fe81d78541958ae7eaea3
Gitweb: http://git.kernel.org/tip/9fb81323eb3085b6a47fe81d78541958ae7eaea3
Author: Jiri Olsa
AuthorDate: Wed, 23 Sep 2015 12:34:00 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 15:50:55 -0300
tools build: Make
Commit-ID: 324c824ade1cad094a21e6177b9aa7977146feeb
Gitweb: http://git.kernel.org/tip/324c824ade1cad094a21e6177b9aa7977146feeb
Author: Jiri Olsa
AuthorDate: Wed, 23 Sep 2015 12:34:01 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 15:50:55 -0300
perf tools: Renam
Commit-ID: 6e06780a98f149f131d46c1108d4ae27f05a9357
Gitweb: http://git.kernel.org/tip/6e06780a98f149f131d46c1108d4ae27f05a9357
Author: Ashok Raj
AuthorDate: Mon, 28 Sep 2015 09:21:43 +0200
Committer: Ingo Molnar
CommitDate: Mon, 28 Sep 2015 10:15:26 +0200
x86/mce: Don't clear shared ba
Commit-ID: 9992c2d50a73f442653968a98a9e5f3bf4e769e9
Gitweb: http://git.kernel.org/tip/9992c2d50a73f442653968a98a9e5f3bf4e769e9
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:34 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:44:31 -0300
perf intel-pt
Commit-ID: 7c422f5572667fef0db38d2046ecce69dcf0afc8
Gitweb: http://git.kernel.org/tip/7c422f5572667fef0db38d2046ecce69dcf0afc8
Author: Jiri Olsa
AuthorDate: Wed, 23 Sep 2015 12:34:02 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 15:50:55 -0300
tools build: Buil
Commit-ID: 116f349c5bf8c7aec4047dd6e06c310354b46e4f
Gitweb: http://git.kernel.org/tip/116f349c5bf8c7aec4047dd6e06c310354b46e4f
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:35 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:45:26 -0300
perf intel-pt
* Oleg Nesterov wrote:
> On 09/22, Linus Torvalds wrote:
> >
> > However, this now becomes a pattern for the series, and that just makes me
> > think
> >
> > "Why is this not a 'for_each_mm()' pattern helper?"
>
> And we already have other users. And note that oom_kill_process() does _not_
Commit-ID: a38f48e300f9dac30a9b2d2ce958c8dbd7def351
Gitweb: http://git.kernel.org/tip/a38f48e300f9dac30a9b2d2ce958c8dbd7def351
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:37 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:51:33 -0300
perf session:
Commit-ID: 35ca01c117da9b8e5b60204f730cdde414735596
Gitweb: http://git.kernel.org/tip/35ca01c117da9b8e5b60204f730cdde414735596
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:38 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:53:07 -0300
perf tools: A
On 09/29/2015 10:36 AM, Cyrille Pitchen wrote:
> The AD1934 codec has no DAC feature. Hence it register mapping is slightly
> different from the register mapping of other members of the AD193x family.
>
> Some ASoC controls and widgets are related to the DAC feature so are not
> relevant in the ca
Commit-ID: 83e1986032dfcd3f9e9fc0d06e11d9153edae19b
Gitweb: http://git.kernel.org/tip/83e1986032dfcd3f9e9fc0d06e11d9153edae19b
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:36 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:46:05 -0300
perf script:
Commit-ID: c7eced63f2f67bd06ceb2269062416db9d81d29d
Gitweb: http://git.kernel.org/tip/c7eced63f2f67bd06ceb2269062416db9d81d29d
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:40 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:54:21 -0300
perf report:
Commit-ID: fb9fab66e6e3ee737e521c899684c6d684b24a22
Gitweb: http://git.kernel.org/tip/fb9fab66e6e3ee737e521c899684c6d684b24a22
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:41 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:54:45 -0300
perf report:
* Linus Torvalds wrote:
> On Mon, Sep 21, 2015 at 11:23 PM, Ingo Molnar wrote:
> > xen_mm_pin_all()/unpin_all() are used to implement full guest instance
> > suspend/restore. It's a stop-all method that needs to iterate through
> > all allocated pgds in the system to fix them up for Xen's use.
Commit-ID: 601897b54c7ed492a89b262dccd7c6f7faf12b30
Gitweb: http://git.kernel.org/tip/601897b54c7ed492a89b262dccd7c6f7faf12b30
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:39 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:53:44 -0300
perf auxtrace
Commit-ID: 051a01b9a2c1c1ef3049973a43d9ed4ddcc946f3
Gitweb: http://git.kernel.org/tip/051a01b9a2c1c1ef3049973a43d9ed4ddcc946f3
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:43 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:57:59 -0300
perf inject:
interrupts-names => interrupt-names
Other line changes are re-aligning.
Signed-off-by: Lee Jones
---
.../bindings/memory-controllers/renesas-memory-controllers.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
a/Documentation/devicetree/bindings/memory-controller
Commit-ID: f86225db3aa0e394915af45eea1c3cca6f3e2dba
Gitweb: http://git.kernel.org/tip/f86225db3aa0e394915af45eea1c3cca6f3e2dba
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:42 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:57:01 -0300
perf report:
Commit-ID: f14445ee72c59f32aa5cbf4d0f0330a5f62a752d
Gitweb: http://git.kernel.org/tip/f14445ee72c59f32aa5cbf4d0f0330a5f62a752d
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:45 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:59:14 -0300
perf intel-pt
Commit-ID: 188bb5e2ce112463428994f91291e5df6fc05521
Gitweb: http://git.kernel.org/tip/188bb5e2ce112463428994f91291e5df6fc05521
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:46 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:03:20 -0300
perf report:
Commit-ID: 03cd1fed2b8730271d3a8dbabd87989abddc33c4
Gitweb: http://git.kernel.org/tip/03cd1fed2b8730271d3a8dbabd87989abddc33c4
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:49 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:08:48 -0300
perf script:
Commit-ID: 96b40f3c05f36e061fd4dde920b9e9c795a88b69
Gitweb: http://git.kernel.org/tip/96b40f3c05f36e061fd4dde920b9e9c795a88b69
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:47 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:06:16 -0300
perf hists: A
Commit-ID: 44cbe7295c3808977159f500a5bcdebf12a7db5f
Gitweb: http://git.kernel.org/tip/44cbe7295c3808977159f500a5bcdebf12a7db5f
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:50 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:09:12 -0300
perf scriptin
On Wed, 2015-09-23 at 11:38 +0200, Daniel Vetter wrote:
> On Wed, Sep 23, 2015 at 11:18 AM, Ander Conselvan De Oliveira
> wrote:
> > On Wed, 2015-09-23 at 10:24 +0200, Daniel Vetter wrote:
> > > On Tue, Sep 15, 2015 at 04:08:53PM +0300, Ander Conselvan De Oliveira
> > > wrote:
> > > > On Mon, 20
Commit-ID: dddcf6abbf5946f9ec1183dd2099cede6dbe12fc
Gitweb: http://git.kernel.org/tip/dddcf6abbf5946f9ec1183dd2099cede6dbe12fc
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:52 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:11:00 -0300
perf evlist:
Commit-ID: 4768230ad57d4e4fc6d36c44e98e0062c89b0dc0
Gitweb: http://git.kernel.org/tip/4768230ad57d4e4fc6d36c44e98e0062c89b0dc0
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:53 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:15:31 -0300
perf evlist:
Commit-ID: f56fb9864c501dc85ebe40af5bf925dd07d990c0
Gitweb: http://git.kernel.org/tip/f56fb9864c501dc85ebe40af5bf925dd07d990c0
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:55 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:19:51 -0300
perf inject:
Commit-ID: 73117308f953afb60a1383725b7d5372feeb2433
Gitweb: http://git.kernel.org/tip/73117308f953afb60a1383725b7d5372feeb2433
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:54 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:17:15 -0300
perf inject:
Commit-ID: 3c5b645faee7afbd417f6127694adbd26778a9eb
Gitweb: http://git.kernel.org/tip/3c5b645faee7afbd417f6127694adbd26778a9eb
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:51 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:09:41 -0300
perf script:
Commit-ID: 385e33063fb963f5cccb0a37fe539319b6481fa5
Gitweb: http://git.kernel.org/tip/385e33063fb963f5cccb0a37fe539319b6481fa5
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:44 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:58:27 -0300
perf intel-pt
Commit-ID: ba11ba65e02836c475427ae199adfc2d8cc4a900
Gitweb: http://git.kernel.org/tip/ba11ba65e02836c475427ae199adfc2d8cc4a900
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:56 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:21:00 -0300
perf intel-pt
Commit-ID: 0b8891a8e62cb537b65ebc55cfbbb4ec22333c44
Gitweb: http://git.kernel.org/tip/0b8891a8e62cb537b65ebc55cfbbb4ec22333c44
Author: He Kuang
AuthorDate: Mon, 28 Sep 2015 03:52:13 +
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:25:53 -0300
perf tools: Adds t
David Ahern writes:
> On 9/23/15 6:37 PM, Huang Ying wrote:
>>>
>>> I take it you have CONFIG_NET_VRF enabled. correct?
>>>
>>> With it disabled I see no relevant change in performance between
>>> 8f58336d3f78 and 192132b9a034. Can you confirm?
>>
>> The kconfig file is attached with the mail. I
Commit-ID: ffeb883e5662e94b14948078e85812261277ad67
Gitweb: http://git.kernel.org/tip/ffeb883e5662e94b14948078e85812261277ad67
Author: He Kuang
AuthorDate: Mon, 28 Sep 2015 03:52:14 +
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:26:54 -0300
perf tools: Show p
Commit-ID: 865582c3f48e12b7ab9e260161868313e4a37f44
Gitweb: http://git.kernel.org/tip/865582c3f48e12b7ab9e260161868313e4a37f44
Author: He Kuang
AuthorDate: Mon, 28 Sep 2015 03:52:15 +
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:29:38 -0300
perf tools: Adds t
On Tue, Sep 29, 2015 at 01:27:24AM -0700, Guenter Roeck wrote:
> Up to now, a new timeout value is only evaluated against min_timeout
> if max_timeout is provided. This does not really make sense; a driver
> can have a minimum timeout even if it does not have a maximum timeout.
> Ensure that it is
On 2015/9/27 0:46, Borislav Petkov wrote:
> On Wed, Sep 23, 2015 at 06:18:39PM +0200, Borislav Petkov wrote:
>> On Wed, Sep 23, 2015 at 06:06:21PM +0200, Borislav Petkov wrote:
>>> On Wed, Sep 23, 2015 at 04:44:50PM +0200, Daniel Vetter wrote:
sorry I sprinkled the locking stuff in the wrong p
Commit-ID: e637d17757a10732fa5d573c18f20b3cd4d31245
Gitweb: http://git.kernel.org/tip/e637d17757a10732fa5d573c18f20b3cd4d31245
Author: He Kuang
AuthorDate: Mon, 28 Sep 2015 03:52:16 +
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 17:30:07 -0300
perf tools: Enable
Commit-ID: 275e2d95591e2714d6b541d4e26959381d6b2705
Gitweb: http://git.kernel.org/tip/275e2d95591e2714d6b541d4e26959381d6b2705
Author: Jiri Olsa
AuthorDate: Wed, 23 Sep 2015 12:33:59 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 15:50:55 -0300
tools build: Move
Commit-ID: e1791347b5d57d13326cf0114df1a3f3b1c4ca24
Gitweb: http://git.kernel.org/tip/e1791347b5d57d13326cf0114df1a3f3b1c4ca24
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:32 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 15:50:56 -0300
perf auxtrace
Hi Minfei,
On Tue, Sep 29, 2015 at 11:50:44AM +0800, Minfei Huang wrote:
> On 09/28/15 at 02:41pm, Lee, Chun-Yi wrote:
> > On big machines have CPU number that's very nearly to consume whole ELF
> > headers buffer that's page aligned, 4096, 8192... Then the page fault error
> > randomly happened.
Commit-ID: d062ac16f53d1a24047bcc9eded5514a71c363b8
Gitweb: http://git.kernel.org/tip/d062ac16f53d1a24047bcc9eded5514a71c363b8
Author: Adrian Hunter
AuthorDate: Fri, 25 Sep 2015 16:15:33 +0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 28 Sep 2015 16:42:38 -0300
perf report:
On 29.09.2015 10:44, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> git://internal_merge_and_test_tree
> revert-482eaa50ff81046e1e9f95af94176953d0743ec9-482eaa50ff81046e1e9f95af94176953d0743ec9
> commit 482eaa50ff81046e1e9f95af94176953d0743ec9 ("sched/fair: Skip
> wake_affin
interrupts-names => interrupt-names
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/stih407-pinctrl.dtsi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/stih407-pinctrl.dtsi
b/arch/arm/boot/dts/stih407-pinctrl.dtsi
index 1683deb..7992063 100644
--- a
On Tue, 29 Sep 2015, Barry Song wrote:
> 2015-09-29 15:16 GMT+08:00 Lee Jones :
> > On Tue, 29 Sep 2015, Barry Song wrote:
> >> >> >> +static int sirfsoc_pwrc_probe(struct platform_device *pdev)
> >> >> >> +{
> >> >> >> + struct device_node *np = pdev->dev.of_node;
> >> >> >> + const struc
On 28/09/15 23:03, Arnaldo Carvalho de Melo wrote:
> Em Fri, Sep 25, 2015 at 04:15:46PM +0300, Adrian Hunter escreveu:
>> perf report has an option (--max-stack) to set the maximum stack depth
>> when processing callchains. The option defaults to the hard-coded
>> maximum definition PERF_MAX_STACK
On 29/09/2015 03:15, Wanpeng Li wrote:
>>>
>> Hi Wanpeng, the comment above is about invept, but the same applies
>> applies to invvpid. We can set only VMX_VPID_EXTENT_GLOBAL_CONTEXT_BIT.
>
> Agreed. I see the patch has already in kvm/queue, if I need to send out
> another patch or you can adj
On Tue, Sep 29, 2015 at 10:19:51AM +0200, Mike Galbraith wrote:
> On Mon, 2015-09-28 at 04:17 +0200, Mike Galbraith wrote:
> > Hi Peter,
> >
> > I bumped into an odd futextest regression, and finally bisected it to
> > $subject. I haven't poked at it yet, chasing down and confirming the
> > littl
* Denys Vlasenko wrote:
> On 09/28/2015 09:58 AM, Ingo Molnar wrote:
> >
> > * Denys Vlasenko wrote:
> >
> >> On 09/26/2015 09:50 PM, H. Peter Anvin wrote:
> >>> NAK. We really should map the GDT read-only on all 64 bit systems,
> >>> since we can't hide the address from SLDT. Same with the
On Sep 28 2015 or thereabouts, Mika Westerberg wrote:
> Some newer Intel Skylake based Dell laptops with Win8 precision touchpad
> fail when initial feature reports are fetched from it. Below is an example
> output with some additional debug included:
>
> i2c_hid i2c-DLL0704:01: Fetching the HID
Hello,
I have a problem with the panel on my Tegra Chromebook taking longer
than expected to be ready during boot (Stéphane Marchesin reported what
is basically the same issue in [0]), and have looked into ordered
probing as a better way of solving this than moving nodes around in the
DT or playin
Reading the periphid when the Primecell device is registered means that
the apb pclk must be available by then or the device won't be registered
at all.
By reading the periphid in amba_match() we can return -EPROBE_DEFER if
the apb pclk isn't there yet and the device will be retried later.
Signed
When looking up a regulator through its OF node, probe it if it hasn't
already.
The goal is to reduce deferred probes to a minimum, as it makes it very
cumbersome to find out why a device failed to probe, and can introduce
very big delays in when a critical device is probed.
Signed-off-by: Tomeu
When adding platform and AMBA devices, set the device node's device
member to point to it.
This speeds lookups considerably and is safe because we only create one
of these devices for any given device node.
Signed-off-by: Tomeu Vizoso
---
Changes in v5:
- Set the pointer to struct device also f
Lets implementations of the match() callback in struct bus_type to
return errors and if it's -EPROBE_DEFER then queue the device for
deferred probing.
This is useful to buses such as AMBA in which devices are registered
before their matching information can be retrieved from the HW
(typically beca
When looking up a pin controller through its OF node, probe it if it
hasn't already.
The goal is to reduce deferred probes to a minimum, as it makes it very
cumbersome to find out why a device failed to probe, and can introduce
very big delays in when a critical device is probed.
Signed-off-by: T
Add a field to struct device that instructs the device-driver core to
defer the probe of this device until the late_initcall level.
By letting all built-in drivers to register before starting to probe, we
can avoid any deferred probes by probing dependencies on demand.
Signed-off-by: Tomeu Vizoso
When looking up a panel through its OF node, probe it if it hasn't
already.
The goal is to reduce deferred probes to a minimum, as it makes it very
cumbersome to find out why a device failed to probe, and can introduce
very big delays in when a critical device is probed.
Signed-off-by: Tomeu Vizo
When looking up an i2c adapter or device through its OF node, probe it
if it hasn't already.
The goal is to reduce deferred probes to a minimum, as it makes it very
cumbersome to find out why a device failed to probe, and can introduce
very big delays in when a critical device is probed.
Signed-o
* Ard Biesheuvel wrote:
> > except that I don't think
> > the condition on 64-bit makes any sense:
> >
> > + if (!efi_enabled(EFI_OLD_MEMMAP) && efi_enabled(EFI_64BIT)) {
> >
> > I can see us being nervous wrt. backported patches, but is there any strong
> > reason
> > to not follow this
1 - 100 of 1100 matches
Mail list logo