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].
>>
>>
>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
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
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
--
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
* 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
>
* 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
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
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:
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
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
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
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)
> >
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
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
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
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
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
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
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
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 ++
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
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
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
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.
>
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
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
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,
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.
> 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
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
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
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
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
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.
>>
>>
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
> >> :
> >> > +++
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
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
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
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
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
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
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);
> //
>
>
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
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
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
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
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
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,
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
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: Eric Dumazet
>
> commit beb39db59d14990e401e235faf66a6b9b31240b0 upstream.
>
> We have two problems in UDP stack
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.
[...]
This is missing the 'udf:' prefix in the subject line. Otherwise fine.
Ben.
--
To unsubscribe from this list: send the line "unsubscribe
ACK. Thanks.
On 09/13/2015 08:15 AM, 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);
//
On 2015/9/14 15:43, Ingo Molnar wrote:
>
> * Xishi Qiu wrote:
>
>> We can only echo 0 or 1 > "/proc/sys/kernel/numa_balancing", usually 1 means
>> enable and 0 means disable. But when echo 1, it shows the value is 65536,
>> this
>> is confusion.
>>
>> Signed-off-by: Xishi Qiu
>> ---
>>
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 really. Maintaining rt is hard work. Try it, you'll see that it
On 2015/9/15 5:37, Arnaldo Carvalho de Melo wrote:
Em Sun, Sep 06, 2015 at 07:13:35AM +, Wang Nan escreveu:
regs_query_register_offset() is a helper function which converts
register name like "%rax" to offset of a register in 'struct pt_regs',
which is required by BPF prologue generator.
On 09/14/2015 02:54 PM, Stephen Boyd wrote:
> The current driver implementation supports only 128 peripherals.
> Add support for more than 128 peripherals by taking a lazy
> caching approach to the mapping tables. Instead of reading the
> tables at boot given some fixed size, read them on an as
Hi,
I have reported the same issue in [0]...
You write in [1]...
[ cut here ]
WARNING: CPU: 3 PID: 24 at drivers/gpu/drm/i915/intel_display.c:1377
assert_planes_disabled+0xe4/0x150 [i915]()
plane A assertion failure, should be disabled but not
...
I can confirm this was
On Mon, Sep 14 2015 at 02:21:04 PM, Rob Herring wrote:
> On Fri, Sep 11, 2015 at 12:31 PM, Mitchel Humpherys
> wrote:
>> Any overlap in the reserved memory regions (those specified in the
>> reserved-memory DT node) is a bug. These bugs might go undetected as
>> long as the contested region
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.
>
> Signed-off-by: Vitaly Wool
> ---
>
I am seeing the following new warning on my test system.
Haven't had a chance to bisect yet. Please let me know
if you like more information. I haven't seen this on 4.2
and all of 4.2-rc releases.
thanks,
-- Shuah
[ cut here ]
WARNING: CPU: 3 PID: 24 at
On 2015/9/14 23:07, Sören Brinkmann wrote:
Hi Shawn,
overall, it looks good to me. I have some questions though.
On Mon, 2015-09-14 at 02:29PM +0800, Shawn Lin wrote:
[...]
+err_phy_exit:
+ phy_init(phy);
Just to confirm, are these actions in the error path correct? E.g.
if the
This patch fixes one cases where abs() was being used with 64-bit
nanosecond values, where the result may be capped at 32-bits.
This potentially could cause watchdog false negatives on 32-bit
systems, so this patch addresses the issue by using abs64().
Cc: Prarit Bhargava
Cc: Richard Cochran
The ext4_fsblk_t type is a long long, which should not be used
with abs(), as is done in ext4_mb_check_group_pa().
This patch modifies ext4_mb_check_group_pa() to use abs64()
instead.
Cc: "Theodore Ts'o"
Cc: Andreas Dilger
Cc: Ingo Molnar
Cc: linux-e...@vger.kernel.org
Signed-off-by: John
s64 values should not be used with abs(), as is one
in __percpu_counter_compare(), since it may cap the
result to 32-bits.
This patch modifies __percpu_counter_compare() to
use abs64() instead.
Cc: Dave Chinner
Cc: Tejun Heo
Cc: Ingo Molnar
Signed-off-by: John Stultz
---
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
returned value is erroniously capped at
This patch fixes a usage of abs() with a 64-bit value which could
truncate the result to 32-bits, by replacing it with abs64().
In this case, its unlikely any issue could have been caused by
this, since we're calculating a second delta, which wouldn't be
larger then 32-bit.
Cc: Prarit Bhargava
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 common
> zpool API and takes care of the callbacks that have to be
>
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 in the kernel, and the results are
then silently capped to 32-bit values on
On (09/14/15 15:50), Vitaly Wool wrote:
> It makes sense to have control over what compression ratios are
> ok to store pages uncompressed and what not.
um... I don't want this to be exported. this is very 'zram-internal'.
besides, you remove the exsiting default value
- static const size_t
This form of the earlycon parameter was added by commit fb11ffe74c794a5
("of/fdt: add FDT serial scanning for earlycon") without documentation.
Signed-off-by: Scott Wood
---
Documentation/kernel-parameters.txt | 4
1 file changed, 4 insertions(+)
diff --git
Hi Heiko,
在 2015年09月15日 02:40, Heiko Stübner 写道:
Hi Caesar, Jinkun,
Am Dienstag, 8. September 2015, 14:18:20 schrieb Caesar Wang:
This add the necessary binding documentation for the power domains
found on Rockchip SoCs.
Signed-off-by: jinkun.hong
Signed-off-by: Caesar Wang
What is Jinkun
On Mon, 14 Sep 2015 17:23:58 PDT (-0700), kir...@shutemov.name 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
On (09/14/15 15:49), Vitaly Wool wrote:
> While using ZRAM on a small RAM footprint devices, together with KSM,
> I ran into several occasions when moving pages from compressed swap back
> into the "normal" part of RAM caused significant latencies in system
> operation.
> By using zbud I lose in
Hi Alan,
On Sat, Sep 12, 2015 at 7:40 PM, Alan Stern wrote:
> On Sat, 12 Sep 2015, Rafael J. Wysocki wrote:
>
>> On Friday, September 11, 2015 03:01:14 PM Alan Stern wrote:
>
>> > There's also an issue about other types of dependencies. For instance,
>> > it's conceivable that device B might be
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, the man pages seem to indicate that
> MAP_UNINITIALIZED should be
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
126835781470996 348904 14503478 dd4e36 before
On 14.09.2015 21:43, Javier Martinez Canillas wrote:
> They aren't needed and are just creating null statements so remove it.
>
> Signed-off-by: Javier Martinez Canillas
>
> ---
>
> drivers/input/touchscreen/mms114.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Patch is
On 2015년 09월 15일 02:49, Vaishali Thakkar wrote:
> Use resource managed functions devm_usb_get_phy and
> devm_gpio_request to make error path simpler. To be
> compatible the change, various gotos are replaced
> with direct returns and unnecessary label
> gpio_req_failed is dropped.
>
> Also,
On 14.09.2015 21:04, Javier Martinez Canillas wrote:
> The Exynos5420 Peach Pit and Exynos5800 Peach Pi boards have a built-in
> Silicon Motion USB UVC WebCam. Enable support for the USB Video Class
> driver and its needed media Kconfig symbols so the camera is supported.
>
> Signed-off-by:
On 09/14, Kuninori Morimoto wrote:
> From: Kuninori Morimoto
>
> This patch adds CS2000 Fractional-N driver as clock provider.
> It is useful if it supports runtime clock setting, but it supports
> fixed clock rate only at this point.
Makes it sound pretty useless!
>
> diff --git
Hello Eric,
On Sun, Sep 13, 2015 at 06:57:27PM -0500, Eric Biggers wrote:
> Signed-off-by: Eric Biggers
> ---
> fs/userfaultfd.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/fs/userfaultfd.c b/fs/userfaultfd.c
> index 634e676..f9aeb40 100644
> ---
On 14.09.2015 21:34, Emilio López wrote:
> The Peach boards use the EC to store the vboot context information,
> so add the corresponding properties on the EC node to indicate so.
>
> Signed-off-by: Emilio López
> ---
>
> Changes from v1:
> - none
>
>
1 - 100 of 1674 matches
Mail list logo
