Hi,
[auto build test ERROR on wsa/i2c/for-next]
[also build test ERROR on v4.7-rc2 next-20160609]
[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-ci/linux/commits/Austin-Christ/i2c-qup-add-ACPI-support/20160609
There are different versions of Boris' name and email in the log, and
one typo. Add his emails in mailmap to have all of his contributions
under the same name/email tuple.
Signed-off-by: Antoine Tenart
Cc: Boris Brezillon
I used "Antoine Ténart" at first but then moved to a name without accent
as this cause some issues from time to time... Add my email in the
mailmap file to have a consistent shortlog output.
Signed-off-by: Antoine Tenart
---
.mailmap | 1 +
1 file changed, 1
* Mike Galbraith | 2016-06-07 06:19:19 [+0200]:
>v4.7 added down_write_killable/killable_nested(), add them to -rt.
looks good, I will postpone this until v4.8-RT
>Signed-off-by: Mike Galbraith
Sebastian
On 09.06.2016 13:12, Lee Jones wrote:
> On Thu, 09 Jun 2016, Wadim Egorov wrote:
>> On 08.06.2016 16:17, Lee Jones wrote:
>>> On Thu, 02 Jun 2016, Wadim Egorov wrote:
>>>
The RK818 chip is a power management IC for multimedia and handheld
>>> "Power Management IC (PMIC)"
>>>
devices.
> From: Wei-Ning Huang [mailto:wnhu...@chromium.org]
> Sent: Friday, May 27, 2016 5:58 PM
> To: Linux-Wireless
> Cc: LKML; Amitkumar Karwar; djku...@chromium.org; Wei-Ning Huang
> Subject: [PATCH v2] mwifiex: fix race condition when downloading
> firmware
>
> The action 'check for winner' and
On May 29 2016 or thereabouts, Corey Minyard wrote:
> From: Corey Minyard
>
> The priv->cmd is called subcmd elsewhere, and that's a more
> appropriate name for it, so rename it.
>
> The "size" parameter passed in to i801_access is passed to other
> functions and those name
On May 29 2016 or thereabouts, Corey Minyard wrote:
> From: Corey Minyard
>
> If a bad number of bytes is read on a transaction, have it
> report an error and return -EPROTO for the transaction.
>
> Signed-off-by: Corey Minyard
> ---
>
Am Donnerstag, 9. Juni 2016, 09:47:53 schrieb Wolfram Sang:
> > this series looks pretty nice now and it seems most everybody is happy
> > with it by now. Do you still have it in your inbox to look at, or should
> > David resend it again?
>
> I use patchwork (as stated in MAINTAINERS), so nothing
On May 29 2016 or thereabouts, Corey Minyard wrote:
> From: Corey Minyard
>
> Don't leave a pointer to some external buffer lying around.
>
> Signed-off-by: Corey Minyard
> ---
Looks good to me.
Reviewed-by: Benjamin Tissoires
Em Wed, Jun 08, 2016 at 06:30:10PM +0900, Masami Hiramatsu escreveu:
> @@ -2555,6 +2556,14 @@ static int __add_probe_trace_events(struct
> perf_probe_event *pev,
> }
> if (ret == -EINVAL && pev->uprobes)
> warn_uprobe_event_compat(tev);
> + if (ret == 0 &&
On Thu, Jun 09, 2016 at 10:43:14AM +0200, Peter Zijlstra wrote:
> On Wed, Jun 08, 2016 at 02:36:46PM -0700, Andi Kleen wrote:
>
> > This patch switches the NMI watchdog to use reference cycles
>
> Are you sure; it seems to only add an #include
Right, sorry a git rebase went wrong. Let me resend
On Thu, Jun 09, 2016 at 02:47:54PM +0200, Paolo Bonzini wrote:
> On 09/06/2016 14:43, Roman Kagan wrote:
> > On Thu, Jun 09, 2016 at 01:23:23PM +0200, Paolo Bonzini wrote:
> >> The version field in struct pvclock_vcpu_time_info basically implements
> >> a seqcount. Wrap it with the usual
Following commit caused failures.
dfaaf3fa0: (Use __jhash_mix() for iterate_chain_key())
Fixed by adding jhash.h with minimal stuff required
75dd602a5: (lockdep: Fix lock_chain::base size)
Fixed by adding ARRAY_SIZE macro definition and
changing the MAX_LOCK_DEPTH value to similar defined
in
The patch tries to fix the compilation errors in liblockdep which were
introduced due to recent changes in kernel. I am not familiar with the internal
working of lockdep, so please suggest if I have done anything wrong while
fixing liblockdep errors.
Vishal Thanki (2):
liblockdep: Fix compile
Em Wed, Jun 08, 2016 at 09:36:52PM +0900, Taeung Song escreveu:
> perf_config_set__delete() delete allocated the config set
> but the global variable 'config_set' is used all around.
> So purge and zfree by an address of the global variable
> , i.e. 'struct perf_config_set **' type
> instead of
Maxim PMIC MAX77620 is Power management IC which have multiple
sub blocks like regulators (DCDC/LDOs), GPIO, RTC, Clock, Watchdog
timer etc.
Add the driver for watchdog timer under watchdog framework.
The driver implements the watchdog callbacks to start, stop,
ping and set timeout for watchodg
The FDP1 is a de-interlacing module which converts interlaced video to
progressive video. It is also capable of performing pixel format conversion
between YCbCr/YUV formats and RGB formats.
Signed-off-by: Kieran Bingham
---
.../devicetree/bindings/media/renesas,fdp1.txt
There are situations when we need to modify the delay of a delayed kthread
work. For example, when the work depends on an event and the initial delay
means a timeout. Then we want to queue the work immediately when the event
happens.
This patch implements kthread_mod_delayed_work() as inspired
kthread_create_on_cpu() was added by the commit 2a1d446019f9a5983e
("kthread: Implement park/unpark facility"). It is currently used
only when enabling new CPU. For this purpose, the newly created
kthread has to be parked.
The CPU binding is a bit tricky. The kthread is parked when the CPU
has
This patch allows to make kthread worker freezable via a new @flags
parameter. It will allow to avoid an init work in some kthreads.
It currently does not affect the function of kthread_worker_fn()
but it might help to do some optimization or fixes eventually.
I currently do not know about any
I send the kthread worker API improvements separately as discussed
in v6, see
https://lkml.kernel.org/g/20160511105224.ge2...@pathway.suse.cz
They seem to be ready for inclusion in 4.8.
I will send the conversion of the particular kthreads once
the API changes are in some maintainers three (-mm?)
On Wed, 08 Jun 2016, Ben Dooks wrote:
> Fix the warnings about the following functions not being
> declared by including omap-usb.h which declares them:
>
> drivers/mfd/omap-usb-tll.c:333:5: warning: symbol 'omap_tll_init' was not
> declared. Should it be static?
>
> From: Julian Calaby [mailto:julian.cal...@gmail.com]
> Sent: Thursday, June 02, 2016 4:44 AM
> To: Javier Martinez Canillas; Xinming Hu
> Cc: linux-kernel@vger.kernel.org; Amitkumar Karwar; Kalle Valo; netdev;
> linux-wireless; Nishant Sarmukadam
> Subject: Re: [PATCH 7/8] mwifiex: don't print
On Tue, Jun 07, 2016 at 02:55:51PM +0800, Tan Jui Nee wrote:
> This is to cater the need for non-ACPI system whereby
> a platform device has to be created in order to bind
> with the Apollo Lake Pinctrl GPIO platform driver.
>
> Signed-off-by: Tan Jui Nee
Acked-by: Mika
On Thu, 9 Jun 2016, Sergei Shtylyov wrote:
> Hello.
>
> On 6/9/2016 10:31 AM, Roger Quadros wrote:
>
> > The OTG core will use struct otg_hcd_ops to interface
> > with the HCD controller.
>
> Host controller driver (HCD) controller? Maybe just HC? :-)
> >>>
> >>> OK.
> >>
>
On Mon, Jun 06, 2016 at 10:43:01PM -0400, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> config PINCTRL_BAYTRAIL
> bool "Intel Baytrail GPIO pin control"
>
> ...meaning that it currently is not being built as a module by anyone.
>
> Lets
On Thu, 2016-06-09 at 12:17 +0100, Ben Dooks wrote:
> The functions inet_diag_msg_common_fill and inet_diag_msg_attrs_fill
> seem to have been missed from the include/linux/inet_diag.h header
> file. Add them to fix the following warnings:
>
> net/ipv4/inet_diag.c:69:6: warning: symbol
Update error couters when DMA is used for receiving data. Do
this by using DMA transaction error event instead error interrupts
to reduce interrupt load.
Signed-off-by: Nandor Han
---
drivers/tty/serial/imx.c | 32
1 file changed, 32
The calculation of the DMA transaction residue supports only fixed
size data transfers. This implementation is not covering all
operations (e.g. data receiving) when we need to know the exact amount
of bytes transferred.
The loop channels handling was changed to clear the buffer
descriptor errors
When devices are instatiated through devicetree the i2c_client->name is
set to the compatible string with company name stripped out. This is
then matched to the i2c_device_id table to pass the device_id to the
probe function. This id parameter is used by some device drivers to
differentiate
This can be used by device drivers as the equivalent of of_match_device
when they are instantiated through ACPI using devicetree IDs. This is
described in Documentation/acpi/enumeration.txt
Signed-off-by: Crestez Dan Leonard
---
drivers/acpi/bus.c | 13 +++--
Linux supports instantiating devices using devicetree ids from ACPI by setting
the id to PRP0001 and adding the devicetree compatible string in _DSD
properties. This is described in Documentation/acpi/enumeration.txt.
I've tried to use this feature using custom ACPI tables and one issue I
On Tue, Apr 19, 2016 at 01:30:11PM +0100, Sudeep Holla wrote:
> Inorder to accomodate bot DT and ACPI LPI support in psci_cpu_init_idle,
> move the device tree specific into psci_dt_cpu_init_idle.
>
> Cc: Mark Rutland
> Cc: Lorenzo Pieralisi
>
This driver supports the VGA/LCD core available from OpenCores:
http://opencores.org/project,vga_lcd
It's intended as a replacement for the "ocfb" framebuffer driver
Signed-off-by: Andrea Merello
Cc: Stefan Kristiansson
Cc: Tomi
On Tue, Jun 7, 2016 at 8:03 PM, Kuthonuzo Luruo wrote:
> Currently, KASAN may fail to detect concurrent deallocations of the same
> object due to a race in kasan_slab_free(). This patch makes double-free
> detection more reliable by serializing access to KASAN object
This patch series add a DRM driver for the OpenCores VGA/LCD display
controller. Another driver exists for this devices, but it is a old
framebuffer driver ("ocfb").
If there is any interest in doing so, this driver could possibly
the "ocfb" driver.
With respect to the old framebuffer driver,
On Thu, Jun 09, 2016 at 10:01:07AM +0900, Minchan Kim wrote:
> A system has big HDD storage and SSD swap.
>
> HDD:200 IOPS
> SSD: 10 IOPS
> From https://en.wikipedia.org/wiki/IOPS
>
> So, speed gap is 500x.
> x + 500x = 200
> If we use PCIe-SSD, the gap will be larger.
> That's why I
On Tue, 07 Jun 2016, Lothar Waßmann wrote:
> 'brightness' is usually an index into a table of duty_cycle values,
> where the value at index 0 may well be non-zero
> (tegra30-apalis-eval.dts and tegra30-colibri-eval-v3.dts are real-life
> examples).
> Thus brightness == 0 does not necessarily mean
On Thu 09-06-16 22:18:28, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > @@ -766,15 +797,12 @@ void oom_kill_process(struct oom_control *oc, struct
> > task_struct *p,
> > * If the task is already exiting, don't alarm the sysadmin or kill
> > * its children or threads, just set
On Thu 2016-04-28 13:53:53, Josh Poimboeuf wrote:
> On Tue, Apr 05, 2016 at 08:44:30AM -0500, Josh Poimboeuf wrote:
> > On Fri, Apr 01, 2016 at 03:39:44PM +0200, Petr Mladek wrote:
> > > > There's also a func->immediate flag which allows users to specify that
> > > > certain functions in the patch
Em Wed, Jun 08, 2016 at 06:30:40PM +0900, Masami Hiramatsu escreveu:
> From: Masami Hiramatsu
>
> perf-probe --del removes caches when --cache is given.
> Note that the delete pattern is not same as normal events.
>
> If you cached probes with event name, --del
This is a note to let you know that I have just added a patch titled
MIPS: Fix siginfo.h to use strict posix types
to the linux-4.2.y-queue branch of the 4.2.y-ckt extended stable tree
which can be found at:
This is a note to let you know that I have just added a patch titled
MIPS64: R6: R2 emulation bugfix
to the linux-4.2.y-queue branch of the 4.2.y-ckt extended stable tree
which can be found at:
This is a note to let you know that I have just added a patch titled
MIPS: Handle highmem pages in __update_cache
to the linux-4.2.y-queue branch of the 4.2.y-ckt extended stable tree
which can be found at:
This is a note to let you know that I have just added a patch titled
MIPS: Force CPUs to lose FP context during mode switches
to the linux-4.2.y-queue branch of the 4.2.y-ckt extended stable tree
which can be found at:
This is a note to let you know that I have just added a patch titled
MIPS: Sync icache & dcache in set_pte_at
to the linux-4.2.y-queue branch of the 4.2.y-ckt extended stable tree
which can be found at:
This is a note to let you know that I have just added a patch titled
MIPS: Disable preemption during prctl(PR_SET_FP_MODE, ...)
to the linux-4.2.y-queue branch of the 4.2.y-ckt extended stable tree
which can be found at:
On Thursday, June 9, 2016 7:42:24 AM CEST Krzysztof Hałasa wrote:
> Arnd Bergmann writes:
>
> > What exactly is the problem we are seeing, and is there a way to fix
> > it on top of my patch? Are we perhaps just missing a call to
> > pcie_bus_configure_settings()?
>
> From:
kbuild test robot wrote:
> net/rxrpc/rxkad.c:1165:1-3: WARNING: PTR_ERR_OR_ZERO can be used
>
>
> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
>
> Generated by: scripts/coccinelle/api/ptr_ret.cocci
>
> CC: David Howells
>
Peter Zijlstra wrote:
> Blergh; so looking at more asm there's still a few tricks we cannot do.
> So while overall size is down, some paths do end up more expensive. (It
> typically boils down to creative use of condition flags, which is very
> hard in C)
It can be done
This is a note to let you know that I have just added a patch titled
MIPS: math-emu: Fix BC1{EQ,NE}Z emulation
to the linux-4.2.y-queue branch of the 4.2.y-ckt extended stable tree
which can be found at:
This is a note to let you know that I have just added a patch titled
MIPS: Fix BC1{EQ,NE}Z return offset calculation
to the linux-4.2.y-queue branch of the 4.2.y-ckt extended stable tree
which can be found at:
This is a note to let you know that I have just added a patch titled
MIPS: lib: Mark intrinsics notrace
to the linux-4.2.y-queue branch of the 4.2.y-ckt extended stable tree
which can be found at:
This is a note to let you know that I have just added a patch titled
SIGNAL: Move generic copy_siginfo() to signal.h
to the linux-4.2.y-queue branch of the 4.2.y-ckt extended stable tree
which can be found at:
This is a note to let you know that I have just added a patch titled
MIPS: math-emu: Fix jalr emulation when rd == $0
to the linux-4.2.y-queue branch of the 4.2.y-ckt extended stable tree
which can be found at:
On Thu, 09 Jun 2016 15:26:47 +0100
David Howells wrote:
> Martin Schwidefsky wrote:
>
> > I hesitate to put another CONFIG_S390 into common code, alternatively
> > __HAVE_ARCH_MEMCMP could be used. There are 7 architectures with the
> > define: arc,
On Wed, 08 Jun 2016, Arnd Bergmann wrote:
> On Wednesday, June 8, 2016 1:37:12 PM CEST Linus Walleij wrote:
> > On Tue, May 10, 2016 at 4:02 PM, Arnd Bergmann wrote:
> >
> > > Except for the constant DB8500_PRCMU_FW_VERSION_OFFSET number, nothing
> > > is ever passed through the
Hi,
and here comes the v8 of Host Notify.
To minimize the merge conflicts, I first applied the following 2 patches:
http://patchwork.ozlabs.org/patch/632768/
http://patchwork.ozlabs.org/patch/626051/
The series Corey sent (http://patchwork.ozlabs.org/patch/627567/ and the 9
after) does not
.alert() is meant to be generic, but there is currently no way
for the device driver to know which protocol generated the alert.
Add a parameter in .alert() to help the device driver to understand
what is given in data.
This patch is required to have the support of SMBus Host Notify protocol
Code obtained from
https://raw.githubusercontent.com/mightybigcar/synaptics-rmi4/jf/drivers/input/rmi4/rmi_smbus.c
and updated to match upstream. And fixed to make it work.
Signed-off-by: Benjamin Tissoires
Signed-off-by: Andrew Duggan
---
SMBus Host Notify allows a slave device to act as a master on a bus to
notify the host of an interrupt. On Intel chipsets, the functionality
is directly implemented in the firmware. We just need to export a
function to call .alert() on the proper device driver.
i2c_handle_smbus_host_notify()
Michal Hocko wrote:
> The only case where the oom_reaper is not triggered for the oom victim
> is when it shares the memory with a kernel thread (aka use_mm) or with
> the global init. After "mm, oom: skip vforked tasks from being selected"
> the victim cannot be a vforked task of the global init
On Thu, Jun 09, 2016 at 10:46:49AM -0400, Damien Riegel wrote:
> Enable FPGA's IRQ controller. It is in charge of dispatching interrupts
> generated by IPs in the FPGA. The SoC is notified that an interrupt
> occurred through a GPIO.
>
> Signed-off-by: Damien Riegel
On Thu, Jun 09, 2016 at 10:42:08AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Jun 09, 2016 at 06:14:39AM -0700, Andi Kleen escreveu:
> > From: Andi Kleen
> >
> > Now that the NMI watchdog runs with reference cycles, and does not
>
> Now as in when? We should at least
Bhuvanchandra DV (5):
tty: serial: fsl_lpuart: Fix broken 8m/s1 support
tty: serial: fsl-lpuart: Use cyclic DMA for Rx
tty: serial: fsl-lpuart: Use scatter/gather DMA for Tx Drop PIO to DMA
switching and use scatter/gather DMA for Tx path to improve
performance.
tty: serial:
On 06/09/2016 09:23 AM, Lee Jones wrote:
> On Wed, 08 Jun 2016, Andrew F. Davis wrote:
>
>> On 06/08/2016 08:06 AM, Lee Jones wrote:
>>> On Tue, 31 May 2016, Andrew F. Davis wrote:
>>>
The TI SM-USB-DIG is a USB to SPI/I2C/1Wire/GPIO adapter.
Add MFD core support.
When DMA mode is enabled one need to make sure the DMA channels are
idle before entering suspend mode especially when UART ports which
are set as wakeup source and console port with no_console_suspend
is set. This patch takes care of gracefully releasing DMA channels
for the above two cases and
From: Stefan Agner
In order to allow wake support in STOP sleep mode, clocks are
needed. Use imx_clk_gate2_cgr to disable automatic clock gating
in low power mode STOP. This allows to enable wake by UART using:
echo enabled > /sys/class/tty/ttyLP0/power/wakeup
However, if wake
Regmap irq implements the generic interrupt service routine which
is common for most of devices. Some devices, like MAX77620, MAX20024
needs the special handling before and after servicing the interrupt
as generic. For the example, MAX77620 programming guidelines for
interrupt servicing says:
1.
WARNING: please, no spaces at the start of a line
+ { "tps6507x", 0 },$
WARNING: please, no spaces at the start of a line
+ { }$
Signed-off-by: Ben Copeland
---
drivers/mfd/tps6507x.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
The programming guidelines of the MAX77620 for servicing interrupt is:
1. When interrupt occurs from PMIC, mask the PMIC interrupt by
setting GLBLM.
2. Read IRQTOP and service the interrupt.
3. Once all interrupts has been checked and serviced, the interrupt
service routine un-masks the
From: Lokesh Vutla
The pinctrl IP used in some of the Keystone 2 devices differ vs other
TI SoCs. Therefore, create a Keystone specific pinctrl header.
Signed-off-by: Lokesh Vutla
Signed-off-by: Franklin S Cooper Jr
Signed-off-by: Tero
On Wed, 08 Jun 2016, Linus Walleij wrote:
> On Tue, Jun 7, 2016 at 7:38 PM, Peter Griffin
> wrote:
>
> > If kzalloc() fails it will issue it's own error message including
> > a dump_stack(). So remove the site specific error messages.
> >
> > Signed-off-by: Peter
Unlike most Keystone 2 devices, K2G supports pinmuxing of its pins. This
patch series enables pinmuxing for Keystone 2 devices.
Version 2 changes:
Rebased on top of linux-next which includes Keerthy patches.
Lokesh Vutla (2):
ARM: dts: keystone: Header file for pinctrl constants
ARM: dts:
From: Vitaly Andrianov
Add pinctrl support.
Signed-off-by: Vitaly Andrianov
Signed-off-by: Franklin S Cooper Jr
Signed-off-by: Lokesh Vutla
Signed-off-by: Dave Gerlach
---
On 06/09/2016 04:00 AM, Kevin Tsai wrote:
> Added Vishay Capella CM36672 Proximity Sensor IIO driver. Support both
> ACPI and Device Tree.
>
> Signed-off-by: Kevin Tsai
> ---
> V2:
> Thanks commends from Peter Meerwald-Stadler, Jonathan Cameron, and Linux
> Walleij.
>From https://bugs.freedesktop.org/show_bug.cgi?id=96461 :
This was kind of a difficult bug to track down. If you're using a
Haswell system running GNOME and you have fbc completely enabled and
working, playing videos can result in video artifacts. Steps to
reproduce:
- Run GNOME
- Ensure FBC is
For KASAN builds:
- switch SLUB allocator to using stackdepot instead of storing the
allocation/deallocation stacks in the objects;
- define SLAB_RED_ZONE, SLAB_POISON, SLAB_STORE_USER to zero,
effectively disabling these debug features, as they're redundant in
the presence of KASAN;
-
On Wed, 2016-06-01 at 14:55 +0200, Martin Kepplinger wrote:
> It's *really* fun to use as an input tablet though! So let's support this
> for everybody.
Nice job, but a few issues are left. I'll comment in the code.
> +static void pegasus_close(struct input_dev *dev)
> +{
> + struct
On Thu, 9 Jun 2016 15:51:56 +0200
Petr Mladek wrote:
> A good practice is to prefix the names of functions and macros
> by the name of the subsystem.
>
> The kthread worker API is a mix of classic kthreads and workqueues.
> Each worker has a dedicated kthread. It runs a
From: Gustavo Padovan
Signalling doesn't need to be enabled at sync_file creation, it is only
required if userspace waiting the fence to signal through poll().
Thus we delay fence_add_callback() until poll is called. It only adds the
callback the first time
From: Gustavo Padovan
Creates a function that given an sync file descriptor returns a
fence_collection containing all fences in the sync_file.
If there is only one fence in the sync_file this fence itself is returned,
however if there is more than one, a
From: Gustavo Padovan
Document the new function added to sync_file.c
v2: Adapt to fence_array
Signed-off-by: Gustavo Padovan
---
Documentation/sync_file.txt | 19 +++
1 file changed, 19 insertions(+)
diff
On 06/06/16 18:56, Marc Zyngier wrote:
> The ARM architected timer specification mandates that the interrupt
> associated with each timer is level triggered (which corresponds to
> the "counter >= comparator" condition).
>
> A number of DTs are being remarkably creative, declaring the interrupt
>
From: Stefan Agner
Commit 8e4934c6d6c6 ("tty: serial: fsl_lpuart: clear receive flag
on FIFO flush") implemented clearing of the receive flag by reading
the status register only. It turned out that even though we flush
the FIFO afterwards, a explicit read of the data
By default the driver always configure the mode as 8s1 even when 8m1
mode is selected. Fix this by adding support to control the space/mark bit.
Signed-off-by: Bhuvanchandra DV
---
drivers/tty/serial/fsl_lpuart.c | 9 +++--
1 file changed, 7 insertions(+), 2
The initial approach of DMA implementatin for RX is inefficient due to switching
from PIO to DMA, this leads to overruns especially on instances with the smaller
FIFO. To address these issues this patch uses a cyclic DMA for receiver path.
Some part of the code is borrowed from atmel serial
On 6/9/2016 6:05 AM, Krzysztof Kozlowski wrote:
> On 06/08/2016 05:26 PM, Rhyland Klein wrote:
>> On 6/8/2016 2:35 AM, Krzysztof Kozlowski wrote:
>>> On 06/07/2016 10:26 PM, Rhyland Klein wrote:
Change power_supply_read_temp() to use power_supply_get_property()
so that it will check the
This patch updates the dmatest client to
Support scatter-gather dma mode.
Signed-off-by: Kedareswara rao Appana
---
Changes for v2:
- Rename sg_resources to sg_buffers as suggested Vinod.
- Fixed coding style issues like spacing issues as suggested by Vinod.
On Wed, Jun 8, 2016 at 12:51 PM, Borislav Petkov wrote:
> On Wed, Jun 08, 2016 at 12:44:12PM -0400, Alex Deucher wrote:
>> If the ring and IB tests pass on resume, you should be good to go.
>
> Yap, they do. I pasted that output earlier but here it is again:
>
> [ 64.745988]
On Thu, Jun 9, 2016 at 3:14 AM, Zhou Jie wrote:
> TO Alex
> TO Michael
>
>In your solution you add a emulate PCI bridge to act as
>a bridge between direct assigned devices and the host bridge.
>Do you mean put all direct assigned devices to
>one emulate
On 06/09/2016 07:34 AM, Konrad Rzeszutek Wilk wrote:
Hey Jens,
Please git pull in your 'for-4.7/drivers' the following
branch (based of your 'for-4.7/drivers):
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
stable/for-jens-4.7
which has two fixes for a guest migrating from
On Thu, Jun 09, 2016 at 03:14:41PM +1000, Stephen Rothwell wrote:
> Hi Paul,
>
> Today's linux-next merge of the rcu tree got a conflict in:
>
> kernel/rcu/tree.c
>
> between commit:
>
> 6428671bae97 ("locking/mutex: Optimize mutex_trylock() fast-path")
>
> from the tip tree and commit:
>
On Thu, Jun 09, 2016 at 02:50:26PM +0200, Rafael J. Wysocki wrote:
> On Thu, Jun 9, 2016 at 12:29 PM, Mark Brown wrote:
> > The external interface shouldn't be DT specific, the Intel people are
> > busy importing all of DT into ACPI
> Well, not really.
> If you are
On 06/09/2016 10:12 AM, Sam Bobroff wrote:
> On Thu, Jun 02, 2016 at 07:38:58AM -0500, Shreyas B. Prabhu wrote:
>
> ...
>
>> +/* Power Management - PSSCR Fields */
>
> It might be nice to give the full name of the register, as below with the
> FPSCR.
>
I'll make the change while posting
On 09/05/2016 11:53, Borislav Petkov wrote:
> From: Borislav Petkov
>
> Use already cached CPUID information instead of querying CPUID again.
>
> No functionality change.
>
> Signed-off-by: Borislav Petkov
> Cc: Joerg Roedel
> Cc:
From: Chen Gang
Merge several statements to one return statement, since the new return
statement is still simple enough.
Try to let the second line function parameters almost align with the
first line parameter (try to be within 80 columns, and in one line).
The
From: Stefan Agner
Currently the tx_empty callback only considers the Transmit Complete
Flag (TC). The reference manual is not quite clear if the TC flag
covers the TX FIFO too. Debug prints on real hardware have shown that
from time to time the TC flag is asserted (indicating
Enable Vybrid's build-in support for RS-485 auto RTS for controlling
line direction of RS-485 transceiver driver.
Enable RS485 feature by either using ioctrl 'TIOCSRS485' or enable it in
the device tree by setting 'linux,rs485-enabled-at-boot-time' property.
Signed-off-by: Bhuvanchandra DV
201 - 300 of 1970 matches
Mail list logo