Hi Kishon and Lorenzo,
On Wed, 28 Feb 2018, Lorenzo Pieralisi wrote:
> On Wed, Feb 28, 2018 at 02:07:19PM +0100, Rolf Evers-Fischer wrote:
> > From: Rolf Evers-Fischer
> >
> > Removes the goto labels completely, handles the errors at the
> > respective call site
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
On 27/02/2018 at 22:01:37 +0100, Jonas Gorski wrote:
> On 16 January 2018 at 11:12, Alexandre Belloni
> wrote:
> > Add a device tree include file for the Microsemi Ocelot SoC.
> >
> > Signed-off-by: Alexandre Belloni
> >
Hi,
On Wednesday 28 February 2018 06:37 PM, Rolf Evers-Fischer wrote:
> From: Rolf Evers-Fischer
>
> Removes the goto labels completely, handles the errors at the
> respective call site and just returns instead of jumping around.
>
> Signed-off-by: Rolf
On 2/15/2018 6:22 AM, frowand.l...@gmail.com wrote:
+static void of_populate_phandle_cache(void)
+{
+ unsigned long flags;
+ u32 cache_entries;
+ struct device_node *np;
+ u32 phandles = 0;
+
+ raw_spin_lock_irqsave(_lock, flags);
+
+ kfree(phandle_cache);
I ran into a randconfig link error on next-20180228 that appears to have
been caused by an older patch:
fs/ext2/inode.o: In function `ext2_setattr':
inode.c:(.text+0x19eb): undefined reference to `iomap_zero_range'
This adds a compile-time conditional around the code path so the
compiler can
usb_autopm_get_interface() that is called in usbtouch_open() does an
autoresume if the device is suspended.
input_dev->mutex used in usbtouch_resume() is in this case already
taken by the input subsystem and will cause a deadlock.
Signed-off-by: Marcus Folkesson
---
usb_autopm_get_interface() that is called in synusb_open() does an
autoresume if the device is suspended.
input_dev->mutex used in synusb_resume() is in this case already
taken by the input subsystem and will cause a deadlock.
Signed-off-by: Marcus Folkesson
---
From: Chao Yu
If we fail in ->remount_fs, it needs to restore old whint_mode as other
mount options.
Fixes: e25afe01822f ("f2fs: support passing down write hints given by users to
block layer")
Signed-off-by: Chao Yu
---
fs/f2fs/super.c | 1 +
1 file
Thanks to new documentation, we have a better view of the clock tree.
There were few mistakes in the first version of this driver, the main one
being the parental link between the clocks. Actually the tree is more
flat that we though. Most of the IP blocks require two clocks: one for
the IP itself
On Wed, Feb 28, 2018 at 10:11 PM, Geert Uytterhoeven
wrote:
> Hi Tomasz,
>
> On Wed, Feb 28, 2018 at 1:49 PM, Tomasz Figa wrote:
>> On Wed, Feb 28, 2018 at 9:32 PM, Geert Uytterhoeven
>> wrote:
>>> On Wed, Feb 28, 2018 at 1:29 PM,
On Wed, Feb 28, 2018 at 10:59:31AM -0300, Henrique de Moraes Holschuh wrote:
> Eek! If I read that right, this effectively halts the entire box until
> every core is updated, with one core entering deep-coma at a time (the
> rest are left either spinning or cpu_relax()ing
I think *you* should
(+ Stefano and Wei)
Hi,
On 02/27/2018 12:40 PM, Oleksandr Andrushchenko wrote:
Please find some more clarifications on VirtIO use with Xen
(I would like to thank Xen community for helping with this)
1. Possible security issues - VirtIO devices are PCI bus masters, thus
allowing real device
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, 2018-02-26 at 15:42 +0300, Dmitry Osipenko wrote:
>
Drop all of the code related to .remove hook and make use of
devm_nvmem_register() instead.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin Hilman
Srinivas, all:
This patchset contains various small changes that I recently made to
ppNVMEM, more specifically:
- Patches 1 and 3 are two changes I am hoping are acceptable upstream
- Patches 4 to 15 are a follow up to patch 2
- Patches 16 to 22 are just trivial fixups and I am more than
Add code to allow avoid having nvmem core append a numeric suffix to
the end of the name by passing config->id of -1.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Introduce devm_nvmem_register()/devm_nvmem_unregister() to make
.remove() unnecessary in trivial drivers.
Cc: Srinivas Kandagatla
Cc: Heiko Stuebner
Cc: Masahiro Yamada
Cc: Carlo Caione
Cc: Kevin
Various Intel SoCs (Cherry Trail, Broxton and others) have an internal USB
role switch for swiching the OTG USB data lines between the xHCI host
controller and the dwc3 gadget controller.
Note on some Cherry Trail systems there is ACPI/AML code listening to
edge interrupts on the id-pin (through
We need to add device-connections for the Type-C mux/switch and usb-role
code to be able to find the PI3USB30532 Type-C cross-switch and the
device/host role-switch integrated in the CHT SoC.
Reviewed-by: Heikki Krogerus
Reviewed-by: Andy Shevchenko
From: Heikki Krogerus
Several frameworks - clk, gpio, phy, pmw, etc. - maintain
lookup tables for describing connections and provide custom
API for handling them. This introduces a single generic
lookup table and API for the connections.
The motivation for this
The function is not small and getting bigger.
Let the compiler decide instead. No profiling done, hopefully
unnecessary.
Signed-off-by: Marc-André Lureau
---
drivers/firmware/qemu_fw_cfg.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Hi,
On 26-02-18 20:34, Randy Dunlap wrote:
On 02/26/2018 10:39 AM, Hans de Goede wrote:
diff --git a/include/linux/connection.h b/include/linux/connection.h
new file mode 100644
index ..0b4430eae53a
--- /dev/null
+++ b/include/linux/connection.h
@@ -0,0 +1,33 @@
+//
> -Original Message-
> From: Borislav Petkov [mailto:b...@suse.de]
> Sent: Wednesday, February 28, 2018 3:43 AM
> To: Ghannam, Yazen ; Tony Luck
>
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> ard.biesheu...@linaro.org;
The following patch is going to use the symbol from the fw_cfg module,
to call the function and write the note location details in the
vmcoreinfo entry, so qemu can produce dumps with the vmcoreinfo note.
CC: Andrew Morton
CC: Baoquan He
CC: Dave
Hi,
That's mostly good
On 22/02/2018 at 12:04:32 -0800, David Daney wrote:
> + priv->rtc->ops = _rtc_ops;
> + priv->rtc->nvram_old_abi = false;
This allocation is not necessary and I would refer not having t so when
the ABI goes away, it is not necessary to change this driver.
> +
On Wed, Feb 28, 2018 at 12:12:22PM +0200, Andy Shevchenko wrote:
> On Mon, 2018-02-26 at 12:19 -0600, Bjorn Helgaas wrote:
> > On Sun, Feb 25, 2018 at 03:27:04PM +0200, Andy Shevchenko wrote:
> > > On Fri, 2018-02-23 at 15:40 -0600, Bjorn Helgaas wrote:
> > > > On Thu, Feb 22, 2018 at 02:59:23PM
On 02/28/2018 07:23 AM, Jason Andryuk wrote:
> A toolstack may delete the vif frontend and backend xenstore entries
> while xen-netfront is in the removal code path. In that case, the
> checks for xenbus_read_driver_state would return XenbusStateUnknown, and
> xennet_remove would hang
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Wanpeng Li
commit d73235d17ba63b53dc0e1051dbc10a1f1be91b71 upstream.
*** Guest State ***
CR0: actual=0x0030, shadow=0x6010,
On Wed, 28 Feb 2018 12:53:27 +0100
Auger Eric wrote:
> Hi Shameer,
>
> On 28/02/18 10:25, Shameerali Kolothum Thodi wrote:
> >
> >
> >> -Original Message-
> >> From: Auger Eric [mailto:eric.au...@redhat.com]
> >> Sent: Wednesday, February 28, 2018 9:02 AM
> >>
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Zhao Qiang
commit c505873eaece2b4aefd07d339dc7e1400e0235ac upstream.
88E1145 also need this autoneg errata.
Fixes: f2899788353c ("net: phy: marvell: Limit errata to
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 85e9b13cbb130a3209f21bd7933933399c389ffe upstream.
Fix child-node lookup during probe, which ended up searching the whole
device tree depth-first
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Juan Zea
commit 544c4605acc5ae4afe7dd5914147947db182f2fb upstream.
usbip bind writes commands followed by random string when writing to
match_busid attribute in sysfs,
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit 1995266727fa8143897e89b55f5d3c79aa828420 upstream.
Commit bdcf0a423ea1 ("kernel: make groups_sort calling a responsibility
group_info
Add device tree binding documentation for the OV2680 camera sensor.
CC: devicet...@vger.kernel.org
Signed-off-by: Rui Miguel Silva
---
.../devicetree/bindings/media/i2c/ov2680.txt | 40 ++
1 file changed, 40 insertions(+)
create mode 100644
This patch adds V4L2 sub-device driver for OV2680 image sensor.
The OV2680 is a 1/5" CMOS color sensor from Omnivision.
Supports output format: 10-bit Raw RGB.
The OV2680 has a single lane MIPI interface.
The driver exposes following V4L2 controls:
- auto/manual exposure,
- exposure,
-
Add driver and bindings for the OV2680 2 megapixel CMOS 1/5" sensor, which has
a single MIPI lane interface and output format of 10-bit Raw RGB.
Features supported are described in PATCH 2/2.
v1->v2:
Fabio Estevam:
- s/OV5640/OV2680 in PATCH 1/2 changelog
Sakari Ailus:
- add description
On Wed, Feb 28, 2018 at 10:53:31AM +0800, jianchao.wang wrote:
> On 02/27/2018 11:13 PM, Keith Busch wrote:
> > On Tue, Feb 27, 2018 at 04:46:17PM +0800, Jianchao Wang wrote:
> >> Currently, adminq and ioq0 share the same irq vector. This is
> >> unfair for both amdinq and ioq0.
> >> - For
2018-02-28 9:15 GMT+09:00 Masahiro Yamada :
> Masahiro Yamada (6):
> kconfig: do not call check_conf() for olddefconfig
> kconfig: remove unneeded input_mode test in conf()
> kconfig: remove redundant input_mode test for check_conf() loop
> kconfig: hide
On 27/02/2018 15:28, Tony Krowiak wrote:
Introduces a new AP device driver. This device driver
is built on the VFIO mediated device framework. The framework
provides sysfs interfaces that facilitate passthrough
access by guests to devices installed on the linux host.
The VFIO AP device driver
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: David Kozub
commit 62354454625741f0569c2cbe45b2d192f8fd258e upstream.
There is another JMS567-based USB3 UAS enclosure (152d:0578) that fails
with the following
On 2/27/2018 11:19 PM, AKASHI Takahiro wrote:
Tyler,
# I missed catching your patch as its subject doesn't contain arm64.
On Fri, Feb 23, 2018 at 12:42:31PM -0700, Tyler Baicar wrote:
Currently on arm64 ESRT memory does not appear to be properly blocked off.
Upon successful initialization,
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Bin Liu
commit bd3486ded7a0c313a6575343e6c2b21d14476645 upstream.
When babble condition happens, the musb controller might automatically
turns off VBUS. On DA8xx platform, the
On Wed, Feb 28, 2018 at 12:51 PM, Bich HEMON wrote:
> For each port, get each IRQ using its specific name instead of its index.
>
> Signed-off-by: Bich Hemon
> ---
> drivers/tty/serial/stm32-usart.c | 4 ++--
> 1 file changed, 2 insertions(+), 2
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Shuah Khan
commit 90120d15f4c397272aaf41077960a157fc4212bf upstream.
usbip driver is leaking socket pointer address in messages. Remove
the messages that aren't
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Steve Wise
commit f55688c45442bc863f40ad678c638785b26cdce6 upstream.
If the RECV CQE is in error, ignore the MSN check. This was causing
recvs that were flushed
Hi,
On 28-02-18 16:15, Heikki Krogerus wrote:
On Wed, Feb 28, 2018 at 04:07:45PM +0100, Hans de Goede wrote:
diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
index 96099a245c69..5917e3095e2a 100644
--- a/drivers/usb/host/xhci.h
+++ b/drivers/usb/host/xhci.h
@@ -1825,6 +1825,7 @@
On 28/02/2018 at 15:56:41 +0100, Nicolas Ferre wrote:
> Change the entry name and move it to its alphabetical location.
> We move to ARM/Microchip instead of ARM/ATMEL to reflect the merger
> that is now nearly 2 years old.
> AT91 is kept as the identity of our community. The atmel pattern is
>
On Wed, Feb 28, 2018 at 10:20:33PM +0800, Jason Wang wrote:
>
>
> On 2018年02月28日 22:01, Michael S. Tsirkin wrote:
> > On Wed, Feb 28, 2018 at 02:28:21PM +0800, Jason Wang wrote:
> > >
> > > On 2018年02月28日 12:09, Michael S. Tsirkin wrote:
> > > > > > Or we can add plist to a union:
> > > > > >
Hi Keith
Thanks for your kindly response and directive
On 02/28/2018 11:27 PM, Keith Busch wrote:
> On Wed, Feb 28, 2018 at 10:53:31AM +0800, jianchao.wang wrote:
>> On 02/27/2018 11:13 PM, Keith Busch wrote:
>>> On Tue, Feb 27, 2018 at 04:46:17PM +0800, Jianchao Wang wrote:
Currently,
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 5a15f289ee87eaf33f13f08a4909ec99d837ec5f upstream.
The commit 89b89d121ffc ("ALSA: usb-audio: Add check return value for
usb_string()") added the check of
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit bb82e0b4a7e96494f0c1004ce50cec3d7b5fb3d1 upstream.
The commit f6f828513290 ("pstore: pass allocated memory region back to
caller") changed the check of the
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 2bd7b4aacdb6efa5ccd4749c365c171b884791d2 upstream.
The global array clashes with a newly added symbol of the same name:
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Max Schulze
commit c6a36ad383559a60a249aa6016cebf3cb8b6c485 upstream.
Add AIRBUS_DS_P8GR device IDs to ftdi_sio driver.
Signed-off-by: Max Schulze
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Hans Verkuil
commit 8ed5a59dcb47a6f76034ee760b36e089f3e82529 upstream.
The struct v4l2_plane32 should set m.userptr as well. The same
happens in v4l2_buffer32 and
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Nikolay Aleksandrov
commit 84aeb437ab98a2bce3d4b2111c79723aedfceb33 upstream.
The early call to br_stp_change_bridge_id in bridge's newlink can cause
a memory
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 7ae2c3c280db183ca9ada2675c34ec2f7378abfa upstream.
The error-handling pathways in usb_add_gadget_udc_release() are messed
up. Aside from the
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit bb82e0b4a7e96494f0c1004ce50cec3d7b5fb3d1 upstream.
The commit f6f828513290 ("pstore: pass allocated memory region back to
caller") changed the check of the
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mohamed Ghannam
commit 8f659a03a0ba9289b9aeb9b4470e6fb263d6f483 upstream.
inet->hdrincl is racy, and could lead to uninitialized stack pointer
usage, so its value
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jia Zhang
commit b94b7373317164402ff7728d10f7023127a02b60 upstream.
Instead of blacklisting all model 79 CPUs when attempting a late
microcode loading, limit that
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Tonghao Zhang
commit 8cb38a602478e9f806571f6920b0a3298aabf042 upstream.
The patch(180d8cd942ce) replaces all uses of struct sock fields'
memory_pressure,
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Mike Looijmans
commit 973593a960ddac0f14f0d8877d2d0abe0afda795 upstream.
Sometimes the USB device gets confused about the state of the initialization and
the
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Martin Kelly
commit 6aa8d5945502baf4687d80de59b7ac865e9e666b upstream.
In mcba_usb, we have observed that when you unplug the device, the driver will
endlessly resubmit
Hi,
On Wed, Feb 28, 2018 at 01:51:58PM +0100, Giulio Benetti wrote:
> sun4i_dclk_round_rate is called before sun4i_tcon_mode_set,
> so it finds dclk_min_div and dclk_max_div set to 0 and fails
> adding crtc.
>
> Move dclk_min_div and dclk_max_div to encoders init functions.
>
> Signed-off-by:
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Maciej W. Rozycki"
commit be07a6a1188372b6d19a3307ec33211fc9c9439d upstream.
Fix a commit 72b22bbad1e7 ("MIPS: Don't assume 64-bit FP registers for
FP regset") public API
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jaejoong Kim
commit 89b89d121ffcf8d9546633b98ded9d18b8f75891 upstream.
snd_usb_copy_string_desc() returns zero if usb_string() fails.
In case of failure, we need to
When dt_to_map_one_config() is called with a pinctrl_dev passed
in, it should only be using this if the node being looked up
is a hog. The code was always using the passed pinctrl_dev
without checking whether the dt node referred to it.
A pin controller can have pinctrl-n dependencies on other
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Robert Lippert
commit bd467e4eababe4c04272c1e646f066db02734c79 upstream.
Power values in the 100s of watt range can easily blow past
32bit math limits when processing
On 28 Feb 2018, at 10:47 PM, Matthew Wilcox wrote:
On Mon, Feb 26, 2018 at 11:04:57PM +0800, Kai-Heng Feng wrote:
+static char quirks_param[128];
+module_param_string(quirks, quirks_param, sizeof(quirks_param), 0644);
+MODULE_PARM_DESC(quirks, "Add/modify USB quirks by
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Oleg Nesterov
commit 4d9570158b6260f449e317a5f9ed030c2504a615 upstream.
As Tsukada explains, the time_is_before_jiffies(acct->needcheck) check
is very wrong, we need
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 0f30cbea005bd3077bd98cd29277d7fc2699c1da upstream.
Adding a specially crafted X.509 certificate whose subjectPublicKey
ASN.1 value is zero-length
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jeremy Compostella
commit 89c6efa61f5709327ecfa24bff18e57a4e80c7fa upstream.
On a I2C_SMBUS_I2C_BLOCK_DATA read request, if data->block[0] is
greater than
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Jia Zhang
commit 7e702d17ed138cf4ae7c00e8c00681ed464587c7 upstream.
Commit b94b73733171 ("x86/microcode/intel: Extend BDW late-loading with a
revision check")
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Maciej W. Rozycki"
commit 9b26616c8d9dae53fbac7f7cb2c6dd1308102976 upstream.
Define the central place the default FCSR value is set from, initialised
in `cpu_probe'.
Hi Philipp,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.16-rc3 next-20180228]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day
3.16.55-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.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit c93e64e91248becd0edb8f01723dff9da890e2ab upstream.
This patch fixes a bug in the error pathway of
usb_add_gadget_udc_release() in udc-core.c. If
3.16.55-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.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Daniele Palmas
commit 08933099e6404f588f81c2050bfec7313e06eeaf upstream.
This patch adds support for PID 0x1101 of Telit ME910.
Signed-off-by: Daniele Palmas
3.16.55-rc1 review patch. If anyone has any objections, please let me know.
--
From: Sergei Shtylyov
commit 50f3d740d376f664f6accc7e86c9afd8f1c7e1e4 upstream.
The TXALCR1 offsets are incorrect in the register offset tables, most
probably
2018-02-27 17:16 GMT+09:00 Cao jin :
> Signed-off-by: Cao jin
> ---
> I guess this belongs to kbuild though get_maintainer.pl doesn't tell me that.
>
Applied to linux-kbuild. Thanks!
--
Best Regards
Masahiro Yamada
We move the former Atmel wording to the the new Microchip name for this SoC
family. With the name of the directory we also change the content
in relation with the update of the MAINTAINERS file.
The Datasheet links now point to real documents instead of 404s.
Signed-off-by: Nicolas Ferre
On 28/02/18 14:37, Heiko Stübner wrote:
> Am Dienstag, 30. Januar 2018, 21:28:35 CET schrieb Thierry Escande:
>> From: zain wang
>>
>> The bridge does not need to be powered in analogix_dp_bind(), so
>> remove the calls to pm_runtime_get()/phy_power_on()/analogix_dp_init_dp()
Sudhir Sreedharan wrote:
> This can be reproduced by bind/unbind the driver multiple times
> in AM3517 board.
>
> Analysis revealed that rtl8187_start() was invoked before probe
> finishes(ie. before the mutex is initialized).
>
> INFO: trying to register non-static
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 appropriate quirk flag instead.
Cc: Hans de Goede
Signed-off-by:
2018-02-28 15:59 GMT+09:00 Arvind Prasanna :
> The package name is ncurses-devel for Redhat based distros
> and libncurses-devel for Debian based distros.
>
> Signed-off-by: Arvind Prasanna
> ---
> scripts/kconfig/lxdialog/check-lxdialog.sh | 3
On 27.02.2018 13:21, Richard Sandiford wrote:
> Hi Alexander,
>
> Sorry for the slow reply, been caught up in an office move.
Thank you very much for the review, Richard!
> Alexander Popov writes:
>> Would you be so kind to take a look at the whole STACKLEAK plugin?
>>
The AXP288 BC1.2 charger detection / extcon code may seem like a strange
place to add code to control the USB role-switch on devices with an AXP288,
but there are 2 reasons to do this inside the axp288 extcon code:
1) On many devices the USB role is controlled by ACPI AML code, but the AML
From: Heikki Krogerus
USB role switch is a device that can be used to choose the
data role for USB connector. With dual-role capable USB
controllers, the controller itself will be the switch, but
on some platforms the USB host and device controllers are
separate
Commit-ID: 1402fd8ed7e5bda1b3e7613b70780b0db392d1e6
Gitweb: https://git.kernel.org/tip/1402fd8ed7e5bda1b3e7613b70780b0db392d1e6
Author: Josh Poimboeuf
AuthorDate: Wed, 28 Feb 2018 07:19:21 -0600
Committer: Thomas Gleixner
CommitDate: Wed, 28 Feb
The xHCI controller on various Intel SoCs has an extended cap mmio-range
which contains registers to control the muxing to the xHCI (host mode)
or the dwc3 (device mode) and vbus-detection for the otg usb-phy.
Having a role-sw driver included in the xHCI code (under drivers/usb/host)
is not
Setting the mux to MUX_NONE and the switch to USB_SWITCH_DISCONNECT when
the data-role is device is not correct. Plenty of devices support
operating as USB device through a (separate) USB device controller.
We really need 2 different versions of USB_SWITCH_CONNECT,
USB_SWITCH_CONNECT_HOST and
On Monday, February 26, 2018 04:04:17 PM Kees Cook wrote:
> This is a small series that cleans up struct consw a bit and
> prepares it for Control Flow Integrity checking (i.e. Clang's
> -fsanitize=cfi).
for drivers/video/ parts:
Acked-by: Bartlomiej Zolnierkiewicz
On Wednesday, February 28, 2018 04:09:47 PM Bartlomiej Zolnierkiewicz wrote:
> On Monday, February 26, 2018 04:04:17 PM Kees Cook wrote:
> > This is a small series that cleans up struct consw a bit and
> > prepares it for Control Flow Integrity checking (i.e. Clang's
> > -fsanitize=cfi).
>
> for
On 02/28/2018 03:51 PM, Sodagudi Prasad wrote:
> Hi All,
>
> Trying to boot 4.14.19 kernel with Android and observed a crash in bpf system.
> From the call stack netd process is trying to access the
> /sys/fs/bfp/traffic_cookie_uid_map file.
> After checking call stack further observed that,
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit c1cfd9025cc394fd137a01159d74335c5ac978ce upstream.
The rawmidi also allows to obtaining the information via ioctl of ctl
API. It means that user can issue
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: "Rafael J. Wysocki"
commit 5839ee7389e893a31e4e3c9cf17b50d14103c902 upstream.
It is incorrect to call pci_restore_state() for devices in low-power
states (D1-D3),
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Thiago Rafael Becker
commit bdcf0a423ea1c40bbb40e7ee483b50fc8aa3d758 upstream.
In testing, we found that nfsd threads may call set_groups in parallel
for the same
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Christoph Paasch
commit 30791ac41927ebd3e75486f9504b6d2280463bf0 upstream.
The MD5-key that belongs to a connection is identified by the peer's
IP-address. When we are in
3.2.100-rc1 review patch. If anyone has any objections, please let me know.
--
From: Martin Kelly
commit 7a31ced3de06e9878e4f9c3abe8f87d9344d8144 upstream.
In mcba_usb, we have observed that when you unplug the device, the driver will
endlessly resubmit
601 - 700 of 2974 matches
Mail list logo