Hi George,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.12]
[cannot apply to next-20170704]
[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/vitaly_kuzmichev
On Tue, Jul 4, 2017 at 1:22 AM, Peter Rosin wrote:
> The MULTIPLEXER question in the Kconfig might be confusing and is
> of dubious value. Remove it. This makes consumers responsible for
> selecting MULTIPLEXER, which they already do.
Yes, this looks good to me.
Still no actual
On 07/04/2017 10:44 PM, Joe Perches wrote:
> On Tue, 2017-07-04 at 21:29 +0200, Heinrich Schuchardt wrote:
>> The U-Boot project uses the same scripts/checkpatch.pl as the Linux
>> kernel. I ran upon the problem below when working on U-Boot. But I
>> guess it should be fixed in the Linux upstream.
On Wed, 28 Jun 2017, Marc Zyngier wrote:
> When assigning an interrupt to a vcpu, it is not unlikely that
> the level of the hierarchy implementing irq_set_vcpu_affinity
> is not the top level (think a generic MSI domain on top of a
> virtualization aware interrupt controller).
>
> In such a
On 06/30/2017 09:49 AM, sean.w...@mediatek.com wrote:
From: Sean Wang
This updates dt-binding documentation for MediaTek MT7622 and
MT7623 SoC. For the both SoCs supported all rely on the fallback
binding of the generic case with "mediatek,efuse".
Signed-off-by: Sean
Remove unnecessary static on local variable _map_.
Such variable is initialized before being used,
on every execution path throughout the function.
The static has no benefit and, removing it reduces
the code size.
This issue was detected using Coccinelle and the following semantic patch:
@bad
Hi Mathieu,
I noticed this morning some commits in the coresight tree that have no
Signed-off-by tags for you as the committer. Please fix these up before
asking your upstream to merge your tree.
--
Cheers,
Stephen Rothwell
Hi Guenter,
On Tue, 4 Jul 2017 08:15:57 -0700 Guenter Roeck wrote:
>
> On Tue, Jun 13, 2017 at 08:54:09PM +1000, Stephen Rothwell wrote:
> >
> > After merging the block tree, today's linux-next build (s390x
> > s390-defconfig) failed like this:
> >
> >
Linus,
Please pull the for-linus branch from the git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
for-linus
HEAD: 296990deb389c7da21c78030376ba244dc1badf5 mnt: Make propagate_umount
less slow for overlapping mount propagation trees
A big break
On Tue, Jul 04, 2017 at 01:26:47PM -0600, Jonathan Corbet wrote:
> That file went away with commit bd8cc5a062f4 (srcu: Remove Classic SRCU)
> during the 4.13 merge window, leading to errors like:
>
> Error: Cannot open file ./kernel/rcu/srcu.c
>
> during the docs build.
>
> Reported-by: Linus
+++ Wanlong Gao [30/06/17 22:07 +0800]:
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/kprobe_example/abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyz.mod.o
On Tue, Jul 04, 2017 at 01:35:18PM -0300, Ben Mezger wrote:
> This patch, allows BFQ to be chosen in the Default I/O scheduler prompt.
Nak, this doesn't work. The default scheduler Kconfig option is for the
legacy block path, but BFQ is a blk-mq scheduler.
> Signed-off-by: Ben Mezger
Takashi Iwai writes:
> On Fri, 30 Jun 2017 21:43:58 +0200,
> Robert Jarzmik wrote:
>> +static struct bus_type ac97_bus_type = {
>> +.name = "ac97",
>
> Name-conflict with the old ac97 bus?
Yeah, fair point. So what should I choose for this new one ?
- ac97new
-
Hi Gaurav,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.12 next-20170704]
[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/Gaurav-Pathak/Replaced-Function-name
On Tue, Jul 4, 2017 at 12:20 PM, Arnd Bergmann wrote:
> On Tue, Jul 4, 2017 at 2:11 PM, Mel Gorman
> wrote:
>>
>> Signed-off-by: Mel Gorman
>
> Acked-by: Arnd Bergmann
Acked-by: Deepa Dinamani
Hi Gaurav,
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v4.12 next-20170704]
[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/Gaurav-Pathak/Replaced-Function-name
On Mon, 26 Jun 2017, Vikram Mulukutla wrote:
> On 6/26/2017 3:18 PM, Vikram Mulukutla wrote:
> > kthread_park waits for the target kthread to park itself with
> > __kthread_parkme using a completion variable. __kthread_parkme - which is
> > invoked by the target kthread - sets the completion
On Mon, 3 Jul 2017 08:25:57 +0200
Mike Looijmans wrote:
> The LTC2741 and LTC2473 are single voltage ADC chips. The LTC2473
> is similar to the LTC2471 but outputs a signed differential value.
>
> Datasheet:
> http://cds.linear.com/docs/en/datasheet/24713fb.pdf
>
>
Thanks to everyone who has participated in the review process so far. There
have only been a few changes since the v3 patch set:
* The cmpxchg64 syscall is no longer enabled on 32-bit systems. It's not
possible to provide this on SMP systems, and it's not necessary as glibc
knows not to
This patch contains the implementation of tasks on RISC-V, most of which
is involved in task switching.
Signed-off-by: Palmer Dabbelt
---
arch/riscv/include/asm/asm-offsets.h | 1 +
arch/riscv/include/asm/current.h | 44
arch/riscv/include/asm/kprobes.h | 22
This patch contains code that is in some way visible to the user:
including via system calls, the VDSO, module loading and signal
handling. It also contains some generic code that is ABI visible.
Signed-off-by: Palmer Dabbelt
---
arch/riscv/include/asm/elf.h |
This patch contains code that interfaces with devices that are mandated
by the RISC-V supervisor specification and that don't have explicit
drivers anywhere else in the tree. This includes the staticly defined
interrupts, the CSR-mapped timer, and virtualized SBI devices.
Signed-off-by: Palmer
This patch contains code to manage the RISC-V MMU, including definitions
of the page tables and the page walking code.
Signed-off-by: Palmer Dabbelt
---
arch/riscv/include/asm/mmu_context.h | 69 ++
arch/riscv/include/asm/page.h | 134 +++
This contains the various __init C functions, the initial assembly
kernel entry point, and the code to reset the system. When a file was
init-related, it contains
Signed-off-by: Palmer Dabbelt
---
arch/riscv/include/asm/bug.h | 88 +++
This patch contains code that is more specific to the RISC-V ISA than it
is to Linux. It contains string and math operations, C wrappers for
various assembly instructions, stack walking code, and uaccess.
Signed-off-by: Palmer Dabbelt
---
arch/riscv/include/asm/asm.h
This contains all the code that directly interfaces with the RISC-V
memory model. While this code corforms to the current RISC-V ISA
specifications (user 2.2 and priv 1.10), the memory model is somewhat
underspecified in those documents. There is a working group that hopes
to produce a formal
This patch contains the code that interfaces with ELF objects on RISC-V
systems, the vast majority of which is present to load kernel modules.
Signed-off-by: Palmer Dabbelt
---
arch/riscv/include/asm/compat.h | 29 ++
arch/riscv/include/asm/elf.h| 83
This patch contains all the build infastructure that actually enables
the RISC-V port. This includes Makefiles, linker scripts, and Kconfig
files. It also contains the only top-level change, which adds RISC-V to
the list of architectures that need a sed run to produce the ARCH
variable when
Hi,
On Sun, Jul 02, 2017 at 05:27:10PM +1000, Jonathan Liu wrote:
> The documentation for drm_do_get_edid in drivers/gpu/drm/drm_edid.c states:
> "As in the general case the DDC bus is accessible by the kernel at the I2C
> level, drivers must make all reasonable efforts to expose it as an I2C
>
On Tue, Jul 4, 2017 at 8:36 PM, Krzysztof Kozlowski wrote:
> On Tue, Jul 04, 2017 at 08:19:47PM +0200, Geert Uytterhoeven wrote:
>> Hi Krzysztof,
>>
>> On Tue, Jul 4, 2017 at 8:10 PM, Krzysztof Kozlowski wrote:
>> > On Tue, Jul 04, 2017 at 03:01:15PM +0200,
On Tue, Jul 04, 2017 at 09:54:10PM +0200, Rafael J. Wysocki wrote:
> On Tue, Jul 4, 2017 at 8:36 PM, Krzysztof Kozlowski wrote:
> > On Tue, Jul 04, 2017 at 08:19:47PM +0200, Geert Uytterhoeven wrote:
> >> Hi Krzysztof,
> >>
> >> On Tue, Jul 4, 2017 at 8:10 PM, Krzysztof Kozlowski
Convert sun7i-a20.dtsi to new CCU driver.
Tested on Cubietruck.
Signed-off-by: Priit Laes
---
arch/arm/boot/dts/sun7i-a20.dtsi | 719 +++-
1 file changed, 84 insertions(+), 635 deletions(-)
diff --git a/arch/arm/boot/dts/sun7i-a20.dtsi
Hi,
This serie brings A10 (sun4i) and A20 (sun7i) SoCs into the
sunxi-ng world. With this patchset we now support all the clocks
in sun4i/sun7i SoCs.
As mentioned in sun5i conversion, this is pretty much standard
stuff as most of the required clocks were already implemented in
the sunxi-ng
Allwinner A20 is now driven by sunxi-ng CCU driver.
Add devicetree binding for it.
Acked-by: Rob Herring
Signed-off-by: Priit Laes
---
Documentation/devicetree/bindings/clock/sunxi-ccu.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
Convert sun4i-a10.dtsi to new CCU driver.
Tested on Gemei G9 tablet.
Signed-off-by: Priit Laes
---
arch/arm/boot/dts/sun4i-a10.dtsi | 646 +++-
1 file changed, 73 insertions(+), 573 deletions(-)
diff --git a/arch/arm/boot/dts/sun4i-a10.dtsi
Introduce a clock controller driver for sun4i A10 and sun7i A20
series SoCs.
Signed-off-by: Priit Laes
---
drivers/clk/sunxi-ng/Kconfig | 14 +-
drivers/clk/sunxi-ng/Makefile |1 +-
drivers/clk/sunxi-ng/ccu-sun4i-a10.c | 1448
SATA clock on sun4i/sun7i is of type (parent) / M / 6 where
6 is fixed post-divider.
Signed-off-by: Priit Laes
---
drivers/clk/sunxi-ng/ccu_div.c | 18 --
drivers/clk/sunxi-ng/ccu_div.h | 3 ++-
2 files changed, 18 insertions(+), 3 deletions(-)
diff --git
Allwinner A10 is now driven by sunxi-ng CCU driver.
Add devicetree binding for it.
Acked-by: Rob Herring
Signed-off-by: Priit Laes
---
Documentation/devicetree/bindings/clock/sunxi-ccu.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
On Sat, Jul 01, 2017 at 01:46:03PM -0700, Dan Williams wrote:
> On Sat, Jul 1, 2017 at 1:38 PM, Jerry Hoemann wrote:
> > On Sat, Jul 01, 2017 at 01:10:31PM -0700, Dan Williams wrote:
> >> On Sat, Jul 1, 2017 at 1:08 PM, Dan Williams
> >> wrote:
>
On Tue, 04 Jul 2017 21:37:48 +0200,
Robert Jarzmik wrote:
>
> Takashi Iwai writes:
>
> > On Fri, 30 Jun 2017 21:43:58 +0200,
> > Robert Jarzmik wrote:
> >> +static struct bus_type ac97_bus_type = {
> >> + .name = "ac97",
> >
> > Name-conflict with the old ac97 bus?
>
On Tue, Jul 4, 2017 at 10:05 PM, Krzysztof Kozlowski wrote:
> On Tue, Jul 04, 2017 at 09:54:10PM +0200, Rafael J. Wysocki wrote:
>> On Tue, Jul 4, 2017 at 8:36 PM, Krzysztof Kozlowski wrote:
>> > On Tue, Jul 04, 2017 at 08:19:47PM +0200, Geert Uytterhoeven
As I try to maintain support for ARM CrOS (read, ChromeOS/ChromiumOS) devices in
upstream Linux on my spare time, I try to test out rc and stable versions as
often as time allows. I have been rolling out 4.12 since Monday and noticed that
the backlight on my tegra124 nyan big stayed dark for this
On Tue, Jul 04, 2017 at 03:25:45PM +0800, Yong wrote:
> On Mon, 3 Jul 2017 13:25:21 +0200
> Maxime Ripard wrote:
>
> > Hi,
> >
> > On Mon, Jul 03, 2017 at 06:59:52PM +0800, Yong wrote:
> > > > > + select VIDEOBUF2_DMA_CONTIG
> > > > > + select
On Tue, Jul 04, 2017 at 10:12:13PM +0200, Rafael J. Wysocki wrote:
> On Tue, Jul 4, 2017 at 10:05 PM, Krzysztof Kozlowski wrote:
>> >> > Thanks for report!
> >> >> >
> >> >> > Damn it, although I couldn't find this in the code, but I was fearing
> >> >> > that this ends up in
Vikram reported the following backtrace:
BUG: scheduling while atomic: swapper/7/0/0x0002
CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.9.32-perf+ #680
schedule
schedule_hrtimeout_range_clock
schedule_hrtimeout
wait_task_inactive
__kthread_bind_mask
__kthread_bind
On Tuesday, July 04, 2017 11:55:47 AM Rob Herring wrote:
> On Tue, Jul 4, 2017 at 11:09 AM, Takashi Iwai wrote:
> > On Tue, 04 Jul 2017 18:00:30 +0200,
> > Rob Herring wrote:
> >>
> >> On Mon, Jul 3, 2017 at 9:10 AM, Takashi Iwai wrote:
> >> > On Mon, 03 Jul 2017
On 2017.07.04 at 10:31 -0500, Goldwyn Rodrigues wrote:
>
>
> On 07/04/2017 02:45 AM, Markus Trippelsdorf wrote:
> > On 2017.07.04 at 06:23 +0200, Markus Trippelsdorf wrote:
> >> commit edf064e7c6fec3646b06c944a8e35d1a3de5c2c3 (HEAD, refs/bisect/bad)
> >> Author: Goldwyn Rodrigues
On Tue, 04 Jul 2017, Thomas Gleixner wrote:
On Tue, 4 Jul 2017, Davidlohr Bueso wrote:
On Tue, 04 Jul 2017, Davidlohr Bueso wrote:
> As a side effect you end up optimizing get/put_online_mems() at the cost
> of more overhead for the actual hotplug operation, which is rare and of less
>
This driver can be used on the aspeed ast2400.
Tested: ast2400 on quanta-q71l
Signed-off-by: Patrick Venture
---
drivers/misc/aspeed-lpc-snoop.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/misc/aspeed-lpc-snoop.c b/drivers/misc/aspeed-lpc-snoop.c
index
On Tue, Jul 04, 2017 at 12:36:11PM +0100, Ben Hutchings wrote:
> > If anywhing this would require to have a loop over all PROT_NONE
> > mappings to not hit into other weird usecases.
>
> That's what I was thinking of. Tried the following patch:
(...)
> - next = vma->vm_next;
> + /*
> +
On Mon, Jul 03, 2017 at 04:34:29PM +0200, Marc Gonzalez wrote:
> Bjorn Helgaas wrote:
>
> > Marc Gonzalez wrote:
> >
> >> On 03/07/2017 01:18, Bjorn Helgaas wrote:
> >>
> >>> On Tue, Jun 20, 2017 at 10:17:40AM +0200, Marc Gonzalez wrote:
> >>>
> +static int tango_check_pcie_link(void __iomem
On 04/07/17 17:18, Linus Torvalds wrote:
> Also, separately, John Haxby kind of implied that the LibreOffice
> regression on i386 is already fixed by commit f4cb767d76cf ("mm: fix
> new crash in unmapped_area_topdown()").
I'm not certain. We had two distinct problems that were avoided by
Hugh's
Hi Greg,
On 3 July 2017 at 19:03, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.36 release.
> There are 172 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being
On Tue, Jul 04, 2017 at 10:15:02AM -0500, Bjorn Helgaas wrote:
> On Mon, Jul 03, 2017 at 07:11:28PM +0100, Russell King - ARM Linux wrote:
> > On Mon, Jul 03, 2017 at 08:40:31AM -0500, Bjorn Helgaas wrote:
> > > The problem is serializing vs. memory accesses, since they don't use
> > > any
On Tue, Jun 27, 2017 at 09:08:40AM -0700, Prakash Sangappa wrote:
> Applications like the database use hugetlbfs for performance reason.
> Files on hugetlbfs filesystem are created and huge pages allocated
> using fallocate() API. Pages are deallocated/freed using fallocate() hole
> punching
On Tue, Jul 04, 2017 at 08:19:47PM +0200, Geert Uytterhoeven wrote:
> Hi Krzysztof,
>
> On Tue, Jul 4, 2017 at 8:10 PM, Krzysztof Kozlowski wrote:
> > On Tue, Jul 04, 2017 at 03:01:15PM +0200, Geert Uytterhoeven wrote:
> >> On Wed, Jun 28, 2017 at 4:56 PM, Krzysztof Kozlowski
On Tue, Jul 4, 2017 at 10:22 AM, Michal Hocko wrote:
>
> Well, I've been thinking about this some more and the more I think about
> it the less I am convinced we should try to be clever here. Why? Because
> as soon as somebody tries to manage stacks explicitly you cannot simply
On Tue, Jul 04, 2017 at 11:37:15AM -0700, Linus Torvalds wrote:
> On Tue, Jul 4, 2017 at 10:22 AM, Michal Hocko wrote:
> >
> > Well, I've been thinking about this some more and the more I think about
> > it the less I am convinced we should try to be clever here. Why? Because
>
Hello Rui,
Please pull the following changes to get the Thermal SoC updates
for 4.13-rc1. Here we have:
- Refactoring of cpucooling device driver to improve cpufreq data handling
- Small fixes on different drivers: IMX, hisilicon, and BCM.
The following changes since commit
On Mon, Jun 19, 2017 at 04:40:43PM +0300, Leonard Crestez wrote:
> On imx6sx accessing the ocotp memory area directly is wrong because the
> ocotp clock needs to be enabled first. Fix this by reinterpreting the
> fsl,tempmon-data phandle as a reference to a nvmem_device and doing all
> the read
From: Sean Wang
Update binding document with adding operating-points-v2 as the required
property and the cooling level as the optional properties and adding more
examples guiding people how to use MediaTek cpufreq driver for MediaTek
SoCs.
Signed-off-by: Sean Wang
On Tue, Jul 4, 2017 at 2:11 PM, Mel Gorman wrote:
>
> Signed-off-by: Mel Gorman
Acked-by: Arnd Bergmann
That file went away with commit bd8cc5a062f4 (srcu: Remove Classic SRCU)
during the 4.13 merge window, leading to errors like:
Error: Cannot open file ./kernel/rcu/srcu.c
during the docs build.
Reported-by: Linus Torvalds
Signed-off-by: Jonathan Corbet
Each time a CPU utilisation update is issued by the scheduler a flag, which
mainly defines which scheduling class is asking for the update, is used by the
frequency selection policy to support the selection of the most appropriate
OPP.
In the current implementation, CPU flags are overridden each
In system where multiple CPUs shares the same frequency domain a small
workload on a CPU can still be subject to frequency spikes, generated by
the activation of the sugov's kthread.
Since the sugov kthread is a special RT task, which goal is just that to
activate a frequency transition, it does
Currently, sg_cpu's flags are set to the value defined by the last call of
the cpufreq_update_util()/cpufreq_update_this_cpu(); for RT/DL classes
this corresponds to the SCHED_CPUFREQ_{RT/DL} flags always being set.
When multiple CPU shares the same frequency domain it might happen that a
CPU
The policy in use for RT/DL tasks sets the maximum frequency when a task
in these classes calls for a cpufreq_update_this_cpu(). However, the
current implementation is still enforcing a frequency switch rate
limiting when these tasks are running.
This is potentially working against the goal to
Currently schedutil updates are triggered for the RT class using a single
call place, which is part of the rt::update_curr_rt() used in:
- dequeue_task_rt:
but it does not make sense to set the schedutil's SCHED_CPUFREQ_RT in
case the next task should not be an RT one
- put_prev_task_rt:
On Tue, 04 Jul 2017 18:55:47 +0200,
Rob Herring wrote:
>
> On Tue, Jul 4, 2017 at 11:09 AM, Takashi Iwai wrote:
> > On Tue, 04 Jul 2017 18:00:30 +0200,
> > Rob Herring wrote:
> >>
> >> On Mon, Jul 3, 2017 at 9:10 AM, Takashi Iwai wrote:
> >> > On Mon, 03 Jul 2017
On Tue, Jul 4, 2017 at 5:28 PM, Takashi Iwai wrote:
> On Tue, 04 Jul 2017 17:14:39 +0200,
> Daniel Vetter wrote:
>> On Thu, Jun 29, 2017 at 12:25 PM, Daniel Vetter wrote:
>> >> Now I took a closer look, and this appears rather like a brown paper
>> >> bag bug, not
On Tue, 4 Jul 2017 13:12:18 +0800
Dison River wrote:
> Hi all:
> I'd found several address leaks of "skb" buffer.When i have a
> arbitrary address write vulnerability in kernel(enabled kASLR),I can
> use skb's address find sk_destruct's address and overwrite it. And
>
Hi Krzysztof,
On Tue, Jul 4, 2017 at 8:10 PM, Krzysztof Kozlowski wrote:
> On Tue, Jul 04, 2017 at 03:01:15PM +0200, Geert Uytterhoeven wrote:
>> On Wed, Jun 28, 2017 at 4:56 PM, Krzysztof Kozlowski wrote:
>> > genpd_syscore_switch() had two problems:
>> > 1.
On 7/4/17, 8:26 AM, "netdev-ow...@vger.kernel.org on behalf of Daniel Borkmann"
wrote:
[ +Lawrence ]
On 07/04/2017 05:21 PM, Colin King wrote:
> From: Colin Ian King
>
> There
Remove unnecessary static on local variables last_frontswap_pages and
tgt_frontswap_pages. Such variables are initialized before being used,
on every execution path throughout the function. The statics have no
benefit and, removing them reduce the code size.
This issue was detected using
On Tue, Jul 4, 2017 at 8:17 AM, Jens Axboe wrote:
> On 07/03/2017 06:00 PM, Linus Torvalds wrote:
>>
>> If they ever do come online, does that get fixed? I don't know.
>> Somebody should check.
>
> Yes, the blk-mq cpu hotplug code updates mappings when CPUs come and
> go, so that
On Tue, Jul 4, 2017 at 11:39 AM, Willy Tarreau wrote:
>
> But what is wrong with stopping the loop as soon as the distance gets
> larger than the stack_guard_gap ?
Absolutely nothing. But that's not the problem with the loop. Let's
say that you are using lots of threads, so that you
On Mon, 2017-07-03 at 15:34 +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Colin Ian King
>
>
> [ Upstream commit 0e73fc9a56f22f2eec4d2b2910c649f7af67b74d ]
>
> The
From: Sean Wang
The old place is Documentation/devicetree/bindings/clock/ that would
let people hard to find how to use MediaTek cpufreq driver, so moving
it to the appropriate place as other cpufreq drivers done would be
better.
Signed-off-by: Sean Wang
From: Sean Wang
MT2701/MT7623 is a 32-bit ARMv7 based quad-core (4 * Cortex-A7) with
single cluster and this hardware is also compatible with the existing
driver through enabling CPU frequency feature with operating-points-v2
bindings. Also, this driver actually supports
From: Sean Wang
Changes since v1:
- drop those patches already accepted
- refine the commit messages and Kconfig dependency
- Kconfig menu entry and file name itself are updated with more
generic name to drop "MT8173" since this driver actually supports
all MediaTek SoCs.
On Tue, Jul 04, 2017 at 11:47:37AM -0700, Linus Torvalds wrote:
> Let's
> say that you are using lots of threads, so that you know your stack
> space is limited. What you do is to use MAP_FIXED a lot, and you lay
> out your stacks fairly densely (with each other, but also possibly
> with other
Remove unnecessary static on local variable _chip_.
Such variable is initialized before being used,
on every execution path throughout the function.
The static has no benefit and, removing it reduces
the code size.
This issue was detected using Coccinelle and the following semantic patch:
@bad
On Tue, 4 Jul 2017, Linus Torvalds wrote:
> On Tue, Jul 4, 2017 at 8:17 AM, Jens Axboe wrote:
> > On 07/03/2017 06:00 PM, Linus Torvalds wrote:
> >>
> >> If they ever do come online, does that get fixed? I don't know.
> >> Somebody should check.
> >
> > Yes, the blk-mq cpu
On Tue, 4 Jul 2017 12:40:33 +0200
Geert Uytterhoeven wrote:
> Hi Nicholas,
>
> On Sun, May 14, 2017 at 10:43 AM, Nicholas Mc Guire wrote:
> > If the timeout-case prints a warning message then probably the interrupted
> > case should also. Further,
On 30/06/17 19:15, Alexei Starovoitov wrote:
> On 6/30/17 9:44 AM, Edward Cree wrote:
>> I haven't measured the test_progs ones, because I *still* haven't gotten
>> around to actually setting up a BPF toolchain (it doesn't help that I'm
>> building everything on a test server that gets reimaged
On Mon, 3 Jul 2017 21:32:33 -0700
Linus Torvalds wrote:
> Eg things like
>
> Error: Cannot open file ./kernel/rcu/srcu.c
> Error: Cannot open file ./kernel/rcu/srcu.c
>
> happen simply because that file no longer exists, and the docs never
> got updated.
>
>
/kernel/git/acme/linux into perf/urgent
(2017-06-27 09:17:02 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-urgent-for-mingo-4.12-20170704
for you to fetch changes up to 1934adf78e33fa69570a763c7ac5353212416bb0:
perf unwind
On Mon, 3 Jul 2017 23:19:45 +0200
Maxime Ripard wrote:
> On Mon, Jul 03, 2017 at 03:09:26PM +0200, Quentin Schulz wrote:
> > When initializing interrupts, the devm_request_any_context_irq will
> > enable them right away. An atomic flag was set in sun4i_irq_init
From: Jiri Olsa
We currently fail the MMAP event processing if we don't have the MMAP
event's specific arch unwind support compiled in.
That's wrong and can lead to unresolved mmaps in report output for 32bit
binaries on 64bit server, like in this example on x86_64 server:
From: Arnaldo Carvalho de Melo
We should set attr.exclude_kernel when probing for attr.precise_ip
level, otherwise !CAP_SYS_ADMIN users will not default to skidless
samples in capable hardware.
The increase in the paranoid level in commit 0161028b7c8a ("perf/core:
Change the
The U-Boot project uses the same scripts/checkpatch.pl as the Linux
kernel. I ran upon the problem below when working on U-Boot. But I
guess it should be fixed in the Linux upstream.
Running checkpatch for this email produces
WARNING: storage class should be at the beginning of the declaration
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 TPM counter, compare and capture registers are clocked by an
asynchronous clock that can remain enabled in low power modes.
NOTE: We observed in a very
Adding NXP Low Power Timer/Pulse Width Modulation Module (TPM)
binding doc.
Cc: Mark Rutland
Cc: devicet...@vger.kernel.org
Cc: Daniel Lezcano
Cc: Thomas Gleixner
Cc: Shawn Guo
Cc: Bai Ping
On July 4, 2017 4:32:18 PM PDT, "Andreas Färber" wrote:
>Commit 18cfd9429d8a82c49add8f3ca9d366599bfcac45 ("ARM: owl: smp: Drop
>bogus holding pen") simplified the S500 SMP code by removing a loop for
>pen_release in owl_secondary_boot(). Since then it is only calling
The Timer/PWM Module (TPM) supports input capture, output compare,
and the generation of PWM signals to control electric motor and power
management applications. The counter, compare and capture registers
are clocked by an asynchronous clock that can remain enabled in low
power modes. TPM can
From 8db74a4eef334f614bf727232e5b88f67f824862 Mon Sep 17 00:00:00 2001
From: Yang Jiaxun
Date: Tue, 4 Jul 2017 11:28:41 +0800
Subject: [PATCH] ideapad-laptop: Add several models to no_hw_rfkill
Some Lenovo ideapad models do not have hardware rfkill switches, but
trying to
Hello Sir,
How is the review result of this patch. I am waiting for it be merged,
thanks.
BR
Ran
-Original Message-
From: Ran Wang [mailto:ran.wan...@nxp.com]
Sent: Friday, June 02, 2017 10:30 AM
To: Rob Herring ; Mark Rutland ;
Catalin
Remove unnecessary static on local variable hostbridge.
Such variable is initialized before being used,
on every execution path throughout the function.
The static has no benefit and, removing it reduces
the code size.
This issue was detected using Coccinelle and the following semantic patch:
On 05-07-17, 02:55, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> Update binding document with adding operating-points-v2 as the required
> property and the cooling level as the optional properties and adding more
> examples guiding people how to use MediaTek
On 05-07-17, 02:55, sean.w...@mediatek.com wrote:
> From: Sean Wang
>
> Changes since v1:
> - drop those patches already accepted
> - refine the commit messages and Kconfig dependency
> - Kconfig menu entry and file name itself are updated with more
> generic name to drop
501 - 600 of 1354 matches
Mail list logo