Hello Fam Zheng,
On 02/05/2015 02:52 AM, Fam Zheng wrote:
> On Wed, 02/04 13:44, Michael Kerrisk (man-pages) wrote:
>> Hello Fam Zheng,
>>
>> On 02/04/2015 11:36 AM, Fam Zheng wrote:
>>> Changes from v1 (https://lkml.org/lkml/2015/1/20/189):
>>>
>>> - As discussed in previous thread [1], split t
On śro, 2015-02-04 at 09:57 -0800, Paul E. McKenney wrote:
> On Wed, Feb 04, 2015 at 05:53:55PM +0100, Krzysztof Kozlowski wrote:
> > The complete() should not be used on offlined CPU. Rewrite the
> > wait-complete mechanism with wait_on_bit_timeout().
> >
> > The CPU triggering hot unplug (e.g. C
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Tuesday, February 03, 2015 6:51 AM
> To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 1/2] f2fs: keep PagePriv
On 02/04/2015 10:53 PM, Andy Lutomirski wrote:
> The lm bit should never have existed in the first place. Sigh.
Thanks, Andy. Applied in the branch.
Cheers,
Michael
> Signed-off-by: Andy Lutomirski
> ---
> man2/modify_ldt.2 | 13 +++--
> 1 file changed, 11 insertions(+), 2 deletions
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Tuesday, February 03, 2015 6:51 AM
> To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net
> Cc: Jaegeuk Kim
> Subject: [f2fs-dev] [PATCH 2/2] f2fs: show the numb
On śro, 2015-02-04 at 14:42 -0800, Stephen Boyd wrote:
> On 02/04/15 08:53, Krzysztof Kozlowski wrote:
> > The complete() should not be used on offlined CPU. Rewrite the
> > wait-complete mechanism with wait_on_bit_timeout().
> >
> > The CPU triggering hot unplug (e.g. CPU0) will loop until some bi
[CC += linux-api@]
Hello Alexander,
The kernel source file Documentation/SubmitChecklist notes that all
Linux kernel patches that change userspace interfaces should be CCed
to linux-...@vger.kernel.org. See also
https://www.kernel.org/doc/man-pages/linux-api-ml.html. Please CC
linux-api@ on futur
[CC += linux-api@]
On Mon, Feb 2, 2015 at 6:05 PM, Alexander Holler wrote:
> Signed-off-by: Alexander Holler
> ---
> arch/x86/syscalls/syscall_32.tbl | 1 +
> arch/x86/syscalls/syscall_64.tbl | 1 +
> fs/namei.c| 38
> ++-
From: Ian Munsie
If an AFU claims to have a configuration record but doesn't actually
contain a vendor and device ID, fail the AFU initialisation. Right now
this is just a way of politely letting AFU developers know that they
need to fix their config space, but later on we may expose the AFUs as
From: Ian Munsie
An AFU may optionally contain one or more PCIe like configuration
records, which can be used to identify the AFU.
This patch adds support for exposing the raw config space and the
vendor, device and class code under sysfs. These will appear in a
subdirectory of the AFU device co
From: Ian Munsie
We were missing a return statement in the PSL interrupt handler in the
case of an AFU error, which would trigger an "Unhandled CXL PSL IRQ"
warning. We do actually handle these type of errors (by notifying
userspace), so add the missing return IRQ_HANDLED so we don't throw
uneces
This is only an API consolidation and should make things more readable
it replaces var * HZ / 1000 by msecs_to_jiffies(var).
Signed-off-by: Nicholas Mc Guire
---
Converting milliseconds to jiffies by "val * HZ / 1000" is technically
ok but msecs_to_jiffies(val) is the cleaner solution and handle
This is only an API consolidation and should make things more readable
it replaces var * HZ / 1000 by msecs_to_jiffies(var).
Signed-off-by: Nicholas Mc Guire
---
Converting milliseconds to jiffies by "val * HZ / 1000" is technically
ok but msecs_to_jiffies(val) is the cleaner solution and handle
This is only an API consolidation and should make things more readable
it replaces var * HZ / 1000 by msecs_to_jiffies(var).
Signed-off-by: Nicholas Mc Guire
---
Converting milliseconds to jiffies by "val * HZ / 1000" is technically
ok but msecs_to_jiffies(val) is the cleaner solution and handle
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Wednesday, February 4, 2015 1:01 AM
> To: KY Srinivasan; de...@linuxdriverproject.org
> Cc: Haiyang Zhang; linux-kernel@vger.kernel.org; Dexuan Cui; Jason Wang
> Subject: [PATCH 1/4] Drivers: hv: vmbus: imple
On 01/13/2015 03:52 PM, Anshuman Khandual wrote:
> This patch series has patches for POWER DSCR fixes, improvements,
> in code documentaion, kernel support user documentation and selftest based
> test cases. It has got five test cases which are derived from Anton's DSCR
> test bucket which ca
On Wed, Feb 4, 2015 at 3:10 AM, Chao Xie wrote:
> At 2015-02-03 21:21:43, "Linus Walleij" wrote:
>>Since this looks like a basic MMIO driver I think
>>you should also use:
>>
>>select GPIO_GENERIC
>>
>
> I think the gpio-mmp is not same as gpio-generic.
> gpio-mmp need control the level/directio
The Altera mailbox allows for interprocessor communication. It supports
only one channel and work as either sender or receiver.
Signed-off-by: Ley Foon Tan
---
v3:
- s/readl/readl_relaxed and s/writel/writel_relaxed
- Change polling interval to 5ms
- Change to use polling mode if request_irq()
Some PCI device drivers assume that pci_dev->irq won't change after
calling pci_disable_device() and pci_enable_device() during suspend and
resume.
Commit c03b3b0738a5 ("x86, irq, mpparse: Release IOAPIC pin when
PCI device is disabled") frees PCI IRQ resources when pci_disable_device()
is called
Hi all,
The next release I will be making will be next-20150209 - which will
probably be after the v3.19 release.
Changes since 20150203:
The sound-asoc tree gained a conflict against the sound tree.
The scsi tree gained a build failure caused by an interaction with the
driver-core tree. I app
On 02/04/2015 01:51 PM, Anshuman Khandual wrote:
> On 01/13/2015 03:52 PM, Anshuman Khandual wrote:
>> >This patch series has patches for POWER DSCR fixes, improvements,
>> > in code documentaion, kernel support user documentation and selftest based
>> > test cases. It has got five test cases w
On Tue, Jan 27, 2015 at 9:31 PM, Laurent Pinchart
wrote:
> The "function", "pins" and "groups" pinmux and pinctrl properties have
> been standardized. Support them in addition to the custom "renesas,*"
> properties. New-style and old-style properties can't be mixed in DT.
>
> Signed-off-by: Laure
On Thu, Jan 29, 2015 at 11:12 AM, Geert Uytterhoeven
wrote:
> Signed-off-by: Geert Uytterhoeven
> Fixes: 1e7d5d849cf4f0c5 ("sh-pfc: Add emev2 pinmux support")
> ---
> Looks like the original UTF-8 was interpreted as ISO-8859-1, and the
> resulting characters being converted to UTF-8 again.
>
> B
Hi Sebastian,
On Tue, Feb 03, 2015 at 11:26:46PM +0100, Sebastian Hesselbarth wrote:
> On 03.02.2015 13:54, Arnd Bergmann wrote:
> >On Tuesday 03 February 2015 12:28:52 Antoine Tenart wrote:
> >>Marvell Berlin SoCs did not have a custom defconfig and were only
> >>supported in multi_v7_defconfig.
On Thu, Jan 29, 2015 at 11:44 AM, Mika Westerberg
wrote:
> If the pin is in HiZ mode when it is requested as GPIO its value cannot be
> read (it always returns 0). In order to cope with the Linux GPIO subsystem
> where we do not have such state at all, turn the pin to be input instead.
>
> Report
Hi Linus,
On Wed, Feb 4, 2015 at 9:54 AM, Linus Walleij wrote:
> On Thu, Jan 29, 2015 at 11:12 AM, Geert Uytterhoeven
> wrote:
>
>> Signed-off-by: Geert Uytterhoeven
>> Fixes: 1e7d5d849cf4f0c5 ("sh-pfc: Add emev2 pinmux support")
>> ---
>> Looks like the original UTF-8 was interpreted as ISO-88
On Sun, 2015-01-25 at 14:07 -0800, Greg Kroah-Hartman wrote:
> On Sun, Jan 25, 2015 at 08:12:54PM +, Mark Brown wrote:
> > On Sun, Jan 25, 2015 at 09:38:53AM -0800, Greg Kroah-Hartman wrote:
> > > On Fri, Jan 23, 2015 at 12:45:29PM +, Mark Brown wrote:
> >
> > > > So, I now see this has ac
On 2015年02月03日 21:53, Mark Rutland wrote:
On Mon, Feb 02, 2015 at 12:45:41PM +, Hanjun Guo wrote:
MADT contains the information for MPIDR which is essential for
SMP initialization, parse the GIC cpu interface structures to
get the MPIDR value and map it to cpu_logical_map(), and add
enabled
On 2015年02月03日 22:55, Rafael J. Wysocki wrote:
On Tuesday, February 03, 2015 09:30:00 PM Hanjun Guo wrote:
On 2015年02月03日 20:15, Catalin Marinas wrote:
On Mon, Feb 02, 2015 at 12:45:34PM +, Hanjun Guo wrote:
diff --git a/arch/arm64/kernel/pci.c b/arch/arm64/kernel/pci.c
index ce5836c..c17e
update_curr_dl() needs actual rq clock.
Signed-off-by: Kirill Tkhai
---
kernel/sched/deadline.c |1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
index e7b2722..f4dbedd 100644
--- a/kernel/sched/deadline.c
+++ b/kernel/sched/deadline.c
@@ -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015/1/29 0:30, Ben Hutchings wrote:
> On Wed, 2015-01-28 at 12:07 +0800, l...@kernel.org wrote:
>> From: Zefan Li
>>
>> This is the start of the stable review cycle for the 3.4.106 release.
>> There are 177 patches in this series, all will be post
I'm announcing the release of the 3.4.106 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015/1/29 0:30, Ben Hutchings wrote:
> On Wed, 2015-01-28 at 12:07 +0800, l...@kernel.org wrote:
>> From: Zefan Li
>>
>> This is the start of the stable review cycle for the 3.4.106 release.
>> There are 177 patches in this series, all will be post
On 02/03/2015 05:35 PM, Stephen Warren wrote:
> On 02/03/2015 06:13 AM, Tomeu Vizoso wrote:
>> On 2 February 2015 at 22:08, Stephen Warren wrote:
>>> On 01/28/2015 03:50 AM, Tomeu Vizoso wrote:
Patches are on its way to add a config file to alsaucm for the Nyan
boards. Use the same
On Wed, Feb 4, 2015 at 1:00 AM, Vitaly Kuznetsov
wrote:
free_channel() function frees the channel unconditionally so we need
to make
sure nobody has any link to it. This is not trivial and there are
several
examples of races we have:
1) In vmbus_onoffer_rescind() we check for channel exist
Hi Brian,
On Mon, Jan 26, 2015 at 03:56:03PM +0100, Maxime Ripard wrote:
> The NDDB register holds the data that are needed by the read and write
> commands.
>
> However, during a read PIO access, the datasheet specifies that after each 32
> bits read in that register, when BCH is enabled, we hav
This change addresses following problem:
[2.560726] [ cut here ]
[2.565341] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:2744
lockdep_trace_alloc+0xec/0x118()
[2.574439] DEBUG_LOCKS_WARN_ON(irqs_disabled_flags(flags))
[2.579821] Modules linked in:
[
Le 02/02/2015 16:43, Nicholas Mc Guire a écrit :
> return type of wait_for_completion_timeout is unsigned long not int, this
> patch adds an appropriate variable and fixes up the assignment. It removes
> the else branch as the only thing it was doing is assigning ret = 0; - but
> ret is never use
On Thu, Jan 29, 2015 at 6:23 PM, Sören Brinkmann
wrote:
> On Mon, 2015-01-19 at 09:54AM +0100, Linus Walleij wrote:
>> On Mon, Jan 19, 2015 at 5:20 AM, Alexandre Courbot wrote:
>> > On Sat, Jan 17, 2015 at 1:49 AM, Sören Brinkmann
>> > wrote:
>> >> On Fri, 2015-01-16 at 12:11PM +0100, Johan Hov
Dexuan Cui writes:
>> -Original Message-
>> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
>> Sent: Wednesday, February 4, 2015 1:01 AM
>> To: KY Srinivasan; de...@linuxdriverproject.org
>> Cc: Haiyang Zhang; linux-kernel@vger.kernel.org; Dexuan Cui; Jason Wang
>> Subject: [PATCH 1/4
В Tue, 3 Feb 2015 11:38:35 -0800
Dmitry Torokhov пишет:
> On Tue, Feb 03, 2015 at 12:48:49AM +0300, Roman Volkov wrote:
> > Use platform_device_probe() instead of platform_create_bundle() when
> > compiled with DT support, since the latter function is not suitable
> > for handling the OF device t
The if and the else branch code are identical - so the condition has no
effect on the effective code - this patch removes the condition and the
duplicated code.
Signed-off-by: Nicholas Mc Guire
---
The conditions in the OMAP_ECC_BCH8_CODE_HW_DETECTION_SW and
OMAP_ECC_BCH4_CODE_HW_DETECTION_SW ca
Jason Wang writes:
> On Wed, Feb 4, 2015 at 1:00 AM, Vitaly Kuznetsov
> wrote:
>> free_channel() function frees the channel unconditionally so we need
>> to make
>> sure nobody has any link to it. This is not trivial and there are
>> several
>> examples of races we have:
>>
>> 1) In vmbus_onoffe
On 2015年02月04日 01:20, Catalin Marinas wrote:
On Mon, Feb 02, 2015 at 12:45:37PM +, Hanjun Guo wrote:
diff --git a/arch/arm64/kernel/acpi.c b/arch/arm64/kernel/acpi.c
index afe10b4..b9f64ec 100644
--- a/arch/arm64/kernel/acpi.c
+++ b/arch/arm64/kernel/acpi.c
@@ -13,6 +13,8 @@
* published
Hi Vinod,
Can you please review this patch set.
Thanks,
with regards,
Ram
On Tue, Feb 3, 2015 at 6:25 PM, Rameshwar Prasad Sahu wrote:
> This patch set implements the APM X-Gene SoC DMA driver
> support to offload the DMA operations such as memory copy(memcpy),
> scatter gathering.
>
> v5 cha
On 2015年02月04日 01:43, Al Stone wrote:
On 02/03/2015 09:47 AM, Mark Rutland wrote:
On Mon, Feb 02, 2015 at 12:45:28PM +, Hanjun Guo wrote:
Hi,
This is the v8 of ACPI core patches for ARM64 based on ACPI 5.1, there are
some updates since v7:
- Add two more documantation to explain why we
On 2015年02月04日 04:09, Catalin Marinas wrote:
On Tue, Feb 03, 2015 at 02:17:49PM +, Mark Rutland wrote:
On Mon, Feb 02, 2015 at 12:45:42PM +, Hanjun Guo wrote:
Introduce a new function map_gicc_mpidr() to allow MPIDRs to be obtained
from the GICC Structure introduced by ACPI 5.1.
MPIDR
Now kprobe status have four flags, so kprobes.txt
should reflect all of them.
Signed-off-by: Wang Long
---
Documentation/kprobes.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/kprobes.txt b/Documentation/kprobes.txt
index 4227ec2..1488b65 100644
--- a/Doc
__FUNCTION__ hasn't been treated as a string literal since gcc 3.4, so
this only helps people who only test-compile using 3.3
(compiler-gcc3.h barks at anything older than that). Besides, there
are almost no occurrences of __FUNCTION__ left in the tree.
Signed-off-by: Rasmus Villemoes
---
includ
Hi,
On 04/02/15 07:13, Oleg Drokin wrote:
Hello!
On Feb 3, 2015, at 5:33 PM, Dave Chinner wrote:
I also wonder if vmalloc is still very slow? That was the case some
time ago when I noticed a problem in directory access times in gfs2,
which made us change to use kmalloc with a vmalloc fallback
Since you mentioned problem does not happen on Windows, what do you use
to emulate the workload (iometer ?)
CrystalDiskMark, HD Tune, ATTO Disk Benchmark
Tested for 2-3 hours, but got stable results. Directly afterwards booted
Live CD with Linux and immediately got poor results.
and did you
On Fri, Jan 30, 2015 at 5:17 PM, Rafael J. Wysocki wrote:
> On Friday, January 30, 2015 03:48:30 PM Linus Walleij wrote:
>> So you could detect one by making a checksum of the binary or something.
>>
>> And then you'd know that the table with this checksum needs patching?
>
> At a single table le
Hi.
Tested-by: Jaehoon Chung
(with exynos4 board)
Acked-by: Jaehoon Chung
Best Regards,
Jaehoon Chung
On 02/04/2015 06:16 PM, Paul Osmialowski wrote:
> This change addresses following problem:
>
> [2.560726] [ cut here ]
> [2.565341] WARNING: CPU: 0 PID: 1 at k
Hi Linus,
On Wednesday 04 February 2015 09:40:48 Linus Walleij wrote:
> On Tue, Jan 27, 2015 at 9:31 PM, Laurent Pinchart wrote:
> > The "function", "pins" and "groups" pinmux and pinctrl properties have
> > been standardized. Support them in addition to the custom "renesas,*"
> > properties. New-
>> The meta_delete() function could be called in four cases by the
>> em_meta_change() function during error handling even if the passed
>> variable "meta" contained still a null pointer.
>>
>> * This implementation detail could be improved by adjustments for jump
>> labels.
>>
>> * Let us return
On Wed, 2015-02-04 at 04:52 +, Vineet Gupta wrote:
> On Wednesday 04 February 2015 01:46 AM, Paul Bolle wrote:
> > Mischa's address bounced. It was used last week! What's going on?
>
> sorry folks, snafu on my part.
>
> Mischa left SNPS about an year ago.
Now I notice the commit is actually
On 02/03/15 18:13, Pablo Anton wrote:
> It is confusing which parts of the driver are adv7604 specific, adv7611
> specific or common for both.
> This patch renames any adv7604 prefixes (both for functions and defines) to
> adv76xx whenever they are common.
>
> Signed-off-by: Pablo Anton
> Signe
Hi,
I hit WARNING below after update to 3.19-rc6, when I running fio with libaio.
Any one see this warning before, or maybe know how to fix it?
>From the call trace:
(gdb) list *read_events+0x1e8
0x81225ad8 is in read_events (fs/aio.c:1259).
1254 * something to be aware of when to
On Fri, Jan 30, 2015 at 5:20 PM, Bjorn Andersson
wrote:
> On Fri 30 Jan 02:27 PST 2015, Stanimir Varbanov wrote:
>
>> + case PIN_CONFIG_INPUT_ENABLE:
>> + /* Pin is output */
>> + if (arg)
>> + return -EINVAL;
>> + arg = 1;
>> +
Hi Hans, and thanks for reviewing.
2015-02-04 10:55 GMT+01:00 Hans Verkuil :
> On 02/03/15 18:13, Pablo Anton wrote:
>> It is confusing which parts of the driver are adv7604 specific, adv7611
>> specific or common for both.
>> This patch renames any adv7604 prefixes (both for functions and define
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Wednesday, February 4, 2015 17:32 PM
> To: Dexuan Cui
> Cc: KY Srinivasan; de...@linuxdriverproject.org; Haiyang Zhang; linux-
> ker...@vger.kernel.org; Jason Wang
> Subject: Re: [PATCH 1/4] Drivers: hv: vmbu
Hi Maxime,
On Mon, 26 Jan 2015 15:56:03 +0100
Maxime Ripard wrote:
> The NDDB register holds the data that are needed by the read and write
> commands.
>
> However, during a read PIO access, the datasheet specifies that after each 32
> bits read in that register, when BCH is enabled, we have to
John Crispin's commit 576c618cf659 ("watchdog: add MT7621 watchdog
support") was included in today's linux-next (ie, next 20150204). I
noticed because a script I use to check linux-next spotted a problem
with it.
That commit adds an (optional) dependency on the Kconfig sy
Hi Sifan,
On 03/02/15 17:30, Sifan Naeem wrote:
> Gets a handle to the system clock, already described in the binding
> document, and calls the appropriate common clock
> framework functions to mark it prepared/enabled, the common clock
> framework initially enables the clock and doesn't disable i
Am 04.02.2015 um 00:33 schrieb Al Viro:
On Tue, Feb 03, 2015 at 07:01:50PM +0100, Alexander Holler wrote:
Yeah, as I've already admitted in the bug, I never should have use
the word secure, because everyone nowadays seems to end up in panic
when reading that word.
So, if I would be able to use
On Tue, Feb 03, 2015 at 04:24:55PM -0700, Jens Axboe wrote:
>
> Yes, from a cursory look, that seems fine to me. Though I will hold the fact
> that you label my code as 'seriously obtuse' against you. Some day.
Hehe, fair enough. I'm sure I've written my fair share of it too, we've
all got our 'b
On 04/02/2015 11:13, Paul Bolle wrote:
> messages. Since I haven't received replies on other, more serious
> issues in over three months I assume John has disappeared.)
into thin air, *pooff*
> Is SOC_MT7621 still being worked on?
yes we dropped the series as it collided with the gic rework th
Hi, Boris
Thanks a lot for your explanation, check my reply for more description
for my suggestion.
On 2/3/2015 5:37 PM, Boris Brezillon wrote:
On Tue, 3 Feb 2015 16:46:15 +0800
Josh Wu wrote:
Hi, Boris, Brian
On 2/2/2015 5:42 PM, Boris Brezillon wrote:
Hi Brian,
On Sun, 1 Feb 2015 23:5
On Wednesday 04 February 2015 09:54:04 Antoine Tenart wrote:
> Hi Sebastian,
>
> On Tue, Feb 03, 2015 at 11:26:46PM +0100, Sebastian Hesselbarth wrote:
> > On 03.02.2015 13:54, Arnd Bergmann wrote:
> > >On Tuesday 03 February 2015 12:28:52 Antoine Tenart wrote:
> > >>Marvell Berlin SoCs did not ha
On Tue 03-02-15 14:44:31, Eric W. Biederman wrote:
> Michal Hocko writes:
>
> > On Tue 03-02-15 16:33:03, Michael Kerrisk wrote:
> >> Hi Michal,
> >>
> >>
> >> On 3 February 2015 at 16:05, Michal Hocko wrote:
> >> > Hi,
> >> > while debugging an unexpected ENOMEM from fork (there was no memory
The Exynos cpuidle driver has coupled cpuidle built-in so it cannot be
built without SMP:
arch/arm/mach-exynos/pm.c: In function ‘exynos_cpu0_enter_aftr’:
arch/arm/mach-exynos/pm.c:246:4: error: implicit declaration of function
‘arch_send_wakeup_ipi_mask’ [-Werror=implicit-function-declaration]
a
On Tue, 3 Feb 2015, Josh Poimboeuf wrote:
> Rename CONFIG_LIVE_PATCHING to CONFIG_LIVEPATCH to make the naming of
> the config and the code more consistent.
>
> Signed-off-by: Josh Poimboeuf
Makes sense. Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line
On Wed, Feb 04, 2015 at 09:05:13AM +, Hanjun Guo wrote:
> On 2015年02月03日 21:53, Mark Rutland wrote:
> > On Mon, Feb 02, 2015 at 12:45:41PM +, Hanjun Guo wrote:
> >> MADT contains the information for MPIDR which is essential for
> >> SMP initialization, parse the GIC cpu interface structures
needs a check by someone who knows the details of the driver
as it could be that the two branches actually should be different.
Patch was only compile-tested for x86_64_defconfig + CONFIG_STAGING=y
CONFIG_R8188EU=m
Patch is against 3.19.0-rc7 (localversion-next is -next-20150204)
drivers/staging
the comments it seems that an effect is actually intended so this
may be a bug.
The comment was updated to reflect the changes
Patch was only compile-tested for x86_64_defconfig + CONFIG_STAGING=y
CONFIG_R8188EU=m
Patch is against 3.19.0-rc7 (localversion-next is -next-20150204)
drivers/stag
On 2015/2/4 18:18, Stefani Seibold wrote:
> The example is intended for int types, not for strings. So it is not a
> bug, it's a feature ;-) But anyway, if you prefer to handle with strings
> your are okay by me.
>
hi,Stefani Seibold
Thanks you for your reply. another question?
This example expo
On Tue, 3 Feb 2015, Daniel Sanders wrote:
> From: Toma Tabacu
>
> Differentiate the 'u' GAS .macro argument from the '\u' C preprocessor unicode
> escape sequence by renaming it to '_u'.
>
> When the 'u' argument is evaluated, we end up writing '\u', which causes
> clang to emit -Wunicode warni
The example is intended for int types, not for strings. So it is not a
bug, it's a feature ;-) But anyway, if you prefer to handle with strings
your are okay by me.
Am Dienstag, den 03.02.2015, 11:51 + schrieb Wang Long:
> echo 99 > /proc/int-fifo > Never return
> echo 1000 >
Changes from v1 (https://lkml.org/lkml/2015/1/20/189):
- As discussed in previous thread [1], split the call to epoll_ctl_batch and
epoll_pwait. [Michael]
- Fix memory leaks. [Omar]
- Add a short comment about the ignored copy_to_user failure. [Omar]
- Cover letter rewritten.
This
In preparation of new epoll syscalls, this patch allows reusing the code from
epoll_pwait implementation. The new functions uses ktime_t for more accuracy.
Signed-off-by: Fam Zheng
---
fs/eventpoll.c | 130 ++---
1 file changed, 59 insertions(+
Later we will add clockid in the interface, so let's start using explicit
clockid internally. Now we specify CLOCK_MONOTONIC, which is the same as before.
Signed-off-by: Fam Zheng
---
fs/eventpoll.c | 27 +++
1 file changed, 15 insertions(+), 12 deletions(-)
diff --git a
Signed-off-by: Fam Zheng
---
arch/x86/syscalls/syscall_32.tbl | 1 +
arch/x86/syscalls/syscall_64.tbl | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/x86/syscalls/syscall_32.tbl b/arch/x86/syscalls/syscall_32.tbl
index b3560ec..fe809f6 100644
--- a/arch/x86/syscalls/syscall_32.tbl
+++
This new syscall is a batched version of epoll_ctl. It will execute each
command as specified in cmds in given order, and stop at first failure
or upon completion of all commands.
Signed-off-by: Fam Zheng
---
fs/eventpoll.c | 48 ++
include
From: Markus Elfring
Date: Wed, 4 Feb 2015 11:28:43 +0100
The release_firmware() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
d
This is the new implementation for poll which uses timespec as timeout,
and has a flags parameter.
Signed-off-by: Fam Zheng
---
fs/eventpoll.c | 34 ++
include/linux/syscalls.h | 5 +
2 files changed, 39 insertions(+)
diff --git a/fs/eventpoll.c b/
This patch was produced using Coccinelle. A simplified version of the
semantic patch is:
@r exists@
identifier f;
local idexpression u8 x;
identifier xname;
@@
f(...) {
...when any
(
x@xname = 1;
|
x@xname = 0;
)
...when any
}
@bad exists@
identifier r.f;
local idexpression u8 r.x
expression
Signed-off-by: Fam Zheng
---
arch/x86/syscalls/syscall_32.tbl | 1 +
arch/x86/syscalls/syscall_64.tbl | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/x86/syscalls/syscall_32.tbl b/arch/x86/syscalls/syscall_32.tbl
index fe809f6..bf912d8 100644
--- a/arch/x86/syscalls/syscall_32.tbl
+++
This is a common part from epoll_ctl implementation which will be shared with
the coming epoll_ctl_wait.
Signed-off-by: Fam Zheng
---
fs/eventpoll.c | 26 ++
1 file changed, 18 insertions(+), 8 deletions(-)
diff --git a/fs/eventpoll.c b/fs/eventpoll.c
index 01f469a..a1c3
(2015/02/04 18:43), Wang Long wrote:
> Now kprobe status have four flags, so kprobes.txt
> should reflect all of them.
Yes, it has been introduced by commit ae6aa16fdc163afe6b04b6c073ad4ddd4663c03b
>
> Signed-off-by: Wang Long
Acked-by: Masami Hiramatsu
Thank you!
> ---
> Documentation/kpr
h local_clock it was used originally in
> the softlockup detector.
>Added #ifdef CONFIG_PPC_PSERIES and optimised the non lpar + vtb cases.
This became commit 3e5aba51e929 ("powerpc: add running_clock for powerpc
to prevent spurious softlockup warnings") in today's linux-n
copy_process will report any failure in alloc_pid as ENOMEM currently
which is misleading because the pid allocation might fail not only when
the memory is short but also when the pid space is consumed already.
The current man page even mentions this case:
"
EAGAIN
A system-imposed limit on
Add missing stubs for regulator_suspend_prepare() and
regulator_suspend_finish() to fix exynos_defconfig build without
REGULATOR:
arch/arm/mach-exynos/built-in.o: In function `exynos_suspend_finish':
arch/arm/mach-exynos/suspend.c:537: undefined reference to
`regulator_suspend_finish'
arch/arm/ma
Hi Josh,
On Wed, 4 Feb 2015 18:06:37 +0800
Josh Wu wrote:
> Hi, Boris
>
> Thanks a lot for your explanation, check my reply for more description
> for my suggestion.
>
> On 2/3/2015 5:37 PM, Boris Brezillon wrote:
> > On Tue, 3 Feb 2015 16:46:15 +0800
> > Josh Wu wrote:
> >
> >> Hi, Boris, B
On Mon, Feb 02, 2015 at 03:05:36PM +0100, Oleg Nesterov wrote:
> attach_to_pi_owner() checks p->mm to prevent attaching to kthreads and
> this looks doubly wrong:
>
> 1. It should actually check PF_KTHREAD, kthread can do use_mm().
>
> 2. If this task is not kthread and it is actually the lock ow
Signed-off-by: Takashi Iwai
---
drivers/edac/i7core_edac.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/edac/i7core_edac.c b/drivers/edac/i7core_edac.c
index 9cd0b301f81b..5da90ded54b6 100644
--- a/drivers/edac/i7core_edac.c
+++ b/drivers/edac/i7core_edac.c
@@ -
... instead of manual device_create_file() and device_remove_file()
calls.
Signed-off-by: Takashi Iwai
---
drivers/edac/highbank_mc_edac.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/edac/highbank_mc_edac.c b/drivers/edac/highbank_mc_edac.c
index f784
On 04.02.2015 02:30, Greg Thelen wrote:
On Mon, Feb 2, 2015 at 11:46 AM, Tejun Heo wrote:
Hey,
On Mon, Feb 02, 2015 at 10:26:44PM +0300, Konstantin Khlebnikov wrote:
Keeping shared inodes in common ancestor is reasonable.
We could schedule asynchronous moving when somebody opens or mmaps
ino
... instead of manual device_create_file() and device_remove_file()
calls.
Signed-off-by: Takashi Iwai
---
drivers/edac/i7core_edac.c | 29 ++---
1 file changed, 10 insertions(+), 19 deletions(-)
diff --git a/drivers/edac/i7core_edac.c b/drivers/edac/i7core_edac.c
index
On Wed, 02/04 18:36, Fam Zheng wrote:
>
>Not that this call isn't atomic in terms of updating the epoll
s/Not/Note/
>descriptor, which means a second epoll_ctl or epoll_ctl_batch call
>during the first epoll_ctl_batch may make the operation sequence
>interleaved.
Instead of manual calls of device_create_file() and
device_remove_file(), use static attribute groups with proper
is_visible callbacks for managing the sysfs entries.
This simplifies the code a lot and avoids the possible races.
Signed-off-by: Takashi Iwai
---
drivers/edac/edac_mc_sysfs.c | 158
701 - 800 of 927 matches
Mail list logo
