On Sat, 2 May 2015, Drokin, Oleg wrote:
>
> On May 2, 2015, at 5:16 PM, Julia Lawall wrote:
>
> > Summarize OBD_CPT_ALLOC_GFP, OBD_CPT_ALLOC, and OBD_CPT_ALLOC_PTR as a
> > function, obd_cpt_alloc.
> >
> > Signed-off-by: Julia Lawall
> >
> > ---
> >
> > Some questions: Is the name OK? Is
Hi Charles,
On Thu, Apr 30, 2015 at 11:43 PM, Charles Keepax
wrote:
> The headphone clamping is not set correctly currently, this was missed
> because the wm8280 patches and the patch fixing the clamping for wm5110
> went upstream at very similar times. This patch sets the headphone
> clamping
On Sun, 3 May 2015 12:02:39 +0900 DaeSeok Youn wrote:
> 2015-04-24 10:45 GMT+09:00 Daeseok Youn :
> > The use of 'status' in __ocfs2_add_entry() can return wrong
> > value. Some functions' return value in __ocfs2_add_entry(),
> > i.e ocfs2_journal_access_di() is saved to 'status'.
> > But
On Sat, May 02, 2015 at 05:03:07PM -0700, Kenneth Westfield wrote:
> On Thu, Apr 30, 2015 at 06:18:26PM +0100, Srinivas Kandagatla wrote:
> > This patch adds bindings for apq8016 machine driver.
> > On APQ8016 4 MI2S can be configured to different sinks like internal
> > codec/external codec, this
Hello!
On May 2, 2015, at 4:14 AM, Dan Carpenter wrote:
> On Fri, May 01, 2015 at 09:13:11PM +, Drokin, Oleg wrote:
The patch was submitted.
But it depends on a symbol that's not exported.
I was not able to change that.
http://www.spinics.net/lists/linux-mm/msg83997.html
2015-04-24 10:45 GMT+09:00 Daeseok Youn :
> The use of 'status' in __ocfs2_add_entry() can return wrong
> value. Some functions' return value in __ocfs2_add_entry(),
> i.e ocfs2_journal_access_di() is saved to 'status'.
> But 'status' is not used in 'bail' label for returning result
> of
On Sun, May 03, 2015 at 07:18:28AM +0800, Fengguang Wu wrote:
> Hi Iulia,
>
> FYI, there are Ubuntu init error messages when CONFIG_MULTIUSER=n.
> Since it's not embedded system and hence the target user of
> CONFIG_MULTIUSER=n, it might be fine..
I would expect a non-trivial amount of work
On Sat, May 02, 2015 at 12:59:16AM +0900, Krzysztof Kozlowski wrote:
> The platform_device_id is not modified by the driver and core uses it as
> const.
>
> Signed-off-by: Krzysztof Kozlowski
Applied to libata/for-4.2.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line
Hey, Jeff.
On Fri, May 01, 2015 at 07:17:41PM -0400, Jeff Layton wrote:
> > Sorry for the noise, and self-reply.. Looks like there's additional context
> > here: http://marc.info/?t=13676151217=1=2
> >
> > Due to a number of locking problems the answer to this problem is likely to
> > be
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Tuesday, April 21, 2015 9:22 AM
> To: KY Srinivasan
> Cc: Haiyang Zhang; de...@linuxdriverproject.org; linux-
> ker...@vger.kernel.org; Dexuan Cui; Dan Carpenter
> Subject: [PATCH v2 3/3] Drivers: hv:
Hello,
On Sat, May 02, 2015 at 10:56:20PM +0800, Ming Lei wrote:
> > Maybe just cap max_active to NR_OF_LOOP_DEVS * 16 or sth? But idk,
>
> It might not work because there are nested loop devices like fedora live CD,
> and
> in theory the max_active should have been set as loop's queue depth *
Normally if driver is busy to dispatch a request the logic is like below:
block layer:driver:
__blk_mq_run_hw_queue
a. blk_mq_stop_hw_queue
b. rq add to ctx->dispatch
later:
1.
On Fri, May 01, 2015 at 11:17:44AM -0700, Tadeusz Struk wrote:
>
> I'm fine with pkey. Herbert do you have preference with regards 'algo' vs
> 'alg'?
For interfaces with the crypto API alg should be used otherwise
you can use algo or whatever you like.
> >> #define CRYPTO_ALG_TYPE_AHASH
On Thu, Apr 30, 2015 at 06:18:26PM +0100, Srinivas Kandagatla wrote:
> This patch adds bindings for apq8016 machine driver.
> On APQ8016 4 MI2S can be configured to different sinks like internal
> codec/external codec, this connection is controlled via 2 iomux
> registers.
>
> +sound: sound {
> +
On Thu, Apr 30, 2015 at 06:18:07PM +0100, Srinivas Kandagatla wrote:
> This patch adds apq8016 machine driver support. This patch was tested on
> two apq8016-sbc and msm8916-mtp board for both hdmi and analog audio
> features.
apq8016 refers to the SOC, whereas machine drivers are board-specific.
On Thu, Apr 30, 2015 at 06:17:42PM +0100, Srinivas Kandagatla wrote:
> This patch adds ablity to lpass driver to handle interrupt per dma
> channel. Without this patch its not possible to use multipl ports on the
> lpass.
> diff --git a/sound/soc/qcom/lpass-platform.c
On Thu, Apr 30, 2015 at 06:17:32PM +0100, Srinivas Kandagatla wrote:
> This patch adds ability to pass dma channel control bits start offset, which
> differ in differnet qcom SOCs. On apq8016 dma channel control bits start
> after an offset of 1.
Alot of the SOCs have similar small differences in
On Thu, Apr 30, 2015 at 06:17:24PM +0100, Srinivas Kandagatla wrote:
> Some LPASS integrations like on APQ8016 do not have OSR clk, so adding
> no osr clk bit would allow such integrations to use lpass driver.
Going forward, as the code is generalized, perhaps having an enable flag
for each
On Thu, Apr 30, 2015 at 06:16:53PM +0100, Srinivas Kandagatla wrote:
> This patch tries to make the lpass driver more generic by moving the
> ipq806x specific bits out of the cpu and platform driver, also allows the
> SOC specific drivers to add the correct register offsets.
>
> This patch also
On Thu, Apr 30, 2015 at 06:15:48PM +0100, Srinivas Kandagatla wrote:
> Hi All,
>
> This patchset adds apq8016 audio support into lpass driver. Existing Lpass
> driver can not be used as-it-is for apq8016 as it contains code specific to
> ipq806x. Also the driver only supports single i2s port,
Well, I'll comment on a couple points, since the material you quoted
is rather misleading at best.
Full disclosure:
My only associations with the VUA are (1) subscribing to this list;
(2) using the devuan repositories, and (3) having an account on the
devuan gitlab, which I have only used to
On Thursday 23 April 2015 19:04:49 Dmitry Torokhov wrote:
> On Thu, Apr 23, 2015 at 9:55 AM, Pali Rohár
> wrote:
> > On Thursday 02 April 2015 16:44:10 Pavel Machek wrote:
> >> On Wed 2015-04-01 23:11:40, Samuel Thibault wrote:
> >> > Pali Rohár, le Wed 01 Apr 2015 22:00:07 +0200, a écrit :
> >>
Hi Oded,
On Sat, May 02, 2015 at 07:59:39PM +0300, Oded Gabbay wrote:
> However, Joerg is not answering my emails for some reason (vacation/sick?)
Sorry, I was travelling for the last 3 weeks and had bad internet
access. But I am back and will take care of this on Monday.
Joerg
--
To
Subject: [PATCH 6/7 v22] LSM: Switch to lists of hooks
Instead of using a vector of security operations
with explicit, special case stacking of the capability
and yama hooks use lists of hooks with capability and
yama hooks included as appropriate.
The security_operations structure is no longer
Hi
On 2015-05-02, Greg Kroah-Hartman wrote:
> 4.0-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Daniel Borkmann
>
> commit afb7718016fcb0370ac29a83b2839c78b76c2960 upstream.
>
> While originally only being intended for outgoing
Subject: [PATCH 7/7 v22] LSM: Remove unused capability.c
The stub functions in capability.c are no longer required
with the list based stacking mechanism. Remove the file.
Signed-off-by: Casey Schaufler
---
security/capability.c | 1158 -
1 file
Subject: [PATCH 3/7 v22] LSM: Remove a comment from security.h
Remove the large comment describing the content of the
security_operations structure from security.h. This
wasn't done in the previous (2/7) patch because it
would have exceeded the mail list size limits.
Signed-off-by: Casey
Subject: [PATCH 5/7 v22] LSM: Add security module hook list heads
Add a list header for each security hook. They aren't used until
later in the patch series. They are grouped together in a structure
so that there doesn't need to be an external address for each.
Macro-ize the initialization of
Subject: [PATCH 4/7 v22] LSM: Introduce security hook calling Macros
Introduce two macros around calling the functions in the
security operations vector. The marco versions here do not
change any behavior.
Signed-off-by: Casey Schaufler
---
security/security.c | 433
Subject: [PATCH 2/7 v22] LSM: Add the comment to lsm_hooks.h
Add the large comment describing the content of the
security_operations structure to lsm_hooks.h. This
wasn't done in the previous (1/7) patch because it
would have exceeded the mail list size limits.
Signed-off-by: Casey Schaufler
Subject: [PATCH 1/7 v22] LSM: Split security.h
The security.h header file serves two purposes,
interfaces for users of the security modules and
interfaces for security modules. Users of the
security modules don't need to know about what's
in the security_operations structure, so pull it
out into
Den 02.05.2015 22:03, Greg Kroah-Hartman skrev:
3.19-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Borkmann
commit afb7718016fcb0370ac29a83b2839c78b76c2960 upstream.
While originally only being intended for outgoing traffic, commit
On Sat, May 02, 2015 at 11:16:48PM +0200, Julia Lawall wrote:
> Some questions: Is the name OK? Is the NULL test needed? If not, should
> the call to kzalloc_node with the call to cfs_cpt_spread_node just be
> inlined into the call sites?
>
>
Subject: [PATCH 0/7 v22] LSM: Multiple concurrent LSMs
Replace the current ad hoc stacking of the capabilities
and Yama security modules with a generalized stacking scheme.
The old structure had a single set of module hooks contained
in a security_operations structure. This structure was
On May 2, 2015, at 5:16 PM, Julia Lawall wrote:
> Summarize OBD_CPT_ALLOC_GFP, OBD_CPT_ALLOC, and OBD_CPT_ALLOC_PTR as a
> function, obd_cpt_alloc.
>
> Signed-off-by: Julia Lawall
>
> ---
>
> Some questions: Is the name OK? Is the NULL test needed? If not, should
> the call to kzalloc_node
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Gu Zheng
commit 74672d069b298b03e9f657fd70915e055739882e upstream.
Simon reported the md io stats accounting issue:
"
I'm seeing "iostat -x -k 1" print this after a RAID1 rebuild on 4.0-rc5.
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Tom Herbert
[ Upstream commit 4e18b9adf2f910ec4d30b811a74a5b626e6c6125 ]
This function changes ip_summed to CHECKSUM_NONE if CHECKSUM_COMPLETE
is set. This is called to discard
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Galbraith
commit f8e617f4582995f7c25ef25b4167213120ad122b upstream.
To fully take advantage of MWAIT, apparently the CLFLUSH instruction needs
another quirk on certain CPUs: proper
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit 517e6341fa123ec3a2f9ea78ad547be910529881 upstream.
Ingo reported that cycles:pp didn't work for him on some machines.
It turns out that in this commit:
af4bdcf675cf
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nadav Amit
commit 9e9c3fe40bcd28e3f98f0ad8408435f4503f2781 upstream.
kvm_init_msr_list is currently called before hardware_setup. As a result,
vmx_mpx_supported always returns false when
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Tom Herbert
[ Upstream commit 3dfb05340ec6676e6fc71a9ae87bbbe66d3c2998 ]
Call checksum_complete_unset in PPP receive to discard checksum-complete
value. PPP does not pull checksum for headers
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Andrzej Pietrasiewicz
commit eb132ccbdec5df46e29c9814adf76075ce83576b upstream.
Function-specific setup requests should be handled in such a way, that
apart from filling in the data buffer,
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Gerald Schaefer
commit 97534127012f0e396eddea4691f4c9b170aed74b upstream.
Commit 61f77eda9bbf ("mm/hugetlb: reduce arch dependent code around
follow_huge_*") broke follow_huge_pmd() on s390,
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: David Hildenbrand
commit 15462e37ca848abac7477dece65f8af25febd744 upstream.
The reinjection of an I/O interrupt can fail if the list is at the limit
and between the dequeue and the
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Serebrin
commit 085e68eeafbf76e21848ad5bafaecec88a11dd64 upstream.
The host's decision to enable machine check exceptions should remain
in force during non-root mode. KVM was writing 0 to
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Markos Chandras
commit f7f8aea4b97c4d48e42f02cb37026bee445f239f upstream.
memsize denotes the amount of RAM we can access from kseg{0,1} and
that should be up to 256M. In case the bootloader
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: James Hogan
commit 98119ad53376885819d93dfb8737b6a9a61ca0ba upstream.
Guest user mode can generate a guest MSA Disabled exception on an MSA
capable core by simply trying to execute an MSA
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Markos Chandras
commit eeb538950367e3966cbf0237ab1a1dc30e059818 upstream.
Commit c1771216ab48 ("MIPS: kernel: unaligned: Handle unaligned
accesses for EVA") allowed unaligned accesses to be
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 845704a535e9b3c76448f52af1b70e4422ea03fd ]
Presence of an unbound loop in tcp_send_fin() had always been hard
to explain when analyzing crash dumps involving
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 79930f5892e134c6da1254389577fffb8bd72c66 ]
build_skb() should look at the page pfmemalloc status.
If set, this means page allocator allocated this page in the
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Khoroshilov
[ Upstream commit 0e03fd3e335d272bee88fe733d5fd13f5c5b7140 ]
Commit 43d3ddf87a57 ("net: pxa168_eth: add device tree support") starts
to use managed resources by adding
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Amir Vadai
[ Upstream commit b37069090b7c5615610a8aa6b36533d67b364d38 ]
mlx4_en_check_rxfh_func() was checking for hardware support before
setting a known RSS hash function, but didn't do any
Summarize OBD_CPT_ALLOC_GFP, OBD_CPT_ALLOC, and OBD_CPT_ALLOC_PTR as a
function, obd_cpt_alloc.
Signed-off-by: Julia Lawall
---
Some questions: Is the name OK? Is the NULL test needed? If not, should
the call to kzalloc_node with the call to cfs_cpt_spread_node just be
inlined into the call
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: =?UTF-8?q?Sebastian=20P=C3=B6hn?=
[ Upstream commit 2ab957492d13bb819400ac29ae55911d50a82a13 ]
Initial discussion was:
[FYI] xfrm: Don't lookup sk_policy for timewait sockets
Forwarded frames
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Oliver Neukum
commit 323ece54e0761198946ecd0c2091f1d2bfdfcb64 upstream.
Values directly from descriptors given in debug statements
must be converted to native endianness.
Signed-off-by:
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Ian Abbott
commit f20fbaad7620af2df36a1f9d1c9ecf48ead5b747 upstream.
`spidev_message()` sums the lengths of the individual SPI transfers to
determine the overall SPI message length. It
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt
commit 80a9b64e2c156b6523e7a01f2ba6e5d86e722814 upstream.
It has come to my attention that this_cpu_read/write are horrible on
architectures other than x86. Worse yet, they
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Krzysztof Kozlowski
commit 68c3ed6fa7e0d69529ced772d650ab128916a81d upstream.
The return value of power_supply_register() call was not checked and
even on error probe() function returned 0. If
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Huacai Chen
commit 0add9c2f1cff9f3f1f2eb7e9babefa872a9d14b9 upstream.
HPET irq is routed to i8259 and then to MIPS CPU irq (cascade). After
commit a3e6c1eff5 (MIPS: IRQ: Fix disable_irq on CPU
Hi,
> Felipe Balbi hat am 1. Mai 2015 um 16:48 geschrieben:
>
>
> clk_dump() will dump data about all clocks in JSON
> format, but it misses a newline character at the
> end of the JSON string. This patch adds that missing
> newline character.
>
> Signed-off-by: Felipe Balbi
Acked-by: Stefan
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Krzysztof Kozlowski
commit a2c1d531854c4319610f1d83351213b47a633969 upstream.
The return values of create_singlethread_workqueue() and
power_supply_register() calls were not checked and even
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit 767bf7e7a1e82a81c59778348d156993d0a6175d upstream.
Normally, when a CPU wants to clear a cache line to zero in the external
L2 cache, it would generate bus cycles to write
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Huacai Chen
commit a843d00d038b11267279e3b5388222320f9ddc1d upstream.
We found that TLB mismatch not only happens after kernel resume, but
also happens during snapshot restore. So move it to
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Ferre
commit 98b80987c940956da48f0c703f60340128bb8521 upstream.
After 57a38effa598 (net: phy: micrel: disable broadcast for KSZ8081/KSZ8091)
the macb1 interface refuses to work
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Andreas Faerber
commit 7e9e20b1faab02357501553d7f4e3efec1b4cfd3 upstream.
Resolve a merge conflict with mmc refactoring aaa25a5a33cb ("ARM: dts:
unuse the slot-node and deprecate the
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Axel Lin
commit 869aee0f31429fa9d94d5aef539602b73ae0cf4b upstream.
The res parameter passed to devm_usb_phy_match() is the location where the
pointer to the usb_phy is stored, hence it needs
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Felipe Balbi
commit 84c0d178eb9f3a3ae4d63dc97a440266cf17f7f5 upstream.
Make sure we're using the new macro, so our
resume signaling will always pass certification.
Signed-off-by: Felipe Balbi
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: NeilBrown
commit 47d68979cc968535cb87f3e5f2e6a3533ea48fbd upstream.
Since commit 20d0189b1012a37d2533a87fb451f7852f2418d1
in v3.14-rc1 RAID0 has performed incorrect calculations
when the
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Gernoth
commit 91bf0c2dcb935a87e5c0795f5047456b965fd143 upstream.
The functions snd_emu10k1_proc_spdif_read and snd_emu1010_fpga_read
acquire the emu_lock before accessing the FPGA.
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Felipe Balbi
commit 7a606ac29752a3e571b83f9b3fceb1eaa1d37781 upstream.
While this driver was already using a 50ms resume
timeout, let's make sure everybody uses the same
macro so it's easy to
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: David Henningsson
commit 7d1b6e29327428993ba568bdd8c66734070f45e0 upstream.
The ALC256 does not have a mixer nid at 0x0b, and there's no
loopback path (the output pins are directly connected
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Hui Wang
commit e8191a8e475551b277d85cd76c3f0f52fdf42e86 upstream.
We have two machines with alc256 codec in the pin quirk table, so
moving the common pins to ALC256_STANDARD_PINS.
BugLink:
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Ferre
commit 361918970b7426bba97a64678ef2b2679c37199b upstream.
We currently need two checks of the peripheral version in MACB_MID register.
One of them got out of sync after
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Oleg Nesterov
commit b72c186999e689cb0b055ab1c7b3cd8fffbeb5ed upstream.
ptrace_resume() is called when the tracee is still __TASK_TRACED. We set
tracee->exit_code and then wake_up_state()
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
commit e819f152104c9f7c9fe50e1aecce6f5d4bf06d65 upstream.
- Remove the unneeded declaration from pnode.h
- Mark umount_tree static as it has no callers outside of
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
commit c003b26ff98ca04a180ff34c38c007a3998d62f9 upstream.
umount_tree builds a list of mounts that need to be unmounted.
Utilize mnt_list for this purpose instead of
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
commit 411a938b5abc9cb126c41cccf5975ae464fe0f3e upstream.
- Modify __lookup_mnt_hash_last to ignore mounts that have MNT_UMOUNTED set.
- Don't remove mounts from the mount
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
commit 7bdb11de8ee4f4ae195e2fa19efd304e0b36c63b upstream.
Create a function unhash_mnt that contains the common code between
detach_mnt and umount_tree, and use unhash_mnt
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
commit ce07d891a0891d3c0d0c2d73d577490486b809e1 upstream.
Modify umount(MNT_DETACH) to keep mounts in the hash table that are
locked to their parent mounts, when the parent
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
commit f53e57975151f54ad8caa1b0ac8a78091cd5700a upstream.
lookup_mountpoint can return either NULL or an error value.
Update the test in __detach_mounts to test for an
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Boris Brezillon
commit 4591243102faa8de92da320edea47219901461e9 upstream.
The at91sam9n12 and at91sam9x5 usb clocks do not propagate rate
modification requests to their parents.
This causes a
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Brian Norris
commit f16db8071ce18819fbd705ddcc91c6f392fb61f8 upstream.
In some of the 'out_not_moved' error paths, lnum may be used
uninitialized. Don't ignore the warning; let's fix it.
This
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Akinobu Mita
commit 38da0f49e8aa1649af397d53f88e163d0e60c058 upstream.
When CONFIG_DEBUG_SG=y and DIF protection support enabled, kernel
BUG()s are triggered due to the following two issues:
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Ploumistos
commit 2eeff0b4317a02f0e281df891d990194f0737aae upstream.
Add 04f2:aff1 to ath3k.c supported devices list and btusb.c blacklist, so
that the device can load the ath3k
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Bo Yan
commit 6d1966dfd6e0ad2f8aa4b664ae1a62e33abe1998 upstream.
Register MIDR_EL1 is masked to get variant and revision fields, then
compared against midr_range_min and midr_range_max when
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Steve Capper
commit ad08fd494bf00c03ae372e0bbd9cefa37bf608d6 upstream.
Commit f4f75ad5 ("efi: efistub: Convert into static library")
introduced a static library for EFI stub, libstub.
The EFI
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit 905e8c5dcaa147163672b06fe9dcb5abaacbc711 upstream.
When running a compat (AArch32) userspace on Cortex-A53, a load at EL0
from a virtual address that matches the bottom 32
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Ellerman
commit 7261b956b276aa97fbf60d00f1d7717d2ea6ee78 upstream.
The patch to add it_page_shift incorrectly changed the increment of
uaddr to use it_page_shift, rather then (1 <<
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: "H.J. Lu"
commit 76aea7731e7050c066943a1d7456ec6510702601 upstream.
Commit:
c6e5e9fbc3ea ("perf tools: Fix building error in x86_64 when dwarf unwind is
on")
removed the definition of
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Manish Badarkhe
commit a57069e33fbc6625f39e1b09c88ea44629a35206 upstream.
As davinci card gets registered using 'devm_' api
there is no need to unregister the card in 'remove'
function.
Hence
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Ellerman
commit b0dd00addc5035f87ec9c5820dacc1ebc7fcb3e6 upstream.
The conversion from __get_cpu_var() to this_cpu_ptr() in iic_setup_cpu()
is wrong. It causes an oops at boot.
We
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Howard Mitchell
commit f073faa73626f41db7050a69edd5074c53ce6d6c upstream.
If den=1 and pllin_rate>20MHz then den and num are adjusted to 0
causing a divide by zero error a few lines further
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Pascal Huerst
commit 74ff960222d90999508b4ba0d3449f796695b6d5 upstream.
The delay time after a reset in the codec probe callback was too short,
and did not work on certain hw because the codec
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Octavian Purdila
commit 77ddc2fe08329e375505bc36a3df3233fe57317b upstream.
ACPICA commit c70434d4da13e65b6163c79a5aa16b40193631c7
ACPI_MTX_TABLES is acquired and released by the callers of
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Anton Blanchard
commit 9a5cbce421a283e6aea3c4007f141735bf9da8c3 upstream.
We cap 32bit userspace backtraces to PERF_MAX_STACK_DEPTH
(currently 127), but we forgot to do the same for 64bit
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Brian Norris
commit d74adbdb9abf0d2506a6c4afa534d894f28b763f upstream.
If aeb->len >= vol->reserved_pebs, we should not be writing aeb into the
PEB->LEB mapping.
Caught by Coverity, CID
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: "Steven Rostedt (Red Hat)"
commit c5e691928bf166ac03430e957038b60adba3cf6c upstream.
When a event PADDING is hit (a deleted event that is still in the ring
buffer), translate_data() sets the
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Collins
commit 0618764cb25f6fa9fb31152995de42a8a0496475 upstream.
I suspect this doesn't show up for most anyone because software
algorithms typically don't have a sense of being too busy.
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: Max Filippov
commit 4949009eb8d40a441dcddcd96e101e77d31cf1b2 upstream.
LCD driver is always built for the XTFPGA platform, but its base address
is not configurable, and is wrong for
4.0-stable review patch. If anyone has any objections, please let me know.
--
From: "K. Y. Srinivasan"
commit 40384e4bbeb9f2651fe9bffc0062d9f31ef625bf upstream.
Correctly rollback state if the failure occurs after we have handed over
the ownership of the buffer to the host.
1 - 100 of 1448 matches
Mail list logo