On Fri, Jun 26, 2015 at 05:52:16PM -0700, Greg Kroah-Hartman wrote:
> On Sat, Jun 20, 2015 at 10:41:14AM +0300, Jari Ruusu wrote:
> > On 6/19/15, Greg Kroah-Hartman wrote:
> > > I would much rather just include the "real" upstream patches, instead of
> > > an odd backport.
> > >
> > > Jari, can
On 06/26/2015 06:08 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.46 release.
There are 17 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 06/26/2015 06:08 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.82 release.
There are 5 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
2015-06-26 22:08 GMT+09:00 Vaibhav Hiremath :
> Instead of hard coding the shift for bit definition, use
> BIT() macro.
I am not convinced that such change improves anything in existing
code. IMHO (1 << n) is quite readable and obvious. The obviousness of
it, is the same as obviousness of BIT(n).
This patch fixes the checkpatch.pl error:
ERROR: Macros with complex values should be enclosed in parentheses
+#define CONSUME(val, ptr) (val) = consume(sizeof(val), (ptr))
by expanding it as this macro is used only once.
Signed-off-by: Vasiliy Korchagin
---
Notes:
Here is another version
On Sat, 2015-06-27 at 05:44 +0100, Vasiliy Korchagin wrote:
> This patch fixes the checkpatch.pl error:
>
> ERROR: Macros with complex values should be enclosed in parentheses
> +#define CONSUME(val, ptr) (val) = consume(sizeof(val), (ptr))
>
> Signed-off-by: Vasiliy Korchagin
> ---
>
This patch fixes the checkpatch.pl error:
ERROR: Macros with complex values should be enclosed in parentheses
+#define CONSUME(val, ptr) (val) = consume(sizeof(val), (ptr))
Signed-off-by: Vasiliy Korchagin
---
drivers/staging/lustre/lustre/obdclass/uuid.c | 2 +-
1 file changed, 1
Hi Linus,
On Fri, 26 Jun 2015 20:18:10 -0700 Linus Torvalds
wrote:
>
> On Fri, Jun 26, 2015 at 9:01 AM, Tejun Heo wrote:
> >
> > Ooh, it isn't in mainline yet but pulling rcu tree will cause a silent
> > conflict with this pull request which leads to build failure.
>
> I tend to try to do a
On Fri, Jun 26, 2015 at 08:05:48PM -0700, Linus Torvalds wrote:
> On Wed, Jun 24, 2015 at 8:46 PM, Theodore Ts'o wrote:
> >
> > A very large number of cleanups and bug fixes --- in particular for
> > the ext4 encryption patches, which is a new feature added in the last
> > merge window. Also fix
On 06/24/2015 01:38 AM, Lorenzo Pieralisi wrote:
On Tue, Jun 23, 2015 at 04:11:38PM +0100, Hanjun Guo wrote:
[...]
diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
index 8fc67bc..d1b2131 100644
--- a/drivers/irqchip/irq-gic.c
+++ b/drivers/irqchip/irq-gic.c
@@ -851,15
On Fri, Jun 26, 2015 at 10:23:32AM -0400, Theodore Ts'o wrote:
> I can no longer boot Linus's tree under KVM using a 32-bit i386 build;
> it just hangs before any messages get sent to the serial console. It
> bisects down to:
>
> commit 4066c33d0308f87e9a3b0c7fafb9141c0bfbfa77
> Author: Gavin
On Thu, Jun 25, 2015 at 04:59:46PM -0400, James Simmons wrote:
> The header socklnd.h includes irq.h which is not need
> and doesn't exist in the OpenSFS lustre branch. Having
> irq.h in socklnd.h does break the build on the m68k
> platform. So we can safely remove it.
>
> Signed-off-by: James
On 06/19/2015 05:49 PM, Greg Kroah-Hartman wrote:
> On Fri, Jun 19, 2015 at 04:57:00PM -0500, Rob Landley wrote:
>> On 06/18/2015 12:59 PM, Greg Kroah-Hartman wrote:
>>> On Thu, Jun 18, 2015 at 10:19:19AM -0700, Rob Landley wrote:
Changes to existing files to add 0pf j2 board support.
On Fri, Jun 26, 2015 at 9:01 AM, Tejun Heo wrote:
>
> Ooh, it isn't in mainline yet but pulling rcu tree will cause a silent
> conflict with this pull request which leads to build failure.
I tend to try to do a full "make allmodconfig" build between all pull
requests (although I can optimize
On 06/26/2015 07:09 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.1.1 release.
> There are 11 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
On 06/26/2015 07:08 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.0.7 release.
> There are 22 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
On 06/26/2015 07:08 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.82 release.
> There are 5 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
On 06/26/2015 07:08 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.46 release.
> There are 17 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
On Wed, Jun 24, 2015 at 8:46 PM, Theodore Ts'o wrote:
>
> A very large number of cleanups and bug fixes --- in particular for
> the ext4 encryption patches, which is a new feature added in the last
> merge window. Also fix a number of long-standing xfstest failures.
> (Quota writes failing due
Hi Ohad,
Any comments?
Thanks,
Lina
On Tue, Jun 09 2015 at 10:23 -0600, Lina Iyer wrote:
This patch follows the discussion based on the first RFC series posted on the
mailing list [1]. The discussion resulted in a couple of directives for
hwspinlocks that do not want the framework imposing a
On Fri, 26 Jun 2015, Jerome Glisse wrote:
> On Thu, Jun 25, 2015 at 04:05:48PM -0700, Mark Hairgrove wrote:
> > On Thu, 21 May 2015, j.gli...@gmail.com wrote:
> > > From: Jérôme Glisse
> > > [...]
> > >
> > > + /* update() - update device mmu following an event.
> > > + *
> > > + *
The code depends on CLKDEV_LOOKUP since commit 225d68d852f1 ("staging:
board: Add support for devices with complex dependencies").
Related build error (powerpc:allmodconfig):
drivers/built-in.o: In function `.board_staging_register_clock':
(.init.text+0x1d8e0): undefined reference to
Add the buddy system interface for address range mirroring feature.
Use mirrored memory for all kernel allocations. If there is no mirrored pages
left, try to use other types pages.
Signed-off-by: Xishi Qiu
---
include/linux/memblock.h | 1 +
mm/memblock.c| 6 +++---
Add the count of free mirrored pages in the following paths:
/proc/meminfo
/proc/zoneinfo
/sys/devices/system/node/node XX/meminfo
/sys/devices/system/node/node XX/vmstat
Signed-off-by: Xishi Qiu
---
drivers/base/node.c | 17 +++--
fs/proc/meminfo.c | 6 ++
mm/page_alloc.c
Abstract the PCP code in __rmqueue_pcp(), and do not call fallback in
rmqueue_bulk() when the migratetype is mirror.
Signed-off-by: Xishi Qiu
---
mm/page_alloc.c | 85 +
1 file changed, 61 insertions(+), 24 deletions(-)
diff --git
Before free bootmem, set mirrored pageblock's migratetype to MIGRATE_MIRROR, so
they could free to buddy system's MIGRATE_MIRROR list.
When set reserved memory, skip the mirrored memory.
Signed-off-by: Xishi Qiu
---
include/linux/memblock.h | 3 +++
mm/memblock.c| 21
This patch introduces a new zone_stat_item called "NR_FREE_MIRROR_PAGES", it is
used to storage free mirrored pages count.
Signed-off-by: Xishi Qiu
---
include/linux/mmzone.h | 1 +
include/linux/vmstat.h | 2 ++
mm/vmstat.c| 1 +
3 files changed, 4 insertions(+)
diff --git
Add a macro for_each_mirror_pfn_range() to find mirrored memory in memblock.
This patch is based on Tony's patchset "Find mirrored memory, use for boot time
allocations"
Signed-off-by: Xishi Qiu
---
include/linux/memblock.h | 25 ++---
mm/memblock.c| 6 +-
2
This patch introduces a new migratetype called "MIGRATE_MIRROR", it is used to
allocate mirrored pages.
When cat /proc/pagetypeinfo, you can see the count of free mirrored blocks.
Signed-off-by: Xishi Qiu
---
include/linux/mmzone.h | 9 +
mm/page_alloc.c| 3 +++
mm/vmstat.c
This patch introduces a new config called "CONFIG_ACPI_MIRROR_MEMORY", set it
off by default.
Signed-off-by: Xishi Qiu
---
mm/Kconfig | 8
1 file changed, 8 insertions(+)
diff --git a/mm/Kconfig b/mm/Kconfig
index 390214d..c40bb8b 100644
--- a/mm/Kconfig
+++ b/mm/Kconfig
@@ -200,6
Intel Xeon processor E7 v3 product family-based platforms introduces support
for partial memory mirroring called as 'Address Range Mirroring'. This feature
allows BIOS to specify a subset of total available memory to be mirrored (and
optionally also specify whether to mirror the range 0-4 GB).
Hi Peter,
I am getting a minor issue trying to boot a lockdep enabled x86_64
kernel with >64 CPUs.
The kernel boots the first 64 CPUs without issues, but then complains
that lockdep wants to allocate memory while start_secondary ->
init_espfix_ap has IRQs disabled:
[0.310566] x86: Booting
On Fri, 26 Jun 2015, Jerome Glisse wrote:
> On Thu, Jun 25, 2015 at 03:57:29PM -0700, Mark Hairgrove wrote:
> > On Thu, 21 May 2015, j.gli...@gmail.com wrote:
> > > From: Jérôme Glisse
> > > [...]
> > > +
> > > +void hmm_pt_iter_init(struct hmm_pt_iter *iter);
> > > +void
On Fri, Jun 26, 2015 at 12:31 PM, Andy Lutomirski wrote:
> On Fri, Jun 26, 2015 at 11:09 AM, Mathieu Desnoyers
> wrote:
>> - On Jun 24, 2015, at 6:26 PM, Paul Turner p...@google.com wrote:
>>
>>> Implements the x86 (i386 & x86-64) ABIs for interrupting and restarting
>>> execution within
On Fri, Jun 26, 2015 at 09:20:19PM -0400, Alan Stern wrote:
> On Fri, 26 Jun 2015, Greg Kroah-Hartman wrote:
>
> > > This doesn't do what the patch title says. USB_DEVICE_FIXED means that
> > > the device can't be unplugged from its upstream port. It doesn't mean
> > > the device is internal to
On Fri, Jun 26, 2015 at 12:29 PM, Borislav Petkov wrote:
> On Fri, Jun 26, 2015 at 04:28:51PM +0800, kbuild test robot wrote:
>> tree: git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp tip-mm
>> head: 7b0982330a1b4d4bdb99bb8382e2363165231a90
>> commit:
This is the start of the stable review cycle for the 3.14.46 release.
There are 17 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 Mon Jun 29 01:08:13 UTC 2015.
Anything
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Steve Cornelius
commit 412c98c1bef65fe7589f1300e93735d96130307c upstream.
The hwrng output buffers (2) are cast inside of a a struct (caam_rng_ctx)
allocated in one DMA-tagged region. While
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Kim Phillips
commit b88657674d39fc2127d62d0de9ca142e166443c8 upstream.
A userspace process can map device MMIO memory via VFIO or /dev/mem,
e.g., for platform device passthrough support in
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Christoffer Dall
commit 4f853a714bf16338ff5261128e6c7ae2569e9505 upstream.
unmap_range() was utterly broken, to quote Marc, and broke in all sorts
of situations. It was also quite
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Tunin
commit 0d0cef6183aec0fb6d0c9f00a09ff51ee086bbe2 upstream.
BugLink: https://bugs.launchpad.net/bugs/1427680
This device requires new firmware files
AthrBT_0x11020100.dfu and
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Adam Jackson
commit 25161084b1c1b0c29948f6f77266a35f302196b7 upstream.
Turns out 1366x768 does not in fact work on this hardware.
Signed-off-by: Adam Jackson
Signed-off-by: Dave Airlie
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: James Smart
commit 27f344eb15dd0da80ebec80c7245e8c85043f841 upstream.
Add a memory barrier to ensure the valid bit is read before
any of the cqe payload is read. This fixes an issue seen
on
On Fri, 26 Jun 2015, Greg Kroah-Hartman wrote:
> > This doesn't do what the patch title says. USB_DEVICE_FIXED means that
> > the device can't be unplugged from its upstream port. It doesn't mean
> > the device is internal to the computer.
> >
> > As an example, consider a composite Apple
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Steve Cornelius
commit 6fd4b15603124c1b56e03db29b41ec39d8a077b9 upstream.
Multiple function in asynchronous hashing use a saved-state block,
a.k.a. struct caam_hash_state, which holds a stash
This is the start of the stable review cycle for the 4.0.7 release.
There are 22 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 Mon Jun 29 01:08:46 UTC 2015.
Anything
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Adam Jackson
commit 25161084b1c1b0c29948f6f77266a35f302196b7 upstream.
Turns out 1366x768 does not in fact work on this hardware.
Signed-off-by: Adam Jackson
Signed-off-by: Dave Airlie
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Tunin
commit 692c062e7c282164fd7cda68077f79dafd176eaf upstream.
BugLink: https://bugs.launchpad.net/bugs/1462614
This device requires new firmware files
AthrBT_0x11020100.dfu and
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Wilson
commit 016a65a39170c3cdca09a6ac343ff4f124668b45 upstream.
With the introduction of multiple views of an obj in the same vm, each
vma was taught to cache its copy of the pages (so
On Fri, Jun 26, 2015 at 4:54 PM, Benjamin Herrenschmidt
wrote:
> On Fri, 2015-06-26 at 15:41 -0700, Luis R. Rodriguez wrote:
>
>> > It wasn't nullified for the main user at the time, the fb. And I
>> > mentioned an IB adapter or two for which the code had been hand
>> tuned.
>>
>> This still
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Sokolov
commit 15bf722e6f6c0b884521a0363204532e849deb7f upstream.
ATOL FPrint fiscal printers require usb_clear_halt to be executed
to work properly. Add quirk to fix the issue.
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Junichi Nomura
commit 3a1407559a593d4360af12dd2df5296bf8eb0d28 upstream.
When stacking request-based DM on blk_mq device, request cloning and
remapping are done in a single call to target's
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Steve Cornelius
commit 412c98c1bef65fe7589f1300e93735d96130307c upstream.
The hwrng output buffers (2) are cast inside of a a struct (caam_rng_ctx)
allocated in one DMA-tagged region. While
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Tunin
commit 0d0cef6183aec0fb6d0c9f00a09ff51ee086bbe2 upstream.
BugLink: https://bugs.launchpad.net/bugs/1427680
This device requires new firmware files
AthrBT_0x11020100.dfu and
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Krzysztof Kozlowski
commit 6f024978e74bda616b27183adee029b65eb27032 upstream.
On Exynos4412 boards (Trats2, Odroid U3) after enabling L2 cache in
56b60b8bce4a ("ARM: 8265/1: dts: exynos4: Add
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Sam Bobroff
commit 0aab3747091db309b8a484cfd382a41644552aa3 upstream.
Patches 7cba160ad "powernv/cpuidle: Redesign idle states management"
and 77b54e9f2 "powernv/powerpc: Add winkle support
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Antoine
commit 364aece01a2dd748fc36a1e8bf52ef639b0857bd upstream.
This patch fixes a timing issue that causes a GPU hang when the system
comes out of power saving.
During pm_resume, We
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eugene Shatokhin
commit c80e5c0c23ce2282476fdc64c4b5e3d3a40723fd upstream.
On x86-64, __copy_instruction() always returns 0 (error) if the
instruction uses %rip-relative addressing. This is
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Boris Brezillon
commit 6c7b03e1aef2e92176435f4fa562cc483422d20f upstream.
The PLL impose a certain input range to work correctly, but it appears that
this input range does not apply on the
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Sagi Grimberg
commit 524630d5824c7a75aab568c6bd1423fd748cd3bb upstream.
iser connection termination process happens in 2 stages:
- isert_wait_conn:
- resumes rdma disconnect
- wait for
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
commit 04c17341b42699a5859a8afa05e64ba08a4e5235 upstream.
When building the kernel with 32-bit binutils built with support
only for the i386 target, we get the following
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Ferre
commit 28df9c2fb6f896179fcffd5a3f5a86e2d1dff0a5 upstream.
Trivial fix that prevents to compile this pmc clock driver if h32mx clock is
present but smd clock isn't.
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Hui Wang
commit 6ab42ff44864d26e8e498b8ac655d24ee389d267 upstream.
On a HP Envy TouchSmart laptop, there are 2 speakers (main speaker
and subwoofer speaker), 1 headphone and 2 DACs, without
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Sokolov
commit 15bf722e6f6c0b884521a0363204532e849deb7f upstream.
ATOL FPrint fiscal printers require usb_clear_halt to be executed
to work properly. Add quirk to fix the issue.
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt
commit 2cf30dc180cea808077f003c5116388183e54f9e upstream.
When the following filter is used it causes a warning to trigger:
# cd /sys/kernel/debug/tracing
# echo
This is the start of the stable review cycle for the 4.1.1 release.
There are 11 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 Mon Jun 29 01:08:53 UTC 2015.
Anything
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Tunin
commit 7e730c7f3d1f39c25cf5f7cf70c0ff4c28d7bec7 upstream.
BugLink: https://bugs.launchpad.net/bugs/1394368
This device requires new firmware files
AthrBT_0x11020100.dfu and
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Sagi Grimberg
commit 9253e667ab50fd4611a60e1cdd6a6e05a1d91cf1 upstream.
Since commit "2426bd456a6 target: Report correct response ..."
we might get a command with data_size that does not fit
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Tunin
commit 0d0cef6183aec0fb6d0c9f00a09ff51ee086bbe2 upstream.
BugLink: https://bugs.launchpad.net/bugs/1427680
This device requires new firmware files
AthrBT_0x11020100.dfu and
The extcon API calls have been changed to add an additional argument.
This causes build errors such as
drivers/power/axp288_charger.c:851:2: error:
too few arguments to function 'extcon_register_notifier'
Fixes: 73b6ecdb93e8 ("extcon: Redefine the unique id of supported
external
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Tunin
commit 692c062e7c282164fd7cda68077f79dafd176eaf upstream.
BugLink: https://bugs.launchpad.net/bugs/1462614
This device requires new firmware files
AthrBT_0x11020100.dfu and
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Shishkin
commit 6b099d9b040b0f3d0aec05b560d7caf879af5077 upstream.
Currently, the intel_bts driver relies on the DS area allocated by the x86_pmu
code in its event_init() path, which
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Oleg Nesterov
commit 2f993cf093643b98477c421fa2b9a98dcc940323 upstream.
While looking for other users of get_state/cond_sync. I Found
ring_buffer_attach() and it looks obviously buggy?
Don't
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Andi Kleen
commit 4b36f1a4139c9284df74c0f5d7655603d67807df upstream.
This patch adds additional model numbers for Broadwell to perf.
Support for Broadwell with Iris Pro (Intel Core i7-57xxC)
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: "Palik, Imre"
commit 2c33645d366d13b969d936b68b9f4875b1fdddea upstream.
Architectural performance monitoring, version 1, doesn't support fixed counters.
Currently, even if a hypervisor
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Tunin
commit 692c062e7c282164fd7cda68077f79dafd176eaf upstream.
BugLink: https://bugs.launchpad.net/bugs/1462614
This device requires new firmware files
AthrBT_0x11020100.dfu and
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
pipe_iov_copy_{from,to}_user() may be tried twice with the same iovec,
the first time atomically and the second time not. The second attempt
needs to continue from the iovec
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Lukas Wunner
commit 75e84ab906ef8935cff3df3d8929f1bafea81599 upstream.
Invoking Makefile.perf with prefix= breaks the build since Makefile.perf
hands that variable down to Makefile.build where
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 1fa451bcc67fa921a04c5fac8dbcde7844d54512 upstream.
vgic_ioaddr_overlap claims to return a bool, but in reality it returns
an int. Shut sparse up by fixing the type
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Auger
commit df6ce24f2ee485c4f9a5cb610063a5eb60da8267 upstream.
Currently when a KVM region is deleted or moved after
KVM_SET_USER_MEMORY_REGION ioctl, the corresponding
intermediate
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 18d457661fb9fa69352822ab98d39331c3d0e571 upstream.
is_valid_cache returns true if the specified cache is valid.
Unfortunately, if the parameter passed it out of range, we
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 4000be423cb01a8d09de878bb8184511c49d4238 upstream.
Running sparse results in a bunch of noisy address space mismatches
thanks to the broken __percpu annotation on
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Victor Kamensky
commit ba083d20d8cfa9e999043cd89c4ebc964ccf8927 upstream.
esr_el2 field of struct kvm_vcpu_fault_info has u32 type.
It should be stored as word. Current code works in LE case
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt
commit 2cf30dc180cea808077f003c5116388183e54f9e upstream.
When the following filter is used it causes a warning to trigger:
# cd /sys/kernel/debug/tracing
# echo
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 6951e48bff0b55d2a8e825a953fc1f8e3a34bf1c upstream.
Sparse kicks up about a type mismatch for kvm_target_cpu:
arch/arm64/kvm/guest.c:271:25: error: symbol 'kvm_target_cpu'
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: James Smart
commit 27f344eb15dd0da80ebec80c7245e8c85043f841 upstream.
Add a memory barrier to ensure the valid bit is read before
any of the cqe payload is read. This fixes an issue seen
on
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Li Liu
commit af92394efc8be73edd2301fc15f9b57fd430cd18 upstream.
HSCTLR.EE is defined as bit[25] referring to arm manual
DDI0606C.b(p1590).
Reviewed-by: Marc Zyngier
Signed-off-by: Li Liu
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
pipe_iov_copy_{from,to}_user() may be tried twice with the same iovec,
the first time atomically and the second time not. The second attempt
needs to continue from the iovec
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Adam Jackson
commit 25161084b1c1b0c29948f6f77266a35f302196b7 upstream.
Turns out 1366x768 does not in fact work on this hardware.
Signed-off-by: Adam Jackson
Signed-off-by: Dave Airlie
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Steve Cornelius
commit 412c98c1bef65fe7589f1300e93735d96130307c upstream.
The hwrng output buffers (2) are cast inside of a a struct (caam_rng_ctx)
allocated in one DMA-tagged region. While
This is the start of the stable review cycle for the 3.10.82 release.
There are 5 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 Mon Jun 29 01:07:49 UTC 2015.
Anything
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt
commit 2cf30dc180cea808077f003c5116388183e54f9e upstream.
When the following filter is used it causes a warning to trigger:
# cd /sys/kernel/debug/tracing
# echo
On Sat, Jun 20, 2015 at 10:41:14AM +0300, Jari Ruusu wrote:
> On 6/19/15, Greg Kroah-Hartman wrote:
> > I would much rather just include the "real" upstream patches, instead of
> > an odd backport.
> >
> > Jari, can you just backport the above referenced patches instead and
> > provide those
Hi,
On Fri, Jun 26, 2015 at 04:53:42PM -0700, Michael Turquette wrote:
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index 28e59a4..e5296c0 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -112,6 +112,12 @@ bool
Hi,
On Fri, Jun 26, 2015 at 04:53:43PM -0700, Michael Turquette wrote:
> diff --git a/kernel/sched/cpufreq_sched.c b/kernel/sched/cpufreq_sched.c
> new file mode 100644
> index 000..5020f24
> --- /dev/null
> +++ b/kernel/sched/cpufreq_sched.c
> @@ -0,0 +1,308 @@
> +/*
> + * Copyright (C)
On Tue, Jun 16, 2015 at 04:22:12PM -0400, Joseph Salisbury wrote:
> From: Nick Meier
>
> BugLink: http://bugs.launchpad.net/bugs/1463584
>
> Hyper-V allows a guest to notify the Hyper-V host that a panic
> condition occured. This notification can include up to five 64
> bit values. These 64
From: Stephen Chandler Paul
A big problem with the current i8042 debugging option is that it outputs
data going to and from the keyboard by default. As a result, many dmesg
logs uploaded by users will unintentionally contain sensitive information
such as their password, as such it's probably a
Hi Rusty,
On Thu, 25 Jun 2015 17:34:31 -0400 Dan Streetman wrote:
>
> On Thu, Jun 25, 2015 at 5:18 PM, Rusty Russell wrote:
> > Dan Streetman writes:
> >> Only include the built-in and per-module param_lock, and corresponding
> >> lock/unlock functions, if sysfs is enabled. If there is no
On Fri, 2015-06-26 at 15:41 -0700, Luis R. Rodriguez wrote:
> > It wasn't nullified for the main user at the time, the fb. And I
> > mentioned an IB adapter or two for which the code had been hand
> tuned.
>
> This still means there could be some affected drivers when used on
> powerpc, no?
Hi Greg,
On Fri, 5 Jun 2015 19:53:46 +0900 Greg KH wrote:
>
> On Thu, Jun 04, 2015 at 07:18:38PM +1000, Stephen Rothwell wrote:
> > Hi all,
> >
> > This is now needed when the char-misc and battery trees are merged ...
> >
> > On Mon, 25 May 2015 21:05:03 +1000 Stephen Rothwell
> > wrote:
>
1 - 100 of 1400 matches
Mail list logo