On Thu, 05 Jan 2017 13:26:07 +0100,
Tomi Valkeinen wrote:
>
> On 04/01/17 15:50, Takashi Iwai wrote:
> > On Tue, 03 Jan 2017 16:03:22 +0100,
> > Takashi Iwai wrote:
> >>
> >> fbcon can deal with vc_hi_font_mask (the upper 256 chars) and adjust
> >> the vc attrs dynamically when vc_hi_font_mask is
This is patchset v8, it takes care of compilation warnings
reported in v7.
Imran Khan (2):
soc: qcom: Add SoC info driver
Documentation/ABI: Add ABI information for QCOM socinfo driver
Documentation/ABI/stable/sysfs-driver-qcom_socinfo | 147 ++
drivers/soc/qcom/Kconfig
On 01/09/2017 06:29 AM, Sekhar Nori wrote:
On Friday 06 January 2017 10:03 AM, David Lechner wrote:
This enables the iio subsystem and the TI ADS7950 driver. This is used by
LEGO MINDSTORMS EV3, which has an ADS7957 chip.
Can you add your sign-off?
---
The CONFIG_TI_ADS7950 driver is
On 1/10/2017 7:00 AM, Lorenzo Pieralisi wrote:
> Commit 618f535a6062 ("ACPI/IORT: Add single mapping function")
> introduced a function (iort_node_get_id()) to retrieve ids for IORT
> named components.
>
> The iort_node_get_id() takes an index as input to refer to a specific
> mapping entry in
On 09/01/17 13:45, Eric Auger wrote:
> From: Robin Murphy
>
> Whilst PCI devices may have 64-bit DMA masks, they still benefit from
> using 32-bit addresses wherever possible in order to avoid DAC (PCI) or
> longer address packets (PCIe), which may incur a performance
On 12/22/2016 03:41 PM, Dr. Greg Wettstein wrote:
> Functionality of the xen-tpmfront driver was lost secondary to
> the introduction of xenbus multi-page support in the following
> commit:
>
> ccc9d90a9a8b5c4ad7e9708ec41f75ff9e98d61d
>
> xenbus_client: Extend interface to support multi-page ring
The SoC info driver provides information such as Chip ID,
Chip family, serial number and other such details about
Qualcomm SoCs to user space, so that if needed some user
space utility(like antutu) can query such information
using sysfs interface.
Signed-off-by: Imran Khan
The socinfo ABI document describes the information provided
by socinfo driver and the corresponding attributes to access
that information.
Signed-off-by: Imran Khan
---
Documentation/ABI/stable/sysfs-driver-qcom_socinfo | 147 +
1 file changed, 147
On Thu 2016-12-08 22:46:55, Abel Vesa wrote:
> On Thu, Dec 08, 2016 at 09:46:35PM +, Abel Vesa wrote:
> > From: Jean-Jacques Hiblot
> >
> > From: Jean-Jacques Hiblot
>
> >From statement twice in the commit message. Will resend.
> >
> >
On Tue, Jan 10, 2017 at 05:33:15PM +0200, Ville Syrjälä wrote:
> On Tue, Jan 10, 2017 at 12:26:53PM +, Jose Abreu wrote:
> > Hi Ville,
> >
> >
> > On 10-01-2017 11:16, Ville Syrjälä wrote:
> > > On Thu, Jan 05, 2017 at 02:46:06PM +, Jose Abreu wrote:
> > >>
> >
> > [snip]
> >
> > >>
On Sat, 7 Jan 2017 14:28:42 +0900
Masami Hiramatsu wrote:
> Find probe events without -m "module" option. If perf-probe
> failed to find given function in kernel image, it tries to
> find same symbol and module in kallsyms, and retry search
> in the found module. E.g.
>
>
On Tue, Jan 10, 2017 at 02:43:05PM +0100, Tomeu Vizoso wrote:
> Use drm_accurate_vblank_count so we have the full 32 bit to represent
> the frame counter and userspace has a simpler way of knowing when the
> counter wraps around.
>
> Signed-off-by: Tomeu Vizoso
>
On Mon, Jan 9, 2017 at 2:30 PM, Stefano Stabellini
wrote:
> On Mon, 9 Jan 2017, Konrad Rzeszutek Wilk wrote:
>> On Mon, Jan 09, 2017 at 10:42:41AM -0500, Dan Streetman wrote:
>> > On Mon, Jan 9, 2017 at 9:59 AM, Boris Ostrovsky
>> > wrote:
>> >
On Tue, Jan 10, 2017 at 3:46 PM, Vivek Goyal wrote:
> On Tue, Jan 10, 2017 at 02:26:48PM +0300, Konstantin Khlebnikov wrote:
>> If overlay was mounted by root then quota set for upper layer does not work
>> because overlay now always use mounter's credentials for operations.
>>
On Fri, Jan 06, 2017 at 11:23:30AM +0100, Jan Kara wrote:
> So what I think needs to be done is that we make backing_dev_info
> independently allocated structure with different lifetime rules to gendisk
> or request_queue - definitely I want it to live as long as block device
> inode exists.
On Tue, 2017-01-10 at 18:11 +0300, Alexey Brodkin wrote:
> With CONFIG_DYNAMIC_DEBUG if dyndbg enables debug output in
> 8250_port.c deadlock happens inevitably on UART IRQ handling.
>
> That's the problematic execution path:
> >8
> UART IRQ:
>
This enables the iio subsystem. This will be used by LEGO MINDSTORMS EV3,
which has a TI ADS7957 A/DC chip.
Signed-off-by: David Lechner
---
arch/arm/configs/davinci_all_defconfig | 6 ++
1 file changed, 6 insertions(+)
diff --git
On Tue, Jan 10, 2017 at 02:26:48PM +0300, Konstantin Khlebnikov wrote:
> If overlay was mounted by root then quota set for upper layer does not work
> because overlay now always use mounter's credentials for operations.
>
Hi Konstantin,
So CAP_SYS_RESOURCE bypasses the quota checks?
I just
Hello,
On Mon, Jan 09, 2017 at 05:11:12PM +0100, Bartlomiej Zolnierkiewicz wrote:
> > Disabling CONFIG_ATA_VERBOSE_ERROR saved 1380 bytes, which is less than the
> > value advertised by Kconfig (6KB).
>
> If it is only ~1kB nowadays I would vote for making the error logging always
> verbose and
Hi,
On Tuesday, January 10, 2017 04:47:30 PM Takashi Iwai wrote:
> On Thu, 05 Jan 2017 13:26:07 +0100,
> Tomi Valkeinen wrote:
> >
> > On 04/01/17 15:50, Takashi Iwai wrote:
> > > On Tue, 03 Jan 2017 16:03:22 +0100,
> > > Takashi Iwai wrote:
> > >>
> > >> fbcon can deal with vc_hi_font_mask
With RMI4 over SMBus, the pass-through device can be instantiated
in a SMBus driver. However, compared to the psmouse-synaptics driver,
this pass-through PS/2 driver has no clue whether the current
serio_interrupt() is the beginning of the frame or not. Instead of
adding a protocol analysis in
If a function needs to communicate with an other, it's better to have
a way to retrieve this other.
Reviewed-by: Andrew Duggan
Signed-off-by: Benjamin Tissoires
---
drivers/input/rmi4/rmi_driver.c | 13 +
This driver is a glue between PS/2 devices that enumerate
the RMI4 devices and Elan touchpads to the RMI4 (or Elan)
SMBus driver.
We use an intermediate platform device to not add a
dependency between psmouse and I2C. It also handles
the subtleties of going around the serio mutex lock by
The SMBus Synaptics devices enumerated as PS/2 devices have
the problem of being deaf to I2C if the touchpad has been
fully initialized over PS/2 (psmouse_activate being called).
A simple PS/2 deactivate command is enough to make it back alive.
We forward the serio parent node to rmi_smbus so it
On Fri, Dec 30, 2016 at 03:01:15PM +0100, Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> This patchset adds m68k/Atari Falcon PATA support to libata.
> The major difference in the new libata's pata_falcon host
> driver when compared to legacy IDE's falconide host driver is
> that we are using polled
In the same way Synaptics devices can use a secondary bus with a better
bandwidth, Elantech touchpads can also be talked over SMBus.
It's unclear right now which devices have this capability, so use a module
parameter to enable/disable this. We can then whitelist them until we find
a more
Most of the Synaptics devices are connected through PS/2 and a different
bus (SMBus or HID over I2C).
The secondary bus capability is indicated by the InterTouch bit in
extended capability 0x0C.
When we encounter such a device, we can create a platform device with
the information gathered through
Hi,
Well, this is the last series which enables RMI4 over SMBus for the Thinkpad
t*40, t*50, t*60 series. Few comments on the patches:
patches 1 to 3 allows the re-routing of the trackstick buttons from the touchpad
to the trackstick
patch 4 to 7 allow rmi_smbus to actually control the PS/2
On the latest series of ThinkPads, the button events for the TrackPoint
are reported through the touchpad itself as opposed to the TrackPoint
device. In order to report these buttons properly, we need to forward
them to the TrackPoint device and send the button presses/releases
through there
The Elan touchpads over I2C/SMBus also can handle a
trackstick. Unfortunately, nothing tells us if the
device supports trackstick (the information lies in
the PS/2 node), so rely on a platform data to enable
or not the trackstick node.
Link: https://bugzilla.redhat.com/show_bug.cgi?id=1313939
In some rare cases, we can't retrieve the SMBus version and so we fail
binding the touchpad back. Instead of leaving a touchpad dead, try again
to reinitialize it.
Signed-off-by: Benjamin Tissoires
---
drivers/input/rmi4/rmi_smbus.c | 19 ++-
1
The RMI4 over SMBus and PS/2 implementation of Synaptics touchpads are
mutually exclusive. We need a way to deactivate the touchpad from the PS/2
node and prevent it to not rebind itself during resume.
Signed-off-by: Benjamin Tissoires
---
On Tue, Jan 10, 2017 at 12:02:12AM +, Parav Pandit wrote:
> Patchset is compiled and tested against below Tejun's cgroup tree
> using cgroup v1 and v2 mode.
> URL: git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git
> Branch: for-4.11
Applied 1-3 to cgroup/for-4.11-rdmacg.
Thanks.
On Monday, November 28, 2016 2:24:00 PM CET Ross Zwisler wrote:
> On Mon, Nov 28, 2016 at 10:12:17PM +0100, Arnd Bergmann wrote:
> > Without the get_block based I/O, we get warnings when CONFIG_FS_IOMAP
> > is disabled:
> >
> > fs/dax.c:736:12: error: ‘dax_insert_mapping’ defined but not used
>
Hello,
I have some trouble with this patch.
It seems the intention is to allow CMA to be placed in highmem. If the
CMA area is larger than highmem and no alloc-ranges is specified (just a
size) it is possible to end up allocating a area that spans from
multiple zones. This later breaks
On Mon, Jan 9, 2017 at 10:05 AM, David Hildenbrand wrote:
>
>> Even though this work is not complete (see limitations below), I'd
>> appreciate
>> early feedback on this RFC. Specifically, I'm interested in:
>> - Is it better to have a kernel config or to make it configurable at
I though a bit more about it, and I don't really like the new compatible
string. I don't feel this should be necessary.
What about the following:
diff --git a/arch/arm/mach-at91/pm.c b/arch/arm/mach-at91/pm.c
index b4332b727e9c..0333aca63e44 100644
--- a/arch/arm/mach-at91/pm.c
+++
Hi Joerg,
On 09/01/2017 14:45, Eric Auger wrote:
> A new iommu-group sysfs attribute file is introduced. It contains
> the list of reserved regions for the iommu-group. Each reserved
> region is described on a separate line:
> - first field is the start IOVA address,
> - second is the end IOVA
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 9e6e7c74315095fd40f41003850690c711e44420 upstream.
We added some new locking but forgot to unlock on error.
Fixes: 57127645d79d ("s390/zcrypt:
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Chen-Yu Tsai
commit 937ff9ded8b6ebe8963ade55bdd77a61ded88075 upstream.
The audio module clocks are supposed to be set according to the sample
rate of the audio stream. The audio
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit 58010fa6f71c9577922b22e46014b95a4ec80fa0 upstream.
The AES key schedule generation is mostly endian agnostic, with the
exception of the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ming Ling
commit 6afcf8ef0ca0a69d014f8edb613d94821f0ae700 upstream.
Since commit bda807d44454 ("mm: migrate: support non-lru movable page
migration")
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit e2a91f4f42018994d7424d405900d17eba6555d0 upstream.
PDF build on Kernel 4.9-rc? returns an error with Sphinx 1.3.x
and Sphinx 1.4.x, when
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit 174122c39c369ed924d2608fc0be0171997ce800 upstream.
The SHA256 digest is an array of 8 32-bit quantities, so we should refer
to them as such in
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Weiner
commit 59749e6ce53735d8b696763742225f126e94603f upstream.
The radix tree counts valid entries in each tree node. Entries stored
in the tree cannot be
On Mon, Jan 09, 2017 at 09:33:42PM -0600, Suthikulpanit, Suravee wrote:
> +static struct amd_iommu *get_amd_iommu(uint idx)
> +{
> + uint i = 0;
> + struct amd_iommu *iommu = NULL;
> +
> + for_each_iommu(iommu) {
> + if (i == idx)
> + break;
> +
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Heikki Krogerus
commit 8f8983a5683623b62b339d159573f95a1fce44f3 upstream.
Intel Gemini Lake SoC has the same DWC3 than Broxton. Add
the new ID to the supported
On Tue, Jan 10, 2017 at 11:47:42AM +0100, Arnd Bergmann wrote:
> I see that we have CONFIG_ARCH_PHYS_ADDR_T_64BIT on a couple of
> 32-bit architectures without swiotlb (arc, arm, some mips32), and
> there are several 64-bit architectures that do not have swiotlb
> (alpha, parisc, s390, sparc). I
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Roger Quadros
commit 9418ee15f718939aa7e650fd586d73765eb21f20 upstream.
DCFG.DEVSPD == 0x3 is not valid and we need to set
DCFG.DEVSPD to 0x1 for full speed mode. Same goes for
Em Tue, Jan 10, 2017 at 10:22:50AM +, Sudeep Holla escreveu:
> All the other occurrence refer "uapi/asm-generic/*.h" directly instead
> of "uapi/asm/*.h" in tools/include except mman.h. Without this patch,
> the following build failure is seen.
>
Seen where? I don't see it here, and I build
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 0a8fd1346254974c3a852338508e4a4cddbb35f1 upstream.
When checking a new device's descriptors, the USB core does not check
for duplicate endpoint
On Mon, Jan 09, 2017 at 10:09:51PM +0100, Julia Lawall wrote:
>
>
> On Mon, 9 Jan 2017, Luis R. Rodriguez wrote:
>
> > On Mon, Dec 19, 2016 at 11:23:17AM +0100, Julia Lawall wrote:
> > >
> > >
> > > On Fri, 16 Dec 2016, Luis R. Rodriguez wrote:
> > >
> > > > We need to ensure that when driver
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Felipe Balbi
commit e71d363d9c611c99fb78f53bfee99616e7fe352c upstream.
Now that we're handling so many transfers at a time
and for some dwc3 revisions LPM events
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit faab50984fe6636e616c7cc3d30308ba391d36fd upstream.
Andrey Konovalov reports that fuzz testing with syzkaller causes a
KASAN warning in gadgetfs:
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit cc0909248258f679c4bb4cd315565d40abaf6bc6 upstream.
Fix NULL-pointer dereference in open() should the device lack the
expected endpoints:
Unable to handle
On Tue, Jan 10, 2017 at 03:47:25PM +0300, Nikita Yushchenko wrote:
> With this direction, semantics of dma mask becomes even more
> questionable. I'd say dma_mask is candidate for removal (or to move to
> swiotlb's or iommu's local area)
We need the dma mask so that the device can advertise what
OPOS6UL is an i.MX6UL based SoM.
OPOS6ULDev is a carrier board for the OPOS6UL SoM.
For more details see:
http://www.opossom.com/english/products-processor_boards-opos6ul.html
http://www.opossom.com/english/products-development_boards-opos6ul_dev.html
Signed-off-by: Sébastien Szymanski
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit f09d1886a41e9063b43da493ef0e845ac8afd2fa upstream.
The write URB was being killed using the synchronous interface while
holding a spin lock in close().
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Lu Baolu
commit 4dea70778c0f48b4385c7720c363ec8d37a401b4 upstream.
In command timer function, xhci_handle_command_timeout(), xhci->lock
is unlocked before call into
The core provides now an ABI to userspace for generation of frame CRCs,
so implement the ->set_crc_source() callback and reuse as much code as
possible with the previous ABI implementation.
When handling the pageflip interrupt, we skip 1 or 2 frames depending on
the HW because they contain wrong
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Srinivas Pandruvada
commit 143fca77cce906d35f7a60ccef648e888df589f2 upstream.
While applying patch d443a0aa3a29: "HID: hid-sensor-hub: clear memory to
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit 58010fa6f71c9577922b22e46014b95a4ec80fa0 upstream.
The AES key schedule generation is mostly endian agnostic, with the
exception of the
On Tue, Jan 10, 2017 at 02:42:23PM +0100, Arnd Bergmann wrote:
> It's a much rarer problem for the IOMMU case though, because it only
> impacts devices that are restricted to addressing of less than 32-bits.
>
> If you have an IOMMU enabled, the dma-mapping interface does not care
> if the device
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit ee71e5f1e7d25543ee63a80451871f8985b8d431 upstream.
The SHA1 digest is an array of 5 32-bit quantities, so we should refer
to them as such in
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit 1803b9a52c4e5a5dbb8a27126f6bc06939359753 upstream.
The core AES cipher implementation that uses ARMv8 Crypto Extensions
instructions
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Pan Bian
commit 20979202ee6e4c68dab7bcf408787225a656d18e upstream.
Fix bug https://bugzilla.kernel.org/show_bug.cgi?id=188561. Function
wm831x_clkout_is_prepared() returns
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jacob Pan
commit 65ca7f5f7d1cdde6c25172fe6107cd16902f826f upstream.
Different encodings are used to represent supported PASID bits
and number of PASID table
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 91a1ff4d53c5184d383d0baeeaeab6f9736f2ff3 upstream.
The interrupt URB was submitted on probe but never stopped on probe
errors. This can lead to
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit af15769ffab13d777e55fdef09d0762bf0c249c4 upstream.
gcc-7 notices that the condition in mvs_94xx_command_active looks
suspicious:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 75dd211e773afcbc264677b0749d1cf7d937ab2d upstream.
Do not submit the interrupt URB until after the parport has been
successfully registered to avoid
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
[resolves a messed up backport, so no matching upstream commit]
The backport of upstream commit 777c6e0daebb ("hotplug: Make
register and unregister notifier API
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit b05aebc25fdc5aeeac3ee29f0dc9f58dd07c13cc upstream.
Fix NULL-pointer dereference at port open if a device lacks the expected
bulk in and out endpoints.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Usyskin
commit 5026c9cb0744a9cd40242743ca91a5d712f468c6 upstream.
Adjust function name in KDoc.
Fixes: d49dc5e76fc9 (mei: bus: use mei_cldev_ prefix for
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Pan Bian
commit 3c3dd1e058cb01e835dcade4b54a6f13ffaeaf7c upstream.
Function klsi_105_open() calls usb_control_msg() (to "enable read") and
checks its return value. When
Hi Murali,
On Wed, Jan 04, 2017 at 02:32:30PM -0500, Murali Karicheri wrote:
> Recent fixes for iATU unroll support introduced a bug that causes
> asynchronous external abort in Keystone PCIe h/w which doesn't have
> ATU port and the corresponding register. So the check should be moved
> below
This makes the handlers for IPMI users able to be const, then
sets all the users const. Trivial, but I need an ack from the
ACPI people on this. Thanks.
With CONFIG_DYNAMIC_DEBUG if dyndbg enables debug output in
8250_port.c deadlock happens inevitably on UART IRQ handling.
That's the problematic execution path:
>8
UART IRQ:
serial8250_interrupt() ->
serial8250_handle_irq(): lock
On Tue, Jan 10, 2017 at 07:46:17PM +0800, Cao jin wrote:
>
>
> On 01/10/2017 07:04 AM, Michael S. Tsirkin wrote:
> > On Sat, Dec 31, 2016 at 05:15:36PM +0800, Cao jin wrote:
> >> Support serious device error recovery
> >
> > serious?
> >
>
> Sorry for my poor vocabulary if it confuses people.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 015105b12183556771e111e93f5266851e7c5582 upstream.
Make sure to drop the references taken by of_parse_phandle() and
bus_find_device() before returning
On Tue, Jan 10, 2017 at 12:26:53PM +, Jose Abreu wrote:
> Hi Ville,
>
>
> On 10-01-2017 11:16, Ville Syrjälä wrote:
> > On Thu, Jan 05, 2017 at 02:46:06PM +, Jose Abreu wrote:
> >>
>
> [snip]
>
> >> The pixel clock rate is half of the TMDS character rate in 4:2:0
> >> (in 24 bit), but
On Mon, 2017-01-09 at 21:54 -0500, Mimi Zohar wrote:
> On Mon, 2017-01-09 at 14:44 -0500, Jeff Layton wrote:
> >
> > On Sun, 2017-01-08 at 20:09 +0100, Christoph Hellwig wrote:
> > >
> > > On Sun, Jan 08, 2017 at 10:57:28AM -0800, James Bottomley wrote:
> > > >
> > > >
> > > > I'm unsure about
On Tue, Jan 10, 2017 at 10:15 AM, Tejun Heo wrote:
> On Tue, Jan 10, 2017 at 12:02:12AM +, Parav Pandit wrote:
>> Patchset is compiled and tested against below Tejun's cgroup tree
>> using cgroup v1 and v2 mode.
>> URL:
Hi,
The patchset generally looks fine to me but I have a question
regarding new VGACON_SOFT_SCROLLBACK_PERSISTENT config option.
Since the code size impact to support the persistent scrollback
feature is minimal wouldn't it be better to always include it?
The feature would be disabled by
On Tue, 2017-01-10 at 14:17 +0100, Andreas Gerstmayr wrote:
> This patch sets the io_pages bdi hint based on the rsize mount option.
> Without this patch large buffered reads (request size > max readahead)
> are processed sequentially in chunks of the readahead size (i.e. read
> requests are sent
On 01/10/2017 09:05 AM, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> On Tuesday, January 10, 2017 07:36:35 AM Shuah Khan wrote:
>> On 01/10/2017 07:16 AM, Shuah Khan wrote:
>>> On 01/10/2017 05:05 AM, Bartlomiej Zolnierkiewicz wrote:
Hi,
On Monday, January 09, 2017 07:21:31
From: Kalle Valo
Date: Tue, 10 Jan 2017 08:18:40 +0200
> here's the pull request with the important rtlwifi fix, more info in the
> tag below.
>
> During the long weekend we had here I finally updated Ubuntu on my
> workstation and git was updated along that. If you see
From: Christian Bewermeyer
Note that this patch does not fix all checkpatch warnings for
gpio.c
Signed-off-by: Christian Bewermeyer
Signed-off-by: Roman Sommer
---
drivers/staging/greybus/gpio.c | 24
Add code to support support for "anatop-enable-bit" device-tree
property. This property translates to LINREG_ENABLE bit in real hardware
and is present on 1p1, 2p5 and 3p0 regulators on i.MX6 and 1p0d regulator
on i.MX7.
Cc: yurov...@gmail.com
Cc: Liam Girdwood
Cc: Mark
ENABLE_LINREG bit is implemented by 3P0, 1P1 and 2P5 regulators on
i.MX6. This property is present in similar code in Fresscale BSP and
made its way upstream in imx6ul.dtsi, so this patch adds this property
to the rest of i.MX6 family for completness.
Cc: yurov...@gmail.com
Cc: Shawn Guo
On 10.01.2017 19:06, Vivek Goyal wrote:
On Tue, Jan 10, 2017 at 02:26:48PM +0300, Konstantin Khlebnikov wrote:
If overlay was mounted by root then quota set for upper layer does not work
because overlay now always use mounter's credentials for operations.
Hi Konstantin,
So CAP_SYS_RESOURCE
> > I copied checkpatch elsewhere and ran it.
>
> Why do you want to copy checkpatch "someplace else"?
> Instead of copy, I think you should soft link it.
Well, no, I have to distribute it with that.
> > Regardless, the current code is utterly stupid - it prints a
> > warning that it won't flag
On Tue, Jan 10, 2017 at 05:54:57PM +0200, Ville Syrjälä wrote:
> On Tue, Jan 10, 2017 at 02:43:05PM +0100, Tomeu Vizoso wrote:
> > Use drm_accurate_vblank_count so we have the full 32 bit to represent
> > the frame counter and userspace has a simpler way of knowing when the
> > counter wraps
On 10/01/2017 at 17:18:21 +0100, Alexandre Belloni wrote :
> I though a bit more about it, and I don't really like the new compatible
> string. I don't feel this should be necessary.
>
> What about the following:
>
> diff --git a/arch/arm/mach-at91/pm.c b/arch/arm/mach-at91/pm.c
> index
In PMU_REG_1P0Dn ENABLE_LINREG is bit 0. Bit 31 is called OVERRIDE and
it serves the funtion of granting permission to GPC IP block to alter
various other bit-fields of the register. The reason why this property,
that trickeld here from Freescale BSP, is set up like that is because in
the code it
On Tue, 2017-01-10 at 16:04 +0100, Johannes Berg wrote:
> On Tue, 2017-01-10 at 07:01 -0800, Joe Perches wrote:
> > On Tue, 2017-01-10 at 15:03 +0100, Johannes Berg wrote:
> > > From: Johannes Berg
> > >
> > > The script says that it won't warn:
> > > "No structs that
On Tue, Jan 10, 2017 at 11:06:47AM -0500, Vivek Goyal wrote:
> On Tue, Jan 10, 2017 at 02:26:48PM +0300, Konstantin Khlebnikov wrote:
> > If overlay was mounted by root then quota set for upper layer does not work
> > because overlay now always use mounter's credentials for operations.
> >
>
>
>>> +static int process_msg(void)
>>> +{
>>> + static struct xs_thread_state_read state;
>>> + struct xb_req_data *req;
>>> + int err;
>>> + unsigned int len;
>>> +
>>> + if (!state.in_msg) {
>>> + state.in_msg = true;
>>> + state.in_hdr = true;
>>> +
On 10.01.2017 18:57, Miklos Szeredi wrote:
On Tue, Jan 10, 2017 at 3:46 PM, Vivek Goyal wrote:
On Tue, Jan 10, 2017 at 02:26:48PM +0300, Konstantin Khlebnikov wrote:
If overlay was mounted by root then quota set for upper layer does not work
because overlay now always use
>> /*
>> * xs_response_mutex is locked as long as we are processing one
>> * message. state.in_msg will be true as long as we are holding the
>> * lock in process_msg().
>
> Then in_msg is the same as mutex_is_locked(_response_mutex). And if
> so, do we really need it?
Nevermind this. The
Hi,
On Tue, Jan 10, 2017 at 02:24:59AM -0800, David Carrillo-Cisneros wrote:
> During sched in, only events that match the current CPU and cgroup can
> be scheduled in. These events should be added to the PMU in increasing
> timestamp order to guaratee fairness in the event rotation.
>
> In task
1 - 100 of 2532 matches
Mail list logo