gcc-6 started warning by default about variables that are not
used anywhere and that are marked 'const', generating many
false positives in an allmodconfig build, e.g.:
arch/arm/mach-davinci/board-da830-evm.c:282:20: warning:
'da830_evm_emif25_pins' defined but not used [-Wunused-const-variable=]
On Tue, May 10, 2016 at 03:44:29PM -0400, Vivien Didelot wrote:
> Some switch models have a STU (per VLAN port state database). Add a new
> capability flag to switches info, instead of checking their family.
>
> Also if the 6165 family has an STU, it must have a VTU, so add the
> MV88E6XXX_FLAG_VT
On Tue, 2016-05-10 at 14:09 -0700, Eric Dumazet wrote:
> On Tue, May 10, 2016 at 1:46 PM, Hannes Frederic Sowa
> wrote:
>
> > I agree here, but I don't think this patch particularly is a lot of
> > bloat and something very interesting people can play with and extend upon.
> >
>
> Sure, very rare
Paolo Valente writes:
> diff --git a/block/bio.c b/block/bio.c
> index 807d25e..e9b136a 100644
> --- a/block/bio.c
> +++ b/block/bio.c
> @@ -622,6 +622,8 @@ struct bio *bio_clone_fast(struct bio *bio, gfp_t
> gfp_mask, struct bio_set *bs)
> }
> }
>
> + bio_clone_blkcg_a
On Tue, 2016-05-10 at 14:31 -0700, Eric Dumazet wrote:
> On Tue, 2016-05-10 at 14:09 -0700, Eric Dumazet wrote:
> >
> > On Tue, May 10, 2016 at 1:46 PM, Hannes Frederic Sowa
> > wrote:
> >
> > >
> > > I agree here, but I don't think this patch particularly is a lot
> > > of
> > > bloat and some
> > valid_block_count =
> > - sbi->total_valid_block_count + (block_t)count;
> > + sbi->total_valid_block_count + (block_t)(*count);
> > if (unlikely(valid_block_count > sbi->user_block_count)) {
> > - spin_unlock(&sbi->stat_lock);
> > - return false;
Hello Alban,
On 05/10/2016 09:19 AM, Alban Bedel wrote:
> v4l2_async_cleanup() is always called before before calling the
> unbind() callback. However v4l2_async_cleanup() clear the asd member,
> so when calling the unbind() callback the v4l2_async_subdev is always
> NULL. To fix this save the asd
Il 10/05/2016 23:34, Jeff Moyer ha scritto:
Paolo Valente writes:
diff --git a/block/bio.c b/block/bio.c
index 807d25e..e9b136a 100644
--- a/block/bio.c
+++ b/block/bio.c
@@ -622,6 +622,8 @@ struct bio *bio_clone_fast(struct bio *bio, gfp_t gfp_mask,
struct bio_set *bs)
}
On Tue, 2016-05-10 at 12:49 -0700, Dan Williams wrote:
> On Tue, May 10, 2016 at 9:23 AM, Toshi Kani wrote:
> >
> > blkdev_dax_capable() is similar to bdev_dax_supported(), but needs
> > to remain as a separate interface for checking dax capability of
> > a raw block device.
> >
> > Rename and r
On Fri, 2016-29-04 at 08:55:15 UTC, Alexey Kardashevskiy wrote:
> We are going to have multiple different types of PHB on the same system
> with POWER8 + NVLink and PHBs will have different IOMMU ops. However
> we only really care about one callback - create_table - so we can
> relax the compatibil
On Thu, 2016-05-05 at 20:44:44 UTC, Lennart Sorensen wrote:
> powerpc: Fix sstep compile on powerpcspe
>
> Commit be96f63375a14ee8e690856ac77e579c75bd0bae introduced ldarx and stdcx
> into the instructions in sstep.c, which are not accepted by the assembler
> on powerpcspe, but does seem to be acc
On Fri, May 06, 2016 at 06:29:40PM +0530, Muhammad Falak R Wani wrote:
> The function setup_timer combines the initialization of a timer with
> the initialization of the timer's function and data fields.
> The multiline code for timer initialization is now replaced
> with function setup_timer.
>
>
On Fri, May 06, 2016 at 06:29:41PM +0530, Muhammad Falak R Wani wrote:
> The function setup_timer combines the initialization of a timer with
> the initialization of the timer's function and data fields.
> The multiline code for timer initialization is now replaced
> with function setup_timer.
>
>
On Tue, 2016-05-10 at 17:35 -0400, Rik van Riel wrote:
> You might need another one of these in invoke_softirq()
>
Excellent.
I gave it a quick try (without your suggestion), and host seems to
survive a stress test.
Of course we do have to fix these problems :
[ 147.781629] NOHZ: local_softi
When a bio is cloned, the newly created bio must be associated with
the same blkcg as the original bio (if BLK_CGROUP is enabled). If
this operation is not performed, then the new bio is not associated
with any group, and the group of the current task is returned when
the group of the bio is reques
Add the PMU so we can get proper perf event support on this SoC.
Signed-off-by: Stephen Boyd
---
arch/arm64/boot/dts/qcom/msm8916.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi
b/arch/arm64/boot/dts/qcom/msm8916.dtsi
index 96812007850e..c440f
Hi Mauro,
thanks for looking after this patch.
On 05/07/16 15:22, Mauro Carvalho Chehab wrote:
Hi Soeren,
Em Sun, 7 Feb 2016 20:22:36 +0100
Soeren Moch escreveu:
On 27.12.2015 21:41, Soeren Moch wrote:
Implement memory barriers according to Documentation/circular-buffers.txt:
- use smp_sto
On Tue, 2016-05-10 at 14:53 -0700, Eric Dumazet wrote:
> On Tue, 2016-05-10 at 17:35 -0400, Rik van Riel wrote:
>
> > You might need another one of these in invoke_softirq()
> >
>
> Excellent.
>
> I gave it a quick try (without your suggestion), and host seems to
> survive a stress test.
>
> O
On Tue, 2016-05-10 at 14:53 -0700, Eric Dumazet wrote:
> On Tue, 2016-05-10 at 17:35 -0400, Rik van Riel wrote:
>
> >
> > You might need another one of these in invoke_softirq()
> >
> Excellent.
>
> I gave it a quick try (without your suggestion), and host seems to
> survive a stress test.
>
>
On 05/07/16 15:26, Mauro Carvalho Chehab wrote:
Em Sat, 7 May 2016 10:22:35 -0300
Mauro Carvalho Chehab escreveu:
Hi Soeren,
Em Sun, 7 Feb 2016 20:22:36 +0100
Soeren Moch escreveu:
On 27.12.2015 21:41, Soeren Moch wrote:
Implement memory barriers according to Documentation/circular-buffer
On Tue, May 10, 2016 at 10:21:39PM +0200, Ingo Molnar wrote:
>
> * Peter Zijlstra wrote:
>
> > Mike reported that the recent commit 3a47d5124a95 ("sched/fair: Fix
> > fairness issue on migration") broke interactivity and the signal
> > starve test.
>
> This looks pretty dangerous for v4.6 - how
On Tue, May 10, 2016 at 2:30 PM, Arnd Bergmann wrote:
> gcc-6 started warning by default about variables that are not
> used anywhere and that are marked 'const', generating many
> false positives in an allmodconfig build, e.g.:
>
> arch/arm/mach-davinci/board-da830-evm.c:282:20: warning:
> 'da83
We use similar structured code to read and write the kmapped
firmware pages. The only difference is read copies from the kmap
region and write copies to it. Consolidate this into one function
to reduce duplication.
Cc: Vikram Mulukutla
Signed-off-by: Stephen Boyd
---
drivers/base/firmware_class
Some systems are memory constrained but they need to load very
large firmwares. The firmware subsystem allows drivers to request
this firmware be loaded from the filesystem, but this requires
that the entire firmware be loaded into kernel memory first
before it's provided to the driver. This can le
Some systems are memory constrained but they need to load very
large firmwares. The firmware subsystem allows drivers to request
this firmware be loaded from the filesystem, but this requires
that the entire firmware be loaded into kernel memory first
before it's provided to the driver. This can le
From: Vikram Mulukutla
Some low memory systems with complex peripherals cannot afford to
have the relatively large firmware images taking up valuable
memory during suspend and resume. Change the internal
implementation of firmware_class to disallow caching based on a
configurable option. In the n
I think you should be sending your patches to linux-arm-kernel rather
than linux-arm...
On Tue, May 10, 2016 at 03:01:49PM -0700, Stephen Boyd wrote:
> Add the PMU so we can get proper perf event support on this SoC.
>
> Signed-off-by: Stephen Boyd
> ---
> arch/arm64/boot/dts/qcom/msm8916.dtsi
On 05/10/16 12:10, Borislav Petkov wrote:
> On Tue, May 10, 2016 at 12:03:48PM -0700, H. Peter Anvin wrote:
>> Also, to be fair... if the problem is with these being in C then we
>> could just do it in assembly easily enough.
>
> I thought about converting the __sw_hweight* variants to asm but
> _
On 10.05.2016 23:09, Eric Dumazet wrote:
> On Tue, May 10, 2016 at 1:46 PM, Hannes Frederic Sowa
> wrote:
>
>> I agree here, but I don't think this patch particularly is a lot of
>> bloat and something very interesting people can play with and extend upon.
>>
>
> Sure, very rarely patch authors
On Tue, May 10, 2016 at 8:59 AM, Daniel Vetter wrote:
>> if (ret)
>> return ret;
>>
>> /* How to handle !visible, is it even possible? */
>
> if (!visible)
> return -EINVAL;
>
> You can't, so need to reject it.
Ok, on further thought I think we need a bit m
On Tue, 2016-05-10 at 15:02 -0700, Eric Dumazet wrote:
> On Tue, 2016-05-10 at 14:53 -0700, Eric Dumazet wrote:
> > On Tue, 2016-05-10 at 17:35 -0400, Rik van Riel wrote:
> >
> > > You might need another one of these in invoke_softirq()
> > >
> >
> > Excellent.
> >
> > I gave it a quick try (wi
Enable the sdcard slot and wire up the regulators for the two
storage controllers found on the apq8074 dragonboard.
Signed-off-by: Stephen Boyd
---
arch/arm/boot/dts/qcom-apq8074-dragonboard.dts | 48 ++
1 file changed, 48 insertions(+)
diff --git a/arch/arm/boot/dts/qco
Add the appropriate min/max voltages for the regulators on the
apq8074 dragonboard so that they can be used by clients properly.
Signed-off-by: Stephen Boyd
---
arch/arm/boot/dts/qcom-apq8074-dragonboard.dts | 199 +
1 file changed, 199 insertions(+)
diff --git a/arch/ar
On 05/09/2016 04:35 AM, Chen Feng wrote:
Add ion cached pool in system heap. This patch add a cached pool
in system heap. It has a great improvement of alloc for cached
buffer.
Can you give some benchmark numbers here?
v1: Makes the cached buffer zeroed before going to pool
Signed-off-by: C
On Wed, 2016-05-11 at 00:32 +0200, Hannes Frederic Sowa wrote:
> Not only did we want to present this solely as a bugfix but also as as
> performance enhancements in case of virtio (as you can see in the cover
> letter). Given that a long time ago there was a tendency to remove
> softirqs complete
Hello. My Name is Precious,i saw your profile and became interested to know
you, hope i will not be embarrassed.
i am very happy to contact you for us to know ourselves distance, age doesn't
matter at all.i have important thing to share with you.
i will like you to send Email to my private Email
Florian Fainelli wrote:
Are you utilizing the PHYLIB APIs properly? You need at least a
phy_start() to start the PHY state machine, and an adjust_link callback
to be provided to phy_connect() (or of_phy_connect()) to manage link
state changes. And that's the very basic minimum here, there could b
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in:
fs/overlayfs/super.c
between commit:
420598d5bf9c ("ovl: ignore permissions on underlying lookup")
from the overlayfs tree and commit:
b9e1d435fdf4 ("ovl_lookup_real(): use lookup_one_len_unlocked()")
from the vfs tree.
Hi Tejun,
2016-05-10 5:50 GMT+08:00 Wanpeng Li :
> Cc Thomas, the new state machine author,
> 2016-05-10 1:00 GMT+08:00 Tejun Heo :
>> Hello,
>>
>> On Thu, May 05, 2016 at 09:41:31AM +0800, Wanpeng Li wrote:
>>> The boot CPU handles housekeeping duty(unbound timers, workqueues,
>>> timekeeping, ...
On 05/10/2016 04:18 PM, Timur Tabi wrote:
> Florian Fainelli wrote:
>> Are you utilizing the PHYLIB APIs properly? You need at least a
>> phy_start() to start the PHY state machine, and an adjust_link callback
>> to be provided to phy_connect() (or of_phy_connect()) to manage link
>> state changes.
The mm-of-the-moment snapshot 2016-05-10-16-31 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
On Tue, 10 May 2016 11:52:15 -0400
Jeff Moyer wrote:
> > +static inline bool blk_trace_note_message_enabled(struct request_queue *q)
> > +{
> > + struct blk_trace *bt = q->blk_trace;
> > + if (likely(!bt))
> > + return false;
> > + return bt->act_mask & BLK_TC_NOTIFY;
>
> Do
CPUID function 0x0d, sub function (i, i > 1) returns in ecx[1] the
alignment requirement of component i when the compacted format is used.
If ecx[1] is 0, component i is located immediately following the preceding
component. If ecx[1] is 1, component i is located on the next 64-byte
boundary follo
Keep init_fpstate.xsave.header.xfeatures as zero for init optimization.
This is important for init optimization that is implemented in processor.
If a bit corresponding to an xstate in xstate_bv is 0, it means the
xstate is in init status and will not be read from memory to the processor
during XRS
Hi Al,
Hopefully this addresses your concerns. I couldn't find a better name for
lookup_hash(), after all it's just that.
Please pull:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-linus
---
Miklos Szeredi (4):
vfs: add vfs_select_inode() helper
vfs: re
XSAVES is a kernel-mode instruction. It offers a compacted format and
memory-write optimization. These patches fix issues in the first
implementation.
Changes since Version 5:
Patch 1, 2 - Change names to fpu_user_xstate_size and fpu_kernel_xstate_size;
fix some comments, etc.
Patch
The XSAVE area of kernel can be in standard or compacted format;
it is always in standard format for user mode. When XSAVES is
enabled, the kernel uses the compacted format and it is necessary
to use a separate fpu_user_xstate_size for signal/ptrace frames.
Based on an earlier patch from Fenghua Y
We did not handle XSAVES instructions correctly. There were issues in
converting between standard and compacted format when interfacing with
user-space. These issues have been corrected.
Add a WARN_ONCE() to make it clear that XSAVES supervisor states are not
yet implemented.
Signed-off-by: Yu-ch
XSAVES is a kernel instruction and uses a compacted format. When working
with user space, the kernel should provide standard-format, non-supervisor
state data. We cannot do __copy_to_user() from a compacted- format kernel
xstate area to a signal frame.
Dave Hansen proposes this method to simplify
When the kernel is using XSAVES compacted format, we cannot do
__copy_from_user() from a signal frame, which has standard-format data.
Fix it by using copyin_to_xsaves(), which converts between formats and
filters out all supervisor states that we do not allow userspace to
write.
Signed-off-by: Yu
It is an error to request a disabled XSAVE/XSAVES component address.
For that case, make __raw_xsave_addr() return a NULL and issue a
warning.
Signed-off-by: Yu-cheng Yu
---
arch/x86/kernel/fpu/xstate.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/x86/kernel/fpu/xstate.c b/arch/
CPUID function 0x0d, sub function (i, i > 1) returns in ebx the offset of
xstate component i. Zero is returned for a supervisor state. A supervisor
state can only be saved by XSAVES and XSAVES uses a compacted format.
There is no fixed offset for a supervisor state. This patch checks and
makes sure
XSAVES uses compacted format and is a kernel instruction. The kernel
should use standard-format, non-supervisor state data for PTRACE.
Signed-off-by: Yu-cheng Yu
---
arch/x86/include/asm/fpu/xstate.h | 5 +-
arch/x86/kernel/fpu/regset.c | 56 +
arch/x86/kernel/fpu/xstate.c
Hi Rob/Mark,
Do you have any more comments, please?
Thanks,
Tai
On Mon, May 2, 2016 at 2:46 PM, Tai Tri Nguyen wrote:
> Hi Rob,
>
> On Mon, May 2, 2016 at 1:56 PM, Rob Herring wrote:
>> On Wed, Apr 20, 2016 at 12:31:22PM +0100, Will Deacon wrote:
>>> On Mon, Apr 18, 2016 at 01:04:53PM -0700, T
On Thu, 2016-05-05 at 18:08 -0400, James Bottomley wrote:
> On Thu, 2016-05-05 at 22:49 +0100, Djalal Harouni wrote:
> > On Thu, May 05, 2016 at 07:56:28AM -0400, James Bottomley wrote:
> > > On Thu, 2016-05-05 at 08:36 +0100, Djalal Harouni wrote:
> > > > On Wed, May 04, 2016 at 05:06:19PM -0400,
In XSAVES mode if fpstate_init() is used to initialize a
task's extended state area, xsave.header.xcomp_bv[63] must
be set. Otherwise, when the task is scheduled, a warning is
triggered from copy_kernel_to_xregs().
One such test case is: setting an invalid extended state
through PTRACE. When xstat
Component offset print out was incorrect for XSAVES. Correct it and move
to a separate function.
Signed-off-by: Yu-cheng Yu
Reviewed-by: Dave Hansen
---
arch/x86/kernel/fpu/xstate.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/fpu/xstat
The arrays xstate_offsets[] and xstate_sizes[] record XSAVE standard-
format offsets and sizes. Values for non-extended state components
fpu and xmm's were not initialized or used. Ptrace format conversion
needs them. Fix it.
Signed-off-by: Yu-cheng Yu
Reviewed-by: Dave Hansen
---
arch/x86/kern
User space uses standard format xsave area. fpstate in signal frame
should have standard format size.
To explicitly distinguish between xstate size in kernel space and the
one in user space, we rename xstate_size to fpu_kernel_xstate_size.
This patch is not fixing a bug. It just makes kernel code
On Tuesday, April 19, 2016 01:30:10 PM Sudeep Holla wrote:
> ACPI 6.0 introduced an optional object _LPI that provides an alternate
> method to describe Low Power Idle states. It defines the local power
> states for each node in a hierarchical processor topology. The OSPM can
> use _LPI object to s
The 'mmc-hs400-enhanced-strobe' property has been acked by Rob Herring,
though it's still not merged.
Signed-off-by: Brian Norris
---
arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-evb.dts
b/arch/
The bindings for rk3399's SDHCI + eMMC PHY have been accepted, so let's
support eMMC now.
Note that 'rockchip,rk3399-sdhci-5.1' is not documented, but per Heiko's
previous suggestion, we don't want to clutter the arasan doc, and it's
just a precautionary measure to have it.
Signed-off-by: Brian N
On Tuesday, April 19, 2016 01:30:12 PM Sudeep Holla wrote:
> This patch adds appropriate callbacks to support ACPI Low Power Idle
> (LPI) on ARM64.
>
> It also selects ARCH_SUPPORTS_ACPI_PROCESSOR_LPI if ACPI is enabled
> on ARM64.
Can you remind me why we need the ARCH_SUPPORTS_ACPI_PROCESSOR_LP
On Monday, May 09, 2016 03:59:29 PM Paul Gortmaker wrote:
> [Re: [PATCH] drivers/acpi: make evged.c explicitly non-modular] On 09/05/2016
> (Mon 15:35) Sinan Kaya wrote:
>
> > +Rafael,
> >
> > On 5/9/2016 2:40 PM, Paul Gortmaker wrote:
> > > The Makefile/Kconfig currently controlling compilation
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
net/netfilter/nf_conntrack_core.c
between commit:
70d72b7e060e ("netfilter: conntrack: init all_locks to avoid debug warning")
from the net tree and commit:
a3efd81205b1 ("netfilter: conntrack: move generation seqc
A cgroup gets assigned a low limit, but the cgroup could never dispatch
enough IO to cross the low limit. In such case, the queue state machine
will remain in LIMIT_LOW state and all other cgroups will be throttled
according to low limit. This is unfair for other cgroups. We will treat
the cgroup i
Add trace log in new low/high logic to help dignose issues.
Signed-off-by: Shaohua Li
---
block/blk-throttle.c | 43 +--
1 file changed, 41 insertions(+), 2 deletions(-)
diff --git a/block/blk-throttle.c b/block/blk-throttle.c
index a5f3435..d35bbf1 10064
We are going to support low/high limit, each cgroup will have 3 limits
after that. This patch prepares for the multiple limits change.
Signed-off-by: Shaohua Li
---
block/blk-throttle.c | 109 ---
1 file changed, 68 insertions(+), 41 deletions(-)
Hi,
This patch set adds low/high limit for blk-throttle cgroup. The interface is
io.low and io.high.
low limit implements best effort bandwidth/iops protection. If one cgroup
doesn't reach its low limit, no other cgroups can use more bandwidth/iops than
their low limit. cgroup without low limit i
When queue is in LIMIT_LOW state and all cgroups with low limit cross
the bps/iops limitation, we will upgrade queue's state to
LIMIT_HIGH/LIMIT_MAX
For a cgroup hierarchy, there are two cases. Children has lower low
limit than parent. Parent's low limit is meaningless. If children's
bps/iops cros
cgroup could be throttled to a limit but when other cgroups are idle,
queue enters a higher state and so the group should be throttled to a
higher limit. It's possible the cgroup is sleeping because of throttle
and other cgroups don't dispatch IO any more. In this case, nobody can
trigger current d
Hi,
> -Original Message-
> From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of
> Rafael J. Wysocki
> Sent: Wednesday, May 11, 2016 3:07 AM
> To: Chen, Yu C
> Cc: linux...@vger.kernel.org; Srinivas Pandruvada; Rafael J. Wysocki; Len
> Brown; Viresh Kumar; Zhang, Rui; Linux K
Add low limit for cgroup and corresponding cgroup interface.
Signed-off-by: Shaohua Li
---
block/blk-throttle.c | 142 +++
1 file changed, 110 insertions(+), 32 deletions(-)
diff --git a/block/blk-throttle.c b/block/blk-throttle.c
index 162d54c..e
Add high limit for cgroup and corresponding cgroup interface.
Signed-off-by: Shaohua Li
---
block/blk-throttle.c | 74
1 file changed, 69 insertions(+), 5 deletions(-)
diff --git a/block/blk-throttle.c b/block/blk-throttle.c
index a462e2f..57
each queue will have a state machine. Initially queue is in LOW_LIMIT
state, which means all cgroups will be throttled according to their low
limit. After all cgroups with low limit cross the limit, the queue state
gets upgraded to high/max state. This will guarantee cgroups with low
limit have at
When queue state machine is in higher state, say LIMIT_MAX state without
LIMIT_HIGH state, but a cgroup is below its low limit for some time, the
queue should be downgraded to lower state as cgroup's low limit doesn't
meet.
Signed-off-by: Shaohua Li
---
block/blk-throttle.c | 160 +++
Handle high limit like we handle low limit including
downgrade/upgrade/idle detection logic. If cgroup has high limit, its
throttling limit is high limit. Otherwise the throttling limit is max
limit.
queue downgrades from LIMIT_HIGH/LIMIT_MAX to LIMIT_LOW if cgroup is below
low limit. queue upgrad
On Tue, May 10, 2016 at 11:52:15AM -0400, Jeff Moyer wrote:
> Shaohua Li writes:
>
> > if trace isn't enabled, parsing cgroup path just wastes cpu
> >
> > Signed-off-by: Shaohua Li
> > ---
> > block/blk-throttle.c | 5 ++---
> > include/linux/blktrace_api.h | 9 +
> > 2 files ch
From: Corey Minyard
Lots of little changes needed to be made to clean these up, remove the
four byte pointer assumption and traverse the pid queue properly.
Also consolidate the traceback code into a single function instead
of having three copies of it.
Signed-off-by: Corey Minyard
---
Changes
On Tue, 2016-05-10 at 18:50 +, Scott Wood wrote:
> On 05/09/2016 03:20 AM, Horia Ioan Geanta Neag wrote:
> > On 5/5/2016 6:37 PM, Horia Geantă wrote:
> > > This will allow device drivers to consistently use io{read,write}XX
> > > also for 64-bit accesses.
> > >
> > > Signed-off-by: Horia Ge
On Tue, May 10, 2016 at 04:36:56PM -0700, James Bottomley wrote:
> mount -t shiftfs
Note to self: do not eat while reading l-k...
On Wed, Apr 27, 2016 at 8:07 PM, David Daney wrote:
> From: David Daney
>
> Based on git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git
> for-next/core branch at commit 643d703d2d2d ("arm64: compat: Check for
> AArch32 state")
>
> ACPI 5.1 already introduced NUMA support for ARM64, whi
2016-05-06 23:43 GMT+08:00 Tomasz Grabiec :
[...]
> prev_comm=python prev_pid=873 prev_prio=120 prev_state=R ==>
> next_comm=python next_pid=874 next_prio=120
> python 874 [002] 3273334.932741: probe:hrtick: (8109b430)
> python 874 [002] 3273334.932742: sched:sched_stat_runtime:
> c
On Tue, May 10, 2016 at 04:36:56PM -0700, James Bottomley wrote:
> +static int shiftfs_rename2(struct inode *olddir, struct dentry *old,
> +struct inode *newdir, struct dentry *new,
> +unsigned int flags)
> +{
> + struct dentry *rodd = olddir->i_p
2016-05-11 8:53 GMT+08:00 Wanpeng Li :
> 2016-05-06 23:43 GMT+08:00 Tomasz Grabiec :
> [...]
>> prev_comm=python prev_pid=873 prev_prio=120 prev_state=R ==>
>> next_comm=python next_pid=874 next_prio=120
>> python 874 [002] 3273334.932741: probe:hrtick: (8109b430)
>> python 874 [002
On 2016/5/11 8:02, Brian Norris wrote:
The 'mmc-hs400-enhanced-strobe' property has been acked by Rob Herring,
though it's still not merged.
Hi Brain,
I'm not sure whether it's acceptable to upstream new property which
isn't merged yet. My major concern is that as the patchset supporting
h400
Hi Greg,
On Mon, May 09, 2016 at 02:26:13PM +0200, Kroah-Hartman wrote:
On Sun, May 08, 2016 at 10:45:16AM -0400, YU Bo wrote:
The patch fixed warning reported by checkpatch.pl: Block comments use a
trailing */ on a separate line.
Signed-off-by: YU Bo
---
drivers/staging/wlan-ng/prism2mgmt.h
Hi all,
After merging the sound-asoc tree, today's linux-next build (x86_64
allmodconfig) failed like this:
sound/soc/intel/boards/bxt_rt298.c:257:3: error: unknown field 'be_id'
specified in initializer
.be_id = 0,
^
sound/soc/intel/boards/bxt_rt298.c:274:3: error: unknown field 'be_id'
On Mon, 2 May 2016, Jiri Kosina wrote:
> On Tue, 19 Apr 2016, Jiri Kosina wrote:
>
> > From: Jiri Kosina
> >
> > bch_writeback_thread() is calling try_to_freeze(), but that's just an
> > expensive no-op given the fact that the thread is not marked freezable.
> >
> > I/O helper kthreads, exactl
+ Huang Lin
On 2016/5/11 8:02, Brian Norris wrote:
The bindings for rk3399's SDHCI + eMMC PHY have been accepted, so let's
support eMMC now.
Note that 'rockchip,rk3399-sdhci-5.1' is not documented, but per Heiko's
previous suggestion, we don't want to clutter the arasan doc, and it's
just a pre
Hi,
On Wed, May 11, 2016 at 08:59:24AM +0800, Shawn Lin wrote:
> On 2016/5/11 8:02, Brian Norris wrote:
> >The 'mmc-hs400-enhanced-strobe' property has been acked by Rob Herring,
> >though it's still not merged.
> >
>
> Hi Brain,
>
> I'm not sure whether it's acceptable to upstream new property
Stefan,
On Tue, May 10, 2016 at 11:05:43AM -0400, Stefan Berger wrote:
> Jeremiah Mahler wrote on 05/10/2016 09:55:23 AM:
>
> >
> > all,
> >
> > My machine is locking up during suspend and I have bisected the
> > problem to this patch (e89f8b1ade9cc1a) in the latest linux-next
> > (20160506) k
In current system, when we set core_pattern to a pipe, both pipe program
and program's output are in host's filesystem.
But when we set core_pattern to a file, the container will write dump
into container's filesystem.
For example, when we set following core_pattern:
# echo "|/my_dump_pipe %s %c
To make the dump_pipe thread run in container's filesystem, we need to
make it possible to select its fs_root from fork.
Then the dump_pipe thread will exec user_defined pipe program in
container's fs_root, and the problem will also write dumpdata into
the same fs_root.
Signed-off-by: Zhao Lei
-
In current system, when we set core_pattern to a pipe, both pipe program
and program's output are in host's filesystem.
But when we set core_pattern to a file, the container will write dump
into container's filesystem.
Reason of above different is:
In pipe_mode dump_pattern setting, the process wh
In current system, when we set core_pattern to a pipe, both pipe program
and program's output are in host's filesystem.
But when we set core_pattern to a file, the container will write dump
into container's filesystem.
For example, when we set following core_pattern:
# echo "|/my_dump_pipe %s %c
在 2016/5/10 21:44, Arnaldo Carvalho de Melo 写道:
Em Tue, May 10, 2016 at 07:40:30AM +, He Kuang escreveu:
When unwinding callchains on a different machine, vdso info should be
provided so the unwind process won't be interrupted if address falls
into vdso region.
Currently, perf does try to
Hi Lee,
2016-05-10 20:26 GMT+09:00 Lee Jones :
>> +};
>> +MODULE_DEVICE_TABLE(of, uniphier_mfd_match);
>
> NACK. Please do not mix MFD and DT registration.
OK, thanks for review.
My basic thought was:
- Add an MFD node to my DTS only once.
If I need to expand it in the future, I will ju
> "Dan" == Dan Carpenter writes:
Dan> This missing break statement bug predates git. It's a very minor
Dan> thing, it means that we print a '?' instead of a 'z' in dmesg.
Applied to 4.7/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
This patch set contains 3 fixes for duplicate symbol creation in the
db-export implementation and one new symbol API required for the fixes.
commit 9c7b37cd63d0 already removed the majority of duplicates, but these
fixes take care of the remaining corner cases.
each patch (except for the 1st, whi
801 - 900 of 988 matches
Mail list logo
