"Chen, Hanxiao" writes:
>> -Original Message-
>> From: Eric W. Biederman [mailto:ebied...@xmission.com]
>> Sent: Thursday, October 09, 2014 1:56 AM
>>
>> Serge Hallyn writes:
>>
>> > Quoting Chen Hanxiao (chenhanx...@cn.fujitsu.com):
>> >> We could use setns to join the current ns,
>>
On 10/02/2014 08:52 PM, Andrzej Hajda wrote:
Hi,
+CC possible victims
On 10/02/2014 12:52 PM, Inki Dae wrote:
On 2014년 10월 02일 17:58, Joonyoung Shim wrote:
Hi Andrzej,
On 10/01/2014 05:14 PM, Andrzej Hajda wrote:
The patch disables vblanks during dpms off only if pagefilp has
not been
(2014/10/08 20:51), Wanpeng Li wrote:
>
> 于 10/8/14, 2:43 PM, Yasuaki Ishimatsu 写道:
>> While offling node by hot removing memory, the following divide error
>> occurs:
>>
>>divide error: [#1] SMP
>>[...]
>>Call Trace:
>> [...] handle_mm_fault
>> [...] ? try_to_wake_up
>>
Le 08/10/2014 22:03, David Miller a écrit :
From: Christophe Leroy
Date: Tue, 7 Oct 2014 15:04:53 +0200 (CEST)
When using a MPC8xx as a router, 'perf' shows a significant time spent in
fs_enet_interrupt() and fs_enet_start_xmit().
'perf annotate' shows that the time spent in
(2014/10/09 1:54), Peter Zijlstra wrote:
On Wed, Oct 08, 2014 at 12:42:24PM -0400, Rik van Riel wrote:
On 10/08/2014 02:43 AM, Yasuaki Ishimatsu wrote:
The divide error is rare case because the trigger is node offline.
By this patch, when both of private and shared are set to 0, diff
Hi Raghu,
On 10/08/2014 08:24 PM, Raghavendra KT wrote:
> On Wed, Oct 8, 2014 at 12:37 PM, Preeti U Murthy
> wrote:
>> There are two masks associated with cpusets. The cpus/mems_allowed
>> and effective_cpus/mems. On the legacy hierarchy both these masks
>> are consistent with each other. This
(2014/10/09 13:10), Xishi Qiu wrote:
> On 2014/10/3 18:06, Yasuaki Ishimatsu wrote:
>
>> Commit 92d585ef067d ("numa: fix NULL pointer access and memory
>> leak in unregister_one_node()") added kfree() of node struct in
>> unregister_one_node(). But node struct is freed by node_device_release()
>>
On 08/28/2014 03:05 AM, Sukadev Bhattiprolu wrote:
> Anshuman Khandual [khand...@linux.vnet.ibm.com] wrote:
> | This patch enables get and set of transactional memory related register
> | sets through PTRACE_GETREGSET/PTRACE_SETREGSET interface by implementing
> | four new powerpc specific
On Tue, Oct 7, 2014 at 5:33 AM, Michal Hocko wrote:
> On Fri 03-10-14 11:16:31, Cong Wang wrote:
>> I am sorry to confuse you that it is my the above test case which caused
>> this bug. No, we saw this bug in *production* in our data center, it happened
>> on 30+ machines!! :) The above insane
Hi all,
Today's linux-next merge of the percpu tree got a conflict in
kernel/irq_work.c between commit 76a33061b932 ("irq_work: Force raised
irq work to run on irq work interrupt") from the tip tree and commit
22127e93c587 ("time: Replace __get_cpu_var uses") from the percpu tree.
I fixed it up
The dgap_init_module() need to unwind for cleanup variables properly.
Because dgap_init_module() calls dgap_cleanup_module() for freeing
variables but this function is possible to free variables
which are not allocated.
Signed-off-by: Daeseok Youn
---
V2: change ulong which is non-standard to
Hi, Michal
On Wed, Oct 8, 2014 at 7:07 AM, Michal Hocko wrote:
> Hi Andrew, Rafael,
>
> this has been originally discussed here [1] but didn't lead anywhere AFAICS
> so I would like to resurrect them.
>
Thanks a lot for taking them for me! I was busy with some networking
stuffs and also
On 10/08/2014 11:23 PM, Will Deacon wrote:
On Thu, Oct 02, 2014 at 10:46:12AM +0100, AKASHI Takahiro wrote:
If tracer specifies -1 as a syscall number, this traced system call should
be skipped with a value in x0 used as a return value.
This patch implements this semantics, but there is one
> -Original Message-
> From: Eric W. Biederman [mailto:ebied...@xmission.com]
> Sent: Thursday, October 09, 2014 1:56 AM
>
> Serge Hallyn writes:
>
> > Quoting Chen Hanxiao (chenhanx...@cn.fujitsu.com):
> >> We could use setns to join the current ns,
> >> which did a lot of
On 2014/10/3 18:06, Yasuaki Ishimatsu wrote:
> Commit 92d585ef067d ("numa: fix NULL pointer access and memory
> leak in unregister_one_node()") added kfree() of node struct in
> unregister_one_node(). But node struct is freed by node_device_release()
> which is called in unregister_node(). So by
Hi all,
Today's linux-next merge of the tip tree got a conflict in
arch/arm64/include/asm/Kbuild between commit 2f06dbe4e4fc ("arm64: use
generic dma-contiguous.h") from the mips tree and commit c5c38ef3d703
("irq_work: Introduce arch_irq_work_has_interrupt()") from the tip tree.
I fixed it up
This patch fix following warning.
Warning(.//net/core/skbuff.c:4142): No description found for parameter
'header_len'
Warning(.//net/core/skbuff.c:4142): No description found for parameter
'data_len'
Warning(.//net/core/skbuff.c:4142): No description found for parameter
'max_page_order'
On Thu, Oct 09, 2014 at 05:30:20AM +0200, Frederic Weisbecker wrote:
> > Do I miss some other essential patch ?
>
> If you have used the diff in that URL then you've missed:
>
> x86: Tell irq work about self IPI support
>
> Without that the whole patchset has no effect.
Ok.
On Thu, Oct 09, 2014 at 11:07:04AM +0800, zhangzhiqiang wrote:
> On 2014/10/8 21:38, Will Deacon wrote:
> > On Wed, Oct 08, 2014 at 02:31:47PM +0100, gre...@linuxfoundation.org wrote:
> >> On Wed, Oct 08, 2014 at 10:17:41AM +0100, Will Deacon wrote:
> >>> On Wed, Oct 08, 2014 at 04:06:12AM +0100,
On 9 October 2014 05:31, Mike Turquette wrote:
> Whether you merge the patches now or later is fine by me. I prefer to
> get my patches out early and often so I can avoid any surprises later
> on. If you have a fundamental objection to these patches then please let
> me know. Otherwise it would
On Wed, Oct 08, 2014 at 10:02:40PM -0400, Dave Jones wrote:
> On Tue, Oct 07, 2014 at 07:42:47PM +0200, Thomas Gleixner wrote:
> > On Tue, 7 Oct 2014, Dave Jones wrote:
> >
> > > On Tue, Oct 07, 2014 at 05:30:27PM +0200, Frederic Weisbecker wrote:
> > >
> > > > > > Right, this patchset
On Fri, 2014-10-03 at 12:40 +0200, Lukasz Majewski wrote:
> Hi Eduardo, Rui,
>
> > On Wed, Sep 24, 2014 at 10:27:12AM +0200, Lukasz Majewski wrote:
> > > Without this check it was possible to execute cooling device
> > > binding code even when wrong max cooling state was read.
> > >
> > >
On Wed, 2014-09-24 at 10:27 +0200, Lukasz Majewski wrote:
> It turns out that some boards can have instance->lower greater than 0 and
> when thermal trend is dropping it results with next_target equal to -1.
>
> Since the next_target is defined as unsigned long it is interpreted as
> 0x
On 2014/10/8 21:38, Will Deacon wrote:
> On Wed, Oct 08, 2014 at 02:31:47PM +0100, gre...@linuxfoundation.org wrote:
>> On Wed, Oct 08, 2014 at 10:17:41AM +0100, Will Deacon wrote:
>>> On Wed, Oct 08, 2014 at 04:06:12AM +0100, zhangzhiqiang wrote:
hi all,
From: Dinh Nguyen
There are certain drivers that are required to get loaded very early using
arch_initcall. An example of such a driver is the SOCFPGA's FPGA bridge driver.
This driver has to get loaded early because it needs to enable FPGA components
that are connected to the bridge.
This FPGA
Hi,
Am 08.10.2014 um 15:02 schrieb Chen-Yu Tsai:
> This is v3 of the initial Allwinner A80 support series.
> This patch series adds very basic support for Allwinner's A80 SoC,
> a big.LITTLE architecture with 4 Cortex-A7s and 4 Cortex-A15s.
>
> Development is done on the A80 Optimus Board, the
On 10/08/2014 11:30 PM, Will Deacon wrote:
On Thu, Oct 02, 2014 at 10:46:15AM +0100, AKASHI Takahiro wrote:
SIGSYS is primarily used in secure computing to notify tracer.
This patch allows signal handler on compat task to get correct information
with SA_SIGINFO specified when this signal is
> As the table shows, it's not an easily reproducible bug -- the possibility is
> less than 10%:
I think i found the problem. Thanks. Hopefully tests will pass now.
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
> -Original Message-
> From: Wood Scott-B07421
> Sent: Thursday, October 09, 2014 7:48 AM
> To: Jia Hongtao-B38951
> Cc: Guenter Roeck; Benjamin Herrenschmidt; Paul Mackerras; Michael
> Ellerman; linuxppc-...@lists.ozlabs.org; linux-kernel@vger.kernel.org;
> Jojy G Varghese; Guenter
Hi Thomas,
This patch has dependency on your patchset to remove
the last caller of setup_timer_IRQ0_pin(). What's the best
way to solve this dependency? Should I pull your patches or
just keeping the temporary "#if 0"?
Regards!
Gerry
On 2014/9/26 22:57, Jiang Liu wrote:
> Now there's no
On Wed, Oct 8, 2014 at 5:28 PM, Dmitry Torokhov
wrote:
> On Wed, Oct 08, 2014 at 05:24:32PM -0700, Jason Gerecke wrote:
>> On Wed, Oct 8, 2014 at 2:40 PM, Dmitry Torokhov
>> wrote:
>> > On Wed, Oct 08, 2014 at 11:25:42AM -0700, Jason Gerecke wrote:
>> >> Repeated connect/disconnect cycles under
0.00]41c2d900 (null) 13ffe000 (null) 4185793e 002e
410c2982 41c11f00
[0.00]410c2df5 (null) (null) (null) 425cc150 00013efe
(null) 41c11f28
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 3.17.0-next-20141008 #815
[0.00] 425cc10
On Tue, Oct 07, 2014 at 07:42:47PM +0200, Thomas Gleixner wrote:
> On Tue, 7 Oct 2014, Dave Jones wrote:
>
> > On Tue, Oct 07, 2014 at 05:30:27PM +0200, Frederic Weisbecker wrote:
> >
> > > > > Right, this patchset fixes it: "[PATCH 0/8] nohz: Fix nohz kick
> > irq work on tick v3"
> >
On 10/09/2014 12:30 AM, Kees Cook wrote:
On Wed, Oct 8, 2014 at 9:13 AM, Will Deacon wrote:
Hi Akashi,
On Thu, Oct 02, 2014 at 10:46:11AM +0100, AKASHI Takahiro wrote:
To allow tracer to be able to change/skip a system call by re-writing
a syscall number, there are several approaches:
(1)
Hi, Dan
2014-10-08 20:37 GMT+09:00 Dan Carpenter :
> All three of these patches are good and a nice improvement. This one is
> a good bugfix. I have some notes for later, though below.
>
> On Wed, Oct 08, 2014 at 08:13:56PM +0900, Daeseok Youn wrote:
>> diff --git a/drivers/staging/dgap/dgap.c
Em Wed, 08 Oct 2014 13:53:33 -0700
Randy Dunlap escreveu:
> On 10/08/14 11:31, Mauro Carvalho Chehab wrote:
> > Em Wed, 08 Oct 2014 10:13:39 -0700
> > Randy Dunlap escreveu:
> >
> >> On 10/07/14 23:49, Stephen Rothwell wrote:
> >>> Hi all,
> >>>
> >>> Please do not add any material intended
(2014/10/09 2:47), Chuck Ebbert wrote:
> On Wed, 8 Oct 2014 10:03:36 +0100
> Chris Wilson wrote:
>
>> and adding that back into the current build, e.g.
>>
>> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
>> index 3632743..48a8a69 100644
>> --- a/arch/x86/Kconfig
>> +++ b/arch/x86/Kconfig
>>
On 10/07/2014 08:21 AM, Tomeu Vizoso wrote:
Hello,
this second version of the series adds several cleanups that were suggested by
Stephen Boyd and contains several improvements to the seventh patch (clk: Make
clk API return per-user struct clk instances) that were suggested by him during
the
On 10/07/2014 08:21 AM, Tomeu Vizoso wrote:
This is in preparation for clock providers to not have to deal with struct clk.
Signed-off-by: Tomeu Vizoso
---
drivers/clk/at91/clk-programmable.c | 4 ++--
drivers/clk/bcm/clk-kona.c | 4 ++--
drivers/clk/clk-composite.c | 9
On 10/07/2014 08:21 AM, Tomeu Vizoso wrote:
Instead of struct clk, as this should be only used by providers.
Signed-off-by: Tomeu Vizoso
Reviewed-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To
On 10/07/2014 08:21 AM, Tomeu Vizoso wrote:
As it's only used internally, in drivers/clk/clk.c.
Signed-off-by: Tomeu Vizoso
Reviewed-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this
On 10/07/2014 08:21 AM, Tomeu Vizoso wrote:
Signed-off-by: Tomeu Vizoso
---
Reviewed-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On 2014年10月09日 04:54, Peter Zijlstra wrote:
> On Thu, Sep 25, 2014 at 04:32:02PM +0800, Lan Tianyu wrote:
>> This patchset is to parallel enabling nonboot cpus with resuming devices
>> during system resume in order to accelerate S2RAM. From test result on
>> a 8 logical core Haswell machine,
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 0cd8f5614fbf8a598a0a47526ac7dc42ab2ba8cd
Peter Zijlstra (1):
tracing: Robustify wait loop
Steven Rostedt (1):
tracing: Clean up scheduling in trace_wakeup_test_thread()
From: Steven Rostedt
Peter's new debugging tool triggers when tasks exit with !TASK_RUNNING.
The code in trace_wakeup_test_thread() also has a single schedule() call
that should be encompassed by a loop.
This cleans up the code a little to make it a bit more robust and
also makes the return
From: Peter Zijlstra
The pending nested sleep debugging triggered on the potential stale
TASK_INTERRUPTIBLE in this code.
While there, fix the loop such that we won't revert to a while(1)
yield() 'spin' loop if we ever get a spurious wakeup.
And fix the actual issue by properly terminating the
On Wed, Oct 08, 2014 at 05:24:32PM -0700, Jason Gerecke wrote:
> On Wed, Oct 8, 2014 at 2:40 PM, Dmitry Torokhov
> wrote:
> > On Wed, Oct 08, 2014 at 11:25:42AM -0700, Jason Gerecke wrote:
> >> Repeated connect/disconnect cycles under GNOME can trigger an occasional
> >> OOPS from within e.g.
On Thu, Oct 09, 2014 at 01:12:13AM +0100, Mark Brown wrote:
> On Wed, Oct 08, 2014 at 05:05:55PM -0700, Guenter Roeck wrote:
> > On Thu, Oct 09, 2014 at 12:45:41AM +0100, Mark Brown wrote:
>
> > > definitely at least add a boot argument or something to suppress them,
> > > let me have a think if
On Wed, Oct 8, 2014 at 2:40 PM, Dmitry Torokhov
wrote:
> On Wed, Oct 08, 2014 at 11:25:42AM -0700, Jason Gerecke wrote:
>> Repeated connect/disconnect cycles under GNOME can trigger an occasional
>> OOPS from within e.g. wacom_led_select_store, presumably due to a timing
>> issue where userspace
> "Mike" == Mike Snitzer writes:
Mike> The math in both blk_stack_limits() and
Mike> queue_limit_alignment_offset() assume that a block device's io_min
Mike> (aka minimum_io_size) is always a power-of-2. Fix the math such
Mike> that it works for non-power-of-2 io_min.
Mike> This issue (of
From: Ian Munsie
If afu_read() returned due to a signal or the AFU file descriptor being
opened non-blocking it would not call finish_wait() before returning,
which could lead to a crash later when something else wakes up the wait
queue.
This patch restructures the wait logic to ensure that the
On 10/08/14 16:18, Andy Lutomirski wrote:
> On Wed, Oct 8, 2014 at 4:11 PM, Peter Foley wrote:
>> On Wed, Oct 8, 2014 at 5:21 PM, H. Peter Anvin wrote:
>>> That we can't solve, but it is not okay to break the kernel build.
>>
>> Should I just make CONFIG_BUILD_DOCSRC depend on CROSS_COMPILE=""?
On Wed, Oct 08, 2014 at 05:05:55PM -0700, Guenter Roeck wrote:
> On Thu, Oct 09, 2014 at 12:45:41AM +0100, Mark Brown wrote:
> > definitely at least add a boot argument or something to suppress them,
> > let me have a think if we want to do that by default.
> It is a nuisance, so I might just
On Thu, Oct 09, 2014 at 12:45:41AM +0100, Mark Brown wrote:
> On Wed, Oct 08, 2014 at 03:59:12PM -0700, Guenter Roeck wrote:
>
> > There is a log message "no parameters" for each regulator. This is printed
> > unconditionally from print_constraints().
>
> > Looking through the code again, looks
Quoting Viresh Kumar (2014-10-08 01:19:40)
> On 8 October 2014 13:41, Thomas Petazzoni
> wrote:
> > On Wed, 8 Oct 2014 13:24:30 +0530, Viresh Kumar wrote:
> >> On 8 October 2014 13:18, Mike Turquette wrote:
>
> >> > This series is partially in response to a discussion around DT bindings
> >> >
md/raid allows metadata management to be performed in user-space.
A various times, particularly on device failure, the metadata needs
to be updated before further writes can be permitted.
This means that the user-space program which updates metadata much
not block on writeout, and so must not
To match the previous patch which used the pre-alloc buffer for
writes, this patch causes reads to use the same buffer.
This is not strictly necessary as the current seq_read() will allocate
on first read, so user-space can trigger the required pre-alloc. But
consistency is valuable.
The read
Hi Tejun,
thanks for the review. This version incorporates your suggestions.
You are certainly right about there being issues deeper than just the
sysfs/kernfs level - I've been cleaning up the locking in md to avoid
the "reconfig_mutex" as much as possible. It is something that has
been
Hi all,
The top commit in the logfs tree was committed in November 2012. Is
there any intention to ask Linus to merge this tree? Or should I just
drop it completely?
It is a pain because it takes considerable time for git to actually
merge it.
$ git log --oneline origin/master..logfs/master
On Tue, 2014-10-07 at 22:08 -0500, Jia Hongtao-B38951 wrote:
>
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Tuesday, September 30, 2014 2:36 AM
> > To: Guenter Roeck
> > Cc: Benjamin Herrenschmidt; Paul Mackerras; Michael Ellerman; linuxppc-
> > d...@lists.ozlabs.org;
On Mon, Sep 29, 2014 at 11:42 AM, Andy Lutomirski wrote:
> On Sep 29, 2014 10:36 AM, wrote:
>>
>> On Mon, 29 Sep 2014 09:39:16 -0700, Andy Lutomirski said:
>>
>> > Would it make sense to restrict rdpmc to tasks that are in mms that
>> > have a perf_event mapping? After all, unless I
On Wed, Oct 8, 2014 at 12:18 AM, Alexandre Courbot wrote:
> On Wed, Oct 8, 2014 at 4:09 PM, Muthu Mani wrote:
>>> -Original Message-
>>> From: Alexandre Courbot [mailto:gnu...@gmail.com]
>>> Sent: Tuesday, October 07, 2014 3:34 PM
>>> To: Muthu Mani
>>> Cc: Samuel Ortiz; Lee Jones;
On Wed, Oct 08, 2014 at 03:59:12PM -0700, Guenter Roeck wrote:
> There is a log message "no parameters" for each regulator. This is printed
> unconditionally from print_constraints().
> Looking through the code again, looks like this is on purpose. It is just a
> bit
> annoying to get lots of
On Wed, Oct 8, 2014 at 4:38 PM, Serge Hallyn wrote:
> Quoting Andy Lutomirski (l...@amacapital.net):
>> On Wed, Oct 8, 2014 at 2:36 PM, Rob Landley wrote:
>> > On 10/08/14 14:31, Andy Lutomirski wrote:
>> >> On Wed, Oct 8, 2014 at 12:23 PM, Eric W. Biederman
>> >> wrote:
>> >>> Andy Lutomirski
Hi Linus,
Please pull hwmon updates for Linux v3.18 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-for-linus-v3.18
Thanks,
Guenter
--
The following changes since commit 4e66cd13ff9cd7eaae69e2fae0335d8d99d8afdf:
hwmon: (tmp103) Fix
Quoting Andy Lutomirski (l...@amacapital.net):
> On Wed, Oct 8, 2014 at 2:36 PM, Rob Landley wrote:
> > On 10/08/14 14:31, Andy Lutomirski wrote:
> >> On Wed, Oct 8, 2014 at 12:23 PM, Eric W. Biederman
> >> wrote:
> >>> Andy Lutomirski writes:
> > Maybe we want to say that rootfs should not
Don't build Documentation targets when cross-compiling.
They are only for build testing, and use the host headers and compiler
which can cause cross-compiles to fail.
Signed-off-by: Peter Foley
---
lib/Kconfig.debug | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Wed, 2014-10-08 at 22:43 +0200, Ricardo Ribalda Delgado wrote:
> Hello Alan
>
> This patchset adds no extra locking features, if the drivers did not
> implement a locking mechanism (and none did) there is chance of
> conflict.
>
> I can add a call to lock/unlock around
Hi Linus,
this series was supposed to be pulled through various trees using it,
and I did not plan to send a separate pull request. As it turns out,
the pinctrl tree did not merge with it, is now upstream, and uses
it, meaning there are now build failures.
Please consider pulling this series
On 10/08/2014 12:39 AM, Jassi Brar wrote:
> Hi Linus,
>
> A framework for Mailbox controllers and clients have been cooking for
> more than a year now. Everybody in the CC list had been copied on
> patchset revisions and most of them have made sounds of approval,
> though just one concrete
On Wed, Oct 8, 2014 at 4:11 PM, Peter Foley wrote:
> On Wed, Oct 8, 2014 at 5:21 PM, H. Peter Anvin wrote:
>> That we can't solve, but it is not okay to break the kernel build.
>
> Should I just make CONFIG_BUILD_DOCSRC depend on CROSS_COMPILE=""?
> I'm not sure how much value would be added by
On Wed, Oct 08, 2014 at 07:09:18PM -0400, Josh Boyer wrote:
> On Wed, Oct 8, 2014 at 6:49 PM, Josh Cartwright wrote:
> > Hey Josh-
> >
> > On Wed, Oct 08, 2014 at 06:42:55PM -0400, Josh Boyer wrote:
> >> We're hitting a build error on ARM with Linus' tree as of Linux
> >> v3.17-2860-gef0625b70dac
On Wednesday, October 08, 2014 8:09 AM, Ian Abbott wrote:
> `do_cmd_ioctl()`, the handler for the `COMEDI_CMD` ioctl can incorrectly
> call the Comedi subdevice's `do_cmd()` handler with a NULL channel list
> pointer. This is a regression as the `do_cmd()` handler has never been
> expected to
On Wed, Oct 08, 2014 at 06:42:55PM -0400, Josh Boyer wrote:
> We're hitting a build error on ARM with Linus' tree as of Linux
> v3.17-2860-gef0625b70dac :
>
> drivers/pinctrl/qcom/pinctrl-msm.c: In function 'msm_pinctrl_setup_pm_reset':
> drivers/pinctrl/qcom/pinctrl-msm.c:875:4: error: implicit
On Wed, Oct 8, 2014 at 5:21 PM, H. Peter Anvin wrote:
> That we can't solve, but it is not okay to break the kernel build.
Should I just make CONFIG_BUILD_DOCSRC depend on CROSS_COMPILE=""?
I'm not sure how much value would be added by implementing targetprogs
in kbuild, simply to increase build
On Wed, Oct 8, 2014 at 6:49 PM, Josh Cartwright wrote:
> Hey Josh-
>
> On Wed, Oct 08, 2014 at 06:42:55PM -0400, Josh Boyer wrote:
>> We're hitting a build error on ARM with Linus' tree as of Linux
>> v3.17-2860-gef0625b70dac :
>>
>> drivers/pinctrl/qcom/pinctrl-msm.c: In function
On Wed, 08 Oct 2014 14:21:00 -0700
"H. Peter Anvin" wrote:
> On 10/08/2014 02:09 PM, Chuck Ebbert wrote:
> >>
> >> Breaking cross-compilation is not okay, though, regardless of what
> >> Fedora does. It should be okay to, for example, build an i386 kernel on
> >> an ARM box.
> >>
> >
> > I
On Wed, Oct 08, 2014 at 11:36:01PM +0100, Mark Brown wrote:
> On Wed, Oct 08, 2014 at 03:34:03PM -0700, Guenter Roeck wrote:
>
> > Would it also be possible to lower the severity of the "no parameters"
> > message ?
>
> Could you be more specific please?
There is a log message "no parameters"
On Wed, Oct 08, 2014 at 08:34:48PM +0200, Rene Kolarik wrote:
> Wrapping two too long lines in two files of the imx-drm driver.
>
> Signed-off-by: Rene Kolarik
> ---
> drivers/staging/imx-drm/imx-drm-core.c | 3 ++-
> drivers/staging/imx-drm/imx-tve.c | 3 ++-
> 2 files changed, 4
On Tue, Oct 07, 2014 at 01:11:42PM +0400, Igor Bogomazov wrote:
> checkpatch.pk tiny fix
> get rid of 2 warnings and 2 errors for hal/fw.c
>
> Signed-off-by: Igor Bogomazov
> Cc: Greg Kroah-Hartman
> Cc: navin patidar
> Cc: Stephen Rothwell
> ---
> linux-next 3.17.0
I think someone else
On Wed, Oct 08, 2014 at 04:52:06PM -0500, Aravind Gopalakrishnan wrote:
> I am not understanding why m.bank is assigned this value..
That's a very good question, see below for some history.
>
> It only causes incorrect decoding-
> [ 608.832916] DEBUG: raise_amd_threshold_event
> [ 608.832926]
On Sat, Oct 04, 2014 at 10:24:28AM +0800, Cheng-wei Lee wrote:
> This patch fix the sparse warnings in wlan-ng/cfg80211.c
> The following functions were only used in this file, so done by
> declaring them into static.
>
> drivers/staging/wlan-ng/cfg80211.c:710:6: warning: symbol
>
Hey Josh-
On Wed, Oct 08, 2014 at 06:42:55PM -0400, Josh Boyer wrote:
> We're hitting a build error on ARM with Linus' tree as of Linux
> v3.17-2860-gef0625b70dac :
>
> drivers/pinctrl/qcom/pinctrl-msm.c: In function 'msm_pinctrl_setup_pm_reset':
> drivers/pinctrl/qcom/pinctrl-msm.c:875:4:
Commit 05f1dd53152173 (block: add queue flag for disabling SG merging) uses
bi_vcnt to assign bio->bi_phys_segments if sg merging is disabled. When
using device mapper on top of a blk-mq device (virtio_blk in my test),
we'd end up overflowing the scatterlist in __blk_bios_map_sg.
__bio_clone_fast
On Wed, Oct 8, 2014 at 3:54 PM, H. Peter Anvin wrote:
> This still has the cross-build problems, no?
>
Yes, but that issue is more general to CONFIG_BUILD_DOCSRC.
This is just a build failure on x86-32.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
From: Dinh Nguyen
There are cases where a system will want to read a reset status bit before
doing any other toggling. Add a reset_control_status helper function to the
reset controller API.
Signed-off-by: Dinh Nguyen
---
drivers/reset/core.c | 13 +
On Wed, Oct 08, 2014 at 02:05:22PM -0600, Shuah Khan wrote:
> On 10/07/2014 05:19 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.16.5 release.
> > There are 26 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Tue, Oct 07, 2014 at 05:54:48PM +0200, Dzmitry Sledneu wrote:
> Fix "Possible unnecessary 'out of memory' message" checkpatch.pl warning
>
> Signed-off-by: Dzmitry Sledneu
>
> ---
> drivers/staging/gs_fpgaboot/gs_fpgaboot.c | 7 ++-
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
>
During list_for_each_entry_safe, next_i is becoming free causing
the loop to never terminate. Advance next_i in those cases where
__iget is not done.
Signed-off-by: Jerry Hoemann
---
fs/notify/inode_mark.c | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git
During file system stress testing on 3.10 and 3.12 based kernels,
the umount command occasionally hung in fsnotify_unmount_inodes
in the section of code:
spin_lock(>i_lock);
if (inode->i_state & (I_FREEING|I_WILL_FREE|I_NEW)) {
On Wed, Oct 08 2014 at 6:38pm -0400,
Jens Axboe wrote:
> On 10/08/2014 04:28 PM, Mike Snitzer wrote:
> > On Wed, Oct 08 2014 at 6:12pm -0400,
> > Jens Axboe wrote:
> >
> >> On 10/08/2014 04:05 PM, Mike Snitzer wrote:
> >>> The math in both blk_stack_limits() and
On Thu, Oct 02, 2014 at 02:32:26PM +0200, Nitin Kuppelur wrote:
> Removed unnecessary else after return to solve
> checkpatch.pl warning
>
> Signed-off-by: Nitin Kuppelur
> ---
> drivers/staging/rtl8712/hal_init.c | 7 ++-
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git
We're hitting a build error on ARM with Linus' tree as of Linux
v3.17-2860-gef0625b70dac :
drivers/pinctrl/qcom/pinctrl-msm.c: In function 'msm_pinctrl_setup_pm_reset':
drivers/pinctrl/qcom/pinctrl-msm.c:875:4: error: implicit declaration
of function 'register_restart_handler'
On Tue, Sep 30, 2014 at 11:29:00PM +0530, Karthik Nayak wrote:
> Removed the else statement occurring after an if statement with a
> return value as per checkpatch warning.
>
> Signed-off-by: Karthik Nayak
> ---
> drivers/staging/bcm/InterfaceMisc.c | 9 -
> 1 file changed, 4
On Tue, Sep 30, 2014 at 10:56:17PM +0530, Karthik Nayak wrote:
> 1. WARNING: else is not generally useful after a break or return
>
> 2. WARNING: quoted string split across lines
>
> 3. WARNING: break quoted strings at a space character
>
> Signed-off-by: Karthik Nayak
> ---
>
On 10/08/2014 04:28 PM, Mike Snitzer wrote:
> On Wed, Oct 08 2014 at 6:12pm -0400,
> Jens Axboe wrote:
>
>> On 10/08/2014 04:05 PM, Mike Snitzer wrote:
>>> The math in both blk_stack_limits() and queue_limit_alignment_offset()
>>> assume that a block device's io_min (aka minimum_io_size) is
On Wed, Oct 08, 2014 at 03:34:03PM -0700, Guenter Roeck wrote:
> Would it also be possible to lower the severity of the "no parameters"
> message ?
Could you be more specific please?
signature.asc
Description: Digital signature
On Wed, Oct 08, 2014 at 05:54:49PM -0400, Linus Torvalds wrote:
> On Wed, Oct 8, 2014 at 2:12 PM, Thomas Gleixner wrote:
> >
> > please pull the latest timers-core-for-linus git tree from:
> >
> >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> > timers-core-for-linus
> >
> >
On Wed, Oct 08, 2014 at 11:09:59PM +0100, Mark Brown wrote:
> Description of regulators should generally be optional so if there is no
> DT node for the regulators container then we shouldn't print an error
> message. Lower the severity of the message to debug level (it might help
> someone work
On Wed, Oct 08 2014 at 6:12pm -0400,
Jens Axboe wrote:
> On 10/08/2014 04:05 PM, Mike Snitzer wrote:
> > The math in both blk_stack_limits() and queue_limit_alignment_offset()
> > assume that a block device's io_min (aka minimum_io_size) is always a
> > power-of-2. Fix the math such that it
1 - 100 of 1426 matches
Mail list logo
