On Fri, Apr 17, 2015 at 11:12:03AM +0200, Sebastian Hesselbarth wrote:
> On 17.04.2015 04:00, Michael Welling wrote:
> >On Fri, Apr 17, 2015 at 01:23:50AM +0200, Sebastian Hesselbarth wrote:
> >>On 17.04.2015 00:09, Michael Welling wrote:
> >>>On Thu, Apr 16, 2015 at 10:37:19PM +0200, Sebastian
On 03/23/2015 08:02 AM, Catalin Marinas wrote:
@@ -121,8 +119,7 @@ int copy_siginfo_from_user32(siginfo_t *to, struct
compat_siginfo __user *from)
>
> err |= __get_user(to->si_pid, >si_pid);
>err |= __get_user(to->si_uid, >si_uid);
>- err |= __get_user(ptr32, >si_ptr);
>-
2015-04-17 18:51 GMT+02:00 Marcel Holtmann :
> Hi Joerg,
>
On Fri, Apr 17, 2015 at 5:36 AM, Jörg Otte wrote:
> The BT mouse is "death" in v4.1.
> The BT mouse has been working in 4.0 and previous kernels, so this
> is a regression.
Any chance of bisecting it?
On 04/16/2015 11:44 PM, Christoph Hellwig wrote:
On Thu, Apr 16, 2015 at 04:02:58PM -0700, Mike Kravetz wrote:
Now that we have hole punching support for hugetlbfs, we can
also support the MADV_REMOVE interface to it.
Meh. Just use fallocate for any new code..
I don't have the complete
On Wed, 2015-04-15 at 16:48 +0200, Michal Schmidt wrote:
> On 04/15/2015 09:31 AM, Mike Galbraith wrote:
> > it seems [systemd] has now mandated group scheduling.
>
> What makes you think so? Was it the fact that by default you have a
> populated /sys/fs/cgroup/cpu/ hierarchy? This is either
> -Original Message-
> From: Paul E. McKenney [mailto:paul...@linux.vnet.ibm.com]
> Sent: Friday, April 17, 2015 7:07 AM
> To: Milos Vyletel
> Cc: Josh Triplett; Steven Rostedt; Mathieu Desnoyers; Lai Jiangshan;
> Jonathan Corbet; open list:READ-COPY UPDATE...; open
> list:DOCUMENTATION;
Hi Joerg,
>>> On Fri, Apr 17, 2015 at 5:36 AM, Jörg Otte wrote:
The BT mouse is "death" in v4.1.
The BT mouse has been working in 4.0 and previous kernels, so this
is a regression.
>>>
>>> Any chance of bisecting it?
>>>
>>> Linus
>> I will try that.
>>
>> Thanks,
2015-04-17 16:51 GMT+02:00 Jörg Otte :
> 2015-04-17 15:44 GMT+02:00 Linus Torvalds :
>> On Fri, Apr 17, 2015 at 5:36 AM, Jörg Otte wrote:
>>> The BT mouse is "death" in v4.1.
>>> The BT mouse has been working in 4.0 and previous kernels, so this
>>> is a regression.
>>
>> Any chance of bisecting
On Fri 17-04-15 12:29:07, Austin S Hemmelgarn wrote:
> On 2015-04-17 12:22, Jan Kara wrote:
> >On Fri 17-04-15 17:08:10, John Spray wrote:
> >>
> >>On 17/04/2015 16:43, Jan Kara wrote:
> >>>On Fri 17-04-15 15:51:14, John Spray wrote:
> On 17/04/2015 14:23, Austin S Hemmelgarn wrote:
>
>
Hi Ezequiel,
On Thu, Apr 16, 2015 at 10:27 PM, Ezequiel Garcia
wrote:
>
> Hi Andrew,
>
> On 04/07/2015 04:44 PM, Andrew Bresticker wrote:
> [..]
>> +static int pistachio_gpio_register(struct pistachio_pinctrl *pctl)
>> +{
>> + struct device_node *node = pctl->dev->of_node;
>> + struct
mmu_virtual_psize shall be set to MMU_PAGE_16K when 16k pages have
been selected
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/mmu-8xx.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/powerpc/include/asm/mmu-8xx.h
b/arch/powerpc/include/asm/mmu-8xx.h
index
Having a macro will help keep clear code.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_8xx.S | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/arch/powerpc/kernel/head_8xx.S b/arch/powerpc/kernel/head_8xx.S
index 9b53fe1..1279018 100644
---
By default, TASK_SIZE is set to 0x8000 for PPC_8xx, which is most
likely sufficient for most cases. However, kernel configuration allows
to set TASK_SIZE to another value, so the 8xx shall handle it.
This patch also takes into account the case of PAGE_OFFSET lower than
0x8000, allthought
We now have SPRG2 available as in it not used anymore for saving CR, so we don't
need to crash DAR anymore for saving r3 for CPU6 ERRATA handling.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_8xx.S | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git
In order to be able to reduce scope during which CR is saved, we take
CR saving/restoring out of exception PROLOG and EPILOG
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_8xx.S | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git
This patchset provides a further optimisation of TLB handling in the 8xx.
Changes are:
- Not saving registers like CR when not needed
- Adding support to any TASK_SIZE
Only the last patch of the set is changed compared to v4
Christophe Leroy (5):
powerpc/8xx: macro for handling CPU15 errata
CR only needs to be preserved when checking if we are handling a kernel address.
So we can preserve CR in a register:
- In ITLBMiss, check is done only when CONFIG_MODULES is defined. Otherwise we
don't need to do anything at all with CR.
- We use r10, then we reload SRR0/MD_EPN into r10 when CR
On Fri, Apr 17, 2015 at 01:03:20PM +0100, S Twiss wrote:
> From: Steve Twiss
>
> Add OnKey driver support for DA9063
>
Isn't this almost to the letter identical to da9062 that I just looked
at? Please find a way to not make a brand new driver for the slightest
variation of the chip...
Thanks.
On 2015-04-17 12:22, Jan Kara wrote:
On Fri 17-04-15 17:08:10, John Spray wrote:
On 17/04/2015 16:43, Jan Kara wrote:
On Fri 17-04-15 15:51:14, John Spray wrote:
On 17/04/2015 14:23, Austin S Hemmelgarn wrote:
For some filesystems, it may make sense to differentiate between a
generic
Hello.
On 04/17/2015 05:24 PM, Alban Bedel wrote:
Signed-off-by: Alban Bedel
---
.../interrupt-controller/qca,ath79-cpu-intc.txt| 45 ++
1 file changed, 45 insertions(+)
create mode 100644
On Fri 17-04-15 17:08:10, John Spray wrote:
>
> On 17/04/2015 16:43, Jan Kara wrote:
> >On Fri 17-04-15 15:51:14, John Spray wrote:
> >>On 17/04/2015 14:23, Austin S Hemmelgarn wrote:
> >>
> >>>For some filesystems, it may make sense to differentiate between a
> >>>generic warning and an error.
On 04/17/2015 05:24 PM, Alban Bedel wrote:
Signed-off-by: Alban Bedel
---
.../devicetree/bindings/clock/qca,ath79-pll.txt| 33 ++
1 file changed, 33 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/qca,ath79-pll.txt
diff --git
On Fri, Apr 17, 2015 at 11:55:20AM -0400, Pranith Kumar wrote:
> On Fri, Apr 17, 2015 at 6:33 AM, Milos Vyletel wrote:
> > Make a note stating that repeated calls of rcu_dereference() may not
> > return the same pointer if update happens while in critical section.
>
> Might as well make it more
On 04/17/2015 06:08 PM, John Spray wrote:
>
> On 17/04/2015 16:43, Jan Kara wrote:
>> On Fri 17-04-15 15:51:14, John Spray wrote:
>>> On 17/04/2015 14:23, Austin S Hemmelgarn wrote:
>>>
For some filesystems, it may make sense to differentiate between a
generic warning and an error. For
On Fri, Apr 17, 2015 at 09:50:56AM +0200, Jens Wiklander wrote:
> + teedev = devm_kzalloc(dev, sizeof(*teedev), GFP_KERNEL);
[..]
> + rc = misc_register(>miscdev);
[..]
> +void tee_unregister(struct tee_device *teedev)
> +{
[..]
> + misc_deregister(>miscdev);
> +}
[..]
>+static int
On Fri, Apr 17, 2015 at 04:19:52PM +0200, Frans Klaver wrote:
> > On Thu, Apr 16, 2015 at 7:27 AM, Huang Ying wrote:
> > I'm happy to
> > send in a patch that restores "mtd->owner = THIS_MODULE" with these
> > drivers, if that's preferred.
>
> Long story short, I should fix it.
>
> Brian, do
Le 17/04/2015 17:14, David Laight a écrit :
From: Christophe Leroy
Linux CodyingStyle recommends to use short variables for local
variables. ptr is just good enough for those 3 lines functions.
It helps keep single lines shorter than 80 characters.
...
-static void to_talitos_ptr(struct
On Mon, Mar 23, 2015 at 01:37:40PM +1100, NeilBrown wrote:
> @@ -1669,13 +1669,14 @@ static inline int nested_symlink(struct path *path,
> struct nameidata *nd)
>
> do {
> struct path link = *path;
> + struct inode *inode = link.dentry->d_inode;
>
Hello,
On Sat, Apr 18, 2015 at 12:35:06AM +0900, Tetsuo Handa wrote:
> If the sender side can wait for retransmission, why can't we use
> userspace programs (e.g. rsyslogd)?
Because the system may be oopsing, ooming or threshing excessively
rendering the userland inoperable and that's exactly
On 04/16/2015 11:28 AM, Frederic Weisbecker wrote:
So unfortunately I had to see the result to realize my mistake on one detail.
With this scheme, it's not clear who allocates and who releases the cpumasks.
If the caller of smpboot_register_percpu_thread() allocates the cpumask, then he
should
On 04/16/2015 09:31 PM, Chai Wen wrote:
On 04/15/2015 03:37 AM, Chris Metcalf wrote:
+/*
+ * The cpumask is the mask of possible cpus that the watchdog can run
+ * on, not the mask of cpus it is actually running on. This allows the
+ * user to specify a mask that will include cpus that have
Hi Baruch, Andrew,
2015-04-16 19:08 GMT+09:00 Baruch Siach :
> Hi Masahiro Yamada,
>
> On Thu, Apr 16, 2015 at 04:59:06PM +0900, Masahiro Yamada wrote:
>> Initial device trees for UniPhier SoCs: PH1-sLD3, PH1-LD4, PH1-Pro4,
>> and PH1-sLD8.
>>
>> Signed-off-by: Masahiro Yamada
>> ---
>
> [...]
>
Hi,
On Fri, Apr 17, 2015 at 03:23:33PM +0100, S Twiss wrote:
> From: S Twiss
>
> Add OnKey driver support for DA9062
>
> Signed-off-by: Steve Twiss
>
> ---
>
> This patch applies against linux-next and v4.0
>
>
>
> drivers/input/misc/Kconfig| 10 ++
>
From: Joe Perches
The documentation shows a need for gcc > 4.9.2, but it's
really >=. The Kconfig entries don't show require versions
so add them. Correct a latter/later typo too.
Also mention that gcc 5 required to catch out of bounds accesses
to global and stack variables.
Signed-off-by:
On 17/04/2015 16:43, Jan Kara wrote:
On Fri 17-04-15 15:51:14, John Spray wrote:
On 17/04/2015 14:23, Austin S Hemmelgarn wrote:
For some filesystems, it may make sense to differentiate between a
generic warning and an error. For BTRFS and ZFS for example, if
there is a csum error on a
On 04/13/2015 04:20 AM, Ben Hutchings wrote:
> Kyle McMartin joined the linux-firmware maintainers, and we now
> have an alias which reaches all of us.
> Include that instead of the individual addresses.
>
> Add some further recommendations that were already included in the
> README in
On 17/04/2015 17:49, Maxime Ripard wrote:
> On Fri, Apr 17, 2015 at 05:01:55PM +0200, Gregory CLEMENT wrote:
>> On 17/04/2015 16:50, Maxime Ripard wrote:
>>> On Fri, Apr 17, 2015 at 04:40:43PM +0200, Gregory CLEMENT wrote:
Hi Maxime,
On 17/04/2015 16:32, Maxime Ripard wrote:
>
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
Changes in v2: None
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f7bbaec..da452f9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1527,6 +1527,13 @@ F: drivers/rtc/rtc-ab3100.c
Initial device trees for UniPhier SoCs: PH1-sLD3, PH1-LD4, PH1-Pro4,
and PH1-sLD8.
Signed-off-by: Masahiro Yamada
---
Changes in v3:
- License under GPL/X11
- Drop "earlyprintk" kernel-parameter, add "stdout-path" property
- Add syscon device for SMP boot support in order not to
On Saturday 18 April 2015 00:48:17 Masahiro Yamada wrote:
> +
> + smp_syscon@59801208 {
> + compatible = "socionext,uniphier-smp-reg", "syscon";
> + reg = <0x59801208 0x4>;
> + };
> +
>
Using syscon here is a good idea, but
On Fri, Apr 17, 2015 at 6:33 AM, Milos Vyletel wrote:
> Make a note stating that repeated calls of rcu_dereference() may not
> return the same pointer if update happens while in critical section.
Might as well make it more explicit with an example then. See below:
>
> Reported-by: Jeff Haran
>
On Fri, Apr 17, 2015 at 05:01:55PM +0200, Gregory CLEMENT wrote:
> On 17/04/2015 16:50, Maxime Ripard wrote:
> > On Fri, Apr 17, 2015 at 04:40:43PM +0200, Gregory CLEMENT wrote:
> >> Hi Maxime,
> >>
> >> On 17/04/2015 16:32, Maxime Ripard wrote:
> >>> On Fri, Apr 17, 2015 at 04:19:22PM +0200,
Mike Snitzer wrote:
> On Thu, Apr 16 2015 at 5:23am -0400,
> Alex Elsayed wrote:
>
>> Mike Snitzer wrote:
>>
>> > On Thu, Apr 09 2015 at 9:28am -0400,
>> > Pali Rohár wrote:
>> >
>> >> On Thursday 09 April 2015 09:12:08 Mike Snitzer wrote:
>> >> > On Mon, Apr 06 2015 at 9:29am -0400,
>>
On Thu, Apr 16, 2015 at 11:26:48PM -0400, Linus Torvalds wrote:
> On Wed, Apr 15, 2015 at 9:04 PM, Al Viro wrote:
> >
> > That leaves only the actual d_inode annotations series out of the
> > stuff already in for-next; there are several piles of stuff from various
> > folks I'm going to
On Friday 17 April 2015 15:46:57 Catalin Marinas wrote:
> On Fri, Apr 17, 2015 at 02:17:32PM +0100, Arnd Bergmann wrote:
> > - If we do not use the exact data structures that we have on aarch32,
> > then I think we should make aarch32 emulation and aarch64-ilp32
> > emulation mutually
Initial commit for a new SoC family, UniPhier, developed by
Socionext Inc. (formerly, System LSI Business Division of
Panasonic Corporation).
This commit includes a minimal set of components for booting the
kernel, including SMP support.
Signed-off-by: Masahiro Yamada
---
Changes in v3:
-
This is an initial series for supporting Socionext UniPhier SoCs,
based on ARM Cortex-A9, mainly used for digital TVs, video recorders, etc.
Masahiro Yamada (4):
ARM: UniPhier: add basic support for UniPhier architecture
ARM: multi_v7_defconfig: enable UniPhier SoC family
ARM: dts:
Add UniPhier, a new citizen in the ARM multi platform.
Signed-off-by: Masahiro Yamada
---
Changes in v3: None
Changes in v2: None
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
b/arch/arm/configs/multi_v7_defconfig
On 15/04/17, Peter Zijlstra wrote:
> On Fri, Apr 17, 2015 at 03:35:54AM -0400, Richard Guy Briggs wrote:
> > Added the macro CLONE_NEW_MASK_ALL to refer to all CLONE_NEW* flags.
>
> A wee bit about why might be nice..
It makes the following patch much cleaner to read:
[PATCH V6 08/10]
On 04/17/2015 09:45 AM, Jens Axboe wrote:
On 04/17/2015 09:41 AM, Dave Jones wrote:
On Fri, Apr 17, 2015 at 09:12:01AM -0600, Jens Axboe wrote:
> Hi Linus,
>
> A commit in the previous pull request introduce a regression. So far
> only observed on qemu-sparc64, but it's a general bug.
Resend to LKML
Lee,
This question is actually more about MFD. Can you point me to the possible
causes for my failure below?
Thanks.
York
On 04/16/2015 05:02 PM, York Sun wrote:
> Julia and other experts,
>
> I am seeking for help on my device driver.
>
> I am working on a module driver for
On 04/17/2015 09:31 AM, Guenter Roeck wrote:
Hi Jens,
On Fri, Apr 17, 2015 at 08:26:11AM -0600, Jens Axboe wrote:
As additional information:
+* Set the map size to the number of mapped software queues.
+* This is more accurate and more efficient than looping
On 04/17/2015 09:41 AM, Dave Jones wrote:
On Fri, Apr 17, 2015 at 09:12:01AM -0600, Jens Axboe wrote:
> Hi Linus,
>
> A commit in the previous pull request introduce a regression. So far
> only observed on qemu-sparc64, but it's a general bug. Please pull this
> single fix to rectify
On Fri 17-04-15 15:51:14, John Spray wrote:
> On 17/04/2015 14:23, Austin S Hemmelgarn wrote:
> >On 2015-04-17 09:04, Beata Michalska wrote:
> >>On 04/17/2015 01:31 PM, Jan Kara wrote:
> >>>On Wed 15-04-15 09:15:44, Beata Michalska wrote:
> >>>...
> +static const match_table_t fs_etypes = {
>
On Fri, Apr 17, 2015 at 09:12:01AM -0600, Jens Axboe wrote:
> Hi Linus,
>
> A commit in the previous pull request introduce a regression. So far
> only observed on qemu-sparc64, but it's a general bug. Please pull this
> single fix to rectify that, thanks.
I hit the same bug on two x86
On 04/16/2015 06:46 AM, Ulrich Obergfell wrote:
if a user changes watchdog parameters in /proc/sys/kernel, the watchdog threads
are not stopped and restarted in all cases. Parameters can also be changed 'on
the fly', for example like 'watchdog_thresh' in the following flow of execution:
On Fri, Apr 17, 2015 at 11:26:36AM +0200, Ulrich Obergfell wrote:
> The 'watchdog_user_enabled' variable is only used as an 'interface'
> to the /proc/sys/kernel/watchdog parameter. The actual state of the
> watchdog is tracked by bits in the 'watchdog_enabled' variable. So,
>
Tejun Heo wrote:
> * Implement netconsole retransmission support. Matching rx socket on
> the source port is automatically created for extended targets and
> the log receiver can request retransmission by sending reponse
> packets. This is completely decoupled from the main write path and
On Sun, Apr 12, 2015 at 06:00:51PM +0200, Mathias Krause wrote:
> When building perf with perl or python support it implicitly gets linked
> with the -export-dynamic linker option through the additional linker
> flags, namely with -Wl,-E via perl or -Xlinker -export-dynamic via
> python. That flag
Hi Tomeu,
Thank you for the patch.
On Friday 17 April 2015 17:24:49 Tomeu Vizoso wrote:
> Introduce a new per-device flag power.force_direct_complete that will
> instruct the PM core to ignore the runtime PM status of its descendants
> when deciding whether to let this device remain in runtime
On Fri, Apr 17, 2015 at 10:41:30AM -0400, Steven Rostedt wrote:
> On Fri, 17 Apr 2015 16:38:04 +0200
> Milos Vyletel wrote:
>
> > Make a note stating that repeated calls of rcu_dereference() may not
> > return the same pointer if update happens while in critical section.
> >
> > Reported-by:
On Fri, Apr 17, 2015 at 05:24:49PM +0200, Tomeu Vizoso wrote:
> Introduce a new per-device flag power.force_direct_complete that will
> instruct the PM core to ignore the runtime PM status of its descendants
> when deciding whether to let this device remain in runtime suspend when
> the system
On Mon, Apr 13, 2015 at 03:59:13PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the tip tree got a conflict in
> tools/perf/config/Makefile between commit 4fd6ce055817 ("perf tools:
> Hook up MIPS unwind and dwarf-regs in the Makefile") from the mips tree
hi,
I
On Fri, Apr 17, Christophe Leroy wrote:
> v3 is a complete rework of the patchset. Since a kernel can be built
> with support for both MPC82xx and MPC83xx at the same time, talitos
> driver shall support both SEC1 and SEC2+ at the same time.
The used git send-email command lacked the --thread
On Wed, Apr 15, 2015 at 01:50:42PM -0700, Sukadev Bhattiprolu wrote:
SNIP
> |
> | - to blindly follow some poorly constructed vendor format with no
> |high level structure, that IMHO didn't work very well when OProfile
> |was written, and misrepresenting it as 'symbolic event names'.
Hi Jens,
On Fri, Apr 17, 2015 at 08:26:11AM -0600, Jens Axboe wrote:
> >>
> >As additional information:
> >
> >+* Set the map size to the number of mapped software queues.
> >+* This is more accurate and more efficient than looping
> >+* over all
At Fri, 17 Apr 2015 17:08:22 +0200,
Richard Weinberger wrote:
> add header includion for CONFIG_LIB to wrap kmalloc and co. This will
> bring malloc(3) based allocator used by arch/lib.
> >>>
> >>> Maybe add another allocator insteadl? SLLB which implements memory
> >>> management
When the system goes to sleep and afterwards resumes, a significant
amount of time is spent suspending and resuming devices that were
already runtime-suspended.
By setting the power.force_direct_complete flag, the PM core will ignore
the state of descendant devices and the device will be let in
Introduce a new per-device flag power.force_direct_complete that will
instruct the PM core to ignore the runtime PM status of its descendants
when deciding whether to let this device remain in runtime suspend when
the system goes into a sleep power state.
This is needed because otherwise it would
v3: * Add a new power.force_direct_complete to let devices express that it's
safe to let them be runtime-suspended at system sleep regardless of the
state
of their descendants
v2: * Let creators of the input device to decide whether it should remain
runtime
On 04/10/2015 05:50 PM, Ming Lin wrote:
On Wed, Mar 25, 2015 at 7:26 AM, Jens Axboe wrote:
On 03/24/2015 08:43 PM, Dave Chinner wrote:
On Tue, Mar 24, 2015 at 09:27:00AM -0600, Jens Axboe wrote:
Get the streamid from the file, if any, and set it on the bio.
Signed-off-by: Jens Axboe
---
More comments below.
> On 17 Apr 2015, at 16:46, Catalin Marinas wrote:
>
> Even in this case, we could enable AArch32 compat knowing that ioctls
> wouldn't work. If this is important, we can add an option to enable
> ioctl support for ILP32 and re-target the asm/compat.h definitions.
>
>> g)
From: Christophe Leroy
> Linux CodyingStyle recommends to use short variables for local
> variables. ptr is just good enough for those 3 lines functions.
> It helps keep single lines shorter than 80 characters.
...
> -static void to_talitos_ptr(struct talitos_ptr *talitos_ptr, dma_addr_t
>
On 16 April 2015 at 20:42, Konrad Rzeszutek Wilk wrote:
> And easier way is to compile the kernel with CONFIG_DMA_API_DEBUG
> and then load the attached module.
>
> That should tell you who and what else is holding on the buffers.
Ok, I have compiled 3.19.4 w/ CONFIG_DMA_API_DEBUG=y + the module
On Fri, Apr 17, 2015 at 06:05:55PM +0300, Alexey Dobriyan wrote:
> Moving Ngid to the end of file minimizes risk of breakage.
Hmmm... how so? The only reason for changing the position is because
there's this specific breakage. The goal should be working around
that specific case while keeping
On 04/17/2015 05:23 AM, Dmitry Monakhov wrote:
Hi Jens, do you have any objections against this patch?
Please let me know if you have any and I'll fix it.
I think it looks fine, and it's a nice win! So good catch. I'll queue it
up for inclusion later in this cycle.
--
Jens Axboe
--
To
Hi Linus,
A commit in the previous pull request introduce a regression. So far
only observed on qemu-sparc64, but it's a general bug. Please pull this
single fix to rectify that, thanks.
git://git.kernel.dk/linux-block.git for-linus
On 16 April 2015 at 18:57, Dorian Gray wrote:
> On 16 April 2015 at 16:24, Suman Tripathi wrote:
>> Try increasing the SWIOTLB size to 128MB .Default is 64MB.
>
> Ok, so I'm back to k3.18.7 (default in the latest Fatdog), although
> I'm not sure what should be the exact value of swiotlb boot
Am 17.04.2015 um 17:02 schrieb Hajime Tazaki:
>
> Hi Christoph, Richard,
>
> At Fri, 17 Apr 2015 14:44:35 +0200,
> Richard Weinberger wrote:
>>
>> Am 17.04.2015 um 14:17 schrieb Christoph Lameter:
>>> On Fri, 17 Apr 2015, Hajime Tazaki wrote:
>>>
add header includion for CONFIG_LIB to wrap
[ Not in this patch: tests (Pranith Kumar has a patch for this), man page. ]
Here is an implementation of a new system call, sys_membarrier(), which
executes a memory barrier on all threads running on the system. It is
implemented by calling synchronize_sched(). It can be used to distribute
the
On Fri, Apr 17, 2015 at 5:26 PM, Tejun Heo wrote:
> Hey,
>
> On Fri, Apr 17, 2015 at 04:23:48PM +0300, Alexey Dobriyan wrote:
>> It was demonstrated that Ngid addition as line 4 breaks apps,
>> but your "what if" remains "what if".
>>
>> I'd say Ngid should be moved to the end and every new field
Hi Alex,
On 04/17/2015 04:29 PM, Alex Williamson wrote:
> On Fri, 2015-04-17 at 15:37 +0200, Eric Auger wrote:
>> This patch introduces a specialized vfio platform driver for the
>> calxeda xgmac. On top of the generic vfio platform driver functionalities,
>> it implements the reset modality.
On 17 April 2015 at 16:08, Lorenzo Pieralisi wrote:
> On Thu, Apr 16, 2015 at 03:37:19PM +0100, Tomeu Vizoso wrote:
>
> [...]
>
>> >> I don't know what FIQs are. :-)
>> >
>> > In short, fast IRQs, it is a separate IRQ line handled as a separate
>> > exception source with some private (banked)
On 17/04/2015 16:50, Maxime Ripard wrote:
> On Fri, Apr 17, 2015 at 04:40:43PM +0200, Gregory CLEMENT wrote:
>> Hi Maxime,
>>
>> On 17/04/2015 16:32, Maxime Ripard wrote:
>>> On Fri, Apr 17, 2015 at 04:19:22PM +0200, Boris Brezillon wrote:
Hi Gregory,
On Fri, 17 Apr 2015 15:01:01
Hi Christoph, Richard,
At Fri, 17 Apr 2015 14:44:35 +0200,
Richard Weinberger wrote:
>
> Am 17.04.2015 um 14:17 schrieb Christoph Lameter:
> > On Fri, 17 Apr 2015, Hajime Tazaki wrote:
> >
> >> add header includion for CONFIG_LIB to wrap kmalloc and co. This will
> >> bring malloc(3) based
On Tue, Apr 07, 2015 at 07:26:35PM +0800, Lai Jiangshan wrote:
> Current apply_workqueue_attrs() includes pwqs-allocation and
> pwqs-installation,
> so when we batch multiple apply_workqueue_attrs()s as a transaction, we can't
> ensure the transaction must succeed or fail as a complete unit.
On 17/04/2015 15:43, Peter Zijlstra wrote:
> On Fri, Apr 17, 2015 at 03:38:58PM +0200, Paolo Bonzini wrote:
>>> The path this notifier is called from has nothing to do with those
>>> costs.
>
> Its attributed to the entity doing the migration, which can be the
> wakeup path or a softirq. And we
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Sasha Levin
commit 6b8d9117ccb4f81b1244aafa7bc70ef8fa45fc49 upstream.
The timeout entries are sizeof(int) rather than sizeof(long), which
means that when they were getting read we'd also leak
On Thu, Apr 09, 2015 at 10:43:10AM +0100, Peter Griffin wrote:
> Yes I can test, although not until Saturday as I only have remote
> access to the board today & tomorrow and the hard drive isn't
> plugged in.
What's the status on this patch? Should I push it through
for-4.1-fixes?
Thanks.
--
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Eli Cohen
commit 377b513485fd885dea1083a9a5430df65b35e048 upstream.
Clear the reserved field of struct ib_uverbs_async_event_desc which is
copied to user space.
Signed-off-by: Eli Cohen
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Christie
commit b815fc12d4dd2b5586184fb4f867caff05a810d4 upstream.
This fixes a oops due to a double list add when adding a reject PDU for
iscsit_allocate_iovecs allocation failures. The
Pin direction configuration was incorrectly overwritten
by output and function values in set_mux(). Fix this.
Signed-off-by: Ivan T. Ivanov
---
drivers/pinctrl/qcom/pinctrl-spmi-gpio.c | 1 +
drivers/pinctrl/qcom/pinctrl-spmi-mpp.c | 1 +
2 files changed, 2 insertions(+)
diff --git
On Fri, Apr 17, 2015 at 04:40:43PM +0200, Gregory CLEMENT wrote:
> Hi Maxime,
>
> On 17/04/2015 16:32, Maxime Ripard wrote:
> > On Fri, Apr 17, 2015 at 04:19:22PM +0200, Boris Brezillon wrote:
> >> Hi Gregory,
> >>
> >> On Fri, 17 Apr 2015 15:01:01 +0200
> >> Gregory CLEMENT wrote:
> >>
> >>> Hi
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit c72efb658f7c8b27ca3d0efb5cfd5ded9fcac89e upstream.
>From 1ebf33901ecc75d9496862dceb1ef0377980587c Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Mon, 23 Mar 2015 00:08:19
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Marek Szyprowski
commit 05b676ab42f624425d5f6519276e506b812fa058 upstream.
TASK_SIZE is depends on the systems architecture (32 or 64 bits) and it
should not be used for defining offset
On Friday 17 April 2015 16:24:26 Alban Bedel wrote:
> Replace the simple GPIO chip registration by a platform driver
> and make ath79_gpio_init() just register the device.
>
> Signed-off-by: Alban Bedel
> ---
> arch/mips/ath79/dev-common.c | 13
> arch/mips/ath79/gpio.c | 73
>
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Gu Zheng
commit b0dc3a342af36f95a68fe229b8f0f73552c5ca08 upstream.
Qiu Xishi reported the following BUG when testing hot-add/hot-remove node under
stress condition:
BUG: unable to handle
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Sasha Levin
commit db27ebb111e9f69efece08e4cb6a34ff980f8896 upstream.
Max unacked packets/bytes is an int while sizeof(long) was used in the
sysctl table.
This means that when they were
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 64b4e2526d1cf6e6a4db6213d6e2b6e6ab59479a upstream.
"ocfs2 syncs the wrong range" had been broken; prior to it the
code was doing the wrong thing in case of O_APPEND, all right,
This is the start of the stable review cycle for the 3.10.75 release.
There are 34 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Apr 19 13:25:20 UTC 2015.
Anything
201 - 300 of 1674 matches
Mail list logo
