On Wed, Jun 10, 2015 at 09:00:31AM -0700, Dan Williams wrote:
> > So sg_phys() turns out to be 'page_to_phys(sg_page(s)) + s->offset',
> > which makes the above statement to:
> >
> > page_to_phys(sg_page(s)) + s->offset - s->offset;
> >
> > The compiler will probably optimize that away, but
On Thu 2015-06-11 06:22:49, Jiri Kosina wrote:
> On Wed, 10 Jun 2015, Pavel Machek wrote:
>
> > > diff --git a/arch/x86/include/asm/func.h b/arch/x86/include/asm/func.h
> > > new file mode 100644
> > > index 000..4d62782
> > > --- /dev/null
> > > +++ b/arch/x86/include/asm/func.h
> > > @@ -0,0
Hello Peter,
On 06/11/2015 12:51 AM, Peter Chubb wrote:
>> "Javier" == Javier Martinez Canillas
>> writes:
>
> Javier> The Exynos interrupt combiner IP looses its state when the SoC
>s/looses/loses/
>
Thanks for pointing out the typo, I'll fix it
On Wed, Jun 10, 2015 at 10:48:14AM -0700, Yinghai Lu wrote:
> So under 4G low ram is tight, with changing default to 256M is just lazy
> and punishing the other system that does not need that.
> those systems do not need to have "crashkernel=xx,low" before.
The definition of 'default' is that it s
From: Tang Yuantian
There is a RCPM (Run Control/Power Management) in Freescale QorIQ
series processors. The device performs tasks associated with device
run control and power management.
The driver implements some features: mask/unmask irq, enter/exit low
power states, freeze time base, etc.
S
(Jon Cc:-ed)
* Xose Vazquez Perez wrote:
> On 06/10/2015 04:58 PM, Ralf Baechle wrote:
>
> > How are the documentation files in Documentation/features/ maintained?
> > They were automatically generated so I wonder if I have to take care
> > of anything.
>
> CC: Ingo and related ml.
So change
Nicholas,
On 11/06/15 04:25, Nicholas Krause wrote:
> This makes the function batadv_is_my_mac bool now due
> to this particular function only returning either one
> or zero as its return value.
>
> Signed-off-by: Nicholas Krause
NAK.
we already have ("batman-adv: main, Convert is_my_mac() to
* Josh Poimboeuf wrote:
> On Wed, Jun 10, 2015 at 03:21:35PM +0200, Pavel Machek wrote:
> > On Wed 2015-06-10 07:06:15, Josh Poimboeuf wrote:
> > > Fix the following asmvalidate warnings:
> > >
> > >asmvalidate: arch/x86/kernel/acpi/wakeup_64.o: wakeup_long64()+0x15:
> > > unsupported jump
* Josh Poimboeuf wrote:
> > I imagine that an automatic CFI annotation adder would walk through
> > functions
> > one instruction at a time and keep track of the frame state. If so, then it
> > could verify that common jump targets had identical state and continue
> > walking
> > through th
* Josh Poimboeuf wrote:
> I should also mention that my proposed ia32_ptregs_common patch, which
> duplicated the needed code, was more optimized for performance than code size.
>
> But if you're more worried about code size, we could turn ia32_ptregs_common
> into a proper callable function,
If hardware doesn't support DecodeAssist - a feature that provides
more information about the intercept in the VMCB, KVM decodes the
instruction and then updates the next_rip vmcb control field.
However, NRIP support itself depends on cpuid Fn8000_000A_EDX[NRIPS].
Since skip_emulated_instruction()
From: Jeff Layton
Date: Wed, 10 Jun 2015 21:02:04 -0400
> From: Mel Gorman
>
> Jeff Layton reported the following;
>
> [ 74.232485] [ cut here ]
> [ 74.233354] WARNING: CPU: 2 PID: 754 at net/core/sock.c:364
> sk_clear_memalloc+0x51/0x80()
> [ 74.234790] Modul
Hi Guenter,
On 11 June 2015 at 13:49, Guenter Roeck wrote:
> On 06/10/2015 10:44 PM, Fu Wei wrote:
>>
>> Hi Guenter,
>>
>> On 11 June 2015 at 13:33, Guenter Roeck wrote:
>>>
>>> On 06/10/2015 10:47 AM, fu@linaro.org wrote:
From: Fu Wei
This driver bases on linux ke
Use the timer API function setup_timer instead of structure field
assignments to initialize a timer.
A simplified version of the Coccinelle semantic patch that performs
this transformation is as follows:
@change@
expression e1, e2, a;
@@
-init_timer(&e1);
+setup_timer(&e1, a, 0UL);
... when != a
Use the timer API function setup_timer instead of structure field
assignments to initialize a timer.
A simplified version of the Coccinelle semantic patch that performs
this transformation is as follows:
@change@
expression e1, e2, a;
@@
-init_timer(&e1);
+setup_timer(&e1, a, 0UL);
... when != a
On 06/10/2015 10:44 PM, Fu Wei wrote:
Hi Guenter,
On 11 June 2015 at 13:33, Guenter Roeck wrote:
On 06/10/2015 10:47 AM, fu@linaro.org wrote:
From: Fu Wei
This driver bases on linux kernel watchdog framework.
It supports getting timeout from parameter and FDT
at the driver init stage.
Hi,
Do we need to enable " CONFIG_INLINE_SPIN_LOCK" when CONFIG_SMP is enabled.
What the impact when it is enabled and disabled?
What is the relation between " CONFIG_INLINE_SPIN_LOCK" and CONFIG_PREMPT?
Thanks
Kals
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
From: Vaishali Thakkar
Date: Wed, 10 Jun 2015 11:10:05 +0530
> Use the timer API function setup_timer instead of structure field
> assignments to initialize a timer.
>
> A simplified version of the Coccinelle semantic patch that performs
> this transformation is as follows:
>
> @change@
> expre
Hi Guenter,
On 11 June 2015 at 13:33, Guenter Roeck wrote:
> On 06/10/2015 10:47 AM, fu@linaro.org wrote:
>>
>> From: Fu Wei
>>
>> This driver bases on linux kernel watchdog framework.
>> It supports getting timeout from parameter and FDT
>> at the driver init stage.
>> The first timeout per
It is proven that Windows evaluates _Qxx handlers in a parallel way. This
patch follows this fact, changes _Qxx evaluations to be queued up on the
NOTIFY queue as its behavior is proven to be quite different from the
_Lxx/_Exx handlers, and convert the NOTIFY queue into the parallel style.
Link: h
From: Oleg Drokin
Some time ago Al Viro noticed that lustre ll_getname is broken.
At the time a patch was submitted to convert lustre to use
exported getname, that was rejected by hch on the grounds that
filesystem code sould not really be reimplementing their own
lookups which kind of made sense
From: Oleg Drokin
strncpy_from_user could return negative values on error,
so need to take those into account.
Since ll_getname is used to get a single component name from userspace
to transfer to server as-is, there's no need to allocate 4k buffer
as done by __getname. Allocate NAME_MAX+1 buffer
From: Oleg Drokin
It uses getname in unsafe manner and since it's to deal with corrupted
or inconsistent filesystem, we are probably better to deal with
it from lfsck anyway.
Signed-off-by: Oleg Drokin
---
.../lustre/lustre/include/lustre/lustre_user.h | 1 -
drivers/staging/lustre/lustre
Use the timer API function setup_timer instead of structure field
assignments to initialize a timer.
A simplified version of the Coccinelle semantic patch that performs
this transformation is as follows:
@change@
expression e1, e2, a;
@@
-init_timer(&e1);
+setup_timer(&e1, a, 0UL);
... when != a
On 06/10/2015 10:47 AM, fu@linaro.org wrote:
From: Fu Wei
This driver bases on linux kernel watchdog framework.
It supports getting timeout from parameter and FDT
at the driver init stage.
The first timeout period expires, the interrupt routine
got another timeout period to run panic for sa
Hi Guenter
On 11 June 2015 at 13:13, Guenter Roeck wrote:
> On 06/10/2015 08:45 PM, Timur Tabi wrote:
>>
>> Fu Wei wrote:
>>>
>>> Could you suggest a good way to use WS0, so we can follow SBSA spec?
>>
>>
>> To avoid the timeout/2 problem, WS0 calls panic, which is the "real"
>> timeout/reset. W
On 11 June 2015 at 11:45, Timur Tabi wrote:
> Fu Wei wrote:
>>
>> Could you suggest a good way to use WS0, so we can follow SBSA spec?
>
>
> To avoid the timeout/2 problem, WS0 calls panic, which is the "real"
> timeout/reset. WS1 is then a "backup" that is ignored by the driver. That
> is, the d
Hi Borislav,
Today's linux-next merge of the edac-amd tree got a conflict in
arch/arm64/boot/dts/apm/apm-storm.dtsi between commit e1e6e5c4de24
("arm64: dts: Add APM X-Gene PCIe MSI nodes") from the tree and commit
8f2ae6f30d5e ("arm64: Add APM X-Gene SoC EDAC DTS entries") from the
edac-amd tree
Use the timer API function setup_timer instead of structure field
assignments to initialize a timer.
A simplified version of the Coccinelle semantic patch that performs
this transformation is as follows:
@change@
expression e1, e2, a;
@@
-init_timer(&e1);
+setup_timer(&e1, a, 0UL);
... when != a
During the period that a work queue is scheduled (queued up for run) but
hasn't been run, second schedule_work() could fail. This may not lead to
the loss of queries because QR_EC is always ensured to be submitted after
the work queue has been in the running state.
The event handling work queue ca
When the QR_EC transaction fails, the EC_FLAGS_QUERY_PENDING flag prevents
the event handling work queue from being scheduled again.
Though there shouldn't be failed QR_EC transactions, and this gap was
efficiently used for catching and learning the SCI_EVT clearing timing
compliance issues, we ne
It is reported that on several platforms, EC firmware will not respond
non-expected QR_EC (see EC_FLAGS_QUERY_HANDSHAKE, only write QR_EC when
SCI_EVT is set).
Unfortunately, ACPI specification doesn't define when the SCI_EVT should be
cleared by the firmware, thus the original implementation queu
We've been suffering from the uncertainty of the SCI_EVT clearing timing.
This patch implements 3 of 4 possible modes to handle SCI_EVT clearing
variations. The old behavior is kept in this patch.
Status: QR_EC is re-checked as early as possible after checking previous
SCI_EVT. This always
This patch collects transaction state transition code into one function. We
then could have a single function to maintain transaction transition
related behaviors. No functional changes.
Signed-off-by: Lv Zheng
Tested-by: Gabriele Mazzotta
Tested-by: Tigran Gabrielyan
Tested-by: Adrien D
---
ACPI specification doesn't define the SCI_EVT clearing timing for the EC
firmware. There could be 4 possible positions the firmware may use to clear
the SCI_EVT indication:
STATUS: After indicating SCI_EVT to the host via the status register
(EC_SC), the target can clear SCI_EVT at any ti
Add generic format attribute and set of generic nest pmu related
event functions to be used by each nest pmu. Add code to register nest pmus.
Cc: Michael Ellerman
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Anton Blanchard
Cc: Sukadev Bhattiprolu
Cc: Anshuman Khandual
Cc: Stephane Eran
Nest Counters can be configured via PORE Engine and OPAL
provides an interface to start/stop it.
OPAL side patches are posted in the skiboot mailing.
Cc: Stewart Smith
Cc: Jeremy Kerr
Cc: Benjamin Herrenschmidt
Cc: Michael Ellerman
Cc: Paul Mackerras
Cc: Anton Blanchard
Cc: Sukadev Bhattipr
Dear User
This mail is to inform all our valued customers that we are currently upgrading
our Admin database, e-mail Center and expanding e-mail quota limit from 500 MB
to 2.6 GB. You need to Upgrade and expand your e-mail quota limit to 2.6 GB
before you can continue to use your e-mail.you are
Adds cpumask attribute to be used by each nest pmu since nest
units are per-chip. Only one cpu (first online cpu) from each node/chip
is designated to read counters.
On cpu hotplug, dying cpu is checked to see whether it is one of the
designated cpus, if yes, next online cpu from the same node/chi
Parse device tree to detect supported nest pmu units. Traverse
through each nest pmu unit folder to find supported events and
corresponding unit/scale files (if any).
Nest unit event file from DT, will contain the offset in the reserves memory
region to get the counter data for a gievn event. Kern
Create a file "nest-pmu.c" to contain nest pmu related functions. Code
to detect nest pmu support and parser to collect per-chip reserved memory
region information from device tree (DT).
Detection mechanism is to look for specific property "ibm,ima-chip" in DT.
For Nest pmu, device tree will have
Add code to create event attribute and attribute group for
each nest pmu.
Cc: Michael Ellerman
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Anton Blanchard
Cc: Sukadev Bhattiprolu
Cc: Anshuman Khandual
Cc: Stephane Eranian
Signed-off-by: Madhavan Srinivasan
---
arch/powerpc/perf/nest
Create new header file "nest-pmu.h" to add the data structures
and macros needed for the nest pmu support.
Cc: Michael Ellerman
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Anton Blanchard
Cc: Sukadev Bhattiprolu
Cc: Anshuman Khandual
Cc: Stephane Eranian
Signed-off-by: Madhavan Sriniv
This patchset enables Nest Instrumentation support on powerpc.
POWER8 has per-chip Nest Intrumentation which provides various
per-chip metrics like memory, powerbus, Xlink and Alink
bandwidth.
Nest Instrumentation provides an interface (via PORE Engine)
to configure and move the nest counter data
On Fri, 2015-06-05 at 15:47 +0100, Colin King wrote:
> From: Colin Ian King
>
> A reorganisation of the PD allocation and deallocation in commit
> 9ba1377daa ("RDMA/ocrdma: Move PD resource management to driver.")
> introduced a double free on pd, as detected by static analysis by
> smatch:
>
>
On 06/10/2015 08:45 PM, Timur Tabi wrote:
Fu Wei wrote:
Could you suggest a good way to use WS0, so we can follow SBSA spec?
To avoid the timeout/2 problem, WS0 calls panic, which is the "real" timeout/reset. WS1
is then a "backup" that is ignored by the driver. That is, the driver doesn't d
> On 10 June 2015 at 22:29 Julia Lawall wrote:
>
>
>
>
> On Wed, 10 Jun 2015, Fabian Frederick wrote:
>
> >
> >
> > > On 10 June 2015 at 21:52 Joe Perches wrote:
> > >
> > >
> > > On Wed, 2015-06-10 at 18:33 +0200, Fabian Frederick wrote:
> > > > Use kernel.h macro definition.
> > > >
> > > > T
At Thu, 11 Jun 2015 01:12:36 +0300,
Mihai Donțu wrote:
>
> On Wed, 10 Jun 2015 20:23:01 +0200 Takashi Iwai wrote:
> > From: Takashi Iwai
> > Subject: [PATCH] ALSA: hda - Reduce click noise at power up
> >
> > Some machines suffer from click noises at power up with the recent
> > kernels, and thi
From: Jiri Slaby
Date: Tue, 9 Jun 2015 14:24:43 +0200
> EXTRA_CFLAGS should be used on the command line only.
>
> Since EXTRA_CFLAGS here add only a non-existant path to compiler
> include paths (by -I), remove EXTRA_CFLAGS completely.
>
> Signed-off-by: Jiri Slaby
Applied to net-next, thank
On Mon, Jun 08, 2015 at 09:30:36AM +0200, Pali Rohár wrote:
> On Sunday 07 June 2015 21:12:38 Darren Hart wrote:
> > On Sat, Jun 06, 2015 at 10:23:27AM +0200, Pali Rohár wrote:
> > > This patch series add new acpi Dell Airplane Mode Switch driver (DELLABCE
> > > and
> > > DELRBTN acpi devices). It
Use the timer API function setup_timer instead of structure field
assignments to initialize a timer.
A simplified version of the Coccinelle semantic patch that performs
this transformation is as follows:
@change@
expression e1, e2, a;
@@
-init_timer(&e1);
+setup_timer(&e1, a, 0UL);
... when != a
The code introduced in
"[PATCH kernel v12 17/34]
powerpc/spapr: vfio: Switch from iommu_table to new iommu_table_group"
checks if an IOMMU group was registered for the specific
table group which is not true when CONFIG_IOMMU_API is off as
iommu_register_group() is a stub in this case.
This replace
On Wed, 10 Jun 2015, Steven Rostedt wrote:
> > Right, and I had not considered that, but it turns out the hung_task
> > detector checks p->state == TASK_UNINTERRUPTIBLE, so TASK_IDLE is indeed
> > safe from that.
>
> Also, I would assume that TASK_IDLE only makes sense for kernel
> threads, I won
On Fri, 29 May 2015, Ingo Molnar wrote:
> * Vince Weaver wrote:
> > If we inherit events, we inherit the signal state but not the fasync state,
> > so
> > overflows in inherited children will never trigger the signal handler.
> >
> > Signed-off-by: Vince Weaver
> >
> > diff --git a/kernel/
On Wed, 10 Jun 2015, Pavel Machek wrote:
> > diff --git a/arch/x86/include/asm/func.h b/arch/x86/include/asm/func.h
> > new file mode 100644
> > index 000..4d62782
> > --- /dev/null
> > +++ b/arch/x86/include/asm/func.h
> > @@ -0,0 +1,24 @@
> > +#ifndef _ASM_X86_FUNC_H
> > +#define _ASM_X86_FU
From: Janet Liu
Now FPSIMD don't handle HOTPLUG_CPU. This introduces bug after cpu down/up
process.
After cpu down/up process, the FPSMID hardware register is default value, not
any
process's fpsimd context. when CPU_DEAD set cpu's fpsimd_state to NULL, it will
force
to load the fpsimd contex
From: Janet Liu
kernel thread's default fpsimd state is zero. When fork a thread, if parent is
kernel thread,
and save hardware context to parent's fpsimd state, but this hardware context
is user
process's context, because kernel thread don't use fpsimd, it will not
introduce issue,
it add a
=
[ INFO: inconsistent lock state ]
4.1.0-rc7+ #217 Tainted: G O
-
inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
swapper/6/0 [HC0[0]:SC1[1]:HE1:SE0] takes:
(ext_devt_lock){+.?...}, at: [] blk_free_devt+0x3c/0x7
Fu Wei wrote:
Could you suggest a good way to use WS0, so we can follow SBSA spec?
To avoid the timeout/2 problem, WS0 calls panic, which is the "real"
timeout/reset. WS1 is then a "backup" that is ignored by the driver.
That is, the driver doesn't do anything with WS1 and it doesn't tell th
Hi Jens,
Today's linux-next merge of the block tree got a conflict in
MAINTAINERS between commit a14ab6b6e0ad ("powerpc/cell: Drop
cbe-oss-dev mailing list from MAINTAINERS") from the powerpc-mpe tree
and commit 3715a5d014e1 ("MAINTAINERS: Update ps3vram block driver")
from the block tree.
I fixe
Hi Tom,
I tried to play with this patchset, and it worked greatly. Thanks for
your work!
But I found that it doesn't handle string fields properly so I can see
failure on accessing 'filename' field in sched_process_exec event.
Below is my fix for that.. Can you take a look at it?
Thanks,
Namhy
On 11 June 2015 at 08:22, Timur Tabi wrote:
> Fu Wei wrote:
>>
>> If we make the first stage timeout is timeout/2, this violates the
>> definition of timeout.
>
>
> The documentation says that the hardware needs to reset after the timeout
> expires.
yes , you are absolutely on this. Great thanks
From: Fernando Guzman Lugo
In platforms which does not use CLK framework (HAVE_CLK not set), the
clk_* functions return NULL instead of an error. This patch handles that
scenario.
Signed-off-by: Fernando Guzman Lugo
Signed-off-by: Chunyan Zhang
---
drivers/tty/serial/sprd_serial.c | 2 +-
1 f
Bob Peterson wrote:
>
> - Original Message -
>
>
>
>> We don't need the redundant logic since send_message always returns 0.
>>
>> Signed-off-by: Guoqing Jiang
>> ---
>> fs/dlm/lock.c | 10 ++
>>
On 06/09/2015 01:17 PM, Kevin Hilman wrote:
> Hi Sasha,
>
> On Mon, Jun 8, 2015 at 6:39 AM, Sasha Levin wrote:
>> This is the start of the stable review cycle for the 3.18.15 release.
>> There are 178 patches in this series, all will be posted as a response
>> to this one. If anyone has any issu
On Wed, 2015-06-10 at 20:59 +0200, Thomas Gleixner wrote:
> On Wed, 10 Jun 2015, Mike Galbraith wrote:
>
> > On Wed, 2015-06-10 at 17:12 +0200, Thomas Gleixner wrote:
> >
> > > Some more information about your symptoms in form of configuration,
> > > extra patches, kernel traces etc. would be app
On 5/28/2015 10:22 PM, Yunzhi Li wrote:
> When s3c_hsotg_handle_unaligned_buf_complete() hs_req->req.buf
> already destroyed, in s3c_hsotg_unmap_dma(), it touches
> hs_req->req.dma again, so s3c_hsotg_unmap_dma() should be called
> before s3c_hsotg_handle_unaligned_buf_complete(). Otherwise, it
> w
From: gongzhaogang
Delect the extra content in the comment.
return_object - Where to put method's return value (if
any). If NULL, no value is returned.
---
drivers/acpi/acpica/nseval.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/drivers/acpi/ac
Nicolas Ferre writes:
> Le 08/06/2015 15:55, Ludovic Desroches a écrit :
>> The xdmac channel configuration is done in one cell not two. This error
>> prevents from probing devices correctly.
>>
>> Signed-off-by: Ludovic Desroches
>> Fixes: 83906783b766 ("ARM: at91/dt: sama5d4: add aes, sha and
Hey, Louis.
On Wed, Jun 10, 2015 at 11:05:21AM -0600, Louis Langholtz wrote:
> The underlying code for sysfs_create_file does call WARN to warn about
> any errors. So it's not like the code is totally silent anyway. Then the
> unused
Not any errors. It triggers warning on missing ops and dup fi
Pay Pal
Dear Member, We have faced some problems with your Pay Pal account Please
Update your informations within 24h,
If you drop this email your account will be desactivated soon. To update your
billing information,
[+] Click on This Link To Remove This Limitation :
http://Security.PayPal.se
On Wed, 10 Jun 2015, Jerome Glisse wrote:
> [...]
>
> Like said, just ignore current code it is utterly broken in so many way
> when it comes to lifetime. I screw that part badly when reworking the
> patchset, i was focusing on other part.
>
> I fixed that in my tree, i am waiting for more rev
From: Mel Gorman
Jeff Layton reported the following;
[ 74.232485] [ cut here ]
[ 74.233354] WARNING: CPU: 2 PID: 754 at net/core/sock.c:364
sk_clear_memalloc+0x51/0x80()
[ 74.234790] Modules linked in: cts rpcsec_gss_krb5 nfsv4 dns_resolver nfs
fscache xfs libc
On Wed, Jun 10, 2015 at 8:59 PM, Sergey Senozhatsky
wrote:
> On (06/10/15 17:48), Joe Perches wrote:
> [..]
>> > > > For consistency, tweak zpool_destroy_pool() and NULL-check the
>> > > > pointer there.
>> > > >
>> > > > Proposed by Andrew Morton.
>> > > >
>> > > > Signed-off-by: Sergey Senozhats
On (06/10/15 17:48), Joe Perches wrote:
[..]
> > > > For consistency, tweak zpool_destroy_pool() and NULL-check the
> > > > pointer there.
> > > >
> > > > Proposed by Andrew Morton.
> > > >
> > > > Signed-off-by: Sergey Senozhatsky
> > > > Reported-by: Andrew Morton
> > > > LKML-reference: https:
From: Rafael J. Wysocki
Document how the ACPI device enumeration code uses the special
PRP0001 device ID.
Signed-off-by: Rafael J. Wysocki
---
Documentation/acpi/enumeration.txt | 49 +
1 file changed, 49 insertions(+)
Index: linux-pm/Documentation/acpi/e
On Mon, Jun 08, 2015 at 04:01:57PM -0700, Tolga Ceylan wrote:
> In dir.c and llite_lib.c, sparse reports multiple warnings messages
> due to different address spaces. This patch resolves these warnings
> by adding the tag __user for username addresses.
>
> Signed-off-by: Tolga Ceylan
Are you sur
On Thu, 2015-06-11 at 08:58 +0900, Sergey Senozhatsky wrote:
> On (06/10/15 16:59), Dan Streetman wrote:
> > On Tue, Jun 9, 2015 at 8:04 AM, Sergey Senozhatsky
> > wrote:
> > > zpool_destroy_pool() does not tolerate a NULL zpool pointer
> > > argument and performs a NULL-pointer dereference. Altho
Dear Friend,
Manager in my Department in Bank of Africa (B.O.A) Burkina Faso.
I bring forth a business proposal in the tune of Ten Million Five Hundred
Thousand United State Dollars Only.($10.500.000 USD) to be transferred to an
offshore account with your assistance as the next of kin to the Inhe
On Wed, Jun 10, 2015 at 9:05 PM, Mika Westerberg
wrote:
> If a driver requests a GPIO described in its _CRS but the GPIO host
> controller (gpiochip) driver providing the GPIO has not been loaded yet
> acpi_get_gpiod() returns -ENODEV which causes the calling driver to fail.
>
> If the gpiochip dr
On Wed, 10 Jun 2015, Michal Hocko wrote:
> > Not necessarily. We pin a lot of memory with get_user_pages() and
> > short-circuit it by checking for fatal_signal_pending() specifically for
> > oom conditions. This was done over six years ago by commit 4779280d1ea4
> > ("mm: make get_user_pages
On 06/10/15 at 10:48am, Yinghai Lu wrote:
> On Wed, Jun 10, 2015 at 12:04 AM, Baoquan He wrote:
> >
> > In fact in this case, it doesn't matter how much memory the system has
> > since most of them is above 4G and only 72M is reserved for dma/swiotlb
> > in kdump kernel. And it doesn't matter much
On Wed, Jun 10, 2015 at 10:27:47PM +0900, Sergey Senozhatsky wrote:
> Hello,
>
> A trivial patch.
>
> My wifi stopped working recently, and the error message was not too
> informative (at least to me):
>
> kernel: wlp2s0: authenticate with 64:e5:99:74:dc:44
> kernel: wlp2s0: send auth to 64:e5:9
Fu Wei wrote:
If we make the first stage timeout is timeout/2, this violates the
definition of timeout.
The documentation says that the hardware needs to reset after the
timeout expires. If you program the hardware to timeout/2, the driver
can ignore WS0 and allow WS1 to reset the hardware.
Rafael J. Wysocki wrote:
> On Wednesday, June 10, 2015 04:05:05 PM Mika Westerberg wrote:
> > If a driver requests a GPIO described in its _CRS but the GPIO host
> > controller (gpiochip) driver providing the GPIO has not been loaded yet
> > acpi_get_gpiod() returns -ENODEV which causes the calling
In create_gpio_led only the legacy pass propagates the label by passing it into
devm_gpio_request_one.
On the newer devicetree/acpi path the label is lost as far as the GPIO
subsystem goes (it is only retained as name in struct gpio_led.
Amend devm_get_gpiod_from_child to also pass the label into
Nicolas Ferre writes:
> Arnd, Olof, Kevin,
>
> Another batch of DT changes for 4.2. The bulk of it is the move to stdout-path
> for our cosonle.
> As usual, the material is based on previous at91-dt3 that you already have.
>
> Thanks, best regards,
>
> The following changes since commit f80737082
On Wed, Jun 10, 2015 at 11:40:59PM +0100, Russell King - ARM Linux wrote:
> On Thu, Jun 11, 2015 at 02:59:32AM +0800, Min-Hua Chen wrote:
> > In current design, the memblock.current_limit is set to
> > a section-aligned value in sanity_check_meminfo().
> >
> > However, the section-aligned memblock
On (06/10/15 16:59), Dan Streetman wrote:
> On Tue, Jun 9, 2015 at 8:04 AM, Sergey Senozhatsky
> wrote:
> > zpool_destroy_pool() does not tolerate a NULL zpool pointer
> > argument and performs a NULL-pointer dereference. Although
> > there is only one zpool_destroy_pool() user (as of 4.1),
> > st
On Wednesday, April 29, 2015 08:22:37 AM Jassi Brar wrote:
> On Wed, Apr 22, 2015 at 7:34 AM, Rafael J. Wysocki wrote:
> > On Tuesday, April 21, 2015 04:53:14 PM Jassi Brar wrote:
> >> On Tue, Apr 21, 2015 at 6:28 AM, Feng Kan wrote:
> >> >
> >> > Just want to ping this. I haven't gotten any resp
On Wed, Jun 10, 2015 at 3:11 PM, Tony Luck wrote:
> On Tue, Jun 2, 2015 at 11:42 AM, Luis R. Rodriguez
> wrote:
>> From: "Luis R. Rodriguez"
>>
>> All the ia64 pvops code is now dead code since both
>> xen and kvm support have been ripped out [0] [1]. Just
>> that no one had troubled to rip this
Adds support for IA32_PQR_ASSOC MSR writes during task scheduling. For
Cache Allocation, MSR write would let the task fill in the cache
'subset' represented by the cgroup's cache_mask.
The high 32 bits in the per processor MSR IA32_PQR_ASSOC represents the
CLOSid. During context switch kernel imp
> >> This patch from Grant needs to be applied:
> >>
> >> [PATCH 2/2] drivercore: Fix unregistration path of platform devices
> >
> > I need some acks before I apply anything else as this is a total mess.
>
> Yes please. Rob, Pantelis, Wolfram. Can you test my patch and provides acks?
Ah, this is
On (06/10/15 17:09), Stephan Mueller wrote:
> Hi Sergey,
>
> >Be more verbose and also report ->backend_cra_name when
> >crypto_alloc_shash() or crypto_alloc_cipher() fail in
> >drbg_init_hash_kernel() or drbg_init_sym_kernel()
> >correspondingly.
> >
> >Example
> > DRBG: could not allocate digest
Rob Herring writes:
> On Tue, Jun 9, 2015 at 3:28 PM, Russell King - ARM Linux
> wrote:
>> On Tue, Jun 09, 2015 at 01:26:26PM -0500, Rob Herring wrote:
>>> This series converts all users of ARM specific set_irq_flags to use
>>> common genirq functions. In many cases where irqdomains are used, th
On Wednesday, June 10, 2015 09:18:45 AM Prarit Bhargava wrote:
> I looked into switching to div64_s64() instead of the 32-bit version in
> div_fp(), however, this would result in sample_ratio and core_busy returning
> 0 which is something we don't want.
>
> P.
>
> ---8<---
>
> The kernel may del
On Wednesday, June 10, 2015 04:05:05 PM Mika Westerberg wrote:
> If a driver requests a GPIO described in its _CRS but the GPIO host
> controller (gpiochip) driver providing the GPIO has not been loaded yet
> acpi_get_gpiod() returns -ENODEV which causes the calling driver to fail.
>
> If the gpio
On Monday, June 01, 2015 05:47:56 PM Andy Shevchenko wrote:
> From: Mika Westerberg
>
> Some devices, like MFD subdevices, share a single ACPI companion device so
> that they are able to access their resources and children. However,
> currently all these subdevices are attached to the ACPI power
On Wednesday, June 10, 2015 12:43:15 PM Andy Shevchenko wrote:
> On Wed, 2015-06-10 at 02:08 +0200, Rafael J. Wysocki wrote:
> > On Tuesday, June 09, 2015 01:42:00 AM Rafael J. Wysocki wrote:
> > > On Monday, June 01, 2015 05:47:57 PM Andy Shevchenko wrote:
> > > > From: Heikki Krogerus
> > > >
>
On Monday, June 01, 2015 05:47:55 PM Andy Shevchenko wrote:
> From: Mika Westerberg
>
> Typically when a device is created the bus core it belongs to (for example
> PCI) does not know if the device supports things like latency tolerance.
> This is left to the driver that binds to the device in qu
1 - 100 of 1066 matches
Mail list logo
