Commit-ID: edfdb7eab0fe5f98f2951598dc679b71bdb3e16b
Gitweb: http://git.kernel.org/tip/edfdb7eab0fe5f98f2951598dc679b71bdb3e16b
Author: Jan Stancek
AuthorDate: Wed, 2 Sep 2015 10:19:16 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 14 Sep 2015 12:50:12 -0300
perf tests: Stop
Commit-ID: 06f679c18fcf414cc8462938466f8361315f18cb
Gitweb: http://git.kernel.org/tip/06f679c18fcf414cc8462938466f8361315f18cb
Author: Jan Stancek
AuthorDate: Thu, 3 Sep 2015 13:23:32 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 14 Sep 2015 12:50:11 -0300
perf tests: Make
Commit-ID: 729a7ed103ae1b04a5c87a5855885e0973161da4
Gitweb: http://git.kernel.org/tip/729a7ed103ae1b04a5c87a5855885e0973161da4
Author: Jan Stancek
AuthorDate: Wed, 2 Sep 2015 10:19:14 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 14 Sep 2015 12:50:10 -0300
perf tests: Take
On 08/09/15 11:08, Jiri Olsa wrote:
> On Tue, Sep 08, 2015 at 10:58:48AM +0300, Adrian Hunter wrote:
>> Hi
>>
>> Here is V3 of "Fix gaps propagating maps" that fixes some problems
>> revealed by to d988d5ee6478 ("perf evlist: Open event on evsel cpus and
>> threads")
>>
>> Changes in V3:
>>
>>
The new helper returns index of the mathing string in an array. We would use it
here.
Signed-off-by: Andy Shevchenko
---
drivers/gpu/drm/drm_edid_load.c | 17 ++---
1 file changed, 6 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/drm_edid_load.c b/drivers/gpu/drm/drm_ed
>From time to time we have to match a string in an array. Make a simple helper
for that purpose.
Signed-off-by: Andy Shevchenko
---
include/linux/string.h | 7 +++
lib/string.c | 26 ++
2 files changed, 33 insertions(+)
diff --git a/include/linux/string.h
There are users of a simple string matching in the array. Let's do a common
helper for that.
Two users are updated in the series. one more is coming [1].
[1] http://www.spinics.net/lists/kernel/msg2074265.html
The series is compile tested.
Andy Shevchenko (3):
lib/string: introduce match_stri
The new helper returns index of the mathing string in an array. We would use it
here.
Signed-off-by: Andy Shevchenko
---
drivers/ata/pata_hpt366.c | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/drivers/ata/pata_hpt366.c b/drivers/ata/pata_hpt366.c
index 0038dc4
* Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> Hi Ingo,
>
> Please consider pulling, this should have all the issues related to
> that 'socket' sort order/filter fixed. I reordered some patches I did to
> get the right infrastructure in place and merged a few fix
On Tue, Sep 15, 2015 at 3:37 AM, Mike Galbraith
wrote:
> On Mon, 2015-09-14 at 19:11 +0200, Daniel Vacek wrote:
>> On Mon, Sep 14, 2015 at 1:42 PM, Thomas Gleixner wrote:
>> > I'm not going to support 4.2. We switched to odd numbers due to 4.1
>> > being a LTS kernel.
>>
>> That's odd.
>
> Not r
On Mon, 2015-09-14 at 17:37 +0300, Mika Westerberg wrote:
> The current implementation hard codes the two supported channels so
> that
> "tx" is always 0 and "rx" is always 1. This is because there has been
> no
> suitable way in ACPI to name resources.
>
> With _DSD device properties we can fin
On 09/14/2015 07:12 PM, Tony Lindgren wrote:
> * Peter Ujfalusi [150911 05:35]:
>> Move the code out from arch/arm/common and merge it inside of the dmaengine
>> driver.
>> This change is done with as minimal change to the code as possible to avoid
>> any possibilities to introducing regression.
>
On Mon, Sep 14, 2015 at 10:34:00AM -0700, bseg...@google.com wrote:
> >> SCHED_LOAD_RESOLUTION and the non-SLR part of SCHED_LOAD_SHIFT are not
> >> required to be the same value and should not be conflated.
> >>
> >> In particular, since cgroups are on the same timeline as tasks and their
> >> sh
This patch factors out core eventfd assign/deassign logic and leaves
the argument checking and bus index selection to callers.
Cc: sta...@vger.kernel.org
Cc: Gleb Natapov
Cc: Paolo Bonzini
Signed-off-by: Jason Wang
---
virt/kvm/eventfd.c | 85 ---
We only want zero length mmio eventfd to be registered on
KVM_FAST_MMIO_BUS. So check this explicitly when arg->len is zero to
make sure this.
Cc: sta...@vger.kernel.org
Cc: Gleb Natapov
Cc: Paolo Bonzini
Signed-off-by: Jason Wang
---
virt/kvm/eventfd.c | 4 ++--
1 file changed, 2 insertions(+
We register wildcard mmio eventfd on two buses, once for KVM_MMIO_BUS
and once on KVM_FAST_MMIO_BUS but with a single iodev
instance. This will lead to an issue: kvm_io_bus_destroy() knows
nothing about the devices on two buses pointing to a single dev. Which
will lead to double free[1] during exit
Currently, if we had a zero length mmio eventfd assigned on
KVM_MMIO_BUS. It will never be found by kvm_io_bus_cmp() since it
always compares the kvm_io_range() with the length that guest
wrote. This will cause e.g for vhost, kick will be trapped by qemu
userspace instead of vhost. Fixing this by u
Cc: Gleb Natapov
Cc: Paolo Bonzini
Signed-off-by: Jason Wang
---
Documentation/virtual/kvm/api.txt | 7 ++-
include/uapi/linux/kvm.h | 1 +
virt/kvm/kvm_main.c | 1 +
3 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/Documentation/virtual/kvm/api.txt
b/Do
On Tue, 2015-09-15 at 00:00 +0200, Rasmus Villemoes wrote:
> On Mon, Sep 14 2015, Vitaly Kuznetsov wrote:
>
Vitaly, thanks for the test cases. My comments below.
> > +static __init void test_string_get_size_one(u64 size, u64
> > blk_size,
> > + const enum
Cc: Gleb Natapov
Cc: Paolo Bonzini
Signed-off-by: Jason Wang
---
arch/x86/kvm/trace.h | 18 ++
arch/x86/kvm/vmx.c | 1 +
arch/x86/kvm/x86.c | 1 +
3 files changed, 20 insertions(+)
diff --git a/arch/x86/kvm/trace.h b/arch/x86/kvm/trace.h
index 4eae7c3..ce4abe3 100644
---
Hi:
This series fixes two issues of fast mmio eventfd:
1) A single iodev instance were registerd on two buses: KVM_MMIO_BUS
and KVM_FAST_MMIO_BUS. This will cause double in
ioeventfd_destructor()
2) A zero length iodev on KVM_MMIO_BUS will never be found but
kvm_io_bus_cmp(). This will l
Hi Jonas,
your commit 158fcc4e050a ("spi/bcm63xx: replace custom io accessors with
standard ones") has shown up in today's Linux next tree (i.e.,
next-20150915).
This commit adds four #ifdef blocks depending on CONFIG_BIG_ENDIAN,
which is not defined in Kconfig breaking the #ifdef #else conditi
Hi!
> > I've got an embedded system with two arizona / wm5102 codecs.
> >
> > Unfortunately, kernel does not seem to be ready for that
> > configuration.
> >
> > In particular, drivers/regulator/arizona-ldo1.c and
> > drivers/regulator/arizona-micsupp.c register system-wide "MICVDD" and
> > "LDO
On Fri, Sep 11, 2015 at 8:18 AM, Sergey Senozhatsky
wrote:
> Constify `struct zs_pool' ->name.
>
> Signed-off-by: Sergey Senozhatsky
Acked-by: Dan Streetman
> ---
> include/linux/zpool.h| 6 --
> include/linux/zsmalloc.h | 2 +-
> mm/zbud.c| 2 +-
> mm/zpool.c
Hello Vitaly,
It seems you sent a mail with gmail web or something which didn't use
plain-text. ;-). I will add newline manually.
Please send a mail with plain-text in future.
On Mon, Sep 14, 2015 at 03:49:01PM +0200, Vitaly Wool wrote:
> While using ZRAM on a small RAM footprint devices, togethe
* Christoph Lameter wrote:
> On Mon, 14 Sep 2015, Austin S Hemmelgarn wrote:
>
> >I can comment at least a little about the -Os aspect (although not I'm no
> >expert on this in particular). In general, for _most_ use cases, a kernel
> >compiled with CONFIG_CC_OPTIMIZE_FOR_SIZE will run slower
On (09/15/15 02:06), Dan Streetman wrote:
> > There are no zbud and zpool users besides zswap so enabling
> > (and building) CONFIG_ZPOOL and CONFIG_ZBUD make sense only
> > when CONFIG_ZSWAP is enabled. In other words, make those
> > options to depend on CONFIG_ZSWAP.
>
> Let's wait on this until
On Tue, Sep 15, 2015 at 03:10:45AM +0100, Ben Hutchings wrote:
> On Sun, 2015-09-13 at 00:56 +0200, Willy Tarreau wrote:
> > 2.6.32-longterm review patch. If anyone has any objections, please let me
> > know.
> >
> > --
> >
> > From: Heiko Carstens
> >
> > commit d744194956334
On (09/15/15 01:42), Dan Streetman wrote:
> Well, zram explicitly expects to be able to store PAGE_SIZE'd objects:
>
> if (unlikely(clen > max_zpage_size))
> clen = PAGE_SIZE;
> handle = zs_malloc(meta->mem_pool, clen);
>
> so the max_zpage_size doesn't prevent zram from trying to store the
>
On Thu, Sep 10, 2015 at 8:28 AM, Sergey Senozhatsky
wrote:
> There are no zbud and zpool users besides zswap so enabling
> (and building) CONFIG_ZPOOL and CONFIG_ZBUD make sense only
> when CONFIG_ZSWAP is enabled. In other words, make those
> options to depend on CONFIG_ZSWAP.
Let's wait on this
* Denys Vlasenko wrote:
> tools/testing/selftests/x86/Makefile| 2 +-
> tools/testing/selftests/x86/test_syscall_vdso.c | 401
>
> tools/testing/selftests/x86/thunks_32.S | 55
> 3 files changed, 457 insertions(+), 1 deletion(-)
> create mo
On Mon, Sep 14, 2015 at 9:12 PM, Sergey Senozhatsky
wrote:
> On (09/14/15 15:55), Vitaly Wool wrote:
>> Update zram driver to use common zpool API instead of calling
>> zsmalloc functions directly. This patch also adds a parameter
>> that allows for changing underlying compressor storage to zbud.
* Andy Lutomirski wrote:
> On Sep 14, 2015 1:15 AM, "Ingo Molnar" wrote:
> >
> >
> > * Denys Vlasenko wrote:
> >
> > > >> + /* INT80 syscall entrypoint can be used by
> > > >> +* 64-bit programs too, unlike
> > > >> SYSCALL/SYSENTER.
> > > >> +
On Fri, 2015-09-11 at 16:33 +0100, Robin Murphy wrote:
> On 03/08/15 11:21, Yong Wu wrote:
> > This patch adds support for mediatek m4u (MultiMedia Memory Management
> > Unit).
> >
> > Signed-off-by: Yong Wu
> > ---
> [...]
> > +/*
> > + * There is only one iommu domain called the m4u domain that
Hi,
On Tuesday 15 September 2015 01:52 AM, Tony Lindgren wrote:
> Hi,
>
> * Ulf Hansson [150904 05:48]:
>>
>> Okay, just to be clear on the way forward. I spoked with Mark Brown
>> offlist, and he will/has picked up the regulator patch and will send
>> it as fix for the 4.3 rc[n].
>>
>> Regardin
>From 64a24d04c6510dcc144aba123fb21ed6f895c6b7 Mon Sep 17 00:00:00 2001
From: Shayan Pooya
Date: Mon, 14 Sep 2015 21:25:09 -0700
Subject: [PATCH] sched/fair: adjust the depth of a sched_entity when its
parent changes
Fixes commit fed14d45f945 ("sched/fair: Track cgroup depth")
Hit this kernel pa
On Mon, Sep 14, 2015 at 9:50 AM, Vitaly Wool wrote:
> It makes sense to have control over what compression ratios are
> ok to store pages uncompressed and what not. Moreover, if we end
> up using zbud allocator for zram, any attempt to allocate a whole
> page will fail, so we may want to avoid thi
Hi Olga,
On Mon, Sep 14, 2015 at 11:54:34PM +, Kornievskaia, Olga wrote:
> Hi Willy,
>
> I believe the patch introduced another problem and needs to be corrected.
Can you be more specific ? What problem, or how to verify which one ?
Should the patch simply be reverted ?
Thanks,
Willy
--
T
On Mon, Sep 14, 2015 at 10:31:05PM +, Martin Pietryka wrote:
> This patch fixes all alignment issues, as well as a multiple
> assignment and multiple blank lines issues.
These are too many things to be included in a single patch. Please break
them into a series. One patch should do only one typ
* John Stultz wrote:
> As noted in the comment above abs():
> "abs() should not be used for 64-bit types (s64, u64, long long)
> - use abs64() for those."
>
> Unfortunately, its quite easy to pass 64-bit values to abs()
> accidentally, and the compiler provides no warning when the
> returne
* John Stultz wrote:
> On Mon, Sep 14, 2015 at 6:49 PM, Tejun Heo wrote:
> > Hello,
> >
> > On Mon, Sep 14, 2015 at 06:05:19PM -0700, John Stultz wrote:
> >> As noted in include/linux/kernel.h:
> >> "abs() should not be used for 64-bit types (s64, u64, long long)
> >> - use abs64() for those.
On Tue, Sep 15, 2015 at 03:23:58AM +0300, Kirill A. Shutemov wrote:
> On Mon, Sep 14, 2015 at 03:50:38PM -0700, Palmer Dabbelt wrote:
> > This used to be hidden behind CONFIG_MMAP_ALLOW_UNINITIALIZED, so
> > userspace wouldn't actually ever see it be non-zero. While I could
> > have kept hiding it
Commit-ID: 1975dbc276c6ab62230cf4f9df5ddc9ff0e0e473
Gitweb: http://git.kernel.org/tip/1975dbc276c6ab62230cf4f9df5ddc9ff0e0e473
Author: Jonathan Corbet
AuthorDate: Mon, 14 Sep 2015 17:11:05 -0600
Committer: Ingo Molnar
CommitDate: Tue, 15 Sep 2015 07:12:06 +0200
locking/static_keys: Fix
On Mon, Sep 14, 2015 at 10:21:14PM +0530, Chandra S Gorentla wrote:
> NULL pointer deference is observed in the wilc1000.ko module
> with bus type SPI and when SPI is not ready.
>
> Signed-off-by: Chandra S Gorentla
> ---
A small spelling mistake in the subject. It should be "staging" and not
"st
On Mon, Sep 14, 2015 at 9:06 PM, Sergey Senozhatsky
wrote:
> On (09/14/15 15:51), Vitaly Wool wrote:
>> As a preparation step for zram to be able to use common zpool API,
>> there has to be some alignment done on it. This patch adds
>> functions that correspond to zsmalloc-specific API to the comm
On Mon, Sep 14, 2015 at 02:53:11PM +0530, Sakshi Vaid wrote:
> Fixed the following error.
> WARNING: More than 80 characters in a line.
>
> Signed-off-by: Sakshi Vaid
> ---
This has already been done by 159dc4bff27a ("staging: lustre: lclient:
remove extra parentheses around right
On Mon, Sep 14, 2015 at 08:48:04AM -0800, Mike Dupuis wrote:
> > In your previous patches this From: line was not there. Why now?
>
> I did not do that by hand. I changed some SSMTP and git configuration
> settings recently-- perhaps that is related. If this is a problem, I will
> correct it.
The
On Mon, 14 Sep 2015, Tyler Hicks wrote:
> On 2015-09-13 14:15:21, Julia Lawall wrote:
> > Remove unneeded NULL test.
> >
> > The semantic patch that makes this change is as follows:
> > (http://coccinelle.lip6.fr/)
> >
> > //
> > @@ expression x; @@
> > -if (x != NULL)
> > \(kmem_cache_dest
On 09/14/15 22:07, Sedat Dilek wrote:
On Tue, Sep 15, 2015 at 5:40 AM, Behan Webster
wrote:
I haven't upstreamed this patch yet because we are still characterizing its
effects on other architectures.
Then embed this information into the changelog of *your* patch.
It's in our tree/build system,
On Mon, Sep 14, 2015 at 10:17:50PM -0500, Rob Landley wrote:
> On 08/25/2015 04:23 PM, Rich Felker wrote:
> > From: Rich Felker
> >
> > Historically SH-2 Linux (and originally uClinux) used a syscall
> > calling convention incompatible with the established SH-3/4 Linux ABI.
> > This choice was ma
On (09/15/15 00:08), Dan Streetman wrote:
[..]
>
> it doesn't. but it has a complex (compared to zbud) way of storing
> pages - many different classes, which each are made up of zspages,
> which contain multiple actual pages to store some number of
> specifically sized objects. So it can get fra
Hi Charles,
On 2015년 09월 11일 16:52, Chanwoo Choi wrote:
> On 2015년 09월 09일 17:34, Charles Keepax wrote:
>> Signed-off-by: Charles Keepax
>> ---
>> Documentation/devicetree/bindings/mfd/arizona.txt | 21
>> +
>> include/dt-bindings/mfd/arizona.h |5 +
Ping?
On Tue, Aug 25, 2015 at 05:23:11PM -0400, Rich Felker wrote:
> From: Rich Felker
>
> Historically SH-2 Linux (and originally uClinux) used a syscall
> calling convention incompatible with the established SH-3/4 Linux ABI.
> This choice was made because the trap range used by the existing A
On Mon, Sep 14, 2015 at 10:14 AM, Vlastimil Babka wrote:
> On 09/14/2015 04:12 PM, Vitaly Wool wrote:
>>
>> On Mon, Sep 14, 2015 at 4:01 PM, Vlastimil Babka wrote:
>>>
>>>
>>> On 09/14/2015 03:49 PM, Vitaly Wool wrote:
While using ZRAM on a small RAM footprint devices, together wit
On Tue, Sep 15, 2015 at 5:40 AM, Behan Webster
wrote:
> Other than you changing the commit comment, this *is* my patch.
>
You were mentioned in the commit-message as original author.
> I haven't upstreamed this patch yet because we are still characterizing its
> effects on other architectures.
>
Hi Charles,
Your following patch-set[1][2] receive the ack message about almost patches.
But, a few patches[3][4][5] must need the ack message from each maintainer.
[1] http://www.spinics.net/lists/devicetree/msg93383.html
[2] https://lkml.org/lkml/2015/8/11/145
[3] patch1 is included in patch-set
Add reset controller for hi6220 hikey-board.
Signed-off-by: Chen Feng
---
arch/arm64/boot/dts/hisilicon/hi6220.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
b/arch/arm64/boot/dts/hisilicon/hi6220.dtsi
index 3f03380..3bbc846 100644
---
Add DT bindings documentation for hi6220 SoC reset controller.
Signed-off-by: Chen Feng
---
.../bindings/reset/hisilicon,hi6220-reset.txt | 97 ++
1 file changed, 97 insertions(+)
create mode 100644
Documentation/devicetree/bindings/reset/hisilicon,hi6220-reset.txt
di
Add reset driver for hi6220-hikey board,this driver supply deassert
of IP. on hi6220 SoC.
Signed-off-by: Chen Feng
---
drivers/reset/Kconfig | 1 +
drivers/reset/Makefile | 1 +
drivers/reset/hisilicon/Kconfig| 5 ++
drivers/reset/hisilicon/Makefile
On Tue, 2015-08-18 at 15:27 +0800, YH Huang wrote:
> This patch series add the use of display PWM driver, documentation
> and device tree for Mediatek SoCs. The driver is used to support
> the backlight of the panel. This is based on v4.2-rc1.
>
> The clock definitions (CLK_MM_DISP_PWM*) are added
On 09/14/2015 05:41 PM, Davidlohr Bueso wrote:
On Mon, 14 Sep 2015, Waiman Long wrote:
You can't use debugfs if we want to have per-cpu stats. We will have
to use sysfs instead. This will require more code changes. It is
certainly doable, but we have to choose between simplicity and
performan
Hello,
On Mon, Sep 14, 2015 at 08:27:08PM -0700, John Stultz wrote:
> Yea. The above make sense to me, but I suspect there's some very
> subtle reason for the existing separated logic.
> But I'd have to defer to akpm for hints on that.
Hmmm... people could be using it for calculating the distance
On Tue, Sep 15, 2015 at 08:38:54AM +0530, Parav Pandit wrote:
> As you precisely described, about wild ratio,
> we are asking vendor driver (bottom most layer) to statically define
> what the resource pool is, without telling him which application are
> we going to run to use those pool.
> Therefo
Other than you changing the commit comment, this *is* my patch.
I haven't upstreamed this patch yet because we are still characterizing
its effects on other architectures.
Clang certainly doesn't require -Oz to be used to be able to boot for
arm nor arm64. So the commit message isn't correct
[+Cc Mark, I thought I cc'd him earlier, but no, I cc'd him only for
the first patch]
On 14-09-15, 15:30, Rob Herring wrote:
> On 09/11/2015 07:01 AM, Viresh Kumar wrote:
> > If 'opp-microvolt' is used to specify values for multiple regulators,
> > then we need this additional information to know
On Mon, Sep 14, 2015 at 6:49 PM, Tejun Heo wrote:
> Hello,
>
> On Mon, Sep 14, 2015 at 06:05:19PM -0700, John Stultz wrote:
>> As noted in include/linux/kernel.h:
>> "abs() should not be used for 64-bit types (s64, u64, long long)
>> - use abs64() for those."
>>
>> Unfortunately, there are quite
Based on a patch of Behan Webster (see [1]).
CLANG (here: v3.7) requires '-Oz' as OptLevel to be set.
A Linux v4.3-rc1 kernel built fine with CONFIG_CC_OPTIMIZE_FOR_SIZE=y
and boots on bare metal.
This is a Ubuntu/precise AMD64 system.
Tested against Linux v4.3-rc1 and a refreshed llvmlinux patc
On 08/25/2015 04:23 PM, Rich Felker wrote:
> From: Rich Felker
>
> Historically SH-2 Linux (and originally uClinux) used a syscall
> calling convention incompatible with the established SH-3/4 Linux ABI.
> This choice was made because the trap range used by the existing ABI,
> 0x10-0x17, overlaps
Hi Jon,
On 11 September 2015 at 06:45, Jon Masters wrote:
> On 06/03/2015 02:53 PM, Timur Tabi wrote:
>> On 06/03/2015 01:25 PM, Guenter Roeck wrote:
>>> In general the idea here would be to use a crashdump kernel, which,
>>> when loaded, would reset the watchdog before it fires. This kernel
>>>
On 9/8/2015 20:23, Mark Brown wrote:
On Tue, Sep 08, 2015 at 05:36:13PM +0800, Wu, Songjun wrote:
On 9/8/2015 00:25, Mark Brown wrote:
Sure, there's no problem at all having that structure in software but it
should be possible to do this without having to represent this structure
in DT. It
> Because actual hardware resources *ARE* the limit. We cannot abstract
> it away. The hardware/driver has real, fixed, immutable limits. No API
> abstraction can possibly change that.
>
> The limits are such there *IS NO* API boundary that can bundle them
> into something simpler. There will alway
On 2015/9/14 20:50, Marc Zyngier wrote:
On 14/09/15 10:29, Yang Yingliang wrote:
Use irq_set_status_flags() helper set irqs status with
IRQ_MOVE_PCNTXT. So that it can do set affinity when
calling irq_set_affinity_locked().
Cc: Jiang Liu
Cc: Thomas Gleixner
Cc: Marc Zyngier
Cc: Mark Rutlan
On 09/14/15 at 04:44pm, Dave Young wrote:
> On 09/14/15 at 03:50pm, Minfei Huang wrote:
> > On 09/13/15 at 11:52am, Eric W. Biederman wrote:
> > > Minfei Huang writes:
> > >
> > > > kexec output message misses the prefix "kexec", when Dave Young split
> > > > the kexec code. To keep the same form
CLANG (here: v3.7) does not support '-fno-delete-null-pointer-checks'
as a compiler-flag.
Fix the HOSTCFLAGS and KBUILD_CFLAGS settings accordingly.
Furthermore, move and correct the $HOSTCC check.
Tested against Linux v4.3-rc1 and a refreshed llvmlinux patchset.
---
Makefile | 8 +---
1 fil
On Sun, 2015-09-13 at 00:56 +0200, Willy Tarreau wrote:
> 2.6.32-longterm review patch. If anyone has any objections, please let me
> know.
>
> --
>
> From: Ralf Baechle
>
> commit 9cdf30bd3bac697fc533988f44a117434a858f69 upstream.
>
> Returns a non-zero value if the current
Hi all,
Changes since 20150914:
Dropped tree: akpm-current (build conflict)
I used the h8300 tree from next-20150828 since the current tree has been
rebased onto something very old :-(
The bluetooth tree still had its build failure.
The akpm-current tree still had its build failure so I
On Mon, Sep 14, 2015 at 4:16 AM, Sudeep Holla wrote:
>
>
> On 12/09/15 10:50, maoguang meng wrote:
>> hi Sudeep:
>>
>> I test flowlling your blow suggestions,but the system can not be woken.
>>
>> beacuse,mtk_eint_suspend will mask it.As we know if eint wakeup system
>> it must be unmasked before
On 14-09-15, 15:22, Rob Herring wrote:
> What if we have a 2nd device and supply rail? For example, what if the
> L2$ has a separate rail from the cores but is linked to the OPPs.
Right, so that is the case with the Mediatek SoC as well, AFAIR. How
do we plan to treat L2 devices? For example, in t
Adding dtor & linux-input as we are now discussing the elan trackpad driver...
On Mon, Sep 14, 2015 at 7:16 PM, Sudeep Holla wrote:
>
>
> On 12/09/15 10:50, maoguang meng wrote:
>> hi Sudeep:
>>
>> I test flowlling your blow suggestions,but the system can not be woken.
>>
>> beacuse,mtk_eint_susp
Hello Kees,
>> +run_crash:
>> + @sh pstore_crash_test || echo "pstore_crash_test: [FAIL]"
>
> This is probably better written to exit 1 on failure, otherwise it
> just _says_ it fails. (Though lots of selftests in the tree already
> have this problem, it's best to avoid the pattern for new
Em Mon, Sep 14, 2015 at 06:05:38PM -0400, Raphaël Beamonte escreveu:
> 2015-09-14 17:36 GMT-04:00 Arnaldo Carvalho de Melo :
> > Em Mon, Sep 14, 2015 at 04:59:41PM -0400, Raphaël Beamonte escreveu:
> >> 2015-09-14 16:53 GMT-04:00 Arnaldo Carvalho de Melo
> >> :
> >> > +++ b/tools/perf/util/evsel.c
On 2015/9/15 0:01, Arthur Marsh wrote:
>
>
> Jiang Liu wrote on 14/09/15 12:38:
>> Hi Authur,
>> As suggested by Bjorn, patch 1-2 set implement a PCI device
>> driver to manage eata PCI devices. And patch 3 tries to support PCI
>> device hot-removal for eata, but I have no change to test due
Hello, Kees,
Thank you for your advise.
>> +be_msg=`dmesg | grep "pstore: Registered [a-zA-Z0-9]\+ as
persistent store backend$"`
...
> This seems unstable if the system hasn't booted recently or if stuff
> is spamming dmesg. What about examining /sys/module/pstore instead?
OK, I'll update in
Hello Mark,
Thank you for your advise.
>> +prlog -n "Checking pmsg file contains TEST_STRING ... "
> Mark this as 'wish to have'
OK. I'll change it to "Checking pmsg file wishes to have TEST_STRING
... ". Should I change other messages in the same way?
> Can TEST_STRING be given an unique valu
On Sun, 2015-09-13 at 00:56 +0200, Willy Tarreau wrote:
> 2.6.32-longterm review patch. If anyone has any objections, please let me
> know.
>
> --
>
> From: Alexander Sverdlin
>
> [ Upstream commit 29c4afc4e98f4dc0ea9df22c631841f9c220b944 ]
>
> There is NULL pointer dereferen
2015-09-15 8:23 GMT+08:00 Stephen Boyd :
> Now that __cpuinit has been removed, the __ref markings on these
> functions are useless. Remove them. This also reduces the size of
> the multi_v7_defconfig image:
>
> $ size before after
>textdata bss dec hex filename
>12683578
2015-09-14 17:23 GMT+09:00 Javier Martinez Canillas :
> If i2c_new_dummy() fails in max77843_chg_init(), an PTR_ERR(NULL) is
> returned which is 0. So the function was wrongly returning a success
> value instead of an error code.
>
> Fixes: c7f585fe46d8 ("mfd: max77843: Add max77843 MFD driver core
On 14-09-15, 17:23, Stephen Boyd wrote:
> Now that __cpuinit has been removed, the __ref markings on these
> functions are useless. Remove them. This also reduces the size of
> the multi_v7_defconfig image:
>
> $ size before after
>textdata bss dec hex filename
>12683578
On 09/15/2015 07:38 AM, Raghavendra K T wrote:
The functions used in the patch are in slowpath, which gets called
whenever alloc_super is called during mounts.
Though this should not make difference for the architectures with
sequential numa node ids, for the powerpc which can potentially have
s
Hi Rich,
On 15/09/15 01:17, Rich Felker wrote:
> On Mon, Sep 14, 2015 at 10:13:03PM +1000, Greg Ungerer wrote:
>> On 26/08/15 11:26, Greg Ungerer wrote:
>>> On 21/08/15 05:11, Rich Felker wrote:
From: Rich Felker
On NOMMU archs, the FDPIC ELF loader sets up the usable brk range to
On Sun, 2015-09-13 at 00:56 +0200, Willy Tarreau wrote:
> 2.6.32-longterm review patch. If anyone has any objections, please let me
> know.
>
> --
>
> From: Heiko Carstens
>
> commit d74419495633493c9cd3f2bbeb7f3529d0edded6 upstream.
>
> Sebastian reported a crash caused by a
On 2015-09-13 14:15:21, Julia Lawall wrote:
> Remove unneeded NULL test.
>
> The semantic patch that makes this change is as follows:
> (http://coccinelle.lip6.fr/)
>
> //
> @@ expression x; @@
> -if (x != NULL)
> \(kmem_cache_destroy\|mempool_destroy\|dma_pool_destroy\)(x);
> //
>
> Signed-
From: Junwei Zhang
the permanent protocol nodes are at the head of the list.
So only need check all these nodes.
and insert the new node after the last permanent protocol node,
no matter new node is permanent or not.
If the inserted proto conflicts with existing permanent protocol,
then goto ou
Many places in the kernel use 'for' loop with nr_node_ids. For the architectures
which supports sparse numa ids, this will result in some unnecessary allocations
for non existing nodes.
(for e.g., numa node numbers such as 0,1,16,17 is common in powerpc.)
So replace the for loop with for_each_node
Signed-off-by: Raghavendra K T
---
arch/powerpc/mm/numa.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c
index 8b9502a..8d8a541 100644
--- a/arch/powerpc/mm/numa.c
+++ b/arch/powerpc/mm/numa.c
@@ -80,7 +80,7 @@ static void __ini
The functions used in the patch are in slowpath, which gets called
whenever alloc_super is called during mounts.
Though this should not make difference for the architectures with
sequential numa node ids, for the powerpc which can potentially have
sparse node ids (for e.g., 4 node system having nu
Use IS_ALIGNED() to determine whether the shadow span two bytes. It
generates less code and more readable. Also add some comments in shadow
check functions.
Please apply "kasan: fix last shadow judgement in memory_is_poisoned_16()"
first.
Signed-off-by: Xishi Qiu
---
mm/kasan/kasan.c | 24 +
Hi David
Konrad just ping me on this patch. I originally think I missed to cc you
but I does.
Could you ack or nak it?
thanks
zduan
在 2015/9/2 19:04, Juergen Gross 写道:
On 09/02/2015 12:51 PM, Zhenzhong Duan wrote:
On some numa system, after dom0 up, we see below warning even if
there are
e
Hi
Just in the list, I see the patch "[PATCH v2] futex: lower the lock contention
on the HB lock during wake up" at
http://www.gossamer-threads.com/lists/linux/kernel/2199938?search_string=futex;#2199938.
But I see another patch with same name, different content here,
23b7776290b10297fe2c
Hello,
On Mon, Sep 14, 2015 at 06:05:19PM -0700, John Stultz wrote:
> As noted in include/linux/kernel.h:
> "abs() should not be used for 64-bit types (s64, u64, long long)
> - use abs64() for those."
>
> Unfortunately, there are quite a number of places where abs()
> was used w/ 64bit values i
1 - 100 of 842 matches
Mail list logo
