From: Markus Elfring
Date: Wed, 30 Aug 2017 22:11:33 +0200
A few update suggestions were taken into account
from static source code analysis.
Markus Elfring (4):
Delete an error message for a failed memory allocation in two functions
Improve a size determination in ds3000_attach()
Delete a
From: Markus Elfring
Date: Wed, 30 Aug 2017 21:41:28 +0200
Omit an extra message for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/media/dvb-frontends/ds3000.c | 8 ++--
1 file changed, 2
From: Markus Elfring
Date: Wed, 30 Aug 2017 21:49:22 +0200
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was det
On Wed, Aug 30, 2017 at 01:04:31PM -0700, Arve Hjønnevåg wrote:
> On Wed, Aug 30, 2017 at 2:29 AM, Dan Carpenter
> wrote:
> > On Tue, Aug 29, 2017 at 05:46:59PM -0700, Sherry Yang wrote:
> >> Binder driver allocates buffer meta data in a region that is mapped
> >> in user space. These meta data c
From: Markus Elfring
Date: Wed, 30 Aug 2017 21:51:26 +0200
The variable "state" will be set to an appropriate pointer a bit later.
Thus omit the explicit initialisation at the beginning.
Signed-off-by: Markus Elfring
---
drivers/media/dvb-frontends/ds3000.c | 2 +-
1 file changed, 1 insertion(
On 08/30/2017 10:13 PM, Shuah Khan wrote:
On 08/30/2017 12:47 PM, Daniel Borkmann wrote:
On 08/30/2017 07:15 PM, Colin King wrote:
From: Colin Ian King
Trivial fix to typos in printf error messages:
"conenct" -> "connect"
"listeen" -> "listen"
thanks to Daniel Borkmann for spotting one of th
From: Markus Elfring
Date: Wed, 30 Aug 2017 22:02:54 +0200
* Return directly after a call of the function "kzalloc" failed
at the beginning.
* Move a bit of exception handling code into an if branch.
* Delete two jump targets which became unnecessary with this refactoring.
Signed-off-by: Mar
>> diff --git a/include/uapi/linux/dvb/video.h b/include/uapi/linux/dvb/video.h
>> index d3d14a59d2d5..6c7f9298d7c2 100644
>> --- a/include/uapi/linux/dvb/video.h
>> +++ b/include/uapi/linux/dvb/video.h
>> @@ -135,7 +135,8 @@ struct video_event {
>> #define VIDEO_EVENT_FRAME_RATE_CHANGED 2
>
On Wed, Aug 30, 2017 at 03:41:18PM +0100, Dietmar Eggemann wrote:
> The following 'capacity-dmips-mhz' dt property values are used:
>
> Cortex-A15: 1024, Cortex-A7: 539
>
> They have been derived from the cpu_efficiency values:
>
> Cortex-A15: 3891, Cortex-A7: 2048
>
> by scaling them so that t
On Wed, 30 Aug 2017 13:02:22 +0530 Prakash Gupta wrote:
> The stacktraces always begin as follows:
>
> [] save_stack_trace_tsk+0x0/0x98
> [] save_stack_trace+0x24/0x28
> ...
>
> This is because the stack trace code includes the stack frames for itself.
> This is incorrect behaviour, and also
Hi!
> >> + * 9 -> Illegal Trap
> >> + * 10 -> Unknown
> >> + * 11 -> Crew Panel Requested
> >
> > Anyway... If you move management chip to .. I don't know, i2c, the
> > path would change. Also it would be different path on N900. Userland
> > should
From: Haiyang Zhang
There are two typos in the document, netvsc.txt,
regarding UDP hashing level. This patch fixes them.
Signed-off-by: Haiyang Zhang
---
Documentation/networking/netvsc.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/networking/netvsc.
Hi,
On 08/29/2017 10:38 PM, Pavel Machek wrote:
> Hi!
>
>>> -As a specific example of this use-case, let's look at vibrate feature on
>>> -phones. Vibrate function on phones is implemented using PWM pins on SoC or
>>> -PMIC. There is a need to activate one shot timer to control the vibrate
>>> -f
On Wed, Aug 30, 2017 at 11:40:08AM -0700, Nadav Amit wrote:
> Jerome Glisse wrote:
>
> > On Wed, Aug 30, 2017 at 07:27:47PM +0200, Andrea Arcangeli wrote:
> >> On Tue, Aug 29, 2017 at 07:46:07PM -0700, Nadav Amit wrote:
> >>> Therefore, IIUC, try_to_umap_one() should only call
> >>> mmu_notifier_
Quoting Shawn Guo (2017-08-16 23:43:49)
> Hi Stephen,
>
> On Fri, Jul 14, 2017 at 02:40:05PM -0700, Stephen Boyd wrote:
> > We currently have three device nodes for the same USB hardware
> > block, as evident by the reuse of the same reg address multiple
> > times. Now that the chipidea driver ful
On Wed, Aug 30, 2017 at 11:40:08AM -0700, Nadav Amit wrote:
> The mmu_notifier users would have to be aware that invalidations may be
> deferred. If they perform their ``invalidations’’ unconditionally, it may be
> ok. If the notifier users avoid invalidations based on the PTE in the
> secondary pa
On Wed, 30 Aug 2017, Roman Gushchin wrote:
> I've spent some time to implement such a version.
>
> It really became shorter and more existing code were reused,
> howewer I've met a couple of serious issues:
>
> 1) Simple summing of per-task oom_score doesn't make sense.
>First, we calculate
@@ -2363,5 +2364,5 @@ static int tsi148_probe(struct pci_dev *pdev, const
struct pci_device_id *id)
master_num--;
tsi148_device->flush_image =
-kmalloc(sizeof(struct vme_master_resource),
GFP_KERNEL);
+
On Wed, Aug 30, 2017 at 04:36:06PM +0100, Marc Zyngier wrote:
> On 28/08/17 19:18, Christoffer Dall wrote:
> > On Mon, Jul 31, 2017 at 06:26:29PM +0100, Marc Zyngier wrote:
> >> When a vPE is not running, a VLPI being made pending results in a
> >> doorbell interrupt being delivered. Let's handle t
Hello Geert,
On Wed, Aug 30, 2017 at 10:15 PM, Geert Uytterhoeven
wrote:
> Hi Javier,
>
> On Wed, Aug 30, 2017 at 9:57 PM, Javier Martinez Canillas
> wrote:
>>> I think we should talk about the same case: Let me repeat what I did:
>>>
>>> 1) I added your patch "eeprom: at24: Add OF device ID tab
On Wed, Aug 30, 2017 at 05:03:51PM +0100, Marc Zyngier wrote:
> On 28/08/17 19:35, Christoffer Dall wrote:
> > On Mon, Jul 31, 2017 at 06:26:34PM +0100, Marc Zyngier wrote:
> >> The GICv4 architecture doesn't prevent CPUs implementing GICv4 to
> >> cohabit with CPUs limited to GICv3 in the same sys
On 08/26, Shawn Guo wrote:
> On Fri, Aug 25, 2017 at 04:18:18PM -0700, Stephen Boyd wrote:
> >
> > Right. Does the GPIO work? If so, it sounds like the read/write
> > access checks in spmi pmic arb don't work properly.
>
> The check works. With the check in there, PM8916 GPIO doesn't work.
> How
I just went back through it -- turns out my email bounced back from
linux-kernel@vger.kernel.org (reason was "may contain a virus"). Sorry
I didn't notice that and resend.
On Wed, Aug 30, 2017 at 1:20 PM, Dan Carpenter wrote:
> On Wed, Aug 30, 2017 at 01:04:31PM -0700, Arve Hjønnevåg wrote:
>> On
On 08/23, Kiran Gunda wrote:
> Check the irq ownership in the irq_request_resources callback
> instead of checking it during the irq mapping. This can prevent
> installing the flow handler for the interrupt that is not owned by the EE
> and allow the irq translation during the gpio driver probe.
>
Hi Divagar,
Thanks for the update.
On Wed, Aug 30, 2017 at 10:35:40PM +0530, Divagar Mohandass wrote:
> Currently the device is kept in D0, there is an opportunity
> to save power by enabling runtime pm.
>
> Device can be daisy chained from PMIC and we can't rely on I2C core
> for auto resume/su
The patch
ASoC: hdmi-codec: Use different name for playback streams
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) a
On Wed, Aug 30, 2017 at 02:12:09PM -0700, Fenghua Yu wrote:
> +static struct cyc2ns_data cyc2ns_early;
> +static bool sched_clock_early_enabled;
Should these two varaibles be "__initdata"?
> +u64 sched_clock_early(void)
This function is only called during boot time. Should it
be a "__init" funct
On Mon, 28 Aug 2017 16:10:09 -0700
Randy Dunlap wrote:
> kernel-doc parsing uses as ASCII codec, so let people know that
> kernel-doc comments should be in ASCII characters only.
>
> WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno
> ../drivers/media/dvb-core/demux.h' processing f
On Fri, 11 Aug 2017 15:16:06 +0200
Eric Auger wrote:
> In vfio_iommu_group_get() we want to increase the reference
> count of the iommu group.
>
> In noiommu case, the group does not exist and is allocated.
> iommu_group_add_device() increases the group ref count. However we
> then call iommu_gr
Hi Pavel,
[auto build test ERROR on sparc/master]
[also build test ERROR on v4.13-rc7 next-20170829]
[cannot apply to mmotm/master]
[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/Pavel-Tatashin/
On Wed, 23 Aug 2017 22:47:15 +0530
Arvind Yadav wrote:
> amba_id are not supposed to change at runtime. All functions
> working with const amba_id. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
> ---
> drivers/vfio/platform/vfio_amba.c | 2 +-
> 1 file changed, 1 inse
On Mon, 28 Aug 2017 16:10:16 -0700
Randy Dunlap wrote:
> Fix non-ASCII charactes in kernel-doc comment to prevent the kernel-doc
> build warning below.
>
> WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno
> ../drivers/media/dvb-core/demux.h' processing failed with: 'ascii' codec
On Wed, Aug 30, 2017 at 11:00:32AM -0700, Nadav Amit wrote:
> It is not trivial to flush TLBs (primary or secondary) without holding the
> page-table lock, and as we recently encountered this resulted in several
> bugs [1]. The main problem is that even if you perform the TLB flush
> immediately af
On Mon, 28 Aug 2017 17:40:39 -0700
Randy Dunlap wrote:
> Drop all references to git daily snapshots of Linux mainline git tree
> since they are no longer generated.
>
> Drop the "Last update" info since 'git log' is a better source of that
> info and since the Last update date is not being updat
> On Mon 2017-08-28 16:09:27, Andrew Lunn wrote:
> > > I may be confused here, but AFAICT:
> > >
> > > 1) Yes, it has standard layout when accessed over MDIO.
> >
> >
> > Section 4.8 of the datasheet says:
> >
> > All the registers defined in this section can be also accessed
> > via the SP
Hi Fenghua,
Thank you for looking at this. Unfortunately I can't mark either of them
__init because sched_clock_early() is called from
u64 sched_clock_cpu(int cpu)
Which is around for the live of the system.
Thank you,
Pasha
On 08/30/2017 05:21 PM, Fenghua Yu wrote:
On Wed, Aug 30,
On 08/25/2017 05:26 AM, Petr Mladek wrote:
> On Wed 2017-07-19 13:18:06, Jason Baron wrote:
>> Introduce atomic replace, by first creating a 'no_op' klp_func for all
>> the functions that are reverted by patch B.
>
>> diff --git a/include/linux/livepatch.h b/include/linux/livepatch.h
>> index 5038
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes
...to receive a single patch removing some structure definitions from a
uapi header file. These payloads are never processed directly by the
kernel they are simply passed through an ioctl as
When doing cumulative patches, if patch A introduces a change to function 1,
and patch B reverts the change to function 1 and introduces changes to say
function 2 and 3 as well, the change that patch A introduced to function 1
is still present.
Introduce atomic replace, by first creating a 'no_op'
In preparation to introducing atomic replace, introduce iterators for klp_func
and klp_object, such that objects and functions can be dynmically allocated
(needed for atomic replace). This patch is intended to effectively be a no-op
until atomic replace is introduced.
Signed-off-by: Jason Baron
C
Hi,
In testing livepatch, I found that when doing cumulative patches, if a patched
function is completed reverted by a subsequent patch (back to its original
state)
livepatch does not revert the funtion to its original state. Specifically, if
patch A introduces a change to function 1, and patch B
Introduce a sysctl knob such that by default livepatch is not in
'atomic replace' mode. A '0' in /proc/sys/kernel/livepatch_mode means the
current default mode, while a '1' means do atomic replace.
This patch is not meant to be applied and is for testing purposes only. The
intent is for the tool t
Hi Timur, Linus & Grygorii,
Looks like commit 108d23e322a2 ("gpiolib: request the gpio before
querying its direction") caused a regression on at least pandaboard
es with booting hanging shortly after gpio init.
It seems to be that we're now calling request and free on all gpios
before they are pr
On Wed, Aug 30, 2017 at 01:48:43PM +0200, Borislav Petkov wrote:
> Btw,
>
> how about communicating stuff to the userspace daemon like this?
>
> This'll simplify a lot of detection in userspace.
>
> Thoughts?
>
> ---
> diff --git a/drivers/ras/debugfs.c b/drivers/ras/debugfs.c
> index 501603057
On 08/30/2017 04:41 PM, Tony Lindgren wrote:
It seems to be that we're now calling request and free on all gpios
before they are properly configured?
Yes, that's what my patch does. At the time, it seemed like a good idea
-- request the GPIO before touching its hardware. But it appears that
Hi,
thanks for the feedback I will rework the patch.
Should I also update the sun8i-h3-bananapi-m2-plus.dts? It uses also the
AP6212 and it is done in the same way like in this patch.
Am 30.08.2017 um 16:52 schrieb Maxime Ripard:
Hi,
On Wed, Aug 30, 2017 at 05:01:07AM +0200, Philipp Rossak wr
On Wed, Aug 30, 2017 at 9:52 AM, Andrea Arcangeli wrote:
>
> I pointed out in earlier email ->invalidate_range can only be
> implemented (as mutually exclusive alternative to
> ->invalidate_range_start/end) by secondary MMUs that shares the very
> same pagetables with the core linux VM of the prim
Hello,
This series adds SMP support for OpenRISC. The OpenRISC multicore platform
and SMP Linux support is based on the work that Stefan Kristiansson did
around 2012. The platform was implemented in Verilog and run on FPGAs. I
have been working to upstream this work. I have additionally tested t
From: Stefan Kristiansson
Previously, the area between 0x0-0x100 have been used as a
"scratch" memory area to temporarily store regs during
exception entry.
In a multi-core environment, this will not work.
This change is to use shadow registers for nested context.
Currently only the "critical"
While working on SMP for OpenRISC I found this is needed for qrwlocks to
work correctly. OpenRISC is big endian so this should have been here
already.
Signed-off-by: Stafford Horne
---
arch/openrisc/Kconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/openrisc/Kconfig b/arch/open
OpenRISC only supports hardware instructions that perform 4 byte atomic
operations. For enabling qrwlocks for upcoming SMP support 1 and 2 byte
implementations are needed. To do this we leverage the 4 byte atomic
operations and shift/mask the 1 and 2 byte areas as needed.
This heavily borrows id
Enable OpenRISC to use qspinlocks and qrwlocks for upcoming SMP support.
Signed-off-by: Stafford Horne
---
arch/openrisc/Kconfig | 2 ++
arch/openrisc/include/asm/Kbuild | 4
arch/openrisc/include/asm/spinlock.h | 12 +++-
arch/openrisc/include
From: Stefan Kristiansson
IPI driver for OpenRISC Multicore programmable interrupt controller as
described in the Multicore support section of the OpenRISC 1.2
proposed architecture specification:
https://github.com/stffrdhrn/doc/raw/arch-1.2-proposal/openrisc-arch-1.2-rev0.pdf
Each OpenRISC
> The KSZ8795 driver will be submitted after Labor Day (9/4) if
> testing reveals no problem. The KSZ8895 driver will be submitted
> right after that. You should have no problem using the driver right
> away.
Hi Tristram
Release early, release often. It stops people wasting time
Also, we a
From: Stefan Kristiansson
This patch introduces the SMP support for the OpenRISC architecture.
The SMP architecture requires cores which have multicore features which
have been introduced a few years back including:
- New SPRS SPR_COREID SPR_NUMCORES
- Shadow SPRs
- Atomic Instructions
- Cac
During SMP testing we were getting the below warning after booting the
secondary cpu:
[0.06] BUG: scheduling while atomic: swapper/1/0/0x
This change follows similar patterns from other architectures to start
the schduler with preempt disabled.
Signed-off-by: Stafford Horne
---
Currently we do a spin on secondary cpus when waiting to boot. This causes
issues with power consumption as well as qemu cycle burning (it starves
cpu 0 from actually being able to boot.)
The secondary interrupt handler is stored in the init section so as to
allow it to be reclaimed after boot.
On 08/30/17 14:23, Jonathan Corbet wrote:
> On Mon, 28 Aug 2017 16:10:09 -0700
> Randy Dunlap wrote:
>
>> kernel-doc parsing uses as ASCII codec, so let people know that
>> kernel-doc comments should be in ASCII characters only.
>>
>> WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno
On Wed, Aug 30, 2017 at 02:47:19PM -0700, mark gross wrote:
> FWIW I this looks fishy in arch independent code. I assume this
> include is for the definition of the mca_cfg global used in the printf
> below.
Yeah, it is a bit ad-hoc. I guess I can add an arch_has_decoder()
wrapper which each arch
From: Jan Henrik Weinstock
On OpenRISC the icache does not snoop data stores. This can cause
aliasing as reported by Jan. This patch fixes the issue to ensure icache
is properly synchronized when code is written to memory. It supports both
SMP and UP flushing.
This supports dcache flush as wel
From: Stefan Kristiansson
Simple enough to be compatible with simulation environments,
such as verilated systems, QEMU and other targets supporting OpenRISC
SMP. This also supports our base FPGA SoC's if the cpu frequency is
upped to 50Mhz.
Signed-off-by: Stefan Kristiansson
[sho...@gmail.com:
Lockdep is needed for proving the spinlocks and rwlocks work fine on our
platform. It also requires calling the trace_hardirqs_off() and
trace_hardirqs_on() pair of routines when entering and exiting an
interrupt.
For OpenRISC the interrupt stack frame does not support frame pointers,
so to call
For lockdep support a reliable stack trace mechanism is needed. This
patch adds support in OpenRISC for the stacktrace framework, implemented
by a simple unwinder api. The unwinder api supports both framepointer
and basic stack tracing.
The unwinder is now used to replace the stack_dump() implem
In case timers are not in sync when cpus start (i.e. hot plug / offset
resets) we need to synchronize the secondary cpus internal timer with
the main cpu. This is needed as in OpenRISC SMP there is only one
clocksource registered which reads from the same ttcr register on each
cpu.
This synchroni
On Wed, Aug 30, 2017 at 12:53:56PM -0700, Tim Harvey wrote:
> Greetings,
>
> I'm seeing RX frame errors when using the mv88e6xxx DSA driver on
> 4.13-rc7. The board I'm using is a GW5904 [1] which has an IMX6 FEC
> MAC (eth0) connected via RGMII to a MV88E6176 with its downstream
> P0/P1/P2/P3 to
On Wed, Aug 16, 2017 at 10:58:05AM -0700, Paul E. McKenney wrote:
> On Wed, Aug 16, 2017 at 12:41:40PM -0400, Steven Rostedt wrote:
> > On Wed, 16 Aug 2017 09:32:28 -0700
> > "Paul E. McKenney" wrote:
> >
> > > Let me see if I understand you... About halfway to the stall limit,
> > > RCU trigger
Em Wed, 30 Aug 2017 15:02:59 -0700
Randy Dunlap escreveu:
> On 08/30/17 14:23, Jonathan Corbet wrote:
> > On Mon, 28 Aug 2017 16:10:09 -0700
> > Randy Dunlap wrote:
> >
> >> kernel-doc parsing uses as ASCII codec, so let people know that
> >> kernel-doc comments should be in ASCII characters
On Wed, Aug 30, 2017 at 04:45:49PM -0400, Jerome Glisse wrote:
> So i look at both AMD and Intel IOMMU. AMD always flush and current pte value
> do not matter AFAICT (i doubt that hardware rewalk the page table just to
> decide not to flush that would be terribly dumb for hardware engineer to do
>
Em Wed, 30 Aug 2017 15:24:30 -0600
Jonathan Corbet escreveu:
> On Mon, 28 Aug 2017 16:10:16 -0700
> Randy Dunlap wrote:
>
> > Fix non-ASCII charactes in kernel-doc comment to prevent the kernel-doc
> > build warning below.
> >
> > WARNING: kernel-doc '../scripts/kernel-doc -rst -enable-lineno
From: Antoine Tenart
Date: Wed, 30 Aug 2017 10:29:11 +0200
> This series, following up the one one the GoP/MAC configuration, aims at
> stopping to depend on the firmware/bootloader configuration when using
> the PPv2 engine. With this series the PPv2 driver does not need to rely
> on a previous
From: Bhumika Goyal
Date: Wed, 30 Aug 2017 14:55:08 +0530
> Make this const as it is never modified.
>
> Signed-off-by: Bhumika Goyal
Applied to net-next.
Hi Anthony,
Thanks for taking the time to provide feedback. My comments inline below.
On 08/25/2017 04:31 PM, Anthony Yznaga wrote:
On Aug 9, 2017, at 2:26 PM, Khalid Aziz wrote:
..deleted..
+provided by the hypervisor to the kernel. Kernel returns the value of
+ADI block size to us
From: Salil Mehta
Date: Wed, 30 Aug 2017 12:06:03 +0100
> This patch removes the wrong check being done for the phy device being
> returned by the mdiobus_get_phy() function. This function never returns
> the error pointers.
>
> Fixes: 256727da7395 ("net: hns3: Add MDIO support to HNS3 Ethernet
On Wed, 30 Aug 2017 19:15:53 -0300
Mauro Carvalho Chehab wrote:
> I suspect that the problem is not related to the version, but to
> what you might have set on LANG.
>
> Maybe if we add something like:
> LANG=C.utf-8
>
> to the Documentation/Makefile
That's worth a try; Randy, can you g
From: Colin King
Date: Wed, 30 Aug 2017 12:40:12 +0100
> From: Colin Ian King
>
> Trivial fix to spelling mistake in DP_NOTICE message
>
> Signed-off-by: Colin Ian King
Applied.
From: Colin King
Date: Wed, 30 Aug 2017 18:15:25 +0100
> From: Colin Ian King
>
> Trivial fix to typos in printf error messages:
> "conenct" -> "connect"
> "listeen" -> "listen"
>
> thanks to Daniel Borkmann for spotting one of these mistakes
>
> Signed-off-by: Colin Ian King
Applied.
From: Khalid Aziz
Date: Wed, 30 Aug 2017 16:27:54 -0600
>>> +#define arch_calc_vm_prot_bits(prot, pkey)
>>> sparc_calc_vm_prot_bits(prot)
>>> +static inline unsigned long sparc_calc_vm_prot_bits(unsigned long
>>> prot)
>>> +{
>>> + if (prot & PROT_ADI) {
>>> + struct pt_regs *regs;
>>
On Wed, 23 Aug 2017 00:39:13 +0600
Alexander Kuleshov wrote:
> Signed-off-by: Alexander Kuleshov
> ---
> lib/assoc_array.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/assoc_array.c b/lib/assoc_array.c
> index 59fd7c0b119c..155c55d8db5f 100644
> --- a/lib/assoc_
Hi Gregory,
Gregory Fong writes:
> Hi all,
>
> In arch/powerpc/sysdev/mpic.c , it looks like IRQ_TYPE_EDGE_BOTH is
> handled the same way as IRQ_TYPE_EDGE_FALLING:
>
> static unsigned int mpic_type_to_vecpri(struct mpic *mpic, unsigned int type)
> {
> /* Now convert sense value */
>
Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
commit d5923ebd7cd211e5925383296723b0fab857afe4
Merge: 11b1743a0d92d 6061efb6ee6fc
Author: Ingo Molnar
AuthorDate: Tue Aug 29 16:19:54 2017
On Tue, 29 Aug 2017 16:01:14 -0700 Joe Stringer wrote:
> Recent changes[0] to make use of __compiletime_assert() from
> container_of() increased the usage of this macro, allowing developers to
> notice type conflicts in usage of container_of() at compile time.
> However, the implementation of __c
On Wed, Aug 30, 2017 at 02:53:38PM -0700, Linus Torvalds wrote:
> On Wed, Aug 30, 2017 at 9:52 AM, Andrea Arcangeli wrote:
> >
> > I pointed out in earlier email ->invalidate_range can only be
> > implemented (as mutually exclusive alternative to
> > ->invalidate_range_start/end) by secondary MMUs
On 08/30/17 15:31, Jonathan Corbet wrote:
> On Wed, 30 Aug 2017 19:15:53 -0300
> Mauro Carvalho Chehab wrote:
>
>> I suspect that the problem is not related to the version, but to
>> what you might have set on LANG.
>>
>> Maybe if we add something like:
>> LANG=C.utf-8
>>
>> to the Documenta
On 08/30/17 16:01, Randy Dunlap wrote:
> On 08/30/17 15:31, Jonathan Corbet wrote:
>> On Wed, 30 Aug 2017 19:15:53 -0300
>> Mauro Carvalho Chehab wrote:
>>
>>> I suspect that the problem is not related to the version, but to
>>> what you might have set on LANG.
>>>
>>> Maybe if we add something li
From: Haiyang Zhang
Date: Wed, 30 Aug 2017 13:37:22 -0700
> From: Haiyang Zhang
>
> There are two typos in the document, netvsc.txt,
> regarding UDP hashing level. This patch fixes them.
>
> Signed-off-by: Haiyang Zhang
Applied, thanks.
The A64 SPI controllers are register compatible to the h3/h5 SPI
controllers.
The A64 has two SPI controllers, each with a single chip select.
The handles for the DMA channels (23/24 for SPI0/SPI1) are omitted,
as the A64 DMA support is currently missing.
Signed-off-by: Stefan Brüns
---
v2: - or
On Thu 17 Aug 00:15 PDT 2017, Oleksij Rempel wrote:
> this patch set to provide remoteproc functionality on
> i.MX7D SoC.
>
Sorry for taking my time on this, applied this to the rpmsg-next branch.
Regards,
Bjorn
Hi Pavel,
[auto build test ERROR on sparc/master]
[also build test ERROR on v4.13-rc7 next-20170829]
[cannot apply to mmotm/master]
[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/Pavel-Tatashin/
Hi Arnaldo,
Please pull an update to the JSON files for POWER9 PMU events. This
removes alternate event codes from the JSON files which seem to confuse
perf.
The following changes since commit 1b2f76d77a277bb70d38ad0991ed7f16bbc115a9:
Merge tag 'perf-core-for-mingo-4.14-20170829' of
git://gi
On 08/30/17 16:04, Randy Dunlap wrote:
> On 08/30/17 16:01, Randy Dunlap wrote:
>> On 08/30/17 15:31, Jonathan Corbet wrote:
>>> On Wed, 30 Aug 2017 19:15:53 -0300
>>> Mauro Carvalho Chehab wrote:
>>>
I suspect that the problem is not related to the version, but to
what you might have se
On 30 August 2017 at 15:59, Andrew Morton wrote:
> On Tue, 29 Aug 2017 16:01:14 -0700 Joe Stringer wrote:
>
>> Recent changes[0] to make use of __compiletime_assert() from
>> container_of() increased the usage of this macro, allowing developers to
>> notice type conflicts in usage of container_of
On 08/30/2017 04:38 PM, David Miller wrote:
From: Khalid Aziz
Date: Wed, 30 Aug 2017 16:27:54 -0600
+#define arch_calc_vm_prot_bits(prot, pkey)
sparc_calc_vm_prot_bits(prot)
+static inline unsigned long sparc_calc_vm_prot_bits(unsigned long
prot)
+{
+ if (prot & PROT_ADI) {
+
[cc’ing IOMMU people, which for some reason are not cc’d]
Andrea Arcangeli wrote:
> On Wed, Aug 30, 2017 at 11:00:32AM -0700, Nadav Amit wrote:
>> It is not trivial to flush TLBs (primary or secondary) without holding the
>> page-table lock, and as we recently encountered this resulted in severa
On Wed, 30 Aug 2017 14:47:19 -0700
mark gross wrote:
> > struct dentry *ras_debugfs_dir;
> >
> > static atomic_t trace_count = ATOMIC_INIT(0);
> > @@ -12,7 +14,9 @@ EXPORT_SYMBOL_GPL(ras_userspace_consumers);
> >
> > static int trace_show(struct seq_file *m, void *v)
> > {
> > - return
This change adds hwmon temp support for w1_therm.
Signed-off-by: Jaghathiswari Rankappagounder Natarajan
Acked-by: Evgeniy Polyakov
Acked-by: Guenter Roeck
---
v2
- make changes to support hwmon_device_register_with_info mentioned by Guenter.
v3
- used IS_REACHABLE()
- rearranged the code to n
Inside the w1_slave_show function refactor the code to read the temp
into a separate function.
Signed-off-by: Jaghathiswari Rankappagounder Natarajan
Acked-by: Guenter Roeck
Acked-by: Evgeniy Polyakov
---
v2
- made changes to support hwmon_device_register_with_info mentioned by Guenter.
v3
- u
Hi Greg,
Please pull in this patchset into the tree. Thanks!
Summary of what this patchset does:
Our board has 4 DS18B20 1-wire temperature sensors. Each 1-wire bus and the
sensor under it is already configured against the Linux 1-wire driver
(called w1). They have a sysfs file(e.g.
/sys/bus/w1/d
This patch has changes to w1.h/w1.c generic files to add (optional) hwmon
support structures.
Signed-off-by: Jaghathiswari Rankappagounder Natarajan
Acked-by: Evgeniy Polyakov
Acked-by: Guenter Roeck
---
v2
- made changes to support hwmon_device_register_with_info mentioned by Guenter.
v3
- us
The A64 SoC has a DMA controller that supports 8 DMA channels
to and from various peripherals.
Add a device node for it.
Signed-off-by: Stefan Brüns
---
Documentation/devicetree/bindings/dma/sun6i-dma.txt | 1 +
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 9 +
2 files changed,
The latest generation of allwinner SoCs (e.g. H3, H5, A64) have some significant
differences to older SoC generations (e.g. A23):
- different register location for the clock autogating register (offset 0x28 vs
0x20)
- different field offset for the src/dest burst length fields in the channel
co
601 - 700 of 843 matches
Mail list logo
