On 07/02/2015 11:41 AM, Peter Zijlstra wrote:
> On Wed, Jul 01, 2015 at 02:54:59PM -0700, Linus Torvalds wrote:
>> On Tue, Jun 30, 2015 at 10:57 PM, Daniel Wagner wrote:
>>>
>>> And an attempt at visualization:
>>>
>>> http://monom.org/posix01/sweep-4.1.0-02756-ge3d06bd.png
>>>
On Sat, Jul 18, 2015 at 11:59:34AM +0200, Guillaume Bienkowski wrote:
> Signed-off-by: Guillaume Bienkowski
> ---
> drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
>
G'Day Masami-san, Namhyung,
I'm really looking forward to this feature -- very useful, thanks!...
On Sat, Jul 18, 2015 at 9:24 PM, Namhyung Kim wrote:
> Hi Masami,
>
> On Fri, Jul 17, 2015 at 12:21:42PM +0900, Masami Hiramatsu wrote:
>> Now I'm thinking that we should avoid using %event syntax
Johannes Berg writes:
> And while at it, please use links that include the message-id (e.g.
> mid.gmane.org) so it's searchable even if the archive disappears.
BTW, I recently found out that kernel.org has a this type of service as
well. From https://lkml.kernel.org/:
http://lkml.kernel.org/r/
On Sat, Jul 18, 2015 at 08:03:27PM +0200, Jakub Sitnicki wrote:
> On Sat, Jul 18, 2015 at 06:46 AM CEST, Sudip Mukherjee
> wrote:
> > On Fri, Jul 17, 2015 at 05:33:55PM +0200, Jakub Sitnicki wrote:
> >> On Thu, Jul 16, 2015 at 01:28 PM CEST, Sudip Mukherjee
> >> wrote:
> >> > Stop using
Hi all,
Changes since 20150717:
The cris tree gained a conflict against Linus' tree.
The sound-asoc tree still had its build failure for which I applied
a patch.
I applied 2 patches to the regmap merge for warnings from an API change.
The akpm-current tree gained a conflict against Linus'
hi, Rafael
thanks for your reply :)
On 2015年07月18日 08:34, Rafael J. Wysocki wrote:
> On Tuesday, July 14, 2015 10:52:35 AM Pan Xinhui wrote:
>> hi, Rafael,
>> let me do more explanation :)
>>
>> On 2015年07月14日 10:09, Pan Xinhui wrote:
>>> hi, Rafael,
>>> thanks for you reply :)
Ping?
On 06/23/2015 08:53 AM, Juergen Gross wrote:
This series adds XEN guest pvUSB support. With pvUSB it is possible to
use physical USB devices from a XEN domain.
The support consists of a frontend in form of a virtual hcd driver in
the unprivileged domU passing I/O-requests to the backend
Hello Andrew/Mark/Goldwyn,
The doc describes OCFS2 online file check feature, which is added by the last
suggestion when I submitted a few online file check code patches.
Online file check patches link:
https://oss.oracle.com/pipermail/ocfs2-devel/2015-June/010886.html
Add a check for the existence of input files and exit (with failure)
if they are missing.
Without this additional check, missing files produce error messages
but still result in an output file being generated and a successful
exit code.
Signed-off-by: Sam Bobroff
---
The current behaviour (of
This document will describe OCFS2 online file check feature.
OCFS2 is often used in high-availaibility systems. However, OCFS2 usually
converts the filesystem to read-only on errors. This may not be necessary, since
turning the filesystem read-only would affect other running processes as well,
Code will fail to be compiled, once it is merged the patch
5ed0a999616a050af1268a99cc442fd0824a2b07(Define kallsyms_cmp_symbol_t
as function type to simplify the code).
The root cause which fails to compile is I included the linux/module.h
head file to linux/kallsyms.h. Now I write the patch to
Pixcir_i2c_tsc driver can now wakeup the system from lower power state
via pinctrl and IO daisy chain using generic wakeirq framwework. Add
optional wakeup irq entry to allow pixcir_i2c_tsc to wake system from
low power state.
Signed-off-by: Vignesh R
---
v2:
* Add interrupt-names property
On am437x-gp-evm, pixcir_i2c_tsc can wake-up system from low power
state via pinctrl and IO daisy chain mechanism. This patch series add
support for such optional wake up interrupt to be handled via recently
introduced generic wake irq handling framework.
Tested on am437x-gp-evm, with some out
On am437x-gp-evm, pixcir touchscreen can wake the system from low power
state by generating wake-up interrupt via pinctrl and IO daisy chain.
Add support for optional wakeup interrupt source by regsitering to
automated wake IRQ framework introduced by commit 4990d4fe327b ("PM /
Wakeirq: Add
Hi Dmitry,
On 7/18/2015 3:21 AM, Dmitry Torokhov wrote:
> Hi Vignesh,
>
> On Fri, Jul 17, 2015 at 12:10:40PM +0530, Vignesh R wrote:
>> On am437x-gp-evm, pixcir touchscreen can wake the system from low power
>> state by generating wake-up interrupt via pinctrl and IO daisy chain.
>> Add support
On 2015/07/19 19:16, Namhyung Kim wrote:
> On Wed, Jul 15, 2015 at 06:15:30PM +0900, Masami Hiramatsu wrote:
>> Allow user to set group name for adding new event.
>> Note that this can easily shot yourself in the foot.
>> E.g. Existing group name can conflict with other events.
>> Especially,
On Mon, Jul 20, 2015 at 05:42:38AM +0200, Mike Galbraith wrote:
> On Mon, 2015-07-20 at 09:34 +0900, Byungchul Park wrote:
>
> > yes, i also think that a preemption granularity has little meaning, atually
> > because of tick granularity.
>
> See HR_TICK. It's not cheap though, why it's default
This patch provides 2 things:
1. Add new control called shrink_memory in /proc/sys/vm/.
This control can be used to aggressively reclaim memory system-wide
in one shot from the user space. A value of 1 will instruct the
kernel to reclaim as much as totalram_pages in the system.
Example: echo 1 >
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/x86/Kconfig
between commit:
5aaeb5c01c5b ("x86/fpu, sched: Introduce
CONFIG_ARCH_WANTS_DYNAMIC_TASK_STRUCT and use it on x86")
from Linus' tree and commit:
caf50fadb4de ("mm: send one IPI per CPU to
On 07/19/2015 07:17 PM, Rasmus Villemoes wrote:
> Last year, Sasha Levin suggested adding wrappers for the
> __builtin_*_overflow functions introduced with gcc 5.1 (based on
> similar, but type-specific, functions in clang). This is another
> attempt at providing such wrappers and fallback code
Hi all,
On Fri, 17 Jul 2015 14:25:01 +1000 Stephen Rothwell
wrote:
>
> After merging the sound-asoc tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> sound/soc/sti/sti_uniperif.c: In function 'sti_uniperiph_dai_suspend':
> sound/soc/sti/sti_uniperif.c:81:2: error:
On Mon, 2015-07-20 at 09:34 +0900, Byungchul Park wrote:
> yes, i also think that a preemption granularity has little meaning, atually
> because of tick granularity.
See HR_TICK. It's not cheap though, why it's default off.
-Mike
--
To unsubscribe from this list: send the line
hi, tglx
thanks for your reply.
On 2015年07月17日 22:50, Thomas Gleixner wrote:
> On Tue, 14 Jul 2015, Pan Xinhui wrote:
>> If pmd or pud is not set, we may set a wrong page mapping level.
>
> No. The behaviour is simply undefined, if the return value of the
> function is NULL.
>
> So what
On 07/19/2015 12:07 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.1.3 release.
There are 65 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
On 2015/07/19 19:46, Namhyung Kim wrote:
> On Wed, Jul 15, 2015 at 06:15:37PM +0900, Masami Hiramatsu wrote:
>> perf buildid-cache --add scans given binary and add
>> the SDT events to probe cache. It is possible to use the cached
>> SDT events as other cached events (perf probe :=).
>
> That
On 07/19/2015 12:10 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.0.9 release.
There are 58 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
On 2015/07/19 19:53, Namhyung Kim wrote:
> On Wed, Jul 15, 2015 at 06:15:44PM +0900, Masami Hiramatsu wrote:
>> To improbe usability, support %[PROVIDER:]SDTEVENT format to
>> add new probes on SDT and cached events.
>
> Ah, you meant we can skip the provider if the event name is unique..
Right,
Hi Paul,
On Sat, 18 Jul 2015 15:41:51 -0400 Paul Gortmaker
wrote:
>
> I noticed there are a bunch of new (appeared in the last day or two)
> fails spread around, so I did a triage/bisect of them so we have a
> better idea of what is going on as we start the week.
Thanks for this. Lets hope
On Fri, Jul 17, 2015 at 03:06:18PM +0300, Roger Quadros wrote:
> >> +
> >> +/**
> >> + * OTG FSM ops function to start/stop host
> >> + */
> >> +static int usb_otg_start_host(struct otg_fsm *fsm, int on)
> >> +{
> >> + struct otg_data *otgd = container_of(fsm, struct otg_data, fsm);
> >> +
Acked-by: Ian Munsie
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Sun, 2015-07-19 at 22:53 +0530, Vaishali Thakkar wrote:
> Macro DEFINE_PCI_DEVICE_TABLE is deprecated. So, here use
> struct pci_device_id instead of DEFINE_PCI_DEVICE_TABLE with
> the goal of getting rid of this macro completely.
>
> The Coccinelle semantic patch that performs this
在 2015/7/15 20:16, Marc Zyngier 写道:
> With the msi_list and the msi_domain properties now being at the
> generic device level, it is starting to be relatively easy to offer
> a generic way of providing non-PCI MSIs.
>
[...]
> diff --git a/include/linux/msi.h b/include/linux/msi.h
> index
Commit 0c8c0f03e3a2 ("x86/fpu, sched: Dynamically allocate 'struct fpu'")
moved the thread_struct to the bottom of task_struct. As a result, the
offset is now too large to be used in an immediate add on arm64 with
some kernel configs:
arch/arm64/kernel/entry.S: Assembler messages:
On Fri, Jul 17, 2015 at 01:47:12PM +0300, Roger Quadros wrote:
> >> + * DRD mode hardware Inputs
> >> + *
> >> + * @id: TRUE for B-device, FALSE for A-device.
> >> + * @vbus: VBUS voltage in regulation.
> >> + *
> >> * OTG hardware Inputs
> >> *
> >> *Common inputs for A
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
git://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs-next.git master
commit 085db2c04557d31db61541f361bd8b4de92c9939
Author: Eric W. Biederman
AuthorDate: Fri Jul 10 18:15:06 2015 -0500
Commit:
The current code tracks the assigned CPUs within a NUMA node in the context of
the primary channel. So, if we have a VM with a single NUMA node with 8 VCPUs,
we may
end up unevenly distributing the channel load. Fix the issue by tracking
affiliations
globally.
Signed-off-by: K. Y. Srinivasan
From: Viresh Kumar
Migrate hv driver to the new 'set-state' interface provided by
clockevents core, the earlier 'set-mode' interface is marked obsolete
now.
This also enables us to implement callbacks for new states of clockevent
devices, for example: ONESHOT_STOPPED.
Cc: "K. Y. Srinivasan"
From: Dexuan Cui
Keep track of CPU affiliations of sub-channels within the scope of the primary
channel. This will allow us to better distribute the load amongst available
CPUs.
Signed-off-by: Dexuan Cui
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel_mgmt.c | 20
From: Christopher Oo
Fixes a bug where previously hv_ringbuffer_read would pass in the old
number of bytes available to read instead of the expected old read index
when calculating when to signal to the host that the ringbuffer is empty.
Since the previous write size is already saved, also
The current Hyper-V clock source is based on the per-partition reference counter
and this counter is being accessed via s synthetic MSR -
HV_X64_MSR_TIME_REF_COUNT.
Hyper-V has a more efficient way of computing the per-partition reference
counter value that does not involve reading a synthetic
In addition to a bug fix and some improvements to the way we distribute channel
load amongst available CPUs, this patch set also includes an implementation of
a clocksource based on the TSC page that Hyper-V supports.
Christopher Oo (1):
Drivers: hv_vmbus: Fix signal to host condition
Dexuan
Hi Nariman,
On Fri, 17 Jul 2015 15:09:26 +0100 Nariman Poushin
wrote:
>
> Introduced by:
> commit 8019ff6cfc04
> ("regmap: Use reg_sequence for multi_reg_write / register_patch")
>
> Interacting with:
> commit 561629755a21 ("mfd: arizona: Add support for WM8998 and WM1814")
> commit
On 07/19/2015 01:25 PM, Rasmus Villemoes wrote:
On Sun, Jul 19 2015, Guenter Roeck wrote:
On Sun, Jul 19, 2015 at 02:20:14PM +0200, Sowmini Varadhan wrote:
Using a 64 bit constant generates "warning: integer constant is too
large for 'long' type" on 32 bit platforms. Instead use ~0l to get
We were mandated to seek the heir to an investor, I believe you are
the heir, reply to this message with your full name and age,cell for
comprehensive details.
Mr. Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6f957724b94cb19f5c1c97efd01dd4df8ced323c
>>
>
> Certainly looks like a plausible solution, will build kernel tonight to
> confirm.
Just to confirm; 4.2rc1 + above patch, and 4.2rc2 both function correctly
and I no
hi, Rafael
thanks for your nice work :)
On 2015年07月18日 09:14, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> acpi_processor_unregister_performance() actually doesn't use its
> first argument, so drop it and update the callers accordingly.
>
> Signed-off-by: Rafael J. Wysocki
>
This patch add the generi devfreq cooling device for generic thermal framework.
The devfreq devices are used ad cooling device to reduce the overheating
temperature. This patch is based on drivers/thermal/cpu_cooling.c. The devfreq
cooling device can change the ragne of the frequency table of
This patch add simply the protoptye of update_devfreq() to devfreq.h header
file to export it. The some device driver (e.g., thermal cooling device) may
use the update_devfreq() to update the range of supported frequency of devfreq
device.
Cc: MyungJoo Ham
Cc: Kyungmin Park
Signed-off-by:
This patchset introduce the generic devfreq cooling device for generic thermal
framework. The devfreq devices are used ad cooling device to reduce the
overheating temperature. This patch is based on drivers/thermal/cpu_cooling.c.
The devfreq cooling device can change the ragne of the frequency
There is no need to save FS and non-lazy GS outside the 32-bit regs. Lazy GS
still needs to be saved because it wasn't saved on syscall entry. Save it in
the gs slot of regs32, which is present but unused.
Signed-off-by: Brian Gerst
---
arch/x86/include/asm/processor.h | 2 --
Allocate a separate structure for the vm86 fields.
Signed-off-by: Brian Gerst
---
arch/x86/include/asm/processor.h | 9 ++--
arch/x86/include/asm/vm86.h | 8 +++
arch/x86/kernel/process.c| 7 ++
arch/x86/kernel/vm86_32.c| 47
There is no legitimate reason for usermode to modify the orig_ax field on
entry to vm86 mode, so copy it from the 32-bit regs.
Signed-off-by: Brian Gerst
---
arch/x86/kernel/vm86_32.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/kernel/vm86_32.c b/arch/x86/kernel/vm86_32.c
Move the userspace accesses down into the common function in preparation for
the next set of patches. Also change to copying the fields explicitly instead
of assuming a fixed order in pt_regs and the kernel data structures.
Signed-off-by: Brian Gerst
---
arch/x86/include/asm/processor.h | 2
Change to use the normal pt_regs area to enter and exit vm86 mode. This is
done by increasing the padding at the top of the stack to make room for the
extra vm86 segment slots in the IRET frame. It then saves the 32-bit regs
in the off-stack vm86 data, and copies in the vm86 regs. Exiting back
Now there is no vm86-specific data left on the kernel stack while in
userspace, except for the 32-bit regs.
Signed-off-by: Brian Gerst
---
arch/x86/include/asm/vm86.h | 25 +---
arch/x86/kernel/vm86_32.c | 93 +++--
2 files changed, 41
Move the non-regs fields to the off-stack data.
Signed-off-by: Brian Gerst
---
arch/x86/include/asm/vm86.h | 16
arch/x86/kernel/vm86_32.c | 42 ++
2 files changed, 30 insertions(+), 28 deletions(-)
diff --git
The goal of this set of patches is to change vm86 support to return to
userspace with the normal exit paths instead of leaving data on the kernel
stack and jumping directly into the exit asm routines. This fixes issues
like ptrace and syscall auditing not working with vm86, and makes possible
[http://blogs-images.forbes.com/tomiogeron/files/2012/10/Stripe-logo.jpeg]
Hello,
Thank you for being a valued Stripe User! According to our records, Your Stripe
Account Needs to
be updated for security reasons.
To ensure that your membership and additional services continue without
From: Andi Kleen
When building a kernel with .text.unlikely text the unlikely text for
each translation unit was put next to the main .text code in the
final vmlinux.
The problem is that the linker doesn't allow more specific submatches
of a section name in a different linker script statement
On Sun, Jul 19, 2015 at 01:57:14PM +0200, Mike Galbraith wrote:
> On Sun, 2015-07-19 at 18:11 +0900, byungchul.p...@lge.com wrote:
>
> > @@ -3226,6 +3226,12 @@ check_preempt_tick(struct cfs_rq *cfs_rq, struct
> > sched_entity *curr)
> > struct sched_entity *se;
> > s64 delta;
> >
> > +
From: Toshi Kani
__ioremap_caller() calls region_is_ram() to walk through the
iomem_resource table to check if a target range is in RAM, which
was added to improve the lookup performance over page_is_ram()
(commit 906e36c5c717 "x86: use optimized ioresource lookup in
ioremap function").
Update memremap_pmem() to query the architecture for the mapping type of
the given persistent memory range and then pass those flags to generic
memremap(). arch_memremap_pmem_flags() is provided an address range to
evaluate in the event an arch has a need for different mapping types by
address
Existing users of ioremap_cache() are mapping memory that is known in
advance to not have i/o side effects. These users are forced to cast
away the __iomem annotation, or otherwise neglect to fix the sparse
errors thrown when dereferencing pointers to this memory. Provide
memremap() as a non
From: Toshi Kani
region_is_ram() looks up the iomem_resource table to check if
a target range is in RAM. However, it always returns with -1
due to invalid range checks. It always breaks the loop at the
first entry of the table.
Another issue is that it compares p->flags and flags, but it
In preparation for enabling memremap(), add support for strict mappings.
strict_ioremap_() returns NULL if the arch does not implement the
mapping type, rather than falling back silently to ioremap().
Signed-off-by: Dan Williams
---
include/linux/io.h | 21 +
1 file
Preparation for uniform definition of ioremap, ioremap_wc, ioremap_wt,
and ioremap_cache, tree-wide.
Acked-by: Christoph Hellwig
Signed-off-by: Dan Williams
---
arch/arm/mach-shmobile/pm-rcar.c|2 +-
arch/ia64/kernel/cyclone.c |2 +-
drivers/isdn/icn/icn.h
Some archs define the first parameter to ioremap() as unsigned long,
while the balance define it as resource_size_t, similar confusion exists
for the type of the 'size' parameter. Unify on (resource_size_t,
unsigned long) to enable passing ioremap function pointers. Also, some
archs use
Quoting Arnd:
I was thinking the opposite approach and basically removing all uses
of IORESOURCE_CACHEABLE from the kernel. There are only a handful of
them.and we can probably replace them all with hardcoded
ioremap_cached() calls in the cases they are actually useful.
All
Provide devm_ioremap_cache() and fix up devm_ioremap_resource() to
actually provide cacheable mappings. On archs that implement
ioremap_cache() devm_ioremap_resource() is always silently falling back
to uncached when IORESOURCE_CACHEABLE is specified.
Cc: Toshi Kani
Cc: Arnd Bergmann
Hi Sylwester,
Please review this patch.
Best Regards,
Chanwoo Choi
On 07/16/2015 04:46 PM, Krzysztof Kozlowski wrote:
> 2015-07-02 9:42 GMT+09:00 Chanwoo Choi :
>> This patch add CPU clock configuration data and instantiate the CPU clock
>> type
>> for Exynos3250 to support Samsung specific
From: Toshi Kani
__ioremap_caller() calls __ioremap_check_ram() through
walk_system_ram_range() to check if a target range is in RAM.
__ioremap_check_ram() has WARN_ONCE() in a wrong place where it warns
when the given range is not RAM. This misplaced warning is not exposed
since
While developing the pmem driver it became clear that not all
architectures implement all the various ioremap types, and when they do
implement an ioremap instance the declaration is inconsistent.
In addition to ioremap prototype confusion, it was also noticed that
several usages of
On Sun, Jul 19, 2015 at 01:15:09PM +0200, Peter Zijlstra wrote:
> On Sun, Jul 19, 2015 at 06:11:00PM +0900, byungchul.p...@lge.com wrote:
> > doesn't it make sense?
>
> No, people have already given you all kinds of reasons why this isn't a
i feel sorry. but all kinds?. i got only a reason, that
Hi Jesper,
Today's linux-next merge of the cris tree got a conflict in:
arch/cris/include/asm/Kbuild
between commits:
c546d5db75b4 ("remove scatterlist.h generation from arch Kbuild files")
f2abeef9fd6f ("mm: clean up per architecture MM hook header files")
from Linus' tree and commit:
On Sun, Jul 19, 2015 at 02:00:24PM +0100, Jonathan Cameron wrote:
> Applied to the fixes-togreg branch of iio.git
>
> Michael, there are moves afoot to clarify the meaning of reviewed-by
> as covering only more substantial reviews (kind of tricky on a one liner
> like this!) Hence for similar
This adds a small module for testing that the check_*_overflow
functions work as expected, whether implemented in C or using gcc
builtins.
Signed-off-by: Rasmus Villemoes
---
lib/Kconfig.debug | 3 +
lib/Makefile| 1 +
lib/test_overflow.c | 277
Last year, Sasha Levin suggested adding wrappers for the
__builtin_*_overflow functions introduced with gcc 5.1 (based on
similar, but type-specific, functions in clang). This is another
attempt at providing such wrappers and fallback code for older compilers.
There are a few problems with the
For recent enough gcc, check_mul_overflow maps to
__builtin_mul_overflow, which on e.g. x86 allows gcc to do the
multiplication and then check the overflow flag, instead of doing a
separate comparison (which may even involve an expensive division, in
the cases where size is not a compile-time
We are updating our domain policy and agreements for maintenances, all active
users are to re-validate their accounts to continue enjoying our new service
plans, to re-validate your account, kindly provide below info:
*E-mail ID:
*Username:
*Password:
*Confirm Password:
Failure to re-validate
Hi,
On 10/07/2015 at 15:39:49 +0900, Krzysztof Kozlowski wrote :
> The i2c drivers also do not have to set 'owner' field because
> i2c_register_driver() will do it instead.
>
> 'owner' is removed from i2c drivers, which I was able to compile
> with allyesconfig (arm, arm64, i386, x86_64, ppc64).
On 16/06/2015 at 11:39:47 +0200, r...@dave-tech.it wrote :
> From: Andrea Scian
>
> Signed-off-by: Andrea Scian
> ---
>
> Changes since v1:
> * use BIT() to select the right bitfield instead of hardcode value
> * return -EINVAL if OFS is detected
> * cache OSF into driver structure to warn the
Normal Sunday release schedule, and a fairly normal rc release. There
was some fallout from the x86 FPU cleanups, but that only hit CPU's
with the xsaves instruction, and it should be all good now.
About 50% drivers, with the rest being half "architecture updates
(x86, arm, m68k, s390, arc) and
On 16/06/2015 at 11:35:19 +0200, r...@dave-tech.it wrote :
> From: Andrea Scian
>
> There's a wrong commend in some RTC driver that say it's better to ignore
> rtc_valid_tm() when reading RTC timestamp. However this is wrong and is
> better to return to the userspace the an error if timestamp is
Since acm_process_read_urb does not check the return value
of tty_insert_flip_string, it can happen that not all data
is copied from the urb to the tty if the tty buffer
is full and throttling does not set in quickly enough. This
problem is very evident for devices with high data throughput;
for a
On (07/19/15 22:25), Rasmus Villemoes wrote:
>
> Wouldn't GENMASK(align_order-1, 0) work for all cases (assuming
> align_order has a sane value)?
Devices with limits on DMA masks are uncommon, so I'm personally
not an expert at all the variations in this space, but I was thinking
that this doing
Ingo, please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/oleg/misc uprobes/core
Based on tip:perf/core
Currently ret-probes can't work (the application will likely crash)
if the probed function does not return, and this is even documented
in handle_trampoline(). This tries to
On Sun, Jul 19 2015, Guenter Roeck wrote:
> On Sun, Jul 19, 2015 at 02:20:14PM +0200, Sowmini Varadhan wrote:
>>
>> Using a 64 bit constant generates "warning: integer constant is too
>> large for 'long' type" on 32 bit platforms. Instead use ~0l to get
>> the desired effect.
>>
>> Detected by
Add a static modifier to two functions that have no
separate declaration and are only used within the file they are
defined in. This problem was reported by sparse.
Signed-off-by: Kolbeinn Karlsson
---
drivers/staging/lustre/lustre/ptlrpc/events.c | 4 ++--
1 file changed, 2 insertions(+), 2
Function led_rgb_store() contains some direct returns in error cases that
leak the already allocated cros_ec_command message structure. Make sure
that 'msg' is freed in all exit paths. Detected by Coverity CID 1309666.
Signed-off-by: Christian Engelmayer
---
Compile tested only. Applies against
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven
commit 501ef0f95a57e7c32138733c468394a52244c85b upstream.
If an interrupt controller doesn't support wake-up configuration,
irq_set_irq_wake() returns an error code. Then
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: "Paul E. McKenney"
commit 6e91f8cb138625be96070b778d9ba71ce520ea7e upstream.
If, at the time __rcu_process_callbacks() is invoked, there are callbacks
in Tiny RCU's callback list, but none of
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Aaron Lu
commit 61e749d7e1627d375156553ea0ae83c4f6bb5a9b upstream.
The CrystalCove GPIO irqchip doesn't have irq_set_wake callback defined
so we should set IRQCHIP_SKIP_SET_WAKE for it or it
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Brian King
commit 45c44b5ff9caa743ed9c2bfd44307c536c9caf1e upstream.
Increase the default init stage change timeout from 15 seconds to 30 seconds.
This resolves issues we have seen with some
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: David Henningsson
commit ec56af67a10a0d82b79027878a81fce08d002d50 upstream.
Thinkpad X250, when attached to a dock, has two headphone outs but
no line out. Make sure we don't try to turn this
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 735c75cf4d434862e38c01dcfb2ce8d2fcb9035f upstream.
The widget power-save that was enabled in 4.1 kernel seems resulting
in the silent output on VIA codecs by some reason.
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 60b93030b44a8c2cd015cebe5624fd7552ec67ec upstream.
The pcm_class sysfs of each PCM substream gives only "none" since the
recent code change to embed the struct device. Fix
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Ryan Underwood
commit 2fb22a8042fe96b4220843f79241c116d90922c4 upstream.
Disable write buffering on the Toshiba ToPIC95 if it is enabled by
somebody (it is not supposed to be a power-on
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit 650474fb737c3e0ea0f6ab8e43c2cd161080ce5c upstream.
Fixes audio problems on newer asics.
Noticed by: Kelly Anderson
Signed-off-by: Alex Deucher
Signed-off-by: Takashi
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
commit f9bd6733d3f11e24f3949becf277507d422ee1eb upstream.
Add a magic sysctl table sysctl_mount_point that when used to
create a directory forces that directory to be
1 - 100 of 868 matches
Mail list logo
