Add support for 2.0 address format. Also, align address bits for 1.2 and
2.0 to be able to operate on channel and luns without requiring a format
conversion. Use a generic address format for this purpose.
Signed-off-by: Javier González
---
drivers/lightnvm/core.c | 20
The function xfs_buftarg_isolate() used by xfs buffer schrinkers
to determine whether a buffer should be isolated and disposed
from LRU list, has inverted logic.
Excerpt from xfs_buftarg_isolate():
/*
* Decrement the b_lru_ref count unless the value is already
* zero.
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Lixin Wang
commit e0638fa400eaccf9fa8060f67140264c4e276552 upstream.
Reference count of device node was increased in of_i2c_register_device,
but without
On address conversions, use the generic device, instead of the target
device. This allows to use conversions outside of the target's realm.
Signed-off-by: Javier González
---
drivers/lightnvm/core.c | 4 ++--
include/linux/lightnvm.h | 8
2 files changed, 6
Thanks, applied.
Normalize nomenclature for naming channels, luns, chunks, planes and
sectors as well as derivations in order to improve readability.
Signed-off-by: Javier González
---
drivers/lightnvm/core.c | 89 +--
Separate the version between major and minor on the generic geometry and
represent it through sysfs in the 2.0 path. The 1.2 path only shows the
major version to preserve the existing user space interface.
Signed-off-by: Javier González
---
drivers/lightnvm/core.c | 4
Complete the generic geometry structure with the maxoc and maxocpu
felds, present in the 2.0 spec. Also, expose them through sysfs.
Signed-off-by: Javier González
---
drivers/nvme/host/lightnvm.c | 17 +
include/linux/lightnvm.h | 2 ++
2 files changed,
Currently, the device geometry is stored redundantly in the nvm_id and
nvm_geo structures at a device level. Moreover, when instantiating
targets on a specific number of LUNs, these structures are replicated
and manually modified to fit the instance channel and LUN partitioning.
Instead, create a
Hello Kees,
Thanks for your time spent on that!
> On 27 Feb 2018, at 23:52, Kees Cook wrote:
>
> I'd like more details on the threat model here; if it's just a matter
> of .so loading order, I wonder if load order randomization would get a
> comparable level of
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dennis Yang
commit 490ae017f54e55bde382d45ea24bddfb6d1a0aaf upstream.
For btree removal, there is a corner case that a single thread
could takes 6 locks which is more
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Thomas Petazzoni
commit 56aeb07c914a616ab84357d34f8414a69b140cdf upstream.
MPP7 is currently muxed as "gpio", but this function doesn't exist for
MPP7,
Assign missing mccap value on 2.0 path
Signed-off-by: Javier González
---
drivers/nvme/host/lightnvm.c | 4 +++-
include/linux/lightnvm.h | 8 +---
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/nvme/host/lightnvm.c
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Xin Long
commit c5006b8aa74599ce19104b31d322d2ea9ff887cc upstream.
The check in sctp_sockaddr_af is not robust enough to forbid binding a
v4mapped v6 addr on a v4
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 898dfe4687f460ba337a01c11549f87269a13fa2 upstream.
The aloop driver tries to update the hw constraints of the connected
target on the cable of the opened
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 06b335cb51af018d5feeff5dd4fd53847ddb675a upstream.
If a message sent to a PF_KEY socket ended with one of the extensions
that takes a 'struct
From: Ludovic Barre
This patch adds support for stm32 SDMMC controller.
The SDMMC controller provides an interface for SD,SDIO
cards and MMC devices.
The SDMMC features include the following:
-Full compliance with MultiMediaCard System Specification Version 4.51.
Card
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Oliver Stäbler
commit f6c23b174c3c96616514827407769cbcfc8005cf upstream.
After commit d75b1ade567f ("net: less interrupt masking in NAPI") napi
repoll is done
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johannes Thumshirn
commit ff658e9c1aae9a84dd06d46f847dc0cd2bf0dd11 upstream.
Currently the cleanup of all error cases are open-coded. Introduce a
common exit path and
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit e4ec40ec4b260efcca15089de4285a0a3411259b upstream.
xHC can generate two events for a short transfer if the short TRB and
last TRB in the TD
Hi,
On 28/02/18 02:27, Samuel Holland wrote:
> If a reception IRQ is pending when a mailbox channel is shut down (for
> example, if the controller uses threaded interrupts), it is possible for
> mbox_chan_received_data to be called while chan->cl is NULL.
>
> This was found while developing a
Hi Samuel,
thank you very much for writing and posting this!
On 28/02/18 08:28, Maxime Ripard wrote:
> Hi,
>
> On Tue, Feb 27, 2018 at 08:27:12PM -0600, Samuel Holland wrote:
>> This mailbox hardware is present in several Allwinner sun8i and sun50i
>> SoCs. Add a device tree binding for it.
>>
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 15fe076edea787807a7cdc168df832544b58eba6 upstream.
syzbot reported crashes [1] and provided a C repro easing bug hunting.
When/if packet_do_bind()
On Wed, 2018-02-28 at 14:20 +0900, Benjamin Poirier wrote:
> Before commit 19110cfbb34d ("e1000e: Separate signaling for link
> check/link
> up"), errors which happen after "get_link_status = false" in the
> copper
> check_for_link callbacks would be ignored and the link considered up.
> After
>
On Wed, Feb 28, 2018 at 05:00:58PM +0100, Marc-André Lureau wrote:
> Hi
>
> On Wed, Feb 28, 2018 at 4:48 PM, Michael S. Tsirkin wrote:
> > On Wed, Feb 28, 2018 at 04:41:51PM +0100, Marc-André Lureau wrote:
> >> I don't know if it's always safe to enable dma in read_raw(), how
>
[Adding MarcZ]
On Wed, Feb 28, 2018 at 06:01:00PM +0100, Grzegorz Jaszczyk wrote:
> Hitherto during machine_kexec_mask_interrupts there was an attempt to
> remove active state using irq_set_irqchip_state() routine and only if it
> failed, the attempt to EOI the interrupt was made. Nevertheless
On Thu, 15/2/18, Sudhir Sreedharan wrote:
...
> Cc: sta...@vger.kernel.org
> Signed-off-by: Sudhir Sreedharan
Acked-by: Hin-Tak Leung
On Wed, Feb 28, 2018 at 04:41:51PM +0100, Marc-André Lureau wrote:
> I don't know if it's always safe to enable dma in read_raw(), how
> could we know? Is there a check we could use to choose one or ther
> other (and thus avoiding explicit dma/readfn argument)?
IMHO the way to go is not to try to
From: Ludovic Barre
Document the binding for stm32 sdmmc controller.
Signed-off-by: Ludovic Barre
---
.../devicetree/bindings/mmc/st,stm32-sdmmc.txt | 35 ++
1 file changed, 35 insertions(+)
create mode 100644
From: Ludovic Barre
This patch adds support of micro sd card connected to sdmmc1.
Signed-off-by: Ludovic Barre
---
arch/arm/boot/dts/stm32h743-pinctrl.dtsi | 26 ++
arch/arm/boot/dts/stm32h743i-eval.dts| 11 +++
2
Hi,
On 02/28/18 02:32, Maxime Ripard wrote:
> On Tue, Feb 27, 2018 at 08:27:14PM -0600, Samuel Holland wrote:
>> +/*
>> + * The failure path should not disable the clock or assert the reset,
>> + * because the PSCI implementation in firmware relies on this device
>> + * being
From: Ludovic Barre
This patch serie adds support of stm32 SDMMC controller.
stm32h7 is the first SoC to use stm32 SDMMC controller
(previous SoC had pl180 controller).
The SDMMC features include the following:
-Full compliance with MultiMediaCard System Specification
Hi,
On 02/28/18 02:24, Maxime Ripard wrote:
> On Tue, Feb 27, 2018 at 08:27:11PM -0600, Samuel Holland wrote:
>> This series adds support for the "hardware message box" in recent
>> Allwinner sunxi SoCs, used for communication with the ARISC management
>> processor (the platform's equivalent of
On Wed, Feb 28, 2018 at 1:53 PM, Evgeniy Didin
wrote:
> In commit 9d9491a7da2a ("mmc: dw_mmc: Fix the DTO timeout calculation") and
> commit 4c2357f57dd5 ("mmc: dw_mmc: Fix the CTO timeout calculation")
> have been made changes which cause multiply overflow for 32-bit
From: Ludovic Barre
This patch adds support of
-mmc framework and stm32 sdmmc controller
-ext2/3/4 filesystem
-LBDAF to support huge file (needed for ext4)
Signed-off-by: Ludovic Barre
---
arch/arm/configs/stm32_defconfig | 4 +++-
1 file changed, 3
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit bcfd09f7837f5240c30fd2f52ee7293516641faa upstream.
Currently esp will happily create an xfrm state with an unknown
encap type for IPv4, without
On Mon, 26 Feb 2018, Vitaly Kuznetsov wrote:
For the non KVM pats of this series:
Acked-by: Thomas Gleixner
> Changes since v1:
> - The only comment I got for v1 was from kbuild test robot. The issue
> was addressed by moving HV_X64_ENLIGHTENED_VMCS_RECOMMENDED
From: Ludovic Barre
This patch adds sdmmc support for stm32h743.
2×SD/SDIO/MMC interfaces (up to 125 MHz)
Signed-off-by: Ludovic Barre
---
arch/arm/boot/dts/stm32h743.dtsi | 26 ++
1 file changed, 26 insertions(+)
diff --git
Add DCMI JPEG support.
Signed-off-by: Hugues Fruchet
---
version 2:
- Removed V4L2_FMT_FLAG_COMPRESSED flag setting already set by V4L2 core
See https://www.mail-archive.com/linux-media@vger.kernel.org/msg126825.html
drivers/media/platform/stm32/stm32-dcmi.c | 193
On 28.02.2018 17:14, Peter De Schrijver wrote:
> On Wed, Feb 28, 2018 at 03:00:23PM +0300, Dmitry Osipenko wrote:
>> On 28.02.2018 12:36, Peter De Schrijver wrote:
>>> On Tue, Feb 27, 2018 at 02:59:11PM +0300, Dmitry Osipenko wrote:
On 27.02.2018 02:04, Marcel Ziswiler wrote:
> On Mon,
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 9a00674213a3f00394f4e3221b88f2d21fc05789 upstream.
syzkaller triggered a NULL pointer dereference in crypto_remove_spawns()
via a program that
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit d16b46e4fd8bc6063624605f25b8c0835bb1fbe3 upstream.
We do not need locking in xfrm_trans_queue because it is designed
to use per-CPU buffers.
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Christian Holl
commit d14ac576d10f865970bb1324d337e5e24d79aaf4 upstream.
This adds the ELV ALC 8xxx Battery Charging device
to the list of USB IDs of
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Steven Rostedt (VMware)"
commit 45d8b80c2ac5d21cd1e2954431fb676bc2b1e099 upstream.
Two info bits were added to the "commit" part of the ring buffer data page
when
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Diego Elio Pettenò
commit 4307413256ac1e09b8f53e8715af3df9e49beec3 upstream.
Add IDs for the OneTouch Verio IQ that comes with an embedded
USB-to-serial converter.
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: David Howells
commit 98801506552593c9b8ac11021b0cdad12cab4f6b upstream.
Fix the default for fscache_maybe_release_page() for when the cookie isn't
valid or the page isn't
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 9685347aa0a5c2869058ca6ab79fd8e93084a67f upstream.
The aloop runtime object and its assignment in the cable are left even
when opening a substream fails.
Hi
On Wed, Feb 28, 2018 at 6:17 PM, Michael S. Tsirkin wrote:
> On Wed, Feb 28, 2018 at 04:41:51PM +0100, Marc-André Lureau wrote:
>> I don't know if it's always safe to enable dma in read_raw(), how
>> could we know? Is there a check we could use to choose one or ther
>> other
Commit-ID: 028091f82eefd5e84f81cef81a7673016ecbe78b
Gitweb: https://git.kernel.org/tip/028091f82eefd5e84f81cef81a7673016ecbe78b
Author: Sebastian Panceac
AuthorDate: Wed, 28 Feb 2018 11:40:49 +0200
Committer: Thomas Gleixner
CommitDate: Wed, 28
From: Jason Wang
Date: Wed, 28 Feb 2018 18:20:04 +0800
> We try to disable NAPI to prevent a single XDP TX queue being used by
> multiple cpus. But we don't check if device is up (NAPI is enabled),
> this could result stall because of infinite wait in
> napi_disable().
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 898dfe4687f460ba337a01c11549f87269a13fa2 upstream.
The aloop driver tries to update the hw constraints of the connected
target on the cable of the opened
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Shuah Khan
commit e1346fd87c71a1f61de1fe476ec8df1425ac931c upstream.
usbip_dump_usb_device() and usbip_dump_urb() print kernel addresses.
Remove kernel addresses from
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 6708913750344a900f2e73bfe4a4d6dbbce4fe8d upstream.
In the OSS emulation plugin builder where the frame size is parsed in
the plugin chain, some places miss
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Anshuman Khandual
commit 4991c09c7c812dba13ea9be79a68b4565bb1fa4e upstream.
While testing on a large CPU system, detected the following RCU stall
many times over
2018-02-28, Masahiro Yamada:
[snip]
> So, my idea is to rename existing
>
> HOSTCFLAGS -> KBUILD_HOSTCFLAGS
> HOSTCXXFLAGS -> KBUILD_HOSTCXXFLAGS
> HOSTLDFLAGS-> KBUILD_HOSTLDFLAGS
> HOST_LOADLIBES -> KBUILD_HOSTLDLIBS
>
>
> ("LOADLIBES" is too long, so rename it to "LDLIBS")
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 06b335cb51af018d5feeff5dd4fd53847ddb675a upstream.
If a message sent to a PF_KEY socket ended with one of the extensions
that takes a 'struct
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit ad23b750933ea7bf962678972a286c78a8fa36aa upstream.
Commit "net: igmp: Use correct source address on IGMPv3 reports"
introduced a check to validate the
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit fe08f34d066f4404934a509b6806db1a4f700c86 upstream.
syzkaller triggered kernel warnings through PCM OSS emulation at
closing a stream:
WARNING: CPU: 0 PID:
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Guillaume Nault
commit 02612bb05e51df8489db5e94d0cf8d1c81f87b0c upstream.
In pppoe_sendmsg(), reserving dev->hard_header_len bytes of headroom
was probably fine before
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Benjamin Poirier
commit 19110cfbb34d4af0cdfe14cd243f3b09dc95b013 upstream.
Lennart reported the following race condition:
\ e1000_watchdog_task
\ e1000e_has_link
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 4e765b4972af7b07adcb1feb16e7a525ce1f6b28 upstream.
If a message sent to a PF_KEY socket ended with an incomplete extension
header (fewer than 4 bytes
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 3ce120b16cc548472f80cf8644f90eda958cf1b6 upstream.
It appears that hardened gentoo enables "-fstack-check" by default for
gcc.
That
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Huacai Chen
commit 90addc6b3c9cda0146fbd62a08e234c2b224a80c upstream.
In non-coherent DMA mode, kernel uses cache flushing operations to
maintain I/O coherency, so scsi's
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Christophe Leroy
commit f8b39039cbf2a15f2b8c9f081e1cbd5dee00aaf5 upstream.
In case of TX timeout, fs_timeout() calls phy_stop(), which
triggers the following BUG_ON()
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Huacai Chen
commit c2e8fbf908afd81ad502b567a6639598f92c9b9d upstream.
The rps_resp buffer in ata_device is a DMA target, but it isn't
explicitly cacheline aligned. Due to
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 29159a4ed7044c52e3e2cf1a9fb55cec4745c60b upstream.
The loops for read and write in PCM OSS emulation have no proper check
of pending signals, and they keep
>From : Archana Sathyakumar
The Power Domain Controller (PDC) on QTI SoCs like SDM845 houses an
interrupt controller along with other domain control functions to handle
interrupt related functions like handle falling edge or active low which
are not detected at the GIC
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Benjamin Poirier
commit 4110e02eb45ea447ec6f5459c9934de0a273fb91 upstream.
e1000e_check_for_copper_link() and e1000_check_for_copper_link_ich8lan()
are the two functions
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Kevin Cernekee
commit a46182b00290839fa3fa159d54fd3237bd8669f0 upstream.
Closing a multicast socket after the final IPv4 address is deleted
from an interface can
On Wed, 2018-02-28 at 08:57 -0800, Guenter Roeck wrote:
> On Wed, Feb 28, 2018 at 03:20:17PM +, Ben Hutchings wrote:
> > This is the start of the stable review cycle for the 3.16.55 release.
> > There are 254 patches in this series, which will be posted as responses
> > to this one. If anyone
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit b088b53e20c7d09b5ab84c5688e609f478e5c417 upstream.
The extra hw constraint rule for the formats the aloop driver
introduced has a slight flaw, where it
Changes since v7:
- fix whitespace alignment for multi-line statement
- add Rob H 'reviewed-by' for DT bindings
- rebase on top of 4.6-rc3
On newer Qualcomm Techonologies Inc's SoCs like the SDM845, the GIC is in a
power domain that can be powered off when not needed.
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Xin Long
commit c5006b8aa74599ce19104b31d322d2ea9ff887cc upstream.
The check in sctp_sockaddr_af is not robust enough to forbid binding a
v4mapped v6 addr on a v4
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Li Jinyue
commit fbe0e839d1e22d88810f3ee3e2f1479be4c0aa4a upstream.
UBSAN reports signed integer overflow in kernel/futex.c:
UBSAN: Undefined behaviour in
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Xin Long
commit a0ff660058b88d12625a783ce9e5c1371c87951f upstream.
After commit cea0cc80a677 ("sctp: use the right sk after waking up from
wait_buf sleep"), it may
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Sergei Shtylyov
commit f9a531d6731d74f1e24298d9641c2dc1fef2631b upstream.
After the Ether platform data is fixed, the driver probe() method would
still
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Rui Hua
commit e393aa2446150536929140739f09c6ecbcbea7f0 upstream.
When we send a read request and hit the clean data in cache device, there
is a situation called cache
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Daniel Mentz
commit 025a26fa14f8fd55d50ab284a30c016a5be953d0 upstream.
Commit b2787845fb91 ("V4L/DVB (5289): Add support for video output
overlays.") added the field
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
commit 7839c672e58bf62da8f2f0197fefb442c02ba1dd upstream.
When we unmap the HYP memory, we try to be clever and unmap one
PGD at a time. If we start with a
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Maciej W. Rozycki"
commit dc24d0edf33c3e15099688b6bbdf7bdc24bf6e91 upstream.
Complement commit d614fd58a283 ("mips/ptrace: Preserve previous
registers for short regset
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Denys Vlasenko
commit 3876488444e71238e287459c39d7692b6f718c3e upstream.
Suggested by Andy.
Suggested-by: Andy Lutomirski
Signed-off-by: Denys
Hi,
On Wed, Feb 28, 2018 at 3:53 AM, Evgeniy Didin
wrote:
> In commit 9d9491a7da2a ("mmc: dw_mmc: Fix the DTO timeout calculation") and
> commit 4c2357f57dd5 ("mmc: dw_mmc: Fix the CTO timeout calculation")
> have been made changes which cause multiply overflow for
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Dmitry Fleytman Dmitry Fleytman
commit 7f038d256c723dd390d2fca942919573995f4cfd upstream.
Commit e0429362ab15
("usb: Add device quirk for Logitech HD Pro Webcams
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 23b19b7b50fe1867da8d431eea9cd3e4b6328c2c upstream.
muldiv32() contains a snd_BUG_ON() (which is morphed as WARN_ON() with
debug option) for checking the
On 27/02/2018 15:28, Tony Krowiak wrote:
Provides interfaces to assign AP adapters, usage domains
and control domains to a KVM guest.
A KVM guest is started by executing the Start Interpretive Execution (SIE)
instruction. The SIE state description is a control block that contains the
state
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Maciej W. Rozycki"
commit a03fe72572c12e98f4173f8a535f32468e48b6ec upstream.
In preparation to fix a commit 72b22bbad1e7 ("MIPS: Don't assume 64-bit
FP registers for FP
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
commit acf568ee859f098279eadf551612f103afdacb4e upstream.
This is an old bugbear of mine:
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit afd7fd81f22bf90474216515dbd6088f9bd70343 upstream.
The usb_add_gadget_udc_release() routine in the USB gadget core will
sometimes but not always
On Wed, 2018-02-28 at 16:01 +0100, Hans de Goede wrote:
> Hi,
>
> On 26-02-18 20:34, Andy Shevchenko wrote:
> > The commit 70216fd937fe introduced a workaround for incorrect
> > IoRestriction mode in ACPI table.
> >
> > Now, when GPIO ACPI library does it in generic way, just set
> > an
The commit
70216fd937fe ("extcon: int3496: Set the id pin to direction-input if
necessary")
introduced a workaround for incorrect IoRestriction mode in ACPI table.
Now, when GPIO ACPI library does it in generic way, see the commit
1b2ca32ab0b8 ("gpiolib: acpi: Introduce NO_RESTRICTION
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Adam Wallis
commit a9df21e34b422f79d9a9fa5c3eff8c2a53491be6 upstream.
Commit adfa543e7314 ("dmatest: don't use set_freezable_with_signal()")
introduced a bug (that is
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Steven Rostedt (VMware)"
commit 4397f04575c44e1440ec2e49b6302785c95fd2f8 upstream.
Jing Xia and Chunyan Zhang reported that on failing to allocate part of the
tracing
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit ddec3bdee05b06f1dda20ded003c3e10e4184cab upstream.
acpi_os_get_root_pointer() may return a valid address even if acpi_disabled
is set,
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Maciej W. Rozycki"
commit ed2d72c1eb3643b7c109bdf387563d9b9a30c279 upstream.
Respect the FCSR exception mask when interpreting the IEEE 754 exception
condition to
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
This is the revised backport of the upstream commit
b3defb791b26ea0683a93a4f49c77ec45ec96f10
We had another backport (e.g. 623e5c8ae32b in 4.4.115), but it applies
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Masakazu Mokuno
commit 81cf4a45360f70528f1f64ba018d61cb5767249a upstream.
As most of BOS descriptors are longer in length than their header
'struct
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Maciej W. Rozycki"
commit 4249548454f7ba4581aeee26bd83f42b48a14d15 upstream.
Fix a floating-point context restoration regression introduced with
commit 9b26616c8d9d ("MIPS:
On Wed, Feb 28, 2018 at 04:35:59PM +0100, Vitaly Kuznetsov wrote:
> Roman Kagan writes:
>
> > On Wed, Feb 28, 2018 at 02:44:01PM +0100, Vitaly Kuznetsov wrote:
> >> Hyper-V 2016 on KVM with SynIC enabled doesn't boot with the following
> >> trace:
> >>
> >> kvm_entry:
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit dcaf12a8b0bbdbfcfa2be8dff2c4948d9844b4ad upstream.
Fix child-node lookup during probe, which ended up searching the whole
device tree depth-first
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Oliver Neukum
commit b9096d9f15c142574ebebe8fbb137012bb9d99c2 upstream.
This modem needs this quirk to operate. It produces timeouts when
resumed without reset.
1001 - 1100 of 2974 matches
Mail list logo