ccing some ppl.
On 17 February 2015 at 08:11, Klaus Ethgen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> After three days of bisect I found the bug for my problem with a broken
> suspend on x61p of lenovo.
>
> The problem is commit e11aa36. It seems to be a wrong assumption
Lee Jones writes:
> What's all this? Please configure your mail client correctly.
>
> For advice, see:
>
> Documentation/email-clients.txt
While at day work, I have only access to web mail ...
>> 2) after v2, we _both_ agreed that the accurate name is "cplds"
>> which exactly what is in
On Mon, Feb 16, 2015 at 10:38:18AM +0800, Wang Xiaoming wrote:
> The maximum of SW-IOMMU is limited to 2^11*128 = 256K.
> And the maximum of IO_TLB_DEFAULT_SIZE is limited to (64UL<<20) 64M.
> While in different platform and different requirement this seems improper.
> So modifing the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
After three days of bisect I found the bug for my problem with a broken
suspend on x61p of lenovo.
The problem is commit e11aa36. It seems to be a wrong assumption that
disabling the interrupts is enough.
I'll try to revert the commit on top of
On Mon, Feb 16, 2015 at 09:44:36PM +0100, Peter Zijlstra wrote:
> On Mon, Feb 16, 2015 at 12:52:34PM -0600, Josh Poimboeuf wrote:
> > +++ b/kernel/sched/core.c
> > @@ -1338,6 +1338,23 @@ void kick_process(struct task_struct *p)
> > EXPORT_SYMBOL_GPL(kick_process);
> > #endif /* CONFIG_SMP */
> >
On Mon, Feb 16, 2015 at 01:07:07PM +0200, Boaz Harrosh wrote:
> In any way this is a problem for the new type-12 NvDIMM memory chips that
> are circulating around. (It is estimated that there are already 100ds of
> thousands NvDIMM chips in active use)
Hang on. NV-DIMM chips don't know anyhing
On Sun, Feb 15, 2015 at 3:03 AM, Michal Malý
wrote:
> This patch series improves handling of various Logitech gaming wheels and
> allows switching between various compatibility modes which might be useful
> to improve compatibility with very old games and testing purposes.
>
> Signed-off-by:
On 16/02/2015 7:47 p.m., Philip Rakity wrote:
On Feb 16, 2015, at 5:39 PM, Arend van Spriel wrote:
On 02/16/15 15:25, Adrian Hunter wrote:
I am in the process of adding an ACPI Device Property to specify
the driver strength (aka drive strength, driver type) for use
with eMMC/SD/SDIO cards,
On January 22, 2015 07:58, Lee Jones wrote:
> On Wed, 21 Jan 2015, Jonathan Cameron wrote:
>
> >
> >
> > On 21 January 2015 16:52:50 GMT+00:00, Sebastian Reichel
> wrote:
> > >Hi,
> > >
> > >On Wed, Jan 21, 2015 at 03:46:25PM +, Adam Thomson wrote:
> > >> This patch set adds initial support
On Sun, Feb 15, 2015 at 1:54 PM, Nicholas Krause wrote:
> This changes the structure sta2x11_dma_ops stucture to use
> switolb_dma_supported
> as it's function for dma_supported hardware verus setting this value to NULL
> as
> this should be set correctly for when dma_supported function needs
Maxime Ripard writes:
>> I don't think an mdelay(256) is acceptable.
>
> That's very true that this driver would need some love, but
> valentine's day was last week.
That doesn't cope with the 256ms mdelay. And a potential big mdelay is not what
I'd call a bug fix, see below.
> I'm sorry, but
Fixed a coding style issue (unnecessary parentheses , unnecessary braces)
Signed-off-by: Ameen-Ali
---
kernel/audit.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/kernel/audit.c b/kernel/audit.c
index 72ab759..0607e12 100644
--- a/kernel/audit.c
+++ b/kernel/audit.c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/16/2015 04:09 PM, Borislav Petkov wrote:
> On Fri, Feb 06, 2015 at 03:02:00PM -0500, r...@redhat.com wrote:
>> From: Oleg Nesterov
>> diff --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c
>> index fb4cb6adf225..51c465846f06 100644
Hello Nicholas,
On 03.02.2015 10:37, Nicholas Mc Guire wrote:
scanning for if STATEMENT else STATEMENT triggered here - and it does look
like it needs a fix-up or at least some comments.
The if-else here has no effect and the printk will not convey any information
as its always
> The timestamp kfifo must be cleared once the
> hardware fifo is reset, thus are removed
> timestamps related to unprocessed events from
> hardware fifo - see "inv_mpu6050_read_fifo"
> method implementation.
comments below
a prefix iio: in the subject would be nice
> Signed-off-by: Viorel
On Mon, Feb 16, 2015 at 4:07 PM, Ameen Ali wrote:
> the following attachment which fix kernel code style issues
Please read Documentation/SubmittingPatches in the kernel sources for
information on how to properly format and submit patches for
consideration. Posting patches inline, and not as an
On Fri, Feb 06, 2015 at 03:02:00PM -0500, r...@redhat.com wrote:
> From: Oleg Nesterov
>
> math_error() calls save_init_fpu() after conditional_sti(), this means
> that the caller can be preempted. If !use_eager_fpu() we can hit the
> WARN_ON_ONCE(!__thread_has_fpu(tsk)) and/or save the wrong
The timestamp kfifo must be cleared once the
hardware fifo is reset, thus are removed
timestamps related to unprocessed events from
hardware fifo - see "inv_mpu6050_read_fifo"
method implementation.
Signed-off-by: Viorel Suman
---
drivers/iio/imu/inv_mpu6050/inv_mpu_trigger.c | 28
From: Peter Rosin
Hi!
I wasn't sure if I should add Documentation/* for these sysfs knobs
or not? A lot of knobs do not seem to have docs (no specific example,
just a gut feeling). And I'm not sure how I should name the doc-file
since the pcm512x driver handles devices connected with both i2c
From: Peter Rosin
Hi!
I wasn't sure if I should add Documentation/* for these sysfs knobs
or not? A lot of knobs do not have docs... And I'm not sure how I
should name the doc-file since the pcm512x driver handles devices
connected with both i2c and spi. So, this isn't perfect, suggestions
From: Peter Rosin
When using non-standard rates, a relatively small amount of overclocking
can make a big difference to a number of cases.
- Not all rates are possible to achieve with the PLL, due to divider
restrictions.
- The higher oversampling rates that can be used by the DAC, the
From: Peter Rosin
Signed-off-by: Peter Rosin
---
sound/soc/codecs/pcm512x.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/sound/soc/codecs/pcm512x.c b/sound/soc/codecs/pcm512x.c
index 884784fb1566..f13ff7578c78 100644
---
On Thu, Jun 12 2014 at 10:13am -0400,
Mike Snitzer wrote:
> Hi Linus,
>
> This pull request is later than I'd have liked because I was waiting for
> some performance data to help finally justify sending the long-standing
> dm-crypt cpu scalability improvements upstream. Unfortunately we came
>
Hi Robert,
On Mon, Feb 16, 2015 at 09:11:24PM +0100, Robert Jarzmik wrote:
> Maxime Ripard writes:
>
> > drivers/mtd/nand/pxa3xx_nand.c | 47
> > --
> > 1 file changed, 41 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/mtd/nand/pxa3xx_nand.c
On 02/15/2015 11:48 PM, Ingo Molnar wrote:
Linus,
Please pull the latest perf-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-core-for-linus
# HEAD: a66734297f78707ce39d756b656bfae861d53f62 perf/x86: Add
/sys/devices/cpu/rdpmc=2 to allow
On 02/16/2015 12:36 PM, Stephen Rothwell wrote:
Hi Guenter,
On Mon, 16 Feb 2015 09:12:13 -0800 Guenter Roeck wrote:
On Thu, Feb 16, 2012 at 04:41:44PM +1100, Stephen Rothwell wrote:
Changes since 20120215:
---
[ Trying again, this time hopefully replying to the correct e-mail.
Sorry
Hi,
Le vendredi 13 février 2015 à 18:06 -0800, Vinson Lee a écrit :
> From: Vinson Lee
>
> This patch fixes this build error with glibc < 2.6.
>
> CC util/cloexec.o
> cc1: warnings being treated as errors
> util/cloexec.c: In function ‘perf_flag_probe’:
> util/cloexec.c:24: error:
On 02/14/2015 09:33 AM, Kees Cook wrote:
From: Hector Marco-Gisbert
The issue is that the stack for processes is not properly randomized on 64 bit
architectures due to an integer overflow.
The affected function is randomize_stack_top() in file "fs/binfmt_elf.c":
static unsigned long
On Friday 13 February 2015 10:09:19 Maxime Ripard wrote:
> Hi Arnd,
>
> On Thu, Feb 12, 2015 at 08:42:34PM +0100, Arnd Bergmann wrote:
> > A lot of drivers for mach-sunxi depend on RESET_CONTROLLER. While
> > this is selected for the drivers that have it, we keep running
> > into build errors in
On Mon, Feb 16, 2015 at 12:52:34PM -0600, Josh Poimboeuf wrote:
> +++ b/kernel/sched/core.c
> @@ -1338,6 +1338,23 @@ void kick_process(struct task_struct *p)
> EXPORT_SYMBOL_GPL(kick_process);
> #endif /* CONFIG_SMP */
>
> +/***
> + * sched_task_call - call a function with a task's state
On Mon, Feb 16, 2015 at 8:50 AM, Tommi Kyntola wrote:
>
> It happened in our custom build system. The kernel there doesn't have a
> dependency to the kernel headers and that's pretty much it.
> It's a tiny thing and I already patched our stuff, but I thought I'd let you
> know. Breaching the
Please pull nfsd bugfixes from:
git://linux-nfs.org/~bfields/linux.git for-3.20
These are fixes for two bugs introduced during the merge window.
--b.
Dan Carpenter (1):
nfsd: fix comparison in fh_fsid_match()
J. Bruce
Hi Guenter,
On Mon, 16 Feb 2015 09:12:13 -0800 Guenter Roeck wrote:
>
> On Thu, Feb 16, 2012 at 04:41:44PM +1100, Stephen Rothwell wrote:
> >
> > Changes since 20120215:
> ---
> [ Trying again, this time hopefully replying to the correct e-mail.
> Sorry for the earlier noise. ]
Did you
On Fri, Jan 30, 2015 at 9:41 PM, Ohad Ben-Cohen wrote:
[..]
> Since the existence of several hwblocks is still fictional (Bjorn,
> please confirm too?), we may prefer to introduce changes to support it
> only when it shows up; it all depends on the amount of changes needed.
> Suman, care to take
On Fri, Feb 06, 2015 at 03:01:59PM -0500, r...@redhat.com wrote:
> From: Oleg Nesterov
>
> unlazy_fpu()->__thread_fpu_end() doesn't look right if use_eager_fpu().
> Unconditional __thread_fpu_end() is only correct if we know that this
> thread can't return to user-mode and use FPU.
>
>
Hi Fabio,
> Fabio Estevam hat am 12. Februar 2015 um 20:08
> geschrieben:
>
>
> Hi Stefan,
>
> On Thu, Feb 12, 2015 at 4:59 PM, Stefan Wahren wrote:
> > Hi Fabio,
> >
> >> Fabio Estevam hat am 11. Februar 2015 um 22:10
> >> geschrieben:
> >>
> >>
> >> On Wed, Feb 11, 2015 at 6:31 PM, Stefan
If the CPU is running a realtime task that does not round-robin with
another realtime task of equal priority, there is no point in keeping
the scheduler tick going. After all, whenever the scheduler tick runs,
the kernel will just decide not to reschedule.
Extend sched_can_stop_tick to recognize
On Mon, Feb 16, 2015 at 2:01 AM, Adrian Hunter wrote:
> On 11/02/15 01:42, Stephane Eranian wrote:
>> This is a standalone JVMTI library to help profile Java jitted
>> code with perf record/perf report. The library is not installed
>> or compiled automatically by perf Makefile. It is not used
>>
On Mon, 16 Feb 2015 21:12:40 +0100
Richard Cochran wrote:
> On Mon, Feb 16, 2015 at 12:18:22PM +0100, Sebastian Andrzej Siewior wrote:
> > - CPU hotplug works in general. Steven's test script however
> > deadlocks usually on the second invocation.
>
> Where can I find Steve's
Randy
On Tue, Feb 10, 2015 at 02:50:47PM -0800, Randy Dunlap wrote:
> On 02/09/15 13:34, Eduardo Valentin wrote:
> > This change introduces a section in the Introduction Chapter to
> > list concepts used by the Thermal Framework.
> >
> > Signed-off-by: Eduardo Valentin
> > ---
> >
It is absolutely not clear why attach_to_pi_owner() returns -EAGAIN which
triggers "retry" if the lock owner is PF_EXITING but not PF_EXITPIDONE.
This burns CPU for no reason and this can even livelock if the rt_task()
caller preempts a PF_EXITING owner.
Remove the PF_EXITING check altogether. We
On 02/02, Oleg Nesterov wrote:
>
> And another question. Lets forget about this ->mm check. I simply can not
> understand this
>
> ret = (p->flags & PF_EXITPIDONE) ? -ESRCH : -EAGAIN
>
> logic in attach_to_pi_owner(). First of all, why do we need to retry if
> PF_EXITING is set but
On Tue, Feb 10, 2015 at 02:50:36PM -0800, Randy Dunlap wrote:
> On 02/09/15 13:34, Eduardo Valentin wrote:
>
> > +
> > + Introduction
> > + Thermal management is any method or technique implied to
> > + mitigate emergencies caused by operating devices within
> > +
On Mon, Feb 16, 2015 at 12:18:22PM +0100, Sebastian Andrzej Siewior wrote:
> - CPU hotplug works in general. Steven's test script however
> deadlocks usually on the second invocation.
Where can I find Steve's hotplug test script?
Thanks,
Richard
--
To unsubscribe from this list:
Maxime Ripard writes:
> drivers/mtd/nand/pxa3xx_nand.c | 47
> --
> 1 file changed, 41 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/mtd/nand/pxa3xx_nand.c b/drivers/mtd/nand/pxa3xx_nand.c
> index 96b0b1d27df1..b2d8d6960765 100644
> ---
Hi Tony,
On 16 Feb 2015 18:10, Tony Lindgren wrote:
* Robert ABEL [150216 07:52]:
GPMC uses GPMCFCLKDIVIDER during synchronous as well as asynchronous accesses
in conjunction with WAITMONITORINGTIME. Thus, it's wrong to only program it for
synchronous accesses. Remove the conditional.
Do you
On Mon, 16 Feb 2015 11:24:03 -0800
Linus Torvalds wrote:
> On Mon, Feb 16, 2015 at 10:46 AM, Linus Torvalds
> wrote:
> >
> > This code is so broken that my initial reaction is "We need to just
> > revert the crap".
Sure, no problem reverting the lock counters. They were an optional
thing
Hi,
on my VPN server (strongswan-5.2.2 + ppp-2.4.7 + xl2tpd-1.3.6) I am
seeing the following errors since linux-3.18 when a client (roadwarrior)
connects (this is not fixed in linux-3.19.0):
> Feb 16 20:36:08 vpn1 kernel: [ 90.265403] ppp0: hw csum failure
> Feb 16 20:36:08 vpn1 kernel: [
One quick patch so that building the DocBook documentation works again...
Thanks,
jon
The following changes since commit
1fa185ebcbcefdc5229c783450c9f0439a69f0c1:
Merge tag 'cris-for-3.20' of
git://git.kernel.org/pub/scm/linux/kernel/git/jesper/cris (2015-02-15 18:02:02
-0800)
are
On Sat, Jan 17, 2015 at 6:26 PM, Ben Hutchings wrote:
> chown() and write() should clear all privilege attributes on
> a file - setuid, setgid, setcap and any other extended
> privilege attributes.
>
> However, any attributes beyond setuid and setgid are managed by the
> LSM and not directly by
The National Instruments USB Host-to-Host Cable is based on the Prolific
PL-25A1 chipset. Add its VID/PID so the plusb driver will recognize it.
Signed-off-by: Ben Shelton
---
drivers/net/usb/plusb.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/net/usb/plusb.c
On Mon, Feb 16, 2015 at 12:25:04PM -0700, Jonathan Corbet wrote:
> On Mon, 16 Feb 2015 16:21:30 +
> Alan Cox wrote:
>
> > > This warning started to appear on Linus's tree, after staging pull
> > > request was merged.
> >
> > I sent GregKH a fix for it a while ago
>
> He seemed to
On Mon, Feb 16, 2015 at 12:25:04PM -0700, Jonathan Corbet wrote:
> On Mon, 16 Feb 2015 16:21:30 +
> Alan Cox wrote:
>
> > > This warning started to appear on Linus's tree, after staging pull
> > > request was merged.
> >
> > I sent GregKH a fix for it a while ago
>
> He seemed to
On Mon, Feb 16, 2015 at 11:27:42AM -0800, Kees Cook wrote:
> > Well, we can apply the rule of the last setting sticks and since the
> > kernel is always going to be adding the last setup_data element of
> > type SETUP_KASLR (the boot loader ones will be somewhere on the list
> > in-between and we
Looks good.
Acked-By: James Smart
-- james
On 1/26/2015 10:18 AM, Thadeu Lima de Souza Cascardo wrote:
Without a shutdown handler, some cards behave very badly after a kexec.
During probe, pending DMA writes will corrupt kernel memory, for
example.
Using the remove handler guarantees we
On Monday 16 February 2015 12:51:35 Rich Felker wrote:
> On Mon, Feb 16, 2015 at 06:20:18PM +0100, Arnd Bergmann wrote:
> > > Would it really be that hard to do:
> > >
> > > if (ILP32_on_64_process) tv_nsec = (int)tv_nsec;
> > >
> > > or similar? That's all that's needed.
> > >
> > > > In
On Mon, Feb 16, 2015 at 03:57:55PM +0800, Peter Hung wrote:
> The F81232 bulk-in is RX data + LSR channel, data format is
> [LSR+Data][LSR+Data]. , We had reimplemented in this patch.
>
> Signed-off-by: Peter Hung
> ---
> drivers/usb/serial/f81232.c | 68
>
On Mon, Feb 16, 2015 at 09:27:09AM -0700, Joseph Kogut wrote:
> It seems that the Synopsys vendor ID is used in usb/dwc2 as well, and
> the rest of the definitions aren't referenced outside of usb/dwc3.
> Would the proper approach be to move the Synopsys vendor ID to
> linux/pci_ids.h, remove the
On Mon 2015-02-16 10:11:13, Jiang Liu wrote:
> Commit b568b8601f05 ("Treat SCI interrupt as normal GSI interrupt")
> accidently removes support of legacy PIC interrupt when fixing a
accidentaly?
> regression for Xen, which causes a nasty regression on HP/Compaq
> nc6000 where we fail to register
On Mon, Feb 16, 2015 at 03:25:28PM +0800, Fengguang Wu wrote:
> Hi Paul,
>
> FYI, this may be very hard to reproduce.
Indeed, I have not seen it.
But was this on a CONFIG_PREEMPT=n kernel?
Thanx, Paul
>
Okay, thanks for your patience with my lack of understanding. I'll work with
Hariprasad tomorrow to get a revised patch out with the "const" change and
eliminate the redundant check of CH_PCI_DEVICE_ID_TABLE_DEFINE_BEGIN to guard
the file contents. Thanks for caching these improvements!
> Adds optimization of i2c transactions in trigger handler and
> usage of available_scan_masks for bmg160.
same concerns as with bmc150 and kxcjk-1013
> Changes in v2:
> - fallback to i2c word transactions if i2c block transactions are not
> supported
> - use available_scan_masks to let the
On Mon, Feb 16, 2015 at 3:55 AM, Borislav Petkov wrote:
> On Fri, Feb 13, 2015 at 03:25:26PM -0800, Kees Cook wrote:
>> No, no; I agree: a malicious boot loader is a lost cause. I mean
>> mostly from a misbehavior perspective. Like, someone sees "kaslr" in
>> the setup args and thinks they can
Hello Gioh,
Thank you for your answer.
On 14/02/15 10:40, Gioh Kim wrote:
>>
>> If this tracer is justifiable, I think that making it conditional is
>> better than just enabling always on CONFIG_CMA_DEBUGFS. Some users
>> don't want to this feature although they enable CONFIG_CMA_DEBUGFS.
>>
>>
> Adds optimization of i2c transactions in trigger handler and
> usage of available_scan_masks for bmc150-accel.
same comments as for kxcjk-1013, this changes the capabilities of the
driver
> Irina Tirdea (2):
> iio: accel: bmc150: use available_scan_masks
> iio: accel: bmc150: optimize
Hello SeongJae,
On 13/02/15 17:18, SeongJae Park wrote:
> Hello, Stefan.
>
> On Fri, 13 Feb 2015, Stefan Strogin wrote:
>
>> #include
>> +#include
>> +#include
>> +#include
>
> Looks like `proc_fs.h` and `time.h` are not necessary.
>
Yes, of course. Thanks.
>> +pr_warn("%s(page
On 02/16/15 16:32, Will Deacon wrote:
> Hi Chris,
>
> On Sun, Feb 15, 2015 at 11:17:19AM +, Chris Clayton wrote:
>> When running "make oldconfig" for an x86_64 kernel, I was prompted for a
>> setting for IOMMU_IO_PGTABLE_LPAE. From the prompt and the help text it
>> appears that this config
The seq_printf return value will eventually be converted to void.
Convert the remaining uses by hand.
Signed-off-by: Joe Perches
---
drivers/staging/lustre/lustre/llite/lproc_llite.c | 34 +---
.../lustre/lustre/obdclass/lprocfs_status.c| 94 +++---
2 files
The seq_printf return value will eventually be converted to void.
Convert these uses to:
seq_printf(seq, ...);
return seq_has_overflowed(seq);
Done via cocci script:
@@
struct seq_file *seq;
@@
- return
\(seq_printf\|seq_puts\|seq_putc\)(seq,
...);
+
On Mon, 16 Feb 2015 16:21:30 +
Alan Cox wrote:
> > This warning started to appear on Linus's tree, after staging pull
> > request was merged.
>
> I sent GregKH a fix for it a while ago
He seemed to indicate that he doesn't have it. The following would seem
to fit the bill; unless
seq_printf should eventually be converted to a void function.
Remove the uses of seq_printf return values and use seq_has_overflowed()
instead.
Joe Perches (3):
staging: lustre: Convert return seq_printf(...) uses to seq_has_overflowed
staging: lustre: Convert uses of "int rc =
The seq_printf return value will eventually be converted to void.
Convert these uses to:
seq_printf(seq, ...);
return seq_has_overflowed(seq);
Done via cocci script:
@@
struct seq_file *seq;
int i;
@@
- i = seq_printf(seq,
+ seq_printf(seq,
...);
> Reading all axis values in one i2c transfer reduces the delays
> introduced by the i2c bus. In case i2c block read is not supported,
> fallback to reading each axis as a separate word.
see comments inline below
> Signed-off-by: Adriana Reus
> Signed-off-by: Irina Tirdea
> Reviewed-by:
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
suspend-to-idle-3.20-rc1
to receive changes adding support for quiescing timers during suspend-to-idle
for v3.20-rc1 with top-most commit c7fb90dfbef49b03e6f3fd6a32338e59cbcf34ee
ACPI / idle:
On Mon, Feb 16, 2015 at 10:46 AM, Linus Torvalds
wrote:
>
> This code is so broken that my initial reaction is "We need to just
> revert the crap".
How the hell is flock_lock_file() supposed to work at all, btw?
Say we have an existing flock, and now do a new one that conflicts. I
see what
On 13/02/15 06:10, Joonsoo Kim wrote:
>> @@ -28,4 +28,13 @@ extern int cma_init_reserved_mem(phys_addr_t base,
>> struct cma **res_cma);
>> extern struct page *cma_alloc(struct cma *cma, int count, unsigned int
>> align);
>> extern bool cma_release(struct
On Mon, 2015-02-16 at 19:07 +, Casey Leedom wrote:
> I understand that OS-independence issues aren't something which are
> normally accommodated, but as long as definitions don't introduce
> unnecessary "foreign intrusion" I would hope that it would be okay.
> As I noted, our t4_regs.h file
When reading blkio.throttle.io_serviced in a recently created blkio
cgroup, it's possible to race against the creation of a throttle policy,
which delays the allocation of stats_cpu.
Like other functions in the throttle code, just checking for a NULL
stats_cpu prevents the following oops caused
> Adds optimization of i2c transactions in trigger handler and
> usage of available_scan_masks for kxcjk-1013.
the 'optimization' changes the capabilities of the driver, reading
individual channel is not possible anymore
> Adriana Reus (2):
> iio: accel: kxcjk-1013: use available_scan_masks
On Mon, Feb 16, 2015 at 7:49 PM, Anshul Garg wrote:
> From: Anshul Garg
>
> Remove unnecessary increment and decrement operation
> in dentry_name function as after increment operation
> loop is breaked and then decrement operation is
> performed. So remove increment and decrement operation
>
Hello,
On 13/02/15 06:10, Joonsoo Kim wrote:
> On Fri, Feb 13, 2015 at 01:15:41AM +0300, Stefan Strogin wrote:
>
> This linear searching make cma_release() slow if we have many allocated
> cma buffers. It wouldn't cause any problem?
>
> Thanks.
>
>
On my board the usual number of CMA buffers
On Mon, Feb 16, 2015 at 10:11:13AM +0800, Jiang Liu wrote:
> Commit b568b8601f05 ("Treat SCI interrupt as normal GSI interrupt")
> accidently removes support of legacy PIC interrupt when fixing a
> regression for Xen, which causes a nasty regression on HP/Compaq
> nc6000 where we fail to register
I understand that OS-independence issues aren't something which are normally
accommodated, but as long as definitions don't introduce unnecessary "foreign
intrusion" I would hope that it would be okay. As I noted, our t4_regs.h file
is also OS-independent and used by six other OS device
On 02/16/2015 01:30 PM, Peter Hurley wrote:
> On 02/16/2015 12:16 PM, Petr Tesarik wrote:
>> On Mon, 16 Feb 2015 11:24:16 -0500
>> Peter Hurley wrote:
>>> On 02/16/2015 08:22 AM, Petr Tesarik wrote:
On Mon, 16 Feb 2015 08:04:02 -0500
Peter Hurley wrote:
> On 02/05/2015 02:11 PM,
On Fri, 13 Feb 2015 16:19:35 -0600
Chris J Arges wrote:
> Documentation/vm/slub.txt | 12 ++--
> 1 file changed, 6 insertions(+), 6 deletions(-)
This one has been applied to the docs tree, thanks.
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
Reading /proc//stack for a running task can show garbage. Use the
new safe version of the stack saving interface. For running tasks
(other than current) it won't show anything.
Signed-off-by: Josh Poimboeuf
---
fs/proc/base.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi Arend,
first of all, thank you for your answer.
I'm very sorry to hear that negative feedback.
So, AFAIU, there is no support in brcmsmac for regdom and power
settings.
I don't know how much Broadcom Corp. is complaint with IEEE Standard
802.11-2007 (page 531), along that decision.
Missing
Hello Joonsoo,
Thank you for your answer.
On 13/02/15 06:03, Joonsoo Kim wrote:
> On Fri, Feb 13, 2015 at 01:15:40AM +0300, Stefan Strogin wrote:
>>
>> Here is an example use case when we need it. We want a big (megabytes)
>> CMA buffer to be allocated in runtime in default CMA region. If
Reading /proc//stack for a running task (other than current) can print
garbage because the saved stack pointer is no longer accurate and the stack
itself can be inconsistent.
Add new sched and stacktrace functions so that /proc//stack only walks the
stack for sleeping tasks and the current task.
It isn't possible to get the stack of a running task (other than
current) because we don't have the stack pointer and the stack can be
inconsistent anyway. Add a safe stack saving facility which only saves
the stack of the task if it's sleeping or if it's the current task.
Suggested-by: Jiri
Add a sched_task_call() to allow a callback function to be called with
the task's rq locked. It guarantees that a task remains either active
or inactive during the function call, without having to expose rq
locking details outside of the scheduler.
Signed-off-by: Josh Poimboeuf
---
On Monday, February 16, 2015 01:14:35 PM Peter Zijlstra wrote:
> Hi,
>
> While working with Rafael on the suspend to idle machinery Thomas made these
> cleanups; since one might as well clean code up while you've done the work of
> thinking through it again.
>
> As it stands there's very little
From: Anshul Garg
Remove unnecessary increment and decrement operation
in dentry_name function as after increment operation
loop is breaked and then decrement operation is
performed. So remove increment and decrement operation
from the function.
Signed-off-by: Anshul Garg
---
lib/vsprintf.c |
On 02/16/2015 10:45 AM, Heinrich Schuchardt wrote:
I am resending this mail because the linux-kernel list was not CCed.
Yes, sorry, that got lost. The "forward" feature on lkml.org doesn't work
as well as it used to, unfortunately, and I keep forgetting.
On 16.02.2015 19:23, Guenter Roeck
From: Anshul Garg
While converting string representation to integer
break the loop if overflow is detected.
Signed-off-by: Anshul Garg
---
lib/kstrtox.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/lib/kstrtox.c b/lib/kstrtox.c
index ec8da78..6f30209 100644
---
On Mon, Feb 16, 2015 at 6:00 AM, Jeff Layton wrote:
>
> I'll look at it again and also see if I can reproduce it with trinity.
> So far, I haven't been able to, but maybe I'll get lucky this time.
Can you please also remove the completely broken counters?
The f*ckers aren't even initialized,
I am resending this mail because the linux-kernel list was not CCed.
On 16.02.2015 19:23, Guenter Roeck wrote:
> On Mon, Feb 16, 2015 at 07:00:44PM +0100, Heinrich Schuchardt wrote:
>> PAGE_SIZE is not guaranteed to be equal to or less than 8 times the
>> THREAD_SIZE.
>>
>> E.g. architecture
On Monday, February 16, 2015 01:14:42 PM Peter Zijlstra wrote:
> From: Thomas Gleixner
>
> clockevents_notify() is a leftover from the early design of the
> clockevents facility. It's really not a notification mechanism, it's a
> multiplex call.
>
> We are way better off to have explicit calls
Various build/boot bots have reported WARNs being triggered by the ARM
iopgtable LPAE self-tests on i386 machines.
This boils down to two instances of right-shifting a 32-bit unsigned
long (i.e. an iova) by more than the size of the type. On 32-bit ARM,
this happens to give us zero, hence my
On Mon, 16 Feb 2015 19:22:38 +0100
Frederic Weisbecker wrote:
> Huang Ying hasn't yet reported a Tested-by but I could reproduce (with both
> function and function_graph tracers btw)
> and the patch fixed it.
Ah right, it's not the recursion from the function tracer that kills
us, it's the
301 - 400 of 1560 matches
Mail list logo
