On Mon, Feb 02, 2015 at 01:50:52PM +, Graeme Gregory wrote:
> On Mon, Feb 02, 2015 at 01:40:33PM +, Leif Lindholm wrote:
> > On Mon, Feb 02, 2015 at 08:45:36PM +0800, Hanjun Guo wrote:
> > > When system supporting both DT and ACPI but firmware providing
> > > no dtb, we can use this linux,u
On Wed, Jan 28, 2015 at 02:51:23PM +, Marc Zyngier wrote:
> void __weak pcibios_update_irq(struct pci_dev *dev, int irq)
> {
> - dev_dbg(&dev->dev, "assigning IRQ %02d\n", irq);
> - pci_write_config_byte(dev, PCI_INTERRUPT_LINE, irq);
> + struct irq_data *d;
> +
> + d = irq_ge
We setup APIC vectors for threshold errors if interrupt_capable.
However, we don't set interrupt_enable by default.
Re-working threshold_restart_bank() here so that the first time we
set up lvt_offset, we also set IntType to APIC.
User is still allowed to disable interrupts through sysfs.
While a
From: Pasi Sjöholm
It is possible to get kernel in deadlock-state if swap_lock is not locked
with spin_lock_bh by calling si_swapinfo() simultaneously through
timer_function and registered vm shinker callback-function.
BUG: spinlock recursion on CPU#0, main/2447
lock: swap_lock+0x0/0x10, .magic:
Hello.
On 02/02/2015 05:02 PM, Jiri Slaby wrote:
From: Tim Chen
Subject: [PATCH] pci-dma: Fix x86 dma_alloc_coherent to fully clear all pages
returned
Commit d92ef66c4f8f ("x86: make dma_alloc_coherent() return zeroed memory
if CMA is enabled") changed the dma_alloc_coherent page clearanc
On Mon, Feb 02, 2015 at 02:58:36PM +0100, Quentin Casasnovas wrote:
> It is possible for the *_read*() functions to fail, in which case it'll
> leave its third argument untouched. Most of the code do not check the
> return value of *_read*() functions, and will happily use garbage from the
> stack
On Thu, Jan 29, 2015 at 07:46:10PM +0100, Rickard Strandqvist wrote:
> Fix a possible null pointer dereference, there is
> otherwise a risk of a possible null pointer dereference.
>
> This was found using a static code analysis program called cppcheck
>
> Signed-off-by: Rickard Strandqvist
> ---
Am Montag, 2. Februar 2015, 07:03:02 schrieb Tadeusz Struk:
Hi Tadeusz,
>On 02/01/2015 10:31 AM, Stephan Mueller wrote:
>> Hi Tadeusz,
>>
>>> > The way the algif_skcipher works currently is that on
>>> > sendmsg/sendpage it builds an sgl for the input data and then on
>>> > read/recvmsg it sends
On 01/20/2015 07:37 PM, Baoquan He wrote:
Leftover problem:
hpa want to see the physical randomization can cover the whole physical
memory. I
checked code and found it's hard to do. Because in
arch/x86/boot/compressed/head_64.S
an identity mapping of 4G is built and then kaslr and decompr
* Arnd Bergmann [150129 15:51]:
> On Thursday 29 January 2015 18:15:51 Murali Karicheri wrote:
> > NetCP on Keystone has cpsw ale function similar to other TI SoCs
> > and this driver is re-used. To allow both ti cpsw and keystone netcp
> > to re-use the driver, convert the cpsw ale to a module an
Hi Sylwester,
On Tue, Feb 3, 2015 at 1:25 AM, Sylwester Nawrocki
wrote:
> Hi Chanwoo,
>
> On 02/02/15 16:51, Chanwoo Choi wrote:
>> On Mon, Feb 2, 2015 at 11:40 PM, Sylwester Nawrocki
>> wrote:
>>> > On 02/02/15 15:08, Chanwoo Choi wrote:
>>> >
>> OK, I'll add more following information:
>>
t;rate during __clk_init()? That would make this call to
> >> >> clk_core_set_rate_nolock() a nop in this case.
> >> >>
> >> >
> >> > Here's a patch to do this
> >> >
> >> > ---8<
> >> > From: Stephen Boy
On Fri, Jan 30, 2015 at 12:28:14PM +, Joerg Roedel wrote:
> On Wed, Jan 28, 2015 at 02:35:24PM +, Will Deacon wrote:
> > On Tue, Jan 27, 2015 at 12:08:57AM +, Joerg Roedel wrote:
> > > @@ -51,6 +51,7 @@ struct iommu_group {
> > > void (*iommu_data_release)(void *iommu_data);
> > > c
On Thu, Jan 29, 2015 at 07:59:12PM +0100, Rickard Strandqvist wrote:
> Fix a possible null pointer dereference, there is
> otherwise a risk of a possible null pointer dereference.
>
> This was found using a static code analysis program called cppcheck
>
> Signed-off-by: Rickard Strandqvist
> ---
On Thu, Jan 29, 2015 at 05:18:33PM -0500, Rob Clark wrote:
> On Thu, Jan 29, 2015 at 2:26 PM, Russell King - ARM Linux
> wrote:
> > On Thu, Jan 29, 2015 at 01:52:09PM -0500, Rob Clark wrote:
> >> Quite possibly for some of these edge some of cases, some of the
> >> dma-buf exporters are going to n
Afternoon, Peter,
On Wed, 2015-01-21 at 20:27 +, Pawel Moll wrote:
> Until now, perf framework never defined the meaning of the timestamps
> captured as PERF_SAMPLE_TIME sample type. The values were obtaining
> from local (sched) clock, which is unavailable in userspace. This made
> it impossi
glibc malloc changed behaviour in glibc 2.10 to have per-thread arenas
instead of creating new areans if the existing ones were contended.
The decision appears to have been made so the allocator scales better but the
downside is that madvise(MADV_DONTNEED) is now called for these per-thread
areans
On Mon 2015-02-02 15:57:20, Petr Mladek wrote:
> On Mon 2015-02-02 17:40:10, Masami Hiramatsu wrote:
> > (2015/01/31 0:45), Petr Mladek wrote:
> > > can_probe() checks if the given address points to the beginning of
> > > an instruction. It analyzes all the instructions from the beginning
> > > of
Signed-off-by: Alexander Holler
---
arch/x86/syscalls/syscall_32.tbl | 1 +
arch/x86/syscalls/syscall_64.tbl | 1 +
fs/namei.c| 38 ++-
include/asm-generic/audit_dir_write.h | 1 +
include/linux/fs.h| 1
Hello,
some people already might have noticed that I've got a bit angry that
no filesystem nor the posix api nor the linux syscalls are offering
the userspace a way to request real deletion of one or more files (there's
the 's' bit, see man chattr, but it is ignored by all FS which know it).
Alm
Simple test, needs the new rm with option -s.
Signed-off-by: Alexander Holler
---
test_unlinkat_s.sh | 27 +++
1 file changed, 27 insertions(+)
create mode 100755 test_unlinkat_s.sh
diff --git a/test_unlinkat_s.sh b/test_unlinkat_s.sh
new file mode 100755
index 000.
Signed-off-by: Alexander Holler
---
fs/fat/fat.h| 1 +
fs/fat/fatent.c | 20
fs/fat/inode.c | 13 +
3 files changed, 34 insertions(+)
diff --git a/fs/fat/fat.h b/fs/fat/fat.h
index e0c4ba3..b9febda 100644
--- a/fs/fat/fat.h
+++ b/fs/fat/fat.h
@@ -81,6 +81,7
Signed-off-by: Alexander Holler
---
fs/ext4/ext4.h| 2 ++
fs/ext4/mballoc.c | 25 +++--
fs/ext4/super.c | 12
3 files changed, 37 insertions(+), 2 deletions(-)
diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
index c55a1fa..e66507c 100644
--- a/fs/ext4/ext4.h
You have to build the new rm yourself
Signed-off-by: Alexander Holler
---
...ion-s-to-rm-to-support-unlinkat_s-current.patch | 111 +
1 file changed, 111 insertions(+)
create mode 100644
0001-WIP-Add-option-s-to-rm-to-support-unlinkat_s-current.patch
diff --git a/0001-WIP-
Freescale ethernet controllers have the capability to re-assemble fragmented
data into a single ethernet frame. This patch uses this capability and
implements NETIP_F_SG feature into the fs_enet ethernet driver.
On a MPC885, I get 53% performance improvement on a ftp transfer of a 15Mb file:
* W
* Mike Turquette [150201 13:27]:
> Quoting Tomeu Vizoso (2015-01-23 03:03:30)
> > Moves clock state to struct clk_core, but takes care to change as little
> > API as
> > possible.
> >
> > struct clk_hw still has a pointer to a struct clk, which is the
> > implementation's per-user clk instance,
dai-link params for codec-codec links were fixed. The fixed
link between codec and another chip which may be another codec,
baseband, bluetooth codec etc may require run time configuaration
changes. This change provides an optional alsa control to select
one of the params from a list of params.
Si
On Sat, Jan 31, 2015 at 05:24:42PM +0530, varsharamt wrote:
The task was to fix a warning which was shown while compiling a driver
called NVEC. I wrote a brief description about how to enable support for
a nVidya complaint embedded controller.
Please note that NVIDIA is spelled/capitalized as
* Roger Quadros [150126 01:38]:
> On 24/01/15 22:28, Semen Protsenko wrote:
> > Some GPMC_CONFIG7 register bits marked as "RESERVED", means they
> > shouldn't be overwritten. A typical approach to handle such bits called
> > "Read-Modify-Write". Writing procedure used in gpmc_cs_set_memconf()
> >
A key concept behind posix capabilities is that the privilege comes from
both the person and the file being executed. As you say below basically
anything can be executed by the program so that is completely violated.
Still, it's not that different from mmapping some arbitrary code and
jumping int
From: Anshul Garg
Unnecessary instructions are executing even though m is
greater than x so added logic to make m less than equal to
x before performing these operations.
Signed-off-by: Anshul Garg
---
lib/int_sqrt.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/int_sqrt.c b/li
On Mon, Feb 02, 2015 at 10:32:53AM -0500, Benjamin Tissoires wrote:
> On Feb 01 2015 or thereabouts, Henrik Rydberg wrote:
> > Hi Benjamin,
> >
> > > Tested this morning, and yes, it solves the problem.
> > > I assumed that the dmax was in mm, and used "10 * priv->x_res", which
> > > seemed to do
From: Grygorii Strashko
Setting a dev_pm_ops suspend/resume pair but not a set of
hibernation functions means those pm functions will not be
called upon hibernation.
Fix this by using SIMPLE_DEV_PM_OPS, which appropriately
assigns the suspend and hibernation handlers.
Signed-off-by: Grygorii Str
On Mon, Feb 2, 2015 at 9:12 AM, Serge Hallyn wrote:
> A key concept behind posix capabilities is that the privilege comes from
> both the person and the file being executed. As you say below basically
> anything can be executed by the program so that is completely violated.
>
> Still, it's not th
On Wed, Jan 28, 2015 at 04:42:30PM +0100, Peter Zijlstra wrote:
> On Wed, Jan 28, 2015 at 01:24:10AM +0100, Frederic Weisbecker wrote:
> > d1f74e20b5b064a130cd0743a256c2d3cfe84010 turned PREEMPT_ACTIVE modifiers
> > to use raw untraced preempt count operations. Meanwhile this prevents
> > from debu
On Mon, Feb 02, 2015 at 07:14:31PM +0200, grygorii.stras...@linaro.org wrote:
> From: Grygorii Strashko
>
> Setting a dev_pm_ops suspend/resume pair but not a set of
> hibernation functions means those pm functions will not be
> called upon hibernation.
> Fix this by using SIMPLE_DEV_PM_OPS, whic
On Wed, Jan 28, 2015 at 04:46:37PM +0100, Peter Zijlstra wrote:
> On Wed, Jan 28, 2015 at 01:24:12AM +0100, Frederic Weisbecker wrote:
> > PREEMPT_ACTIVE implies non-preemptible context and thus atomic context
> > despite what in_atomic*() APIs reports about it. These functions
> > shouldn't ignore
On Mon, Feb 02, 2015 at 11:56:09PM +0900, Namhyung Kim wrote:
> Hi Jiri and Adrian,
>
> On Mon, Feb 2, 2015 at 9:13 PM, Jiri Olsa wrote:
> > On Mon, Feb 02, 2015 at 02:07:27PM +0200, Adrian Hunter wrote:
> >
> > SNIP
> >
> >> >>
> >> >> Why not make it the same as all the other data. i.e. find th
On Mon, Feb 02, 2015 at 04:42:40PM +0100, Peter Zijlstra wrote:
> On Mon, Feb 02, 2015 at 01:33:14AM -0500, Vince Weaver wrote:
> > [407484.309136] [ cut here ]
> > [407484.588602] <>[]
> > perf_prepare_sample+0x2ec/0x3c0
> > [407484.597358] [] __perf_event_overflow+
On 2 Feb 2015, Myron Stowe verbalised:
> Nix:
>
> Thanks for the work you've already done with the bisection. Let's see
> if we can get to the bottom of this. Would you capture two couple sets
> of logs, one without the issue and another set with the commit at issue
> included for comparison.
>
The following changes since commit 26bc420b59a38e4e6685a73345a0def461136dce:
Linux 3.19-rc6 (2015-01-25 20:04:41 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ras/ras.git
tags/please-pull-fixmcelog
for you to fetch changes up to 728b6f14abaa7f
On 31 Jan 2015, n...@esperi.org.uk told this:
> I'll let it run overnight and give it a reboot in the morning.
Alas, my latest reboot hit:
[ 215.245158] BUG: unable to handle kernel NULL pointer dereference at 0004
[ 215.251602] IP: [] rpc_new_client+0x13b/0x1f2
[ 215.251602] *pde = 00
This patch set re-introduces the gpio hogging concept first
presented by Boris Brezillion.
This patch set provides a way to initially configure specific GPIO
when the GPIO controller is probed.
The actual DT scanning to collect the GPIO specific data is performed
as part of of_gpiochip_add().
Th
Add GPIO hogging documentation to gpio.txt
Signed-off-by: Benoit Parrot
Reviewed-by: Alexandre Courbot
---
Documentation/devicetree/bindings/gpio/gpio.txt | 30 +
1 file changed, 30 insertions(+)
diff --git a/Documentation/devicetree/bindings/gpio/gpio.txt
b/Documentat
Based on Boris Brezillion's work this is a reworked patch
of his initial GPIO hogging mechanism.
This patch provides a way to initially configure specific GPIO
when the GPIO controller is probed.
The actual DT scanning to collect the GPIO specific data is performed
as part of gpiochip_add().
The
te"
> > >> >> > parameter,
> > >> >> > e.g. on r8a7791:
> > >> >>
> > >> >> Hmm.. I wonder if we should assign core->req_rate to be the same as
> > >> >> core->rate during __clk_init()? Tha
can_probe() checks if the given address points to the beginning of
an instruction. It analyzes all the instructions from the beginning
of the function until the given address. The code might be modified
by another Kprobe. In this case, the current code is read into a buffer,
int3 breakpoint is repl
On Mon, Feb 02, 2015 at 09:46:46AM -0800, Mike Turquette wrote:
> This looks like mis-matched enable/disable calls. We now have unique
> struct clk pointers for every call to clk_get. I haven't yet looked
> through the hwmod code but I have a feeling that we're doing something
> like this:
>
>
On Wed, Jan 28, 2015 at 04:50:44PM +0100, Peter Zijlstra wrote:
> On Wed, Jan 28, 2015 at 01:24:11AM +0100, Frederic Weisbecker wrote:
> > +++ b/kernel/sched/core.c
> > @@ -2760,7 +2760,6 @@ static void __sched __schedule(void)
> > struct rq *rq;
> > int cpu;
> >
> > - preempt_disable()
On 2/2/2015 8:21 AM, Christoph Lameter wrote:
> Linux capabilities suffer from the problem that they are not inheritable
> like regular process characteristics under Unix. This is behavior that
> is counter intuitive to the expected behavior of processes in Unix.
http://wt.tuxomania.net/publicatio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/30/2015 04:46 PM, Dave Hansen wrote:
> On 01/30/2015 09:49 AM, r...@redhat.com wrote:
>> @@ -440,8 +440,9 @@ static inline fpu_switch_t
>> switch_fpu_prepare(struct task_struct *old, struct ta
>> new->thread.fpu_counter > 5); if (__thread_has_fp
On Mon, 2015-02-02 at 17:26 +0100, h...@lst.de wrote:
> On Mon, Feb 02, 2015 at 03:30:27PM +, James Bottomley wrote:
> > Cc added for linux-scsi, since this is the origin of the problem. How
> > important is bisectability in this? It won't affect any non-embedded
> > user, since most don't bu
From: Rik van Riel
We need another lazy restore related function, that will be called
from a function that is above where the lazy restore functions are
now. It would be nice to keep all three functions grouped together.
Signed-off-by: Rik van Riel
---
arch/x86/include/asm/fpu-internal.h | 36
From: Rik van Riel
Currently there are a few magic assignments sprinkled through the
code that disable lazy FPU state restoring, some more effective than
others, and all equally mystifying.
It would be easier to have a helper to explicitly disable lazy
FPU state restoring for a task.
Signed-off
From: Rik van Riel
Use an explicit if/else branch after __save_init_fpu(old) in
switch_fpu_prepare. This makes substituting the assignment
with a call to task_disable_lazy_fpu() in the next patch easier
to review.
Signed-off-by: Rik van Riel
---
arch/x86/include/asm/fpu-internal.h | 5 +++--
These go on top of Oleg's patches.
The mechanism to disable lazy FPU restore is inscrutible
in several places, and dubious at best in one.
These patches make things explicit.
They also get rid of some apparently useless or redundant
code, and make fpu_lazy_restore work when in eager FPU mode.
-
From: Rik van Riel
Replace magic assignments of fpu.last_cpu = ~0 with more explicit
disable_task_lazy_fpu_restore calls.
This also fixes the lazy FPU restore disabling in drop_fpu, which
only really works when !use_eager_fpu(). This is fine for now,
because fpu_lazy_restore() is only used when
From: Rik van Riel
fpu.preload only gets set if new->thread.fpu_counter is already
larger than 5. Incrementing it further does absolutely nothing.
Remove those lines.
Signed-off-by: Rik van Riel
---
arch/x86/include/asm/fpu-internal.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/x
On Mon, Feb 2, 2015 at 5:34 AM, Josh Boyer wrote:
> Hi Sasha and John,
>
> As we rolled out 3.18.5 in Fedora, we've had a number of people
> complain about chrony no longer working when they reboot. It seems
> the calls to adjtimex chrony is making are failing, and then it fails
> to start. Look
From: Rik van Riel
With Oleg's patch "x86, fpu: don't abuse FPU in kernel threads if
use_eager_fpu()", kernel threads no longer have an FPU state even
on systems with use_eager_fpu()
That in turn means that a task may still have its FPU state
loaded in the FPU registers, if the task only got int
Quoting Casey Schaufler (ca...@schaufler-ca.com):
> I'm game to participate in such an effort. The POSIX scheme
> is workable, but given that it's 20 years old and hasn't
> developed real traction it's hard to call it successful.
Over the years we've several times discussed possible reasons for th
Hi Russell,
On 02/02/15 16:33, Russell King - ARM Linux wrote:
> On Wed, Jan 28, 2015 at 02:51:23PM +, Marc Zyngier wrote:
>> void __weak pcibios_update_irq(struct pci_dev *dev, int irq)
>> {
>> -dev_dbg(&dev->dev, "assigning IRQ %02d\n", irq);
>> -pci_write_config_byte(dev, PCI_INTE
Quoting Andy Lutomirski (l...@amacapital.net):
> On Mon, Feb 2, 2015 at 9:12 AM, Serge Hallyn wrote:
> > A key concept behind posix capabilities is that the privilege comes from
> > both the person and the file being executed. As you say below basically
> > anything can be executed by the program
On 01/29/2015 05:33 PM, Rik van Riel wrote:
>> > Hmm, if the the thread was not using the FPU, and this fails to
>> > save anything in to the xsave_buf, what will bndcsr point to?
> If the thread was not using the FPU, can we reach the
> bound range exception?
>
> I believe the MPX feature uses in
* Roger Quadros [150126 01:23]:
> On 24/01/15 22:28, Semen Protsenko wrote:
> > Fix sparse warning:
> > warning: symbol 'gpmc_cs_get_name' was not declared. Should it be static?
> >
> > Signed-off-by: Semen Protsenko
>
> Acked-by: Roger Quadros
Roger is going to queue this, so:
Acked-by: T
Ivan,
On Mon, Feb 02, 2015 at 05:19:30PM +0200, Ivan T. Ivanov wrote:
> Add support for the temperature alarm peripheral found inside
> Qualcomm plug-and-play (QPNP) PMIC chips. The temperature alarm
> peripheral outputs a pulse on an interrupt line whenever the
> thermal over temperature stage va
On Mon, Feb 02, 2015 at 06:08:17PM +, Marc Zyngier wrote:
> Hi Russell,
>
> On 02/02/15 16:33, Russell King - ARM Linux wrote:
> > What your change would mean is that the IRQs currently being programmed
> >> = 16 would be programmed into with numbers with 16 removed from them.
> > This means t
On Mon, Feb 02, 2015 at 09:33:09AM +0530, Viresh Kumar wrote:
> On 1 February 2015 at 00:29, Eduardo Valentin wrote:
> > From: Arnd Bergmann
> >
>
> Acked-by: Viresh Kumar
Thanks!
>
> Now as these are all compilable as modules, should we look into the drivers as
> well to see what they ar
From: Markus Elfring
Date: Mon, 2 Feb 2015 18:26:34 +0100
The pci_dev_put() 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
---
driver
Fix minor code stype problems found by checkpatch.pl
Ricardo Ribalda Delgado (2):
staging/unisys/visorutil/procobjecttree: Code Style
staging/unisys/visorutil/procobjecttree: Replace typedef
drivers/staging/unisys/visorutil/procobjecttree.c | 23 +--
1 file changed, 13 in
Lines should not be over 80 characters
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/staging/unisys/visorutil/procobjecttree.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/unisys/visorutil/procobjecttree.c
b/drivers/staging/unisys/visorutil
Instead of declaring a new type, define a new struct.
Signed-off-by: Ricardo Ribalda Delgado
---
drivers/staging/unisys/visorutil/procobjecttree.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/unisys/visorutil/procobjecttree.c
b/drivers/stagin
On 1/27/2015 9:31 AM, Guenter Roeck wrote:
On Tue, Jan 27, 2015 at 07:51:23PM +1100, Stephen Rothwell wrote:
Hi all,
Changes since 20150123:
The arm64 tree gained a conflict against Linus' tree.
The net-next tree gained conflicts against the arm-soc and net trees.
The drm-panel tree gained a
On Mon, 2015-02-02 at 19:26 +0100, Ricardo Ribalda Delgado wrote:
> Instead of declaring a new type, define a new struct.
[]
> diff --git a/drivers/staging/unisys/visorutil/procobjecttree.c
> b/drivers/staging/unisys/visorutil/procobjecttree.c
[]
> @@ -340,7 +341,9 @@ EXPORT_SYMBOL_GPL(visor_proc_
On 02/02, r...@redhat.com wrote:
>
> From: Rik van Riel
>
> fpu.preload only gets set if new->thread.fpu_counter is already
> larger than 5. Incrementing it further does absolutely nothing.
> Remove those lines.
I _think_ that we increment it further on purpose. Note that fpu_counter
is "char", s
On Mon, 2 Feb 2015, Ricardo Ribalda Delgado wrote:
> apic_force_enable is not defined for amd64.
>
> Without this patch:
>
> LD init/built-in.o
> arch/x86/built-in.o: In function `dtb_lapic_setup':
> kernel/devicetree.c:155:
> undefined reference to `apic_force_enable'
> Makefile:923: recip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/02/2015 01:34 PM, Oleg Nesterov wrote:
> On 02/02, r...@redhat.com wrote:
>>
>> From: Rik van Riel
>>
>> fpu.preload only gets set if new->thread.fpu_counter is already
>> larger than 5. Incrementing it further does absolutely nothing.
>> Re
On Mon, Feb 02, 2015 at 09:08:30AM +0100, Michal Simek wrote:
> Hi Greg,
>
> On 01/31/2015 12:22 AM, Greg Kroah-Hartman wrote:
> > On Thu, Jan 15, 2015 at 03:55:07PM +0100, Michal Simek wrote:
> >> No functional changes.
> >>
> >> Signed-off-by: Michal Simek
> >> ---
> >
> > I can't take gpg-sig
On Sun, Feb 1, 2015 at 9:54 PM, Dave Chinner wrote:
>
> Simple enough - the patch below removes the warning from generic/036
> for me.
So because this is a debugging thing, I'd actually prefer these
"sched_annotate_sleep()" calls to always come with short comments in
code why they exist and why
On Mon, Feb 02, 2015 at 12:43:50AM -0500, Peter Hurley wrote:
> On 02/02/2015 12:33 AM, Eddie Huang wrote:
> > Hi Peter,
> >
> > On Sun, 2015-02-01 at 21:24 -0800, Greg Kroah-Hartman wrote:
> >> On Mon, Feb 02, 2015 at 12:15:31AM -0500, Peter Hurley wrote:
> >>> On 02/01/2015 11:28 PM, Greg Kroah-
On Mon, 2015-02-02 at 18:08 +, Serge Hallyn wrote:
> Quoting Casey Schaufler (ca...@schaufler-ca.com):
> > I'm game to participate in such an effort. The POSIX scheme
> > is workable, but given that it's 20 years old and hasn't
> > developed real traction it's hard to call it successful.
>
>
On 2/1/2015 7:55 PM, Wang, Yalin wrote:
This patch change non-atomic bitops,
add a if() condition to test it, before set/clear the bit.
so that we don't need dirty the cache line, if this bit
have been set or clear. On SMP system, dirty cache line will
need invalidate other processors cache line,
Hi,
On Sat, Jan 31, 2015 at 10:53:30AM +0100, Pali Rohár wrote:
> This patch adds removable mass storage support to g_nokia gadget (for N900).
> It means that at runtime block device can be exported or unexported.
> So it does not export anything by default and thus allows to use MyDocs
> partitio
Instead of declaring a new type, define a new struct.
Signed-off-by: Ricardo Ribalda Delgado
---
v2: Suggested by Joe Perches
Replace unnecessary casting.
drivers/staging/unisys/visorutil/procobjecttree.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers
On 02/02, r...@redhat.com wrote:
>
> From: Rik van Riel
>
> With Oleg's patch "x86, fpu: don't abuse FPU in kernel threads if
> use_eager_fpu()", kernel threads no longer have an FPU state even
> on systems with use_eager_fpu()
>
> That in turn means that a task may still have its FPU state
> load
On Monday 02 February 2015 19:54:58 Felipe Balbi wrote:
> Hi,
>
> On Sat, Jan 31, 2015 at 10:53:30AM +0100, Pali Rohár wrote:
> > This patch adds removable mass storage support to g_nokia
> > gadget (for N900). It means that at runtime block device
> > can be exported or unexported. So it does not
On 2/2/2015 10:08 AM, Serge Hallyn wrote:
> Quoting Casey Schaufler (ca...@schaufler-ca.com):
>> I'm game to participate in such an effort. The POSIX scheme
>> is workable, but given that it's 20 years old and hasn't
>> developed real traction it's hard to call it successful.
> Over the years we've
Hmm. I don't disagree, but would like some more feedback.
Davidlohr - you were the person to touch this function last (commit
30493cc9dddb: "lib/int_sqrt.c: optimize square root algorithm"), and
you did so for performance reasons. And in fact, when you did that,
you removed that initial loop:
-
On 02/02/2015 06:45 AM, Hanjun Guo wrote:
From: Graeme Gregory
Add documentation for the guidelines of how to use ACPI
on ARM64.
This patch has a slight corruption to it:
In-Reply-To: <1422881149-8177-1-git-send-email-hanjun@linaro.org>
References: <1422881149-8177-1-git-send-email-hanju
Hi,
On Mon, Feb 02, 2015 at 07:58:59PM +0100, Pali Rohár wrote:
> On Monday 02 February 2015 19:54:58 Felipe Balbi wrote:
> > Hi,
> >
> > On Sat, Jan 31, 2015 at 10:53:30AM +0100, Pali Rohár wrote:
> > > This patch adds removable mass storage support to g_nokia
> > > gadget (for N900). It means t
On Mon, Feb 2, 2015 at 2:20 PM, Takashi Iwai wrote:
> we've got a bug report about the mishandling of DVD/CDROM media eject
> button, and it seems indeed broken since some time ago. In short:
> when the eject button is pressed, the media is forcibly ejected no
> matter whether it's mounted or in
On 02/02/2015 11:11 AM, Paul E. McKenney wrote:
> On Tue, Jan 20, 2015 at 09:03:12AM -0500, Peter Hurley wrote:
>> On 01/19/2015 07:30 PM, Paul E. McKenney wrote:
>>> On Tue, Jan 06, 2015 at 12:47:53PM -0800, Paul E. McKenney wrote:
On Tue, Jan 06, 2015 at 02:57:37PM -0500, Peter Hurley wrote:
Quoting Steven Rostedt (2015-02-02 08:00:33)
> On Fri, 30 Jan 2015 16:16:11 -0800
> Stephen Boyd wrote:
>
> > It's useful to have tracepoints around operations that change the
> > hardware state so that we can debug clock hardware performance
> > and operations. Four basic types of events are sup
On 2015-02-02 13:47, Mimi Zohar wrote:
On Mon, 2015-02-02 at 18:08 +, Serge Hallyn wrote:
Quoting Casey Schaufler (ca...@schaufler-ca.com):
I'm game to participate in such an effort. The POSIX scheme
is workable, but given that it's 20 years old and hasn't
developed real traction it's hard
On Monday 02 February 2015 20:01:11 Felipe Balbi wrote:
> Hi,
>
> On Mon, Feb 02, 2015 at 07:58:59PM +0100, Pali Rohár wrote:
> > On Monday 02 February 2015 19:54:58 Felipe Balbi wrote:
> > > Hi,
> > >
> > > On Sat, Jan 31, 2015 at 10:53:30AM +0100, Pali Rohár wrote:
> > > > This patch adds remov
On Mon, 2015-02-02 at 09:12 -0800, Anshul Garg wrote:
> From: Anshul Garg
>
> Unnecessary instructions are executing even though m is
> greater than x so added logic to make m less than equal to
> x before performing these operations.
>
> Signed-off-by: Anshul Garg
> ---
> lib/int_sqrt.c |
On Wednesday 28 January 2015 14:51:23 Marc Zyngier wrote:
> void __weak pcibios_update_irq(struct pci_dev *dev, int irq)
> {
> - dev_dbg(&dev->dev, "assigning IRQ %02d\n", irq);
> - pci_write_config_byte(dev, PCI_INTERRUPT_LINE, irq);
> + struct irq_data *d;
> +
> + d = ir
On Mon, Feb 2, 2015 at 11:00 AM, Linus Torvalds
wrote:
>
> (I'm also not entirely sure what uses int_sqrt() that ends up being so
> performance-critical, so it would be good to document that too, since
> that probably also matters for the "what's the normal argument range"
> question..)
... it's
On 02.02.2015 15:16, Al Viro wrote:
> On Mon, Feb 02, 2015 at 02:36:43PM +0100, Andreas Ruprecht wrote:
>> When running sparse on the osc/ subdirectory, it shows the
>> following warning:
>>
>> andreas@workbox:~/linux-next$ make C=1 M=drivers/staging/lustre/lustre/osc/
>> [...]
>> drivers/staging/l
On Mon, Feb 02, 2015 at 08:07:51PM +0100, Pali Rohár wrote:
> On Monday 02 February 2015 20:01:11 Felipe Balbi wrote:
> > Hi,
> >
> > On Mon, Feb 02, 2015 at 07:58:59PM +0100, Pali Rohár wrote:
> > > On Monday 02 February 2015 19:54:58 Felipe Balbi wrote:
> > > > Hi,
> > > >
> > > > On Sat, Jan 3
401 - 500 of 835 matches
Mail list logo
