Commit-ID: 7aca0c07207385cca76025cc85231519935722b9
Gitweb: http://git.kernel.org/tip/7aca0c07207385cca76025cc85231519935722b9
Author: Alexander Kuleshov
AuthorDate: Fri, 26 Feb 2016 19:14:13 -0800
Committer: Thomas Gleixner
CommitDate: Sat, 27 Feb 2016 08:55:30 +0100
clocksource: Intr
Commit-ID: 232d26373d310a941ef2ab46e53ea62fe076ed13
Gitweb: http://git.kernel.org/tip/232d26373d310a941ef2ab46e53ea62fe076ed13
Author: Alexander Kuleshov
AuthorDate: Fri, 26 Feb 2016 19:14:14 -0800
Committer: Thomas Gleixner
CommitDate: Sat, 27 Feb 2016 08:55:31 +0100
jiffies: Use CLOC
A device is not able to use direct complete if its children do not
also use direct complete. Even though the SCSI layer leaves devices
runtime suspended, the way it does it still prevents its parent from
using direct complete.
On Fri, Feb 26, 2016 at 11:26 PM, Mika Westerberg
wrote:
> On Wed, Feb
Hi Bjorn,
On Tue, Feb 23, 2016 at 8:42 PM, Bjorn Helgaas wrote:
>
> [+cc Andi, linux-kernel, x86 for Intel Broadwell-EP non-BAR issue]
>
> On Tue, Feb 23, 2016 at 08:10:03PM +0530, Jayachandran Chandrashekaran Nair
> wrote:
> > On Thu, Feb 18, 2016 at 9:19 PM, Bjorn Helgaas wrote:
> > > On Wed,
On Sat, Feb 27, 2016 at 12:10:03AM -0800, dbasehore . wrote:
> A device is not able to use direct complete if its children do not
> also use direct complete. Even though the SCSI layer leaves devices
> runtime suspended, the way it does it still prevents its parent from
> using direct complete.
Ok
Hi Leo,
On 16/02/2016 09:21, Chen Feng wrote:
> Lee,
> Thanks for your review.
>
> On 2016/2/15 16:32, Lee Jones wrote:
>> On Sun, 14 Feb 2016, Chen Feng wrote:
>>
>>> DT bindings for hisilicon hi655x MFD PMIC chip.
>>>
>>> Signed-off-by: Chen Feng
>>> Signed-off-by: Fei Wang
>>> Signed-off-by:
Agreed. Is it better to change the man page and document the behaviour?
Regards,
PrasannaKumar
On Fri, Feb 26, 2016 at 10:09:29AM -0800, scott.law...@intel.com wrote:
> From: Scott Lawson
>
> These PCI device IDs in the AHCI driver conflict with proprietary drivers,
> preventing them from loading.
And that's a good thing!
On Fri, Feb 26, 2016 at 10:09:52AM -0800, scott.law...@intel.com wrote:
> From: Scott Lawson
>
> These PCI device IDs have been removed from the Intel Lewisburg design
> specification. They are no longer needed.
Let's keep them just in case..
On Fri, Feb 26, 2016 at 01:47:39PM -0800, Yang Shi wrote:
> commit 5634cc2aa9aebc77bc862992e7805469dcf83dac ("writeback: update writeback
> tracepoints to report cgroup") made writeback tracepoints report cgroup
> writeback, but it may trigger the below bug on -rt kernel since kernfs_path
> and ker
Hi Bjorn, Lorenzo
Many Thanks for your replies and suggestions
> -Original Message-
> From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci-
> ow...@vger.kernel.org] On Behalf Of Bjorn Helgaas
> Sent: 25 February 2016 19:59
> To: Lorenzo Pieralisi
> Cc: Gabriele Paoloni; 'Mark Rutland';
On Sat, Feb 27, 2016 at 12:38 AM, Mika Westerberg
wrote:
> On Sat, Feb 27, 2016 at 12:10:03AM -0800, dbasehore . wrote:
>> A device is not able to use direct complete if its children do not
>> also use direct complete. Even though the SCSI layer leaves devices
>> runtime suspended, the way it does
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit 06466212a69c0511c5dcff7363c207ffc8913731:
>
> Merge tag 'perf-core-for-mingo-20160224' of
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into pe
fixed space around initialization in assignment(multiple)
fixed assignment in if condition(single)
fixed a blank line after declarations(multiple)
line over 80 characters(multiple)
Signed-off-by: amar-laksh
---
ipc/shm.c | 47 +++
1 file changed, 35 in
Commit-ID: 7e9551bc72201838ebaf388224ff43ddf2b0d853
Gitweb: http://git.kernel.org/tip/7e9551bc72201838ebaf388224ff43ddf2b0d853
Author: Stephane Eranian
AuthorDate: Thu, 25 Feb 2016 06:27:36 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 25 Feb 2016 10:43:28 -0300
perf jvmti
Commit-ID: 5104ffb229c357d9672344126040721e5dc4cc7b
Gitweb: http://git.kernel.org/tip/5104ffb229c357d9672344126040721e5dc4cc7b
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 25 Feb 2016 10:14:50 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 25 Feb 2016 10:14:50 -0300
pe
Commit-ID: 8560bae02a948876b26d1d86423cf5e0bb04a815
Gitweb: http://git.kernel.org/tip/8560bae02a948876b26d1d86423cf5e0bb04a815
Author: Taeung Song
AuthorDate: Fri, 26 Feb 2016 00:13:10 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 25 Feb 2016 16:14:33 -0300
perf script: Re
Commit-ID: 8579aca3f9a8f890d6d94ccaed7cf5fd54a0c3bd
Gitweb: http://git.kernel.org/tip/8579aca3f9a8f890d6d94ccaed7cf5fd54a0c3bd
Author: Taeung Song
AuthorDate: Fri, 26 Feb 2016 00:12:59 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 25 Feb 2016 12:54:20 -0300
perf script: Ex
Commit-ID: a7b5895b91fb97f2b0dcc2e3ce47413c18d19ca5
Gitweb: http://git.kernel.org/tip/a7b5895b91fb97f2b0dcc2e3ce47413c18d19ca5
Author: Namhyung Kim
AuthorDate: Fri, 26 Feb 2016 21:13:16 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 11:20:35 -0300
perf hists: Ad
Commit-ID: bd4abd39db92225dde8335c37d6f4efb319f9cf2
Gitweb: http://git.kernel.org/tip/bd4abd39db92225dde8335c37d6f4efb319f9cf2
Author: Namhyung Kim
AuthorDate: Fri, 26 Feb 2016 21:13:17 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 11:20:36 -0300
perf report: S
Commit-ID: 2ddda792373065577eb9207370cb7a28395caffa
Gitweb: http://git.kernel.org/tip/2ddda792373065577eb9207370cb7a28395caffa
Author: Namhyung Kim
AuthorDate: Fri, 26 Feb 2016 21:13:20 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 11:20:36 -0300
perf report: S
Commit-ID: 201fde73b111e7c31fdc0e9fa6bc4b73dfef699d
Gitweb: http://git.kernel.org/tip/201fde73b111e7c31fdc0e9fa6bc4b73dfef699d
Author: Namhyung Kim
AuthorDate: Fri, 26 Feb 2016 21:13:18 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 11:20:36 -0300
perf hists bro
Commit-ID: 79dded8776c2dc4d6e1229de69f4027e84d63673
Gitweb: http://git.kernel.org/tip/79dded8776c2dc4d6e1229de69f4027e84d63673
Author: Namhyung Kim
AuthorDate: Fri, 26 Feb 2016 21:13:19 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 11:20:36 -0300
perf hists bro
Commit-ID: d3a72fd8187b7fa0014394c9dec95ba349b3301e
Gitweb: http://git.kernel.org/tip/d3a72fd8187b7fa0014394c9dec95ba349b3301e
Author: Namhyung Kim
AuthorDate: Sat, 27 Feb 2016 03:52:44 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 18:36:11 -0300
perf report: F
Commit-ID: 84b6ee8ea36ff797afa13c297a86ed0144482bee
Gitweb: http://git.kernel.org/tip/84b6ee8ea36ff797afa13c297a86ed0144482bee
Author: Namhyung Kim
AuthorDate: Sat, 27 Feb 2016 03:52:43 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 18:35:57 -0300
perf hists: Fi
Commit-ID: e049d4a3fa194c8aa0d3ca29a9b11b32387ca6e3
Gitweb: http://git.kernel.org/tip/e049d4a3fa194c8aa0d3ca29a9b11b32387ca6e3
Author: Namhyung Kim
AuthorDate: Sat, 27 Feb 2016 03:52:46 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 19:37:38 -0300
perf hists: Fi
Commit-ID: b8cbb349061edda648463b086cfa869a7ab583af
Gitweb: http://git.kernel.org/tip/b8cbb349061edda648463b086cfa869a7ab583af
Author: Wang Nan
AuthorDate: Fri, 26 Feb 2016 09:31:51 +
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 19:49:16 -0300
perf config: Bring
Commit-ID: abab5e7fcec16e526968f8a5448cd81c635705ce
Gitweb: http://git.kernel.org/tip/abab5e7fcec16e526968f8a5448cd81c635705ce
Author: Namhyung Kim
AuthorDate: Sat, 27 Feb 2016 03:52:47 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 19:38:48 -0300
perf report: U
Commit-ID: cb1fab917206f822d1f905cbc45971eefdef361d
Gitweb: http://git.kernel.org/tip/cb1fab917206f822d1f905cbc45971eefdef361d
Author: Namhyung Kim
AuthorDate: Sat, 27 Feb 2016 03:52:45 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 18:37:06 -0300
perf report: L
Commit-ID: 1d6c9407d45dd622b277ca9f725da3cc9e95b5de
Gitweb: http://git.kernel.org/tip/1d6c9407d45dd622b277ca9f725da3cc9e95b5de
Author: Wang Nan
AuthorDate: Fri, 26 Feb 2016 09:31:55 +
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 19:57:07 -0300
perf trace: Print
Commit-ID: fdf14720fbd02d406ac2c1c50444774b4c7eed9a
Gitweb: http://git.kernel.org/tip/fdf14720fbd02d406ac2c1c50444774b4c7eed9a
Author: Wang Nan
AuthorDate: Fri, 26 Feb 2016 09:31:53 +
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 19:50:01 -0300
perf tools: Only s
Commit-ID: ba50423530200659d4deb703a8f72d3b69bc13ce
Gitweb: http://git.kernel.org/tip/ba50423530200659d4deb703a8f72d3b69bc13ce
Author: Wang Nan
AuthorDate: Fri, 26 Feb 2016 09:31:54 +
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 26 Feb 2016 19:50:40 -0300
perf trace: Call b
In multi-core SoC, if enable USB endpoint/transmit urb/disable
USB endpoint repeatedly,it can cause a NULL pointer dereference bug:
Unable to handle kernel NULL pointer dereference at virtual address 0010
pgd = d3eb4000
[0010] *pgd=
Internal error: Oops: 5 [#1] PREEMPT SMP
Pid: 101
Am 25.02.2016 08:47, schrieb Dan Carpenter:
> It's simpler to just use snprintf() to print this to one buffer instead
> of using strcpy() and strcat(). Also using snprintf() is slightly safer
> than using sprintf().
>
> Signed-off-by: Dan Carpenter
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/
Hi Guodong,
On 19/02/2016 19:58, Guodong Xu wrote:
> As of V4, this patchset has been ack'ed by Rob Herring.
>
> V5, added pmx0 pmx1 pmx2 nodes description into hi6220.dtsi.
>
> Zhong Kaihua (3):
> arm64: dts: Add Hi6220 gpio configuration nodes
> arm64: dts: add Hi6220 pinctrl configuration
Hi Guodong,
On 19/02/2016 13:19, Guodong Xu wrote:
> This patchset include more dts changes for hi6220 SoC and HiKey board.
>
> Patch 1 adds pinctrl to uart ports in SoC and enables them for HiKey board.
> Patch 2 adds gpio LEDs device nodes.
> Patch 3 adds dwmmc nodes description for hi6220. It
On 2016-02-26 16:32:42 [-0500], Steven Rostedt wrote:
> 3.18.27-rt26-rc1 stable review patch.
> If anyone has any objections, please let me know.
Please merge this one along with "kernel: migrate_disable() do fastpath
in atomic & irqs-off". Otherwise we might get recursive with lockdep and
CPU-hot
On Sat, Feb 27, 2016 at 10:50:40AM +0100, walter harms wrote:
>
>
> Am 25.02.2016 08:47, schrieb Dan Carpenter:
> > It's simpler to just use snprintf() to print this to one buffer instead
> > of using strcpy() and strcat(). Also using snprintf() is slightly safer
> > than using sprintf().
> >
>
If we throw away the very last item on the list, then we could end up
with a use after free of "dr".
Fixes: 15ca17645f19 ('PCI: hv: Add paravirtual PCI front-end for Microsoft
Hyper-V VMs')
Signed-off-by: Dan Carpenter
diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyperv.c
i
Ezequiel Garcia writes:
> On 12 February 2016 at 19:29, Robert Jarzmik wrote:
>> When the driver is initialized in a pure device-tree platform, the
>> driver's probe fails allocating the dma channel :
>> [ 525.624435] pxa3xx-nand 4310.nand: no resource defined for data DMA
>> [ 525.632088]
There is a missing curly brace so we only look at the first item in the
list and then exit.
Fixes: ac90aa02d5b9 ('[media] saa7134: add media controller support')
Signed-off-by: Dan Carpenter
diff --git a/drivers/media/pci/saa7134/saa7134-core.c
b/drivers/media/pci/saa7134/saa7134-core.c
index 4
26.02.2016, 22:41, "Vivek Goyal" :
>
> So what's the problem we are trying to solve. Why should we able to
> override the DAC checks of lower layer if same directory in upper
> is searchable for user but it is not searchable in lower layer.
>
If I right, this is a one of the main feature of overla
The ->input_ent[] array has TVP5150_INPUT_NUM elements so the > here
should be >=.
Fixes: f7b4b54e6364 ('[media] tvp5150: add HW input connectors support')
Signed-off-by: Dan Carpenter
diff --git a/drivers/media/i2c/tvp5150.c b/drivers/media/i2c/tvp5150.c
index ef393f5..ff18444 100644
--- a/driv
Oh... There is no [patch 2/2]. I decided to report that one instead.
regards,
dan carpenter
Checksum should be unsigned 32-bit otherwise the calculation overflows
resulting in undefined behaviour:
[0.00]
[0.00] UBSAN: Undefined behaviour in
arch/x86/kernel/cpu/microcode/intel_lib.c:105:12
[
On Sat, Feb 27, 2016 at 08:47:41AM +0100, Thomas Gleixner wrote:
> On Fri, 26 Feb 2016, Paul E. McKenney wrote:
> > > > --- a/kernel/cpu.c
> > > > +++ b/kernel/cpu.c
> > > > @@ -762,6 +762,7 @@ void cpuhp_report_idle_dead(void)
> > > > BUG_ON(st->state != CPUHP_AP_OFFLINE);
> > > >
Hello,
On Fri, Feb 26, 2016 at 01:47:39PM -0800, Yang Shi wrote:
> Call synchronize_sched() when kernfs_node is updated since tracepoints are
> protected by rcu_read_lock_sched.
Adding synchronize_sched() to operations which can be triggered from
userland usually turns out to be problematic. If
Am 27.02.2016 11:40, schrieb Dan Carpenter:
> On Sat, Feb 27, 2016 at 10:50:40AM +0100, walter harms wrote:
>>
>>
>> Am 25.02.2016 08:47, schrieb Dan Carpenter:
>>> It's simpler to just use snprintf() to print this to one buffer instead
>>> of using strcpy() and strcat(). Also using snprintf() i
On Sat, Feb 27, 2016 at 12:51:54AM -0800, Christoph Hellwig wrote:
> On Fri, Feb 26, 2016 at 10:09:52AM -0800, scott.law...@intel.com wrote:
> > From: Scott Lawson
> >
> > These PCI device IDs have been removed from the Intel Lewisburg design
> > specification. They are no longer needed.
>
> Let
On Fri, Feb 26, 2016 at 10:09:29AM -0800, scott.law...@intel.com wrote:
> From: Scott Lawson
>
> These PCI device IDs in the AHCI driver conflict with proprietary drivers,
> preventing them from loading.
So, the default ahci driver can't attach if these PCI IDs are in use?
I don't think breaking
On Sat, 27 Feb 2016, Paul E. McKenney wrote:
> On Sat, Feb 27, 2016 at 08:47:41AM +0100, Thomas Gleixner wrote:
> > On Fri, 26 Feb 2016, Paul E. McKenney wrote:
> > > > > --- a/kernel/cpu.c
> > > > > +++ b/kernel/cpu.c
> > > > > @@ -762,6 +762,7 @@ void cpuhp_report_idle_dead(void)
> > > > >
On Thu, 25 Feb 2016 15:52:02 +0100
Peter Zijlstra wrote:
> On Thu, Feb 25, 2016 at 03:25:58PM +0100, luca abeni wrote:
>
> > > > (BTW, it seems to me that switched_to_dl() is never invoked, for
> > > > some reason...)
> > >
> > > Hmm, it should be invoked if you do sched_setattr() to get
> > >
On Sat, 27 Feb 2016, Tejun Heo wrote:
> On Fri, Feb 26, 2016 at 01:47:39PM -0800, Yang Shi wrote:
> > Call synchronize_sched() when kernfs_node is updated since tracepoints are
> > protected by rcu_read_lock_sched.
>
> Adding synchronize_sched() to operations which can be triggered from
> userland
On Sat, Feb 27, 2016 at 12:37:23PM +0100, Thomas Gleixner wrote:
> On Sat, 27 Feb 2016, Tejun Heo wrote:
> > On Fri, Feb 26, 2016 at 01:47:39PM -0800, Yang Shi wrote:
> > > Call synchronize_sched() when kernfs_node is updated since tracepoints are
> > > protected by rcu_read_lock_sched.
> >
> > Ad
* Stephen Rothwell wrote:
> Hi,
>
> On Fri, 26 Feb 2016 09:44:00 -0800 "H. Peter Anvin" wrote:
> >
> >
> > __u64 is okay, "unsigned long" is really messy in the presence of 32-on-64
> > bit ABIs...
>
> Yeah, but unfortunately, any 64 bit scalar type here will change the
> alignment of the e
* Alexander Kuleshov wrote:
> The arch/x86/include/asm/bitops.h provides IS_IMMEDIATE macro which expands to
> the call of the __builtin_constant_p(). Let's use this macro in the test_bit()
> to be more clear.
>
> Signed-off-by: Alexander Kuleshov
> ---
> arch/x86/include/asm/bitops.h | 2 +-
On Sat, 27 Feb 2016, Tejun Heo wrote:
> On Sat, Feb 27, 2016 at 12:37:23PM +0100, Thomas Gleixner wrote:
> > On Sat, 27 Feb 2016, Tejun Heo wrote:
> > > On Fri, Feb 26, 2016 at 01:47:39PM -0800, Yang Shi wrote:
> > > > Call synchronize_sched() when kernfs_node is updated since tracepoints
> > > >
Hello,
On Sat, Feb 27, 2016 at 6:45 AM, Thomas Gleixner wrote:
>> It can be, but we can print out the ino and userland can match that up
>> with path if necessary.
>
> Wouldn't be cgroup id the better choice?
AFAIK we aren't exposing cgroup id to userland anywhere right now.
Eventually, I think
Hello,
On Fri, Feb 26, 2016 at 03:47:18PM +0100, Petr Mladek wrote:
> > Could you explain in more detail what did you mean by IPC problems?
>
> I guess that the idea was to make IPC more effective in general.
> You definitely could not move all functionality that needs IPC
> into the kernel.
1.
* Borislav Petkov wrote:
> > void __init setup_arch(char **cmdline_p)
> > {
> > + struct ramdisk ramdisk = {
> > + .start_addr = get_ramdisk_image(),
> > + .size = PAGE_ALIGN(get_ramdisk_size()),
> > + .reserve_ramdisk = true
> > + };
>
> More readable:
>
>
On 02/25/2016 05:42 PM, John Garry wrote:
> In hisi_sas_exec_internal_tmf_task(), the check for
> SAM_STAT_GOOD is replaced with
> TMF_RESP_FUNC_COMPLETE, which is a genuine tmf
> response code.
> SAM_STAT_GOOD and TMF_RESP_FUNC_COMPLETE have the
> same value, so this is why it worked before.
>
>
On 02/25/2016 05:42 PM, John Garry wrote:
> Add a function to abort a slot (task) in the target
> device and then cleanup and complete the task.
> The function is called from work queue context as
> it cannot be called from the context where it is
> triggered (interrupt).
> Flag hisi_sas_slot.abort
On 02/25/2016 05:42 PM, John Garry wrote:
> When TRANS_TX_CREDIT_TIMEOUT_ERR or
> TRANS_TX_CLOSE_NORMAL_ERR error occur in
> a slot, the command should be re-attempted.
> This error is equivalent to meaning that the queue
> is full in the sdev (and not the host).
>
> Signed-off-by: John Garry
> -
On 02/25/2016 05:42 PM, John Garry wrote:
> When TRANS_TX_ERR_FRAME_TXED error occurs in
> a slot, the command should be re-attempted.
> This error is equivalent to meaning that the queue
> is full in the sdev (and not the host).
> A superflous debug statement is also removed in the
> slot complete
On 02/25/2016 05:42 PM, John Garry wrote:
> In high-datarate aging tests, it is found that the
> SCSI framework can periodically issue lu resets as
> some commands timeout.
> Response TASK SET FULL and SAS_QUEUE_FULL may be
> returned many times for the same command, causing the
> timeouts.
> The S
On 02/25/2016 05:42 PM, John Garry wrote:
> Signed-off-by: John Garry
> ---
> drivers/scsi/hisi_sas/hisi_sas.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/hisi_sas/hisi_sas.h
> b/drivers/scsi/hisi_sas/hisi_sas.h
> index c92e65b..29e89f3 100644
> --- a/d
* Borislav Petkov wrote:
> From: Borislav Petkov
> Date: Mon, 15 Feb 2016 19:50:33 +0100
> Subject: [PATCH] x86/FPU: Fix double FPU regs activation
>
> sys_sigreturn() calls fpu__restore_sig() with interrupts enabled. When
> restoring a 32-bit signal frame. And it can happen that we get preemp
If pci_register_driver() fails then dgnc_NumBoards can never be more
than zero. dgnc_NumBoards is incremented only at the end of a successful
probe. And moreover if the pci driver has failed to register then we
never need to unregister it. Lets just print the warning, perform the
cleanup and exit w
If pci_enable_device() fails then we can return directly.
Signed-off-by: Sudip Mukherjee
---
I saw there is some pending dgnc patch in outreachy, so this series
might not apply. This series is based on staging-testing.
I will resend v2 if it fails.
drivers/staging/dgnc/dgnc_driver.c | 14 +
dgnc_cleanup_module() was called when the module unloaded to do a total
cleanup and it was also called if pci_register_driver() fails. But
dgnc_cleanup_module() will try dgnc_remove_driver_sysfiles() but the
sysfiles will be created only if pci_register_driver() succeeds.
So if pci_register_driver(
We may choose to load the module without the hardware present. That will
register the pci driver but since probe will not succeed so
dgnc_NumBoards will be 0. Now if we unload the module then the pci
driver stays registered as dgnc_NumBoards is 0. And if we try to load
the module again it fails wit
hi,
we are getting hard lockups on Core2 cpus (model 23)
just by running 'perf test'
PID: 10425 TASK: 880068562e00 CPU: 3 COMMAND: "perf"
#0 [88007d985a08] machine_kexec at 8105521b
#1 [88007d985a68] crash_kexec at 810f7412
#2 [88007d985b38] panic at
Em Sat, 27 Feb 2016 08:48:05 +0100
Takashi Iwai escreveu:
> On Sat, 27 Feb 2016 03:55:39 +0100,
> Shuah Khan wrote:
> >
> > On 02/26/2016 01:50 PM, Takashi Iwai wrote:
> > > On Fri, 26 Feb 2016 21:08:43 +0100,
> > > Shuah Khan wrote:
> > >>
> > >> On 02/26/2016 12:55 PM, Takashi Iwai wrote:
On Sat, Feb 27, 2016 at 12:55:46PM +0100, Ingo Molnar wrote:
> So I find it highly annoying that this review feedback was done by Boris, but
> not
> implemented in v8 :-(
And I missed it when going over v8. :-(
FWIW, since recently I get the impression that people don't take review
feedback ser
From: Colin Ian King
The boolean want is not initialized and hence garbage. The default should
be false (later it is only set to true on tne sinfo->authattrs check).
Found with static analysis using CoverityScan
Signed-off-by: Colin Ian King
---
crypto/asymmetric_keys/pkcs7_parser.c | 2 +-
1
From: Colin Ian King
The boolean 'found' is not initialized and hence garbage. It should
be initialized as false.
Found with static analysis using CoverityScan
Signed-off-by: Colin Ian King
---
drivers/power/lp8788-charger.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/
serial8250_em485_init() is supposed to be protected with
p->port.lock spinlock.
This may lead to issues when kmalloc sleeps, so it is better to use
GFP_ATOMIC in this spinlocked context.
Fixes: e490c9144cfa ("tty: Add software emulated RS485 support for 8250")
Reported-by: Ильяс Гасанов
Signed-of
Hello,
On Thu, Feb 25, 2016 at 05:49:34PM -0800, Laura Abbott wrote:
> At least one user reported that this fixed the issue and he said
> you could add
>
> Tested-by: Bob Schultz
Great, Manuel, can you please send a proper patch?
Thanks.
--
tejun
On Sat, Feb 27, 2016 at 01:02:11PM +0100, Ingo Molnar wrote:
> So I'm wondering, why did this commit:
>
> 58122bf1d856 x86/fpu: Default eagerfpu=on on all CPUs
>
Hmm, so looking at switch_fpu_prepare():
/*
* If the task has used the math, pre-load the FPU on xsave processors
cp210x_get_config and cp210x_set_config are cumbersome to use. This change
switches large register access to use new block functions. The old
functions are removed because now they become unused.
Signed-off-by: Konstantin Shkolnyy
---
change in v4: Instead of adding all new functions a one separa
cp210x_get_config and cp210x_set_config are cumbersome to use. This change
introduces new register access functions for 8 and 32-bit values, instead
of the above functions.
Signed-off-by: Konstantin Shkolnyy
---
change in v4: Instead of adding all new functions a one separate patch, added
them wi
cp210x_get_config and cp210x_set_config are cumbersome to use. This change
introduces new register access functions for 16-bit values, instead of
the above functions.
Signed-off-by: Konstantin Shkolnyy
---
change in v4: Instead of adding all new functions a one separate patch, added
them with pat
Morning, Thomas!
On Wed, Feb 24, 2016 at 04:24:54PM +0100, Thomas Petazzoni wrote:
> As requested by Rob Herring, this commit adds a SoC-specific
> compatible string to the Marvell ODMI DT binding.
>
> Signed-off-by: Thomas Petazzoni
> ---
> This commit applies on top of the Marvell ODMI driver
fixed all whitespaces in .c files in the fs
folder (not in the sub-folders)
Signed-off-by: amar-laksh
---
fs/aio.c | 8
fs/bad_inode.c | 16
fs/binfmt_aout.c | 6 +++---
fs/binfmt_elf.c| 26 +-
fs/binfmt_em86.c | 4 ++--
- On Feb 27, 2016, at 1:24 AM, H. Peter Anvin h...@zytor.com wrote:
> On 02/26/16 16:40, Mathieu Desnoyers wrote:
>>>
>>> I think it would be a good idea to make this a general pointer for the
>>> kernel to
>>> be able to write per thread state to user space, which obviously can't be
>>> don
On 2/27/16 10:45, Theodore Ts'o wrote:
> On Fri, Feb 26, 2016 at 11:26:02PM +0800, Chen Gang wrote:
>>> As for coding style, actually IMHO this patch is even _not_ a coding
>>> style, more like a code shuffle, indeed.
>>>
>>
>> "80 column limitation" is about coding style, I guess, all of us agree
On Sat, Feb 27, 2016 at 01:44:49PM +0530, Jayachandran Chandrashekaran Nair
wrote:
> On Tue, Feb 23, 2016 at 8:42 PM, Bjorn Helgaas wrote:
> > On Tue, Feb 23, 2016 at 08:10:03PM +0530, Jayachandran Chandrashekaran Nair
> > wrote:
> > > On Thu, Feb 18, 2016 at 9:19 PM, Bjorn Helgaas wrote:
> > >
On Saturday, February 27, 2016 08:39:42 AM Thomas Gleixner wrote:
> Rafael,
>
> On Sat, 27 Feb 2016, Rafael J. Wysocki wrote:
> > On Friday, February 26, 2016 06:43:32 PM Thomas Gleixner wrote:
> > > Make it possible to write a target state to the per cpu state file, so we
> > > can
> > > switch
On Sat, Feb 27, 2016 at 01:37:01PM +0100, Jiri Olsa wrote:
> we are getting hard lockups on Core2 cpus (model 23)
> I can't find what's special about Core2 CPU PEBS setup,
> it seems that oher CPUs are ok (tried on ivb/snb/hsw).
>
> reverting the 156174999dd1 fixed the issue for me
>
> ideas? th
From: Colin Ian King
The error return err is not initialized for the case when pci_map_rom
fails and no ROM can me mapped. Fix this by setting ret to -ENODATA;
(this is the same error value that is returned if the ROM data is
successfully mapped but does not match the expected ROM signature.).
On Sat, Feb 27, 2016 at 02:15:01PM +, Mathieu Desnoyers wrote:
> I'm concerned that this thread-local ABI structure may become messy.
> Let's just imagine how we would first introduce a "cpu_id" field (int32_t),
> and eventually add a "seqnum" field for rseq in the future (unsigned long).
The
On February 27, 2016 6:15:01 AM PST, Mathieu Desnoyers
wrote:
>- On Feb 27, 2016, at 1:24 AM, H. Peter Anvin h...@zytor.com wrote:
>
>> On 02/26/16 16:40, Mathieu Desnoyers wrote:
I think it would be a good idea to make this a general pointer for
>the kernel to
be able to write
On Fri, Feb 26, 2016 at 10:57:13AM -0300, Arnaldo Carvalho de Melo wrote:
> Ingo, Peter, have you guys followed this case?
>
> Summary: Some tracepoint have multiple fields with the same name, 'nr',
> the first one is a unique syscall ID, the other is a syscall
> argument:
I'm
Hi Linus,
The big chunk here is the paravirtual front-end for Linux guests of a
Microsoft Hyper-V VM. It's new, so no risk of regressions to pci-hyperv
itself. It does include minor changes to common code, but they are
low-risk.
This also reverts a few pieces of the recent IOAPIC hotplug work b
On Fri, Feb 26, 2016 at 06:00:56PM +0100, Petr Mladek wrote:
> On Fri 2016-02-26 17:25:52, Peter Zijlstra wrote:
> > On Fri, Feb 26, 2016 at 04:38:18PM +0100, Petr Mladek wrote:
> > > On Thu 2016-02-25 13:59:32, Peter Zijlstra wrote:
> > > > On Wed, Feb 24, 2016 at 05:18:05PM +0100, Petr Mladek wro
On Fri, Feb 26, 2016 at 04:23:09PM +0100, Petr Mladek wrote:
> I do not have a strong opinion here. On one hand, such a check might
> help with debugging. On the other hand, workqueues have happily lived
> without it for years.
TJ and me have a different view on these things. I'm always for the
st
On Friday, February 26, 2016 08:33:19 PM Steve Muckle wrote:
> On 02/25/2016 01:14 PM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Add a new cpufreq scaling governor, called "schedutil", that uses
> > scheduler-provided CPU utilization information as input for making
> > its deci
Hi Emil,
2016-02-27 Emil Velikov :
> Hi Gustavo,
>
> On 26 February 2016 at 21:00, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Change SYNC_IOC_FILE_INFO behaviour to avoid future API breaks and
> > optimize buffer allocation. In the new approach the ioctl needs to be called
> > tw
Hi Emil,
2016-02-27 Emil Velikov :
> Hi Gustavo,
>
> On 26 February 2016 at 18:31, Gustavo Padovan wrote:
> > From: Gustavo Padovan
> >
> > Play safe and add flags member to all structs. So we don't need to
> > break API or create new IOCTL in the future if new features that requires
> > flags
> I can't find what's special about Core2 CPU PEBS setup,
> it seems that oher CPUs are ok (tried on ivb/snb/hsw).
>
> reverting the 156174999dd1 fixed the issue for me
Ok multi-record PEbS was never tested on Core 2. I suppose we
can enable it only on Nehalem+
-Andi
--
a...@linux.intel.com -
1 - 100 of 247 matches
Mail list logo