Hi Duc,
On 08/10/15 08:48, Duc Dang wrote:
> GICv2m driver currently only supports single v2m frame. This
> patch extend this driver to support multiple v2m frames. All of
> the v2m frames will be own by a single MSI domain. Each PCIe node
> can specify msi-parent as the first frame of the v2m fra
On 2015/10/8 15:55, Chen Feng wrote:
Signed-off-by: Chen Feng
Signed-off-by: Yu Dongbin
---
drivers/staging/android/ion/Kconfig| 7 +
drivers/staging/android/ion/Makefile | 1 +
drivers/staging/android/ion/hisilicon/Kconfig | 5 +
drivers/staging/
Hi Steve,
On 08/10/15 21:40, Steve Muckle wrote:
> Hi Juri,
>
> On 07/07/2015 11:24 AM, Morten Rasmussen wrote:
>> From: Juri Lelli
>>
>> When a CPU is going idle it is pointless to ask for an OPP update as we
>> would wake up another task only to ask for the same capacity we are already
>> runn
This is pure code movement, making sure the widen_string() helper is
defined before the string() function.
Signed-off-by: Rasmus Villemoes
---
lib/vsprintf.c | 62 +-
1 file changed, 31 insertions(+), 31 deletions(-)
diff --git a/lib/vspri
If the string corresponding to a %s specifier can change under us, we
might end up copying a \0 byte to the output buffer. There might be
callers who expect the output buffer to contain a genuine C string
whose length is exactly the snprintf return value (assuming truncation
hasn't happened or has
Pull out the logic in dentry_name() which handles field width space
padding, in preparation for reusing it from string(). Rename the
widen() helper to move_right(), since it is used for handling the
!(flags & LEFT) case.
Signed-off-by: Rasmus Villemoes
---
lib/vsprintf.c | 46 +++
> You forgot to call pm_runtime_disable() in the error path.
> I think some of your other patches suffer from the same issue.
Ouch! Thanks a lot, Geert!
signature.asc
Description: Digital signature
On 08/10/15 18:28, Catalin Marinas wrote:
On Thu, Oct 08, 2015 at 06:22:34PM +0100, Suzuki K. Poulose wrote:
On 08/10/15 15:45, Christoffer Dall wrote:
On Wed, Oct 07, 2015 at 10:26:14AM +0100, Marc Zyngier wrote:
I just had a chat with Catalin, who did shed some light on this.
It all has to d
Felipe Tonello wrote:
> req->actual == req->length means that there is no data left to enqueue,
This condition is not checked in the patch.
> so free the request.
>
> Signed-off-by: Felipe F. Tonello
> ---
> drivers/usb/gadget/function/f_midi.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 de
On 2015/10/09 15:46, Xishi Qiu wrote:
On 2015/10/9 22:56, Taku Izumi wrote:
Xeon E7 v3 based systems supports Address Range Mirroring
and UEFI BIOS complied with UEFI spec 2.5 can notify which
ranges are reliable (mirrored) via EFI memory map.
Now Linux kernel utilize its information and alloca
On Thu, Oct 08, 2015 at 02:22:25PM +0530, Vineet Gupta wrote:
> On Tuesday 06 October 2015 08:53 PM, Kirill A. Shutemov wrote:
> > With new refcounting we don't need to mark PMDs splitting. Let's drop code
> > to handle this.
> >
>
> >
> > diff --git a/include/asm-generic/pgtable.h b/includ
On 2015/10/9 17:08, Kamezawa Hiroyuki wrote:
> On 2015/10/09 14:52, Jiang Liu wrote:
>> On 2015/10/9 4:20, Andrew Morton wrote:
>>> On Wed, 19 Aug 2015 17:18:15 -0700 (PDT) David Rientjes
>>> wrote:
>>>
On Wed, 19 Aug 2015, Patil, Kiran wrote:
> Acked-by: Kiran Patil
Where
Hi Antoine,
On Fri, 9 Oct 2015 11:03:53 +0200
Antoine Tenart wrote:
> Hi Jisheng,
>
> On Fri, Oct 09, 2015 at 04:17:05PM +0800, Jisheng Zhang wrote:
> > diff --git a/drivers/pinctrl/berlin/Kconfig b/drivers/pinctrl/berlin/Kconfig
> > index b18322b..c13f6d2 100644
> > --- a/drivers/pinctrl/berli
On Thu, 8 Oct 2015, Andy Lutomirski wrote:
> I want to propose a new primitive that might go a long way toward
> solving this issue. The new primitive would be called the "big percpu
> lock".
It took us 15+ years to get rid of the "Big Kernel Lock", so we really
don't want to add a new "Big XXX L
On 10/08/15 at 08:20pm, Hannes Frederic Sowa wrote:
> Hi Alexei,
>
> On Thu, Oct 8, 2015, at 07:23, Alexei Starovoitov wrote:
> > The feature is controlled by sysctl kernel.unprivileged_bpf_disabled.
> > This toggle defaults to off (0), but can be set true (1). Once true,
> > bpf programs and map
On Fri, 2015-10-09 at 16:47 +0800, wangx...@gmail.com wrote:
> From: Xiang Wang
>
> 1. Add High-speed mode support in designware core
> 2. Add function i2c_dw_acpi_setup_speed to determine
> the bus speed from ACPI table.
>
> Signed-off-by: Xiang Wang
> ---
> drivers/i2c/busses/i2c-designware-
On 10/08/2015 07:07 PM, Andrey Ryabinin wrote:
> 2015-10-08 18:11 GMT+03:00 Catalin Marinas :
>> On Thu, Oct 08, 2015 at 02:09:26PM +0200, Ard Biesheuvel wrote:
>>> On 8 October 2015 at 13:23, Andrey Ryabinin wrote:
On 10/08/2015 02:11 PM, Mark Rutland wrote:
> On Thu, Oct 08, 2015 at 01:
Hi,Pavel,
> -Original Message-
> From: Pavel Machek [mailto:pa...@ucw.cz]
> Sent: Sunday, October 04, 2015 11:16 PM
> To: Chen, Yu C
> Cc: r...@rjwysocki.net; Brown, Len; linux...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Zhang, Rui; j...@suse.com;
> joeyli.ker...@gmail.com; ying..
On Fri, 2015-10-09 at 16:47 +0800, wangx...@gmail.com wrote:
> From: Xiang Wang
>
> 1. Support setting hs_hcnt and hs_lcnt
> 2. Get bus speed mode from ACPI companion of the
> i2c controller.
>
> Signed-off-by: Xiang Wang
> ---
> drivers/i2c/busses/i2c-designware-pcidrv.c | 7 +++
> 1 file
Thanks Pavel !
Hi, Ingo,
do you have a bandwidth to help look at this version,
since this bug has been on bugzilla for a while.
Thanks a lot.
Best Regards,
Yu
> -Original Message-
> From: Pavel Machek [mailto:pa...@ucw.cz]
> Sent: Thursday, September 17, 2015 1:30 PM
> To: Chen, Yu C
>
On 08/10/2015 18:11, Lina Iyer wrote:
Hi Marc,
Thanks for rebasing on top of my latest series.
On Tue, Oct 06 2015 at 08:27 -0600, Marc Titinger wrote:
Devices may register an intermediate retention state into the domain upon
I may agree with the usability of dynamic adding a state to the do
From: Wolfram Sang
The core may register clients attached to this master which may use
funtionality from the master. So, RuntimePM must be enabled before, otherwise
this will fail. While here, move drvdata, too.
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-s3c2410.c | 12 +++-
From: Wolfram Sang
The core may register clients attached to this master which may use
funtionality from the master. So, RuntimePM must be enabled before, otherwise
this will fail.
Signed-off-by: Wolfram Sang
---
drivers/spi/spi-coldfire-qspi.c | 3 ++-
1 file changed, 2 insertions(+), 1 delet
On Fri, Oct 09, 2015 at 10:31:38AM +0200, Peter Zijlstra wrote:
> On Thu, Oct 08, 2015 at 02:44:39PM -0700, Paul E. McKenney wrote:
> > On Thu, Oct 08, 2015 at 01:16:38PM +0200, Peter Zijlstra wrote:
> > > On Thu, Oct 08, 2015 at 02:50:36PM +1100, Michael Ellerman wrote:
> > > > On Wed, 2015-10-07
From: Wolfram Sang
The core may register clients attached to this master which may use
funtionality from the master. So, RuntimePM must be enabled before, otherwise
this will fail.
Signed-off-by: Wolfram Sang
---
drivers/i2c/busses/i2c-designware-platdrv.c | 13 +++--
1 file changed, 7
From: Wolfram Sang
The core may register clients attached to this master which may use
funtionality from the master. So, RuntimePM must be enabled before, otherwise
this will fail. While here, move drvdata, too.
Reported-by: Geert Uytterhoeven
Signed-off-by: Wolfram Sang
---
drivers/i2c/busse
On Thu, 8 Oct 2015, Miroslav Lichvar wrote:
> On Thu, Oct 08, 2015 at 10:52:05AM +0200, Arnd Bergmann wrote:
> > On Thursday 08 October 2015 08:23:44 Miroslav Lichvar wrote:
> > > The difference is that with the one-week step the kernel and userspace
> > > still agree on the current time and it is
Hi Jisheng,
>> + res = platform_get_resource_byname(pdev, IORESOURCE_MEM, "mbus");
>> + pxa->mbus_win_regs = devm_ioremap_resource(&pdev->dev, res);
>> + if (IS_ERR(pxa->mbus_win_regs)) {
>> + dev_err(mmc_dev(host->mmc),
>> + "failed to obtain MBus wind
On Tue, Sep 22, 2015 at 04:04:52PM +0530, Vineet Gupta wrote:
> This reduces/simplifies the diff for the next patch which moves THP
> specific code.
>
> Signed-off-by: Vineet Gupta
Okay, so you group pte-related helpers together, right?
It would be nice to mention it in commit message.
Acked-by
On Thu, Sep 24, 2015 at 04:57:37AM -0700, Shawn Guo wrote:
> On Thu, Sep 24, 2015 at 01:43:24PM +0800, Shengjiu Wang wrote:
> > On Wed, Sep 23, 2015 at 08:33:41AM -0700, Shawn Guo wrote:
> > > On Tue, Sep 15, 2015 at 06:01:01PM +0800, Shengjiu Wang wrote:
> > > > As spdif driver will register SPDIF
On Fri, Oct 09, 2015 at 12:32:18PM +0300, Andrey Ryabinin wrote:
[...]
> I thought the EFI stub isolation patches create a copy of mem*() functions in
> the stub,
> but they are just create aliases with __efistub_ prefix.
>
> We only need to create some more aliases for KASAN.
> The following pa
Hi, LV
> -Original Message-
> From: Zheng, Lv
> Sent: Friday, October 09, 2015 4:33 PM
> To: Chen, Yu C; r...@rjwysocki.net; l...@kernel.org
> Cc: linux...@vger.kernel.org; linux-a...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Zhang, Rui
> Subject: RE: [PATCH][v3] ACPI / PM: Fix inc
From: Joerg Roedel
Currently we always write the next_rip of the shadow vmcb to
the guests vmcb when we emulate a vmexit. This could confuse
the guest when its cpuid indicated no support for the
next_rip feature.
Fix this by only propagating next_rip if the guest actually
supports it.
Cc: Banda
Hi Paul,
On Thu, Oct 08, 2015 at 03:17:16PM -0700, Paul E. McKenney wrote:
> On Thu, Oct 08, 2015 at 01:59:38PM +0100, Will Deacon wrote:
> > I thought Paul was talking about something like this case:
> >
> > CPU A CPU B CPU C
> > foo = 1
> > UNLOCK x
> > LOCK x
> >
On Tue, Sep 22, 2015 at 04:04:53PM +0530, Vineet Gupta wrote:
> - pgtable-generic.c: Fold individual #ifdef for each helper into a top
> level #ifdef. Makes code more readable
Makes sense.
> - Per Andrew's suggestion removed the dummy implementations for !THP
> in asm-generic/page-table.h to
Hi Thomas,
On 9 okt. 2015, at 11:06, Thomas Gleixner wrote:
On Mon, 5 Oct 2015, Jaccon Bastiaansen wrote:
>> We did some tests with different compilers, kernel versions and kernel
>> configs, with the following results:
> You cannot use an explicit 32bit read. We need an access which handles the
On Thu, 2015-10-08 at 16:41 +0200, Arnd Bergmann wrote:
> On Thursday 08 October 2015 11:27:13 Sjoerd Simons wrote:
> > On Thu, 2015-10-08 at 10:37 +0200, Arnd Bergmann wrote:
> > > On Thursday 08 October 2015 16:46:27 Krzysztof Kozlowski wrote:
> > > > On 08.10.2015 16:41, Arnd Bergmann wrote:
> >
On 08/10/2015 18:27, Lina Iyer wrote:
On Tue, Oct 06 2015 at 08:27 -0600, Marc Titinger wrote:
This patch allows cluster-level C-states to being soaked in as generic
domain power states, in order for the domain governor to chose the most
efficient power state compatible with the device constrain
> From: Xunlei Pang
>
> Currently, get_unbound_pool() uses kzalloc() to allocate the
> worker pool. Actually, we can use the right node to do the
> allocation, achieving local memory access.
>
> This patch selects target node first, and uses kzalloc_node()
> instead.
>
> Signed-off-by: Xunlei P
On 10/08/2015 04:56 PM, Alexandre Belloni wrote:
> struct at91_can_data was used to pass a callback to the driver, allowing it
> to switch the transceiver on and off. As all at91 boards are now using DT,
> this is not used anymore, remove that structure.
One board was obviously not converted prope
On Tue, Sep 22, 2015 at 04:04:54PM +0530, Vineet Gupta wrote:
Commit message: -ENOENT.
Otherwise, looks good:
Acked-by: Kirill A. Shutemov
--
Kirill A. Shutemov
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
Mo
Dear Sirs,
Nice to meet you!
This is Leon from Sayfu Multilayer Circuits Co.,ltd,we are PCB manufacture in
China,From your Website,I think you need
Print Circuit Board,right?We are no MOV for new order,no matter your order how
much?we also accept it.
Can you give me business chance to try us?
Andrew Morton writes:
> On Thu, 08 Oct 2015 11:51:13 +0200 Vitaly Kuznetsov
> wrote:
>
>> > On Wed, 7 Oct 2015 19:02:22 +0200 Vitaly Kuznetsov
>> > wrote:
>> >
>> >> In some cases we may end up killing the CPU holding the console lock
>> >> while still having valuable data in logbuf. E.g. I'
Andrew Morton writes:
> On Thu, 08 Oct 2015 12:03:25 +0200 Vitaly Kuznetsov
> wrote:
>
>> > If we picked up patch "kernel: Avoid softlockups in
>> > stop_machine() during heavy printing" from my series (it's completely
>> > independent, I've attached the latest version), the result would look l
On Fri, Oct 09, 2015 at 03:03:26PM +0530, Vineet Gupta wrote:
> On Thursday 01 October 2015 11:32 AM, Vineet Gupta wrote:
> > On Tuesday 22 September 2015 04:04 PM, Vineet Gupta wrote:
> >> > Hi,
> >> >
> >> > This series brings THP support to ARC. It also introduces an optional new
> >> > thp hoo
Olaf Hering writes:
> On Thu, Oct 08, KY Srinivasan wrote:
>
>> > yes, but after doing fcopy_respond_to_host(). I'd suggest we leave the
>> > check in place, better safe than sorry.
>>
>> Agreed; Olaf, if it is ok with you, I can fix it up and send.
>
> I will retest with this part reverted. I t
On Wed, Oct 07, 2015 at 11:28:18AM -0700, Drew Richardson wrote:
> Add additional information about the ARM architected hardware events
> to make counters self describing. This makes the hardware PMUs easier
> to use as perf list contains possible events instead of users having
> to refer to docume
On 10/08/2015 03:28 PM, Yaowei Bai wrote:
> This patch makes can_dropped_invalid_skb return bool due to this
> particular function only using either one or zero as its return
> value.
>
> No functional change.
>
> Signed-off-by: Yaowei Bai
Acked-by: Marc Kleine-Budde
Yaowei, feel free to send
Hi Thomas,
2015-10-09 9:52 GMT+02:00 Thomas Petazzoni
:
> Dear Marcin Wojtas,
>
> On Fri, 9 Oct 2015 03:03:53 +0200, Marcin Wojtas wrote:
>> The newest revisions of A388-GP (v1.5 and higher) support only
>> DAT3-based card detection. Revisions < v1.5 based on GPIO detection
>> via I2C expander,
2015-10-09 12:48 GMT+03:00 Mark Rutland :
> On Fri, Oct 09, 2015 at 12:32:18PM +0300, Andrey Ryabinin wrote:
> [...]
>
>> I thought the EFI stub isolation patches create a copy of mem*() functions
>> in the stub,
>> but they are just create aliases with __efistub_ prefix.
>>
>> We only need to cre
On 08/10/15 15:27, Stephen Warren wrote:
> On 10/08/2015 03:58 AM, Jon Hunter wrote:
[snip]
>> That's fine. From my perspective I don't have a strong objection either
>> way, however, I can see that given that the name indicates rx or tx,
>> then the direction in the binding could be seen as red
Rename get_device_type() to da9062_get_device_type().
This function is only used in this file so make it static.
Signed-off-by: Axel Lin
---
drivers/mfd/da9062-core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/mfd/da9062-core.c b/drivers/mfd/da9062-core.c
ind
From: Joerg Roedel
The pcibios-irq and MSI both use dev->irq to store the IRQ
number. While the MSI code checks for that and frees the
pcibios-irq before overwriting dev->irq, the
pcibios_alloc_irq function does not.
Usually this is not a problem, as the pcibios-irq is
allocated before probe tim
On Tue, Oct 06, 2015 at 09:13:11PM +0800, Jiang Liu wrote:
> We are on leave for Chinese National Holiday and has limited
> access to my working environment. It would be appreciated if you could
> help to send out a patch for it. Otherwise I will send out a patch
> within 2-3 days.
Okay, I j
On 09/10/2015 10:50, Peter Zijlstra wrote:
> Not having actually read or thought about the issue at hand, its
> perfectly valid to pair an smp_mb() with either spin_lock() or
> spin_unlock().
>
> IOW. MB <-> {ACQUIRE, RELEASE} is a valid pairing.
In this case it's an smp_mb() (store-load barrie
Hans,
On Fri, 9 Oct 2015, Hans Zuidam wrote:
> On 9 okt. 2015, at 11:06, Thomas Gleixner wrote:
> > You cannot use an explicit 32bit read. We need an access which
> > handles the fault gracefully.
>
> The reason for the explicit read suggestion is to avoid the
> _builtin_constant_p() in __copy_fr
On Fri, 9 Oct 2015, Joerg Roedel wrote:
> From: Joerg Roedel
>
> The pcibios-irq and MSI both use dev->irq to store the IRQ
> number. While the MSI code checks for that and frees the
> pcibios-irq before overwriting dev->irq, the
> pcibios_alloc_irq function does not.
>
> Usually this is not a p
On 09/10/2015 11:04, Kosuke Tatsukawa wrote:
> smp_store_mb() called from set_current_state(), which is called from
> prepare_to_wait() should prevent reordering such as below from
> happening. wait_event*() also calls set_current_state() inside.
Ah, I missed that set_current_state has a memory
On Friday 09 October 2015 11:59:05 Sjoerd Simons wrote:
>
> > I realize that building things as modules is a hassle, it is so for
> > some things more than for others, so I keep asking the question
> > to everyone to find out what a good balance is to make as much as
> > possible modules without h
MINSIGSTKSZ and SIGSTKSZ for ARM64 are not correctly set in latest kernel.
This patch fixes this issue.
This issue is reported in LTP (testcase: sigaltstack02.c).
Testcase failed when sigaltstack() called with stack size "MINSIGSTKSZ - 1"
Since in Glibc-2.22, MINSIGSTKSZ is set to 5120 but in kern
On Fri, Oct 09, 2015 at 03:59:40PM +0530, Manjeet Pawar wrote:
> MINSIGSTKSZ and SIGSTKSZ for ARM64 are not correctly set in latest kernel.
> This patch fixes this issue.
>
> This issue is reported in LTP (testcase: sigaltstack02.c).
> Testcase failed when sigaltstack() called with stack size "MIN
On Fri, Oct 09, 2015 at 10:46:16AM +0100, Thomas Gleixner wrote:
> On Thu, 8 Oct 2015, Miroslav Lichvar wrote:
> > Applications are not allowed to rely on system time being sane?
> > To me the current behavior looks like the kernel is throwing the
> > applications off a cliff, while it's the only t
I started multiple docker containers in centos6.6(linux-2.6.32-504.16.2),
and there's one bad program was running in one container.
This program produced many child threads continuously without free, so more and
more pid numbers were consumed by this program, until hitting the pix_max limit
(32768
On 2015/10/9 17:24, Kamezawa Hiroyuki wrote:
> On 2015/10/09 15:46, Xishi Qiu wrote:
>> On 2015/10/9 22:56, Taku Izumi wrote:
>>
>>> Xeon E7 v3 based systems supports Address Range Mirroring
>>> and UEFI BIOS complied with UEFI spec 2.5 can notify which
>>> ranges are reliable (mirrored) via EFI m
On Tue, 6 Oct 2015, Felipe Balbi wrote:
> this commit causes a performance regression for the USB driver on
> several platforms (anybody using drivers/usb/dwc3, basically).
>
> Here's the USB throughput with linux-next in 3 different scenarios:
>
> 1) Linux next without threadirqs cmdline
>
>
On Fri, 9 Oct 2015, Miroslav Lichvar wrote:
> On Fri, Oct 09, 2015 at 10:46:16AM +0100, Thomas Gleixner wrote:
> > On Thu, 8 Oct 2015, Miroslav Lichvar wrote:
> > > Applications are not allowed to rely on system time being sane?
> > > To me the current behavior looks like the kernel is throwing the
pcnet32 can't work on my machine recently. It says "architecture
does not support 32bit PCI busmaster DMA". There is a logic error
in it: pci_set_dma_mask() return 0 means return successfully.
Signed-off-by: Geliang Tang
---
drivers/net/ethernet/amd/pcnet32.c | 2 +-
1 file changed, 1 insertion(
W dniu 09.10.2015 o 19:28, Arnd Bergmann pisze:
> On Friday 09 October 2015 11:59:05 Sjoerd Simons wrote:
>>
>>> I realize that building things as modules is a hassle, it is so for
>>> some things more than for others, so I keep asking the question
>>> to everyone to find out what a good balance is
On Fri, Oct 09, 2015 at 12:38:32PM +0200, Thomas Gleixner wrote:
> On Fri, 9 Oct 2015, Miroslav Lichvar wrote:
> > Do you feel the same about preventing the time from reaching
> > KTIME_MAX?
>
> That's going to happen in ~500 years from now.
At any time if you include accidents and attacks on ser
On 09/10/2015 at 12:07:40 +0200, Marc Kleine-Budde wrote :
> On 10/08/2015 04:56 PM, Alexandre Belloni wrote:
> > struct at91_can_data was used to pass a callback to the driver, allowing it
> > to switch the transceiver on and off. As all at91 boards are now using DT,
> > this is not used anymore,
On Friday 09 October 2015 11:33:52 Will Deacon wrote:
> Acked-by: Will Deacon
>
> Arnd: are you planning to take this via asm-generic, or shall I queue it
> on the arm64 fixes branch?
>
Please merge it for arm64 with my
Acked-by: Arnd Bergmann
Arnd
--
To unsubscribe from this list:
Hi Krzysztof,
On 9 October 2015 at 16:17, Krzysztof Kozlowski wrote:
> W dniu 09.10.2015 o 19:28, Arnd Bergmann pisze:
>> On Friday 09 October 2015 11:59:05 Sjoerd Simons wrote:
>>>
I realize that building things as modules is a hassle, it is so for
some things more than for others, so
On 08/10/15 10:55, Suzuki K. Poulose wrote:
On 07/10/15 18:16, Catalin Marinas wrote:
On Mon, Oct 05, 2015 at 06:01:56PM +0100, Suzuki K. Poulose wrote:
diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
index 1ae8b24..d42ad90 100644
--- a/arch/arm64/kernel/cpufeature.
>> MINSIGSTKSZ and SIGSTKSZ for ARM64 are not correctly set in latest kernel.
>> This patch fixes this issue.
>>
>> This issue is reported in LTP (testcase: sigaltstack02.c).
>> Testcase failed when sigaltstack() called with stack size "MINSIGSTKSZ - 1"
>> Since in Glibc-2.22, MINSIGSTKSZ is set t
W dniu 09.10.2015 o 01:45, Alim Akhtar pisze:
> Hello,
>
> On Thu, Oct 8, 2015 at 11:04 AM, Krzysztof Kozlowski
> wrote:
>> During probe if the regulator could not be enabled, the error exit path
>> would still disable it. This could lead to unbalanced counter of
>> regulator enable/disable.
>>
>
Hi
This would desperately neeed Tested-by's (with Haswell PTT).
/Jarkko
On Tue, Sep 15, 2015 at 08:05:40PM +0300, Jarkko Sakkinen wrote:
> The command buffer address must be read with exactly two 32-bit reads.
> Otherwise, on some HW platforms, it seems that HW will abort the read
> operation, w
On 08/10/2015 20:23, Radim Krčmář wrote:
> v2:
> * rewritten [1/2] and
> * refactored [2/2], all thanks to Paolo's comments
>
> This problem is not fixed for split userspace part as I think that it
> would be better to solve that by excluding edge interrupts from
> eoi_exit_bitmap (see the nex
This would need Tested-by's. I've run it both with dTPM 2.0 and fTPM
based platforms. It would require testing with TPM 1.2 chip to make
sure it doesn't break anything. Thank you.
/Jarkko
On Tue, Sep 29, 2015 at 10:36:32AM +0300, Jarkko Sakkinen wrote:
> Moved PPI attributes to the character devi
On Fri, Oct 09, 2015 at 10:40:39AM +0100, Will Deacon wrote:
> Stepping back a second, I believe that there are three cases:
>
>
> RELEASE X -> ACQUIRE Y (same CPU)
>* Needs a barrier on TSO architectures for full ordering
+PPC
> UNLOCK X -> LOCK Y (same CPU)
>* Needs a barrier
On 08/10/2015 20:34, Radim Krčmář wrote:
> 2015-10-08 20:30+0200, Radim Krčmář:
>> On real hardware, edge-triggered interrupts don't set a bit in TMR,
>> which means that IOAPIC isn't notified on EOI. Do the same here.
>>
>> Staying in guest/kernel mode after edge EOI is what we want for most
>>
> -Original Message-
> From: linux-input-ow...@vger.kernel.org
> [mailto:linux-input-ow...@vger.kernel.org] On Behalf Of Arnd Bergmann
> Sent: 08 October, 2015 17:32
> To: Tirdea, Irina
> Cc: Dmitry Torokhov; Bastien Nocera; Aleksei Mamlin;
> linux-in...@vger.kernel.org; Mark Rutland; P
Hello Will,
Thank you so much for your patience. My sincere apologies with the issues with
formatting. I have taken care of them and hope now things are ok.
- Included patchesATarm.linux.org.uk.
- Removed the changelog from commit message.
- Moved the patch to "superseded" in patch system.
- Corr
From: Colin Ian King
Static analysis with cppcheck found the following memory leak:
[drivers/staging/wilc1000/linux_mon.c:255]: (error) Memory leak: mgmt_tx
Free mgmt_tx on the error return path when mgmt_tx->buff fails to be
allocated.
Signed-off-by: Colin Ian King
---
drivers/staging/wilc1
On Fri, Oct 09, 2015 at 10:40:39AM +0100, Will Deacon wrote:
> > Which leads me to think I would like to suggest alternative rules for
> > RELEASE/ACQUIRE (to replace those Will suggested; as I think those are
> > partly responsible for my confusion).
>
> Yeah, sorry. I originally used the phrase
On Fri, Oct 09, 2015 at 10:40:39AM +0100, Will Deacon wrote:
>
> > - RELEASE -> ACQUIRE _chains_ (on shared variables) preserve causality,
> >(because each link is fully ordered) but are not transitive.
>
> Yup, and that's the same for UNLOCK -> LOCK, too.
Agreed, except RELEASE/ACQUIRE is
On 09/10/2015 11:51, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Currently we always write the next_rip of the shadow vmcb to
> the guests vmcb when we emulate a vmexit. This could confuse
> the guest when its cpuid indicated no support for the
> next_rip feature.
>
> Fix this by only propaga
On Fri 2015-10-09 10:08:12, Jacek Anaszewski wrote:
> On 10/09/2015 09:02 AM, Pavel Machek wrote:
> >On Fri 2015-10-09 08:28:44, Jacek Anaszewski wrote:
> >>On 10/08/2015 05:50 PM, Pavel Machek wrote:
> >>>On Mon 2015-09-21 16:29:26, Jacek Anaszewski wrote:
> This patch removes SET_BRIGHTNESS_A
On Fri 2015-10-09 10:19:48, Jacek Anaszewski wrote:
> On 10/08/2015 05:51 PM, Pavel Machek wrote:
> >On Mon 2015-09-28 17:13:39, Jacek Anaszewski wrote:
> >>This patch isn't going to be applied since it can cause
> >>legal implications for existing users.
> >>
> >
> >Are there any? Best do this ASA
On 08/10/2015 06:43, Wu, Feng wrote:
> Hi Thomas & Paolo,
>
> What is your option about this patch, Thanks a lot!
>
> Thanks,
> Feng
>
>>> diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
>>> index 1c58655..90b378d 100644
>>> --- a/kernel/irq/manage.c
>>> +++ b/kernel/irq/manage.c
>>> @@
Chevrolet auto mobile company selected your email for the electronic
Balloting. 900,000.00 USD was issued to you as winner send name,address and
mobile for claim: chev.cla...@yandex.com
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
--
On Thu, 8 Oct 2015, Andy Lutomirski wrote:
> Will this really end up working? I can see two problems:
>
> 1. It's rather expensive. For processes that still make syscalls but
> just not many, it means that you're forcibly quiescing every time.
A process that does a lot of syscalls to networking
On Fri, Oct 09, 2015 at 10:51:29AM +0100, Will Deacon wrote:
> > The corresponding litmus tests are below.
>
> How do people feel about including these in memory-barriers.txt? I find
> them considerably easier to read than our current kernel code + list of
> possible orderings + wall of text, but
On 2015/10/7 22:32, Vinod Koul wrote:
On Tue, Oct 06, 2015 at 05:21:13PM +0800, Shawn Lin wrote:
+ int (*device_get_quirks)(struct dma_chan *chan);
And why do we want to expose this to users? THis doesnt seem right!
Basically I agree not to expose dma's quirk to slave controllers...B
Comedi subdevices that support asynchronous acquisition commands have a
wait queue head used for blocking reads or writes and for the poll file
operation. The comedi device may have several subdevices that support
"read" and/or "write" commands, but each open file object has at most
one "read" sub
The main mutex in a comedi device can get held for quite a while when
processing comedi instructions, so for performance reasons, the "read"
and "write" file operations do not use it; they use use the
`attach_lock` rwsemaphore to protect against the comedi device becoming
detached at an inopportune
Add a new function `comedi_buf_write_n_available()` to return the amount
of buffer space available for writing, including space already allocated
by `comedi_buf_write_alloc()` plus any unallocated space available.
This is currently just for internal use by the comedi core, so is not
exported.
Sign
Rename the local function `comedi_buf_write_n_available()` to
`comedi_buf_write_n_unalloc()`. It is the amount of unallocated space
available in the buffer that is available to be allocated for writing
and does not include the space that has already been allocated for
writing. This is unlike the
Currently, the "poll" file operation checks if an asynchronous "read"
(or "write" command is active on the "read" (or "write" subdevice, but
does not consider whether the command was started from the file object
being polled. Since that is the only file object able to read (or
write) data, take it
When handling the "poll" file operation and checking for `POLLOUT`,
don't allocate space from the buffer for writing, just check that space
is available for writing. That check is done after checking that an
asynchronous "write" command is running on the subdevice. Allocating
the buffer space bef
A few changes for the "poll" file operation to avoid poll-waiting on the
same subdevice for both read and write (patch 1), avoid allocating write
buffer space unnecessarily and possibly inappropriately (patch 4),
consider whether any active commands belong to the current file object
(patch 5), and
101 - 200 of 790 matches
Mail list logo
