Hi Keerthy
Some minor comment
> +static int lp873x_gpio_direction_output(struct gpio_chip *chip,
> + unsigned int offset, int value)
> +{
> + struct lp873x_gpio *gpio = gpiochip_get_data(chip);
> +
> + /* Set the initial value */
> + regmap_
Hi Keerthy,
sorry ignore my last two comments in previous mail.
On Wed, Jun 29, 2016 at 4:13 PM, Manish Badarkhe
wrote:
> Hi Keerthy
>
> Some minor comment
>
>> +static int lp873x_gpio_direction_output(struct gpio_chip *chip,
>> + unsigned int offset, int va
On 28.06.2016 18:12, Duc Dang wrote:
On Tue, Jun 28, 2016 at 6:04 AM, Christopher Covington
wrote:
Hi Tomasz,
On 06/28/2016 03:54 AM, Tomasz Nowicki wrote:
diff --git a/drivers/pci/host/mcfg-quirks.c b/drivers/pci/host/mcfg-quirks.c
new file mode 100644
index 000..fb2b184
--- /dev/null
+
On Wed, Jun 29, 2016 at 4:00 PM, Heikki Krogerus
wrote:
> On Wed, Jun 29, 2016 at 02:21:10PM +0530, Rajaram R wrote:
>> On Mon, Jun 27, 2016 at 5:43 PM, Heikki Krogerus
>> wrote:
>> > Hi,
>> >
>> > On Mon, Jun 27, 2016 at 03:51:08PM +0530, Rajaram R wrote:
>> >> May be I am missing user or usage
This patch fixes the wrong description about extcon_set/get_cable_state_()
because they use the unique id of external connector instead of legacy name.
Signed-off-by: Chanwoo Choi
---
include/linux/extcon.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/extcon.
Currently ftrace_graph_ent{,_entry} and ftrace_graph_ret{,_entry} struct
can have padding bytes at the end due to alignment in 64-bit data type.
As these data are recorded so frequently, those paddings waste
non-negligible space. As the ring buffer maintains alignment properly
for each architectur
Am 28.06.2016 um 21:05 schrieb Jani Nikula :
> On Tue, 28 Jun 2016, Markus Heiser wrote:
>> Hi Jonathan, hi Mauro,
>>
>> here is my DocBook to reST movement on top of Jon's docs-next branch. It
>> includes:
>>
>> * kernel-doc parser & directive
>> * flat-table directive
>> * man page builder
Hi
> -Original Message-
> From: Peter Chen [mailto:hzpeterc...@gmail.com]
> Sent: Wednesday, June 29, 2016 5:44 PM
> To: Stephen Boyd
> Cc: Peter Chen ; Felipe Balbi ;
> linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org; linux-
> u...@vger.kernel.org; Jun Li ; Greg Kroah-
Introduce new flags that defines which ABI to use on creating sigframe.
Those flags kernel will set according to sigaction syscall ABI,
which set handler for the signal being delivered.
So that will drop the dependency on TIF_IA32/TIF_X32 flags on signal deliver.
Those flags will be used only unde
The following changes are available since v1:
- killed PR_REG_SIZE macro as Oleg suggested
- cleared SA_IA32_ABI|SA_X32_ABI from oact->sa.sa_flags in do_sigaction()
as noticed by Oleg
- moved SA_IA32_ABI|SA_X32_ABI from uapi header as those flags shouldn't
be exposed to user-space
I also rewor
If remapping of vDSO blob failed on vvar mapping,
we need to unmap previously mapped vDSO blob.
Cc: Andy Lutomirski
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: "H. Peter Anvin"
Cc: Cyrill Gorcunov
Cc: Pavel Emelyanov
Cc: x...@kernel.org
Signed-off-by: Dmitry Safonov
---
arch/x86/entry/vdso/vma
Add API to change vdso blob type with arch_prctl.
As this is usefull only by needs of CRIU, expose
this interface under CONFIG_CHECKPOINT_RESTORE.
Cc: Andy Lutomirski
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: "H. Peter Anvin"
Cc: Cyrill Gorcunov
Cc: Pavel Emelyanov
Cc: x...@kernel.org
Signed-o
Make in-kernel API to map vDSO blobs on x86.
Cc: Andy Lutomirski
Cc: Ingo Molnar
Cc: Thomas Gleixner
Cc: "H. Peter Anvin"
Cc: Cyrill Gorcunov
Cc: Pavel Emelyanov
Cc: x...@kernel.org
Signed-off-by: Dmitry Safonov
---
arch/x86/entry/vdso/vma.c | 70 +
As the task isn't executing at the moment of {GET,SET}REGS,
return regset that corresponds to code selector, rather than
value of TIF_IA32 flag.
I.e. if we ptrace i386 elf binary that has just changed it's
code selector to __USER_CS, than GET_REGS will return
full x86_64 register set.
Note, that t
Killed PR_REG_SIZE and PR_REG_PTR macro as we can get regset size
from regset view.
Suggested-by: Oleg Nesterov
Cc: Oleg Nesterov
Cc: Andy Lutomirski
Cc: Ingo Molnar
Cc: Cyrill Gorcunov
Cc: Pavel Emelyanov
Cc: x...@kernel.org
Cc: Alexander Viro
Cc: linux-fsde...@vger.kernel.org
Signed-off-b
Perf can currently only support code navigation (branches and calls) in
annotate when run on the same architecture where perf.data was recorded.
But cross arch annotate is not supported.
This patchset enables cross arch annotate. Currently I've used x86
and arm instructions which are already avail
From: Naveen N. Rao
Powerpc has long list of branch instructions and hardcoding them in
table appears to be error-prone. So, add new function to find
instruction instead of creating table. This function dynamically
create table(list of 'struct ins'), and instead of creating object
every time, fir
Change current data structures and function to enable cross arch
annotate.
Current implementation does not contain logic of record on one arch
and annotating on other. This remote annotate is partially possible
with current implementation for x86 (or may be arm as well) only.
But, to make remote a
Add Utility function to fetch arch using evsel. (evsel->env->arch)
Signed-off-by: Ravi Bangoria
---
Changes in v2:
- No changes
tools/perf/util/evsel.c | 7 +++
tools/perf/util/evsel.h | 2 ++
2 files changed, 9 insertions(+)
diff --git a/tools/perf/util/evsel.c b/tools/perf/util/evsel.c
Define macro for each arch name and use them instead of using arch
name as string.
Signed-off-by: Ravi Bangoria
---
Changes in v2:
- No changes
tools/perf/arch/common.c | 36 ++--
tools/perf/arch/common.h | 11 +++
tools/perf/util/an
On 06/27/2016 03:58 PM, Krzysztof Kozlowski wrote:
> The SoC-specific devfreq and event drivers can be build tested on all
> architectures.
>
> Signed-off-by: Krzysztof Kozlowski
>
> ---
>
> Success of compilation tested on ARM, ARM64, i386, x86_64 and powerpc
> architectures (allyesconfigs).
>
From: Wanpeng Li
INFO: rcu_sched detected stalls on CPUs/tasks:
1-...: (11800 GPs behind) idle=45d/140/0 softirq=0/0 fqs=21663
(detected by 0, t=65016 jiffies, g=11500, c=11499, q=719)
Task dump for CPU 1:
qemu-system-x86 R running task0 3529 3525 0x00080808
880202
From: Wanpeng Li
Introduce cancel_hv_tscdeadline() to encapsulate preemption
timer cancel stuff.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Yunhong Jiang
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/lapic.c | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/a
On Wed, Jun 29, 2016 at 04:21:49PM +0530, Rajaram R wrote:
> On Wed, Jun 29, 2016 at 4:00 PM, Heikki Krogerus
> wrote:
> > On Wed, Jun 29, 2016 at 02:21:10PM +0530, Rajaram R wrote:
> >> On Mon, Jun 27, 2016 at 5:43 PM, Heikki Krogerus
> >> wrote:
> >> > Hi,
> >> >
> >> > On Mon, Jun 27, 2016 at
Hyper-V Sockets (hv_sock) supplies a byte-stream based communication
mechanism between the host and the guest. It's somewhat like TCP over
VMBus, but the transportation layer (VMBus) is much simpler than IP.
With Hyper-V Sockets, applications between the host and the guest can talk
to each other d
On Wed, Jun 29, 2016 at 10:56:42AM +, Jun Li wrote:
> > > }
> > >
> > > +static void otg_stop_hnp_polling(struct otg_fsm *fsm) {
> > > + /*
> > > + * The memory of host_req_flag should be allocated by
> > > + * controller driver, otherwise, hnp polling is not started.
> > > + */
> > > + if
Hyper-V Sockets (hv_sock) supplies a byte-stream based communication
mechanism between the host and the guest. It's somewhat like TCP over
VMBus, but the transportation layer (VMBus) is much simpler than IP.
With Hyper-V Sockets, applications between the host and the guest can talk
to each other d
On Sun, Jun 26, 2016 at 12:28:34AM -0700, Stephen Boyd wrote:
> If two devices are probed with this same driver, they'll share
> the same platform data structure, while the chipidea core layer
> writes and modifies it. This can lead to interesting results
> especially if one device is an OTG type c
The driver was originally written for MIPS based SoC. These required the
IRQ mask register to be read after writing it to ensure that the content
was actually applied. As this version only works on ARM based SoCs, we can
safely remove the 2 reads as they are no longer required.
Signed-off-by: John
The code currently uses variables to store and never modify the bit masks
of interrupts. This is legacy code from an early version of the driver
that supported MIPS based SoCs where the IRQ bits depended on the actual
SoC. As the bits are the same for all ARM based SoCs using this driver we
can rem
This series contains 2 small code cleanups that are leftovers from the
MIPS support. There is also a small fix that adds proper locking to the
code accessing the IRQ registers. Without this fix we saw deadlocks caused
by the last patch of the series, which adds IRQ grouping. The grouping
feature al
The ethernet core has 3 IRQs. Using the IRQ grouping registers we are able
to separate TX and RX IRQs, which allows us to service them on separate
cores. This patch splits the IRQ handler into 2 separate functions, one for
TX and another for RX. The TX housekeeping is split out into its own NAPI
ha
The code that enables and disables IRQs is missing proper locking. After
adding the IRQ grouping patch and routing the RX and TX IRQs to different
cores we experienced IRQ stalls. Fix this by adding proper locking.
We use a dedicated lock to reduce the latency if the IRQ code.
Signed-off-by: John
On Wed, Jun 29, 2016 at 02:48:11PM +0800, Peter Chen wrote:
> On Sun, Jun 26, 2016 at 12:28:30AM -0700, Stephen Boyd wrote:
> > The chipidea core gets the usb phy and initializes the phy at the
> > right point now so we don't need to get the phy in this driver.
> >
> > Cc: Peter Chen
> > Cc: Greg
On Sun, Jun 26, 2016 at 12:28:35AM -0700, Stephen Boyd wrote:
> The MSM chipidea wrapper has two bits that are used to reset the
> first or second phy. Add support for these bits via the reset
> controller framework, so that phy drivers can reset their
> hardware at the right time during initializa
From: Michal Hocko
"mm, oom: fortify task_will_free_mem" has dropped task_lock around
task_will_free_mem in oom_kill_process bacause it assumed that a
potential race when the selected task exits will not be a problem
as the oom_reaper will call exit_oom_victim.
Tetsuo was objecting that nommu do
Sorry, I was trying to backport to 2.23, and failed. Won't happen
again.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
Hi,
Baolin Wang writes:
>>> For supporting the usb charger, it adds the usb_charger_init() and
>>> usb_charger_exit() functions for usb charger initialization and exit.
>>>
>>> It will report to the usb charger when the gadget state is changed,
>>> then the usb charger can do
Hi,
On Tue, Jun 28, 2016 at 09:56:22PM +0800, Icenowy Zheng wrote:
> The reason for a dedicate driver is:
> 1. This IP have only thermal function, so it's not suitable to use a
> driver at drivers/input/touchscreen/.
That's not a problem, and it's being worked on [1].
> 2. Control Register are q
Andrew Cooper writes:
> On 28/06/16 17:47, Vitaly Kuznetsov wrote:
>> @@ -1808,6 +1822,8 @@ static int xen_hvm_cpu_notify(struct notifier_block
>> *self, unsigned long action,
>> int cpu = (long)hcpu;
>> switch (action) {
>> case CPU_UP_PREPARE:
>> +/* vLAPIC_ID == Xen
From: Philippe Reynes
Date: Tue, 28 Jun 2016 23:59:44 +0200
> The private structure contain a pointer to phydev, but the structure
> net_device already contain such pointer. So we can remove the pointer
> phydev in the private structure, and update the driver to use the
> one contained in struct
Hi Felipe,
On 29 June 2016 at 20:06, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
For supporting the usb charger, it adds the usb_charger_init() and
usb_charger_exit() functions for usb charger initialization and exit.
It will report to the usb charger
From: Philippe Reynes
Date: Tue, 28 Jun 2016 23:59:45 +0200
> There are two generics functions phy_ethtool_{get|set}_link_ksettings,
> so we can use them instead of defining the same code in the driver.
>
> Signed-off-by: Philippe Reynes
Applied.
On 28/06/16 17:47, Vitaly Kuznetsov wrote:
> HYPERVISOR_vcpu_op passes Linux's idea of vCPU id as a parameter while
> Xen's idea is expected. In some cases these ideas diverge so we need to
> do remapping.
>
> There is an issue, however. PV guests do VCPUOP_is_up very early
> (see xen_fill_possibl
On 29/06/16 13:16, Vitaly Kuznetsov wrote:
> Andrew Cooper writes:
>
>> On 28/06/16 17:47, Vitaly Kuznetsov wrote:
>>> @@ -1808,6 +1822,8 @@ static int xen_hvm_cpu_notify(struct notifier_block
>>> *self, unsigned long action,
>>> int cpu = (long)hcpu;
>>> switch (action) {
>>> case CP
Hi,
Baolin Wang writes:
> For supporting the usb charger, it adds the usb_charger_init() and
> usb_charger_exit() functions for usb charger initialization and exit.
>
> It will report to the usb charger when the gadget state is changed,
> then the usb char
On 28/06/16 17:47, Vitaly Kuznetsov wrote:
> shared_info page has space for 32 vcpu info slots for first 32 vCPUs but
> these are the first 32 vCPUs from Xen's perspective and we should map them
> accordingly with the newly introduced xen_vcpu_id mapping.
>
> Signed-off-by: Vitaly Kuznetsov
> ---
On 29/06/16 10:16, Vitaly Kuznetsov wrote:
> David Vrabel writes:
>
>> On 28/06/16 17:47, Vitaly Kuznetsov wrote:
>>> It may happen that Xen's and Linux's ideas of vCPU id diverge. In
>>> particular, when we crash on a secondary vCPU we may want to do kdump
>>> and unlike plain kexec where we do
On Wed, Jun 29, 2016 at 06:35:12PM +0800, Wangnan (F) wrote:
>
>
> On 2016/6/29 18:15, Hekuang wrote:
> >hi
> >
> >在 2016/6/28 22:57, Alexei Starovoitov 写道:
> >>
> >> return 0;
> >> }
> >>@@ -465,7 +465,7 @@ EXPORT_SYMBOL_GPL(__bpf_call_base);
> >> *
> >> * Decode and execute eBPF in
On Wednesday 29 June 2016 04:15 PM, Manish Badarkhe wrote:
Hi Keerthy,
sorry ignore my last two comments in previous mail.
On Wed, Jun 29, 2016 at 4:13 PM, Manish Badarkhe
wrote:
Hi Keerthy
Some minor comment
+static int lp873x_gpio_direction_output(struct gpio_chip *chip,
+
Am 27.06.2016 um 19:08 schrieb Mauro Carvalho Chehab :
> Em Mon, 27 Jun 2016 08:15:28 +0200
> Markus Heiser escreveu:
>
>> Am 24.06.2016 um 12:40 schrieb Mauro Carvalho Chehab
>> :
>>
>>> Em Tue, 31 May 2016 12:16:25 +0200
>>> Markus Heiser escreveu:
>>>
Am 30.05.2016 um 23:23 schrieb
On 27/06/16 08:24, Jan Beulich wrote:
On 24.06.16 at 17:01, wrote:
>> On 07/06/16 07:31, Jan Beulich wrote:
>>> - drop unused function parameter of read_dev_bar()
>>> - drop rom_init() (now identical to bar_init())
>>> - fold read_dev_bar() into its now single caller
>>> - simplify determinat
On Mon, Jun 20, 2016 at 04:50:37PM +0900, byungchul.park wrote:
> > -Original Message-
> > From: xinhui [mailto:xinhui@linux.vnet.ibm.com]
> > Sent: Monday, June 20, 2016 4:29 PM
> > To: Byungchul Park; pet...@infradead.org; mi...@kernel.org
> > Cc: linux-kernel@vger.kernel.org; npig...
On Mon, Jun 20, 2016 at 01:55:10PM +0900, Byungchul Park wrote:
> Currently, bit-based lock e.g. bit_spin_lock cannot use the lock
> correctness validator using lockdep. However, it would be useful if
> the validator supports for even bit-based lock as well.
>
> Therefore, this patch provides inte
On 01/06/16 15:15, Bhaktipriya Shridhar wrote:
> System workqueues have been able to handle high level of concurrency
> for a long time now and there's no reason to use dedicated workqueues
> just to gain concurrency. Replace dedicated xen_pcibk_wq with the
> use of system_wq.
>
> Unlike a dedica
Andrew Cooper writes:
> On 29/06/16 13:16, Vitaly Kuznetsov wrote:
>> Andrew Cooper writes:
>>
>>> On 28/06/16 17:47, Vitaly Kuznetsov wrote:
@@ -1808,6 +1822,8 @@ static int xen_hvm_cpu_notify(struct notifier_block
*self, unsigned long action,
int cpu = (long)hcpu;
sw
On 31/05/16 17:56, Bhaktipriya Shridhar wrote:
> System workqueues have been able to handle high level of concurrency
> for a long time now and there's no reason to use dedicated workqueues
> just to gain concurrency. Replace dedicated xenbus_frontend_wq with the
> use of system_wq.
>
> Unlike a
Add a helper macro to return if a device has a bus type of fsl_mc.
This makes the bus driver code more readable and provides a way for
drivers like the SMMU driver to easily check the bus type.
Signed-off-by: Nipun Gupta
Signed-off-by: Bharat Bhushan
---
drivers/staging/fsl-mc/bus/dprc-driver.c
On Tue, 2016-06-28 at 11:17 +0800, Kefeng Wang wrote:
> Make dw8250_set_termios() as the default set_termios callback for 8250
> dw uart, correct me
> if I am wrong.
>
> Then add ACPI support for uart on Hisilicon Hip05 soc, be careful that
> it is not 16500
> compatible.
You mean it has Busy Fun
发自我的 iPhone
> 在 2016年6月29日，下午8:37，Alexei Starovoitov 写道：
>
>> On Wed, Jun 29, 2016 at 06:35:12PM +0800, Wangnan (F) wrote:
>>
>>
>>> On 2016/6/29 18:15, Hekuang wrote:
>>> hi
>>>
在 2016/6/28 22:57, Alexei Starovoitov 写道:
return 0;
}
@@ -465,7 +465,7 @@ EXPOR
I've been travelling so this accumulates more than week or so of bug
fixing. It perhaps looks a little worse than it really is.
1) Fix deadlock in ath10k driver, from Ben Greear.
2) Increase scan timeout in iwlwifi, from Luca Coelho.
3) Unbreak STP by properly reinjecting STP packets back into
On Wed, Jun 29, 2016 at 10:27 AM, Sinan Kaya wrote:
> The change introduced in commit 103544d86976 ("ACPI,PCI,IRQ: reduce
> resource requirements") omitted the initially assigned POSSIBLE penalty
> when the IRQ is active.
It would be good to say what can go wrong with that here.
> The original c
On Wed, 29 Jun 2016, Markus Heiser wrote:
> Am 28.06.2016 um 21:05 schrieb Jani Nikula :
>> Perhaps you misunderstood, I don't know. When we ask you to rebase your
>> work on something, in this case docs-next, it generally means, accept
>> what is there, and iteratively build and extend upon it, *
Hello,
On Wed, Jun 29, 2016 at 10:17:48AM +0200, Petr Mladek wrote:
> > Ah, okay, I don't think we need to change this. I was suggesting to
> > simplify it by dropping the draining and just do flush from destroy.
>
> I see. But then it does not address the original concern from Peter
> Zijlstra.
On Wed, Jun 29, 2016 at 10:27 AM, Sinan Kaya wrote:
> The omitted parenthesis prevents the addition operation when
> acpi_penalize_isa_irq function is called.
>
> Signed-off-by: Sinan Kaya
Well, this is a rather obvious one, so I'm wondering why it is the
last one in the series?
> ---
> driver
There are two if ... else which check the same thing in different
part of the code, they can be merged in a single check.
Signed-off-by: Andi Shyti
---
drivers/media/rc/lirc_dev.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/drivers/media/rc/lirc_dev.c b/drive
Some drivers don't necessarily need to have a FIFO managed buffer
for their transfers. Drivers now should call
lirc_register_bufferless_driver in order to handle the buffer
themselves.
The function works exaclty like lirc_register_driver except of
the buffer allocation.
Signed-off-by: Andi Shyti
If ioctl is called, it cannot be a case of invalid system call
number (ENOSYS), that is an operation not permitted (EPERM).
Replace ENOSYS with EPERM.
Signed-off-by: Andi Shyti
---
drivers/media/rc/lirc_dev.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/med
The three if statements check the same thing, merge them in only
one statement.
Signed-off-by: Andi Shyti
---
drivers/media/rc/lirc_dev.c | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/media/rc/lirc_dev.c b/drivers/media/rc/lirc_dev.c
index 7dff92c..0c266
When opening or closing a lirc character device, the framework
provides to the user the possibility to keep track of opening or
closing of the device by calling two functions:
- set_use_inc() when opening the device
- set_use_dec() when closing the device
if those are not set by the lirc user,
The Lirc framework works mainly with receivers, but there is
nothing that prevents us from using it for transmitters as well.
For that we need to have more control on the device frequency to
set (which is a new concept fro LIRC) and we also need to provide
to userspace, as feedback, the values of
There is no need to check in precompilation whether the ioctl is
compat or unlocked, depending on the configuration it will be
called the correct one.
Signed-off-by: Andi Shyti
---
drivers/media/rc/lirc_dev.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/media/rc/lirc_dev.c b/driv
The whole function is inside an 'if' statement
("if (ir->d.add_to_buf)").
Check the opposite of that statement at the beginning and exit,
this way we can have one level less of indentation.
Signed-off-by: Andi Shyti
---
drivers/media/rc/lirc_dev.c | 33 -
1 file
Hi,
because I wanted to add three ioctl commands in lirc, I ended up
with the patchset below.
This is a collection of fixes, added functionality, coding rework
and trivial coding style fixes.
The first patch is preparatory to the second, which allows the
user to create a lirc driver without rece
Hello, Roger.
On Wed, Jun 29, 2016 at 11:54:11AM +0800, Roger Lu wrote:
> Please allow me to elaborate my previous concern about printing
> freezable workqueue info only in this case.
>
> The benefit of it is that debugger can quickly understand which
> freezable workqueues block suspend flow and
The code can be rearranged so that some goto paths can be removed
Signed-off-by: Andi Shyti
---
drivers/media/rc/lirc_dev.c | 34 --
1 file changed, 12 insertions(+), 22 deletions(-)
diff --git a/drivers/media/rc/lirc_dev.c b/drivers/media/rc/lirc_dev.c
index b11
... use "do .. while" instead.
Signed-off-by: Andi Shyti
---
drivers/media/rc/lirc_dev.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/media/rc/lirc_dev.c b/drivers/media/rc/lirc_dev.c
index 400ab80..cc00b9a 100644
--- a/drivers/media/rc/lirc_dev.c
+++ b
This patch mutes also all the checkpatch warnings related to
printk.
Reword all the printouts so that the string doesn't need to be
split, which fixes the following checkpatch warning:
WARNING: quoted string split across lines
Signed-off-by: Andi Shyti
---
drivers/media/rc/lirc_dev.c | 76 ++
Signed-off-by: Andi Shyti
---
drivers/media/rc/lirc_dev.c | 25 -
1 file changed, 25 deletions(-)
diff --git a/drivers/media/rc/lirc_dev.c b/drivers/media/rc/lirc_dev.c
index fa562a3..ee997ab 100644
--- a/drivers/media/rc/lirc_dev.c
+++ b/drivers/media/rc/lirc_dev.c
@@ -8
When comparing a variable with a constant, the comparison should
start from the variable and not from the constant. It's also
written in the human DNA.
Swap the terms of comparisons whenever the constant comes first
and fix the following checkpatch warning:
WARNING: Comparisons should place the
Hello, Linus.
Three fix patches. Two are for cgroup / css init failure path. The
last one makes css_set_lock irq-safe as the deadline scheduler ends up
calling put_css_set() from irq context.
Thanks.
The following changes since commit ea8ea737c46cffa5d0ee74309f81e55a7e5e9c2a:
Merge tag 'nfs
Signed-off-by: Andi Shyti
---
drivers/media/rc/lirc_dev.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/rc/lirc_dev.c b/drivers/media/rc/lirc_dev.c
index 6f3402c..0a3d65d 100644
--- a/drivers/media/rc/lirc_dev.c
+++ b/drivers/media/rc/lirc_dev.c
@@ -692,7 +69
During the driver registration, move the buffer allocation on a
separate function.
Signed-off-by: Andi Shyti
---
drivers/media/rc/lirc_dev.c | 57 +++--
1 file changed, 34 insertions(+), 23 deletions(-)
diff --git a/drivers/media/rc/lirc_dev.c b/drivers/m
Of course this should have been "[GIT] Networking", sigh...
Hi Tomasz,
On 06/29/2016 06:48 AM, Tomasz Nowicki wrote:
> On 28.06.2016 18:12, Duc Dang wrote:
>> On Tue, Jun 28, 2016 at 6:04 AM, Christopher Covington
>> wrote:
>>> Hi Tomasz,
>>> Ard's comments on v3 included:
>>>
>>> "... exact OEM table/rev id matches ..."
>>> "... substring match ... out
Hi,
The USB Type-C class is meant to provide unified interface to the
userspace to present the USB Type-C ports in a system.
Changes since v3:
- Documentation cleanup as proposed by Roger Quadros
- Setting partner altmodes member to NULL on removal and fixing a
warning, as proposed by Guenter R
The purpose of USB Type-C connector class is to provide
unified interface for the user space to get the status and
basic information about USB Type-C connectors on a system,
control over data role swapping, and when the port supports
USB Power Delivery, also control over power role swapping
and Alt
This adds driver for the USB Type-C PHY on Intel WhiskeyCove
PMIC which is available on some of the Intel Broxton SoC
based platforms.
Signed-off-by: Heikki Krogerus
---
drivers/usb/typec/Kconfig | 14 ++
drivers/usb/typec/Makefile | 1 +
drivers/usb/typec/typec_wcove.c | 371 +
sh used P1 address space in early device tree.
So need convert P1 to physical address before reserve memory.
Changes v4
none
Signed-off-by: Yoshinori Sato
---
arch/sh/boards/of-generic.c | 12
1 file changed, 12 insertions(+)
diff --git a/arch/sh/boards/of-generic.c b/arch/sh/boar
Changes v4
- split patches
- remove unneeded line
- example update
Signed-off-by: Yoshinori Sato
---
.../interrupt-controller/iodata-landisk.txt| 31 ++
drivers/irqchip/Makefile | 2 +-
drivers/irqchip/irq-io-landisk.c | 72 +++
Changes v4
none
Signed-off-by: Yoshinori Sato
---
arch/sh/boards/of-generic.c | 64 +
1 file changed, 64 insertions(+)
diff --git a/arch/sh/boards/of-generic.c b/arch/sh/boards/of-generic.c
index 2d3cda3..709006a 100644
--- a/arch/sh/boards/of-generic
Convert SH specific clock framework to CCF.
Changes v4
Add acked-by
Signed-off-by: Yoshinori Sato
Acked-by: Rob Herring
---
.../bindings/clock/renesas,sh7750-cpg.txt | 25 ++
arch/sh/boards/Kconfig | 1 +
arch/sh/kernel/cpu/Makefile
SH3/4 have register bank of R0-R7.
Preset FDT address assigned bank depend on boot loader.
Before setting a bank because we don't depend on a boot loader, it's evacuated.
Changes v4
none
Signed-off-by: Yoshinori Sato
---
arch/sh/kernel/head_32.S | 7 +++
1 file changed, 3 insertions(+), 4 d
Could you fix the typo "a,k.a" => "a.k.a."?
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
`-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
On Wed, Jun 29, 2016 at 09:31:39PM +0800, Icenowy Zheng wrote:
> However, sun8iw3/5 ths is not even a GPADC... It's a specified IP,
> only used as an ADC suitable for temperature sensor.
It doesn't matter. It's the same IP, labelled differently.
Maxime
--
Maxime Ripard, Free Electrons
Embedded
On Wed, Jun 29, 2016 at 5:15 AM, Yakir Yang wrote:
> eDP controller need to declare which vop provide the video source,
> and it's defined in GRF registers.
>
> But different chips have different GRF register address, so we need to
> create a device data to declare the GRF messages for each chips.
Since it should always be ok for normal users to operate the accelerator,
it makes sense to change it in our driver, rather than adding udev rules
for all Linux distributions.
Signed-off-by: Frank Haverkamp
---
drivers/misc/genwqe/card_base.c | 15 +++
1 file changed, 15 insertions(+
On Monday 27 June 2016 11:09 PM, Douglas Anderson wrote:
> Two times out of 2000 reboots I ran into the error message
> "rockchip_emmc_phy_power: dllrdy timeout". Presumably there is some
> corner case where the DLL just takes a little longer to timeout. Let's
> give it even more time to handle
Hi,
On Monday 27 June 2016 11:09 PM, Douglas Anderson wrote:
> It's possible that there are some reasons to turn the PHY on while the
> clock is 0. In this case we just won't wait for the DLL to lock.
>
> This is a bit of a stopgap until we figure out exactly when we're
> supposed to wait for th
On 29 June 2016 at 15:34, Christopher Covington wrote:
> Hi Tomasz,
>
> On 06/29/2016 06:48 AM, Tomasz Nowicki wrote:
>> On 28.06.2016 18:12, Duc Dang wrote:
>>> On Tue, Jun 28, 2016 at 6:04 AM, Christopher Covington
>>> wrote:
Hi Tomasz,
>
Ard's comments on v3 included:
"...
201 - 300 of 844 matches
Mail list logo
