On Mon, Aug 08, 2016 at 05:35:34PM -0700, Laura Abbott wrote:
> Executing from a non-executable area gives an ugly message:
>
> lkdtm: Performing direct entry EXEC_RODATA
> lkdtm: attempting ok execution at 084c0e08
> lkdtm: attempting bad execution at 08880700
> Bad mode in Synchr
Hello.
On 08/09/2016 03:35 PM, Paul Burton wrote:
Probe the system parallel flash using device tree rather than platform
code, in order to reduce the amount of the latter.
Signed-off-by: Paul Burton
---
arch/mips/boot/dts/mti/sead3.dts | 17 +
arch/mips/mti-sead3/sead3-p
- On Aug 7, 2016, at 7:35 PM, Boqun Feng boqun.f...@gmail.com wrote:
> On Sun, Aug 07, 2016 at 03:36:24PM +, Mathieu Desnoyers wrote:
>> - On Aug 3, 2016, at 11:45 AM, Boqun Feng boqun.f...@gmail.com wrote:
>>
>> > On Wed, Aug 03, 2016 at 03:19:40PM +0200, Peter Zijlstra wrote:
>> >>
On 09/08/16 05:25, John Stultz wrote:
...
> So actually no. We usually call irqd_set_trigger_type() but something
> still doesn't work.
>
> Interestingly, just adding irq_set_irq_type(virq, type); to the top of
> that block (leaving the rest of the code) also works.
Interesting. By saving the
Am Dienstag, 09 August 2016, 09:01:13 schrieb Mimi Zohar:
> On Tue, 2016-08-09 at 20:59 +1000, Michael Ellerman wrote:
> > Mimi Zohar writes:
> > > diff --git a/security/integrity/ima/ima.h
> > > b/security/integrity/ima/ima.h
> > > index b5728da..84e8d36 100644
> > > --- a/security/integrity/ima/
Hi Mark,
[auto build test WARNING on regmap/for-next]
[also build test WARNING on v4.8-rc1 next-20160809]
[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/Mark-Brown/Applied-regmap-debugfs-Add
On Tuesday 09 Aug 2016 16:17:57 Laurent Pinchart wrote:
> On Wednesday 08 Jun 2016 18:12:31 Magnus Damm wrote:
> > On Wed, Jun 8, 2016 at 5:48 PM, Laurent Pinchart wrote:
> >> On Wednesday 08 Jun 2016 09:04:17 Geert Uytterhoeven wrote:
> >>> On Wed, Jun 8, 2016 at 2:18 AM, Laurent Pinchart wrote:
>
Hi Magnus,
On Wednesday 08 Jun 2016 18:12:31 Magnus Damm wrote:
> On Wed, Jun 8, 2016 at 5:48 PM, Laurent Pinchart wrote:
> > On Wednesday 08 Jun 2016 09:04:17 Geert Uytterhoeven wrote:
> >> On Wed, Jun 8, 2016 at 2:18 AM, Laurent Pinchart wrote:
> --- 0031/drivers/iommu/ipmmu-vmsa.c
> +
Hi David,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.8-rc1 next-20160809]
[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/David-Howells/cachefiles-Fix-attempt-to-read
Hi Mark,
[auto build test ERROR on regmap/for-next]
[also build test ERROR on v4.8-rc1 next-20160809]
[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/Mark-Brown/Applied-regmap-debugfs-Add
On Fri, 05 Aug 2016, Axel Lin wrote:
> It's only used in this driver and never get modified, make it static const.
>
> Signed-off-by: Axel Lin
> ---
> drivers/mfd/altera-a10sr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
> diff --git a/drivers/mfd/altera-a10sr.c
When we don't have a tracee (i.e. we're attaching to a task or CPU),
counters can still be running after our workload finishes, and can still
be running as we read their values. As we read events one-by-one, there
can be arbitrary skew between values of events, even within a group.
This means that
> frequencies in an SoC agnostic manner. The actual clock access can be
> put in firmware, which is by definition SoC specific and thus can
> be easier and much quicker adapted to support a new SoC.
Hmm... what do you mean by "firmware"?
Stefan "just a by-stander trying to understand"
Hi,
I noticed that with v4.8-rc1 serial console of some of our Broxton
systems does not work properly anymore. I'm able to see output but input
does not work.
I bisected it down to commit 4ef03d328769eddbfeca1f1c958fdb181a69c341
("tty/serial/8250: use mctrl_gpio helpers").
The reason why it fail
On Tue, 2016-08-09 at 20:59 +1000, Michael Ellerman wrote:
> Mimi Zohar writes:
>
> > diff --git a/security/integrity/ima/ima.h b/security/integrity/ima/ima.h
> > index b5728da..84e8d36 100644
> > --- a/security/integrity/ima/ima.h
> > +++ b/security/integrity/ima/ima.h
> > @@ -102,6 +102,13 @@ s
On 08.08.16 15:05:36, Tomasz Nowicki wrote:
> Quirk handling relies on an idea of matching MCFG OEM ID, TABLE ID and
> revision (the ones from standard header of MCFG table).
>
> Static array is used to keep quirk entries. Each entry consists of
> mentioned MCFG IDs along with custom pci_ops struc
On Tue, Aug 09, 2016 at 01:40:25PM +0100, Luis de Bethencourt wrote:
> On 09/08/16 13:32, Salah Triki wrote:
> > flags field records the superblock state, so check if it is equal to
> > BEFS_DIRTY.
> >
> > Signed-off-by: Salah Triki
> > ---
> > fs/befs/super.c | 2 +-
> > 1 file changed, 1 inser
On Mon, Aug 01, 2016 at 10:04:53AM -0400, Lucile Quirion wrote:
> diff --git a/arch/arm/boot/dts/imx6dl-ts4900.dts
> b/arch/arm/boot/dts/imx6dl-ts4900.dts
> new file mode 100644
> index 000..909fd5c
> --- /dev/null
> +++ b/arch/arm/boot/dts/imx6dl-ts4900.dts
> +/dts-v1/;
> +#include "imx6dl
On Tue, Aug 09, 2016 at 01:36:17PM +0200, Wolfram Sang wrote:
[...]
> diff --git a/drivers/i2c/busses/i2c-tegra.c b/drivers/i2c/busses/i2c-tegra.c
> index b126dbaa47e370..d9979da11485ae 100644
> --- a/drivers/i2c/busses/i2c-tegra.c
> +++ b/drivers/i2c/busses/i2c-tegra.c
> @@ -932,10 +932,8 @@ stati
On Tue, 9 Aug 2016, Rafael J. Wysocki wrote:
> Here's a list of commits from Thomas that are related to memory randomization.
>
> 210e7a43fa90 mm: SLUB freelist randomization
> 7c00fce98c3e mm: reorganize SLAB freelist randomization
> 4ff5308744f5 x86/mm: Do not reference phys addr beyond kernel
On Tue, Aug 09, 2016 at 01:36:17PM +0200, Wolfram Sang wrote:
> The core will do this for us now.
>
> Signed-off-by: Wolfram Sang
> ---
> drivers/i2c/busses/i2c-amd756.c | 5 +
> drivers/i2c/busses/i2c-at91.c | 2 --
> drivers/i2c/busses/i2c-axxia.c | 8 +---
>
An NULL-pointer dereference happens in cachefiles_mark_object_inactive()
when it tries to read i_blocks so that it can tell the cachefilesd daemon
how much space it's making available.
The problem is that cachefiles_drop_object() calls
cachefiles_mark_object_inactive() after calling cachefiles_del
On Sun, 07 Aug 2016, Andrey Smirnov wrote:
> Use of_iomap instead of explicitly calling of_address_to_resource() and
> ioremap().
>
> Signed-off-by: Andrey Smirnov
> ---
> drivers/mfd/syscon.c | 7 +--
> 1 file changed, 1 insertion(+), 6 deletions(-)
Applied, thanks.
> diff --git a/driver
and as the fuzzing continues I started to get these, a bit worrying.
[ 6501.254564] Slab corruption (Tainted: GW ): task_struct
start=8800c072e000, len=5760
[ 6501.264971] 010: 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
jkkk
[ 6501.273650] Single bit error det
On 10/02/16 08:04, Bjorn Helgaas wrote:
> On Wed, Jan 13, 2016 at 12:25:34PM +0100, Hannes Reinecke wrote:
>> PCI-2.2 VPD entries have a maximum size of 32k, but might actually
>> be smaller than that. To figure out the actual size one has to read
>> the VPD area until the 'end marker' is reached.
On Fri, 29 Jul 2016, Uwe Kleine-König wrote:
> This fixes a compile failure:
>
> drivers/built-in.o: In function `wm8350_i2c_probe':
> core.c:(.text+0x828b0): undefined reference to `__devm_regmap_init_i2c'
> Makefile:953: recipe for target 'vmlinux' failed
>
> Fixes: 52b461b86
On Wed, Jul 13, 2016 at 11:06:36AM +0800, Ming Lei wrote:
> Now there are several locks which are marked as
> no_validate, so name of the lock class can be
> different with the no_validate lock.
Hurgh, how did that happen? See checkpatch saying:
scripts/checkpatch.pl: "lockdep_no_validate class
On Mon, 08 Aug 2016, Keerthy wrote:
> The LP873X chip is a power management IC for Portable Navigation Systems
> and Tablet Computing devices. It contains the following components:
>
> - Regulators.
> - Configurable General Purpose Output Signals(GPO).
>
> PMIC interacts with the m
On Tuesday 09 August 2016 05:03 PM, Mark Brown wrote:
> On Tue, Aug 09, 2016 at 04:33:11PM +0530, Vignesh R wrote:
>
>> +static int ti_qspi_map_buf(struct ti_qspi *qspi, void *buf,
>> + unsigned int len, struct sg_table *sgt)
>> +{
>> +unsigned int max_seg_size =
>> +
If a device tree specifies a preferred device for kernel console output
via the stdout-path or linux,stdout-path chosen node properties or the
stdout alias then the kernel ought to honor it & output the kernel
console to that device. As it stands, this isn't the case. Whilst we
parse the stdout-pat
On Mon, 08 Aug 2016, Keerthy wrote:
> The lp873x series of PMICs have a bunch of regulators and a couple
> of GPO(General Purpose Outputs).
> Add information for the MFD and regulator drivers.
>
> Acked-by: Rob Herring
> Signed-off-by: Keerthy
These should be in chronological order. Rob could
On Mon, 08 Aug 2016, Steve Twiss wrote:
> From: Steve Twiss
>
> Remove incorrect e-mail addresses from the copyright header and
> MODULE_AUTHOR() macro. These e-mail addresses are no longer in use.
>
> The author names have not been changed, only the e-mail addresses have
> been deleted from th
On 09/08/16 13:32, Salah Triki wrote:
> Fixing jornal to Journal.
>
> Signed-off-by: Salah Triki
> ---
> fs/befs/befs.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/befs/befs.h b/fs/befs/befs.h
> index 511d16d..55f3ea2 100644
> --- a/fs/befs/befs.h
> +++ b/fs/befs
On Mon, 08 Aug 2016, loic pallardy wrote:
> Hi Lee,
>
> After splitting this patch in 2, it may be good to add a debugfs entry to
> display current rsc associated to one rproc.
Happy to take suggestions to add functionality, but I would like to
prevent *this* set from suffering from feature cree
On Mon, 08 Aug 2016, loic pallardy wrote:
> Hi Lee
>
> On 08/04/2016 11:21 AM, Lee Jones wrote:
> > Most of the new resource table handling function are now in place, so
> > it's time to put it all together. Once new resource table information
> > has been requested, the structures will be held
The patch
ASoC: lpass-platform: don't use snd_soc_pcm_set_drvdata()
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
The patch
regmap: Add a function to check if a regmap register is cached
has been applied to the regmap tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
ASoC: remove snd_soc_pcm_set/get_drvdata()
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) and sent to Linu
On Tue, 9 Aug 2016, Alexander Shishkin wrote:
> Awesome, I'll have a look. Can you tell it it was messing around with
> intel_bts driver from the fuzzer log?
the fuzzer is messing around with the aux buffer, but this particular bug
triggered quickly so I can't easily tell if this particular bug
On 8/9/2016 4:54 AM, Leon Romanovsky wrote:
> On Mon, Aug 8, 2016 at 6:37 PM, Doug Ledford wrote:
>> On 8/7/2016 9:58 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> With Linus' tree, today's linux-next build (powerpc allyesconfig) failed
>>> like this:
>>>
>>> drivers/infiniband/sw/built-in.o:(.o
On Thu, Aug 04, 2016 at 06:44:09PM +0200, Peter Zijlstra wrote:
> On Thu, Jul 28, 2016 at 04:33:34PM -0700, Davidlohr Bueso wrote:
> > Hi,
> >
> > I'm resending Sebastian's sysv msg queue use of wake_qs but updated
> > to the last observations I need wrt the need of explicit barriers
> > after rem
The patch
regmap: debugfs: Add support for dumping write only device registers
has been applied to the regmap tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the ne
On Mon 2016-08-08 12:03:38, Chris Metcalf wrote:
> When doing an nmi backtrace of many cores, most of which are idle,
> the output is a little overwhelming and very uninformative. Suppress
> messages for cpus that are idling when they are interrupted and just
> emit one line, "NMI backtrace for N
Hey,
Op 08-08-16 om 23:03 schreef Lyude:
> Since the watermark calculations for Skylake are still broken, we're apt
> to hitting underruns very easily under multi-monitor configurations.
> While it would be lovely if this was fixed, it's not. Another problem
> that's been coming from this however,
SEAD3 is now using the generic syscon & regmap based register-bit-led
driver, so remove the unused custom SEAD3 LED driver.
Signed-off-by: Paul Burton
---
drivers/leds/Kconfig | 10 --
drivers/leds/Makefile | 1 -
drivers/leds/leds-sead3.c | 78
Probe the img-ascii-lcd driver using device tree in order to display a
message on the SEAD3 board's LCD display, and remove the platform code
that was formerly performing this function. This removes more platform
code and moves SEAD3 further towards being entirely DT-based.
Signed-off-by: Paul Bur
The 2 line * 16 character LCD display on the SEAD3 board has no real use
as a framebuffer device. It's far too small to produce any meaningful
output if used as the kernel console, SEAD3 is a development board that
will essentially always have a far more useful UART connection & the
code in sead3-d
The SEAD3 board defines a custom implementation of read_persistent_clock
which does exactly the same dummy operation as the generic weak version.
Remove the not really implemented custom version.
Signed-off-by: Paul Burton
---
arch/mips/mti-sead3/sead3-time.c | 6 --
1 file changed, 6 dele
Remove the custom platform code to restart when instructed to power off,
instead relying upon the generic restart-poweroff driver probed via DT
to do the same thing.
Remove also the halt implementation, which is incorrect. The generic
MIPS version will hang the system as halt should.
Signed-off-b
Add documentation for a devicetree binding for the simple ASCII LCD
displays found on development boards such as the MIPS Boston, MIPS Malta
& MIPS SEAD3 from Imagination Technologies.
Signed-off-by: Paul Burton
---
.../devicetree/bindings/auxdisplay/img-ascii-lcd.txt| 17 +
Probe a driver for the PLED & FLED LEDs found on the SEAD3 board using
the register-bit-led driver via device tree, rather than a custom driver
via platform code. Enable support for the register-bit-led driver & its
prerequisite syscon in sead3_defconfig.
Signed-off-by: Paul Burton
---
arch/mip
Parse the memsize argument provided by the bootloader in the DT shim
code, allowing the user to override it on the command line. This places
all of the DT manipulation code into sead3-dtshim.c.
Signed-off-by: Paul Burton
---
arch/mips/mti-sead3/sead3-dtshim.c | 72 ++
The SEAD3 board no longer uses the cobalt_lcdfb driver, so remove the
SEAD3-specific code from it.
Signed-off-by: Paul Burton
---
drivers/video/fbdev/Kconfig| 2 +-
drivers/video/fbdev/cobalt_lcdfb.c | 42 --
2 files changed, 1 insertion(+), 43 delet
On Mon, Aug 08, 2016 at 03:21:20PM +0100, Luis de Bethencourt wrote:
> befs_btree_find(), the only caller of befs_find_key(), only cares about if
> the return from that function is BEFS_BT_MATCH or not. It never uses the
> partial match given with BEFS_BT_PARMATCH. Make the overflow return clearer
Remove the SEAD3 implementation of _machine_restart & instead make use
of the generic syscon-reboot driver probed via device tree.
Signed-off-by: Paul Burton
---
arch/mips/boot/dts/mti/sead3.dts | 12
arch/mips/configs/sead3_defconfig | 3 ++-
arch/mips/mti-sead3/sead3-reset.c |
Add a driver for simple ASCII LCD displays found on the MIPS Boston,
Malta & SEAD3 development boards. The Boston display is an independent
memory mapped device with a simple memory mapped 8 byte register space
containing the 8 ASCII characters to display. The Malta display is
exposed as part of th
On 09/08/16 13:32, Salah Triki wrote:
> flags field records the superblock state, so check if it is equal to
> BEFS_DIRTY.
>
> Signed-off-by: Salah Triki
> ---
> fs/befs/super.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/befs/super.c b/fs/befs/super.c
> index 5a
Now that the SEAD3 board is probing the EHCI controller using device
tree, remove the non-DT support from the probe function.
Signed-off-by: Paul Burton
---
drivers/usb/host/ehci-sead3.c | 16
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/drivers/usb/host/ehci-
Probe the SEAD3 EHCI controller using device tree rather than platform
code, in order to reduce the amount of the latter.
Now that no devices probed from platform code require interrupts, remove
the retrieval of the IRQ domain & sead3int.h.
Signed-off-by: Paul Burton
---
arch/mips/boot/dts/mti
Probe the UARTs on SEAD3 boards using device tree rather than platform
code, in order to reduce the amount of the latter. This requires that
CONFIG_SERIAL_OF_PLATFORM be enabled, so enable it in sead3_defconfig.
The SEAD3 DT shim code is extended to read bootloader environment
variables to determin
Probe the CPU interrupt controller & optional Global Interrupt
Controller (GIC) using devicetree rather than platform code. Because the
bootloader on SEAD3 does not provide a device tree to the kernel & the
device tree is always built in, we patch out the GIC node during boot if
we detect that a GI
On Tue, 2016-08-09 at 15:19 +1000, Balbir Singh wrote:
>
> On 04/08/16 22:24, Mimi Zohar wrote:
> > The TPM PCRs are only reset on a hard reboot. In order to validate a
> > TPM's quote after a soft reboot (eg. kexec -e), the IMA measurement list
> > of the running kernel must be saved and then re
On Mon 2016-08-08 12:03:36, Chris Metcalf wrote:
> Currently on arm there is code that checks whether it should call
> dump_stack() explicitly, to avoid trying to raise an NMI when the
> current context is not preemptible by the backtrace IPI. Similarly,
> the forthcoming arch/tile support uses an
Introduce support for probing the SEAD3 EHCI driver using device tree.
Signed-off-by: Paul Burton
---
drivers/usb/host/ehci-sead3.c | 29 +++--
1 file changed, 23 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/host/ehci-sead3.c b/drivers/usb/host/ehci-sead3.c
in
The newly introduced shmem_huge_enabled() function has two definitions,
but neither of them is visible if CONFIG_SYSFS is disabled, leading
to a build error:
mm/khugepaged.o: In function `khugepaged':
khugepaged.c:(.text.khugepaged+0x3ca): undefined reference to
`shmem_huge_enabled'
This changes
Probe the smsc911x ethernet controller using device tree rather than
platform code, reducing the amount of the latter.
Signed-off-by: Paul Burton
---
arch/mips/boot/dts/mti/sead3.dts | 12 ++
arch/mips/include/asm/mips-boards/sead3int.h | 2 --
arch/mips/mti-sead3/sead3-dts
Probe the system parallel flash using device tree rather than platform
code, in order to reduce the amount of the latter.
Signed-off-by: Paul Burton
---
arch/mips/boot/dts/mti/sead3.dts | 17 +
arch/mips/mti-sead3/sead3-platform.c | 37
2
Stop selecting SYS_HAS_EARLY_PRINTK & remove the custom support for
early output to the ns16550a UARTs, instead relying upon generic
ns16550a earlycon support. This reduces the amount of platform code
required for SEAD3 without losing any functionality.
Signed-off-by: Paul Burton
---
arch/mips/
Split the obj-y entries for SEAD3 onto a line each, so that they're more
independent & can be modified more clearly by later commits.
Signed-off-by: Paul Burton
---
arch/mips/mti-sead3/Makefile | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/arch/mips/mti-sead3/M
Although the SEAD3 board has already made some minimal use of device
tree, until now most peripherals have been left probed by platform code.
This series converts all SEAD3 peripherals to instead be probed from
device tree. The amount of platform code is significantly reduced
leaving SEAD3 primed
On Mon 2016-08-08 12:03:35, Chris Metcalf wrote:
> Currently you can only request a backtrace of either all cpus, or
> all cpus but yourself. It can also be helpful to request a remote
> backtrace of a single cpu, and since we want that, the logical
> extension is to support a cpumask as the under
In page_remove_file_rmap(.) we have the following check:
VM_BUG_ON_PAGE(compound && !PageTransHuge(page), page);
This is meant to check for either HugeTLB pages or THP when a compound
page is passed in.
Unfortunately, if one disables CONFIG_TRANSPARENT_HUGEPAGE, then
PageTransHuge(.) will alway
flags field records the superblock state, so check if it is equal to
BEFS_DIRTY.
Signed-off-by: Salah Triki
---
fs/befs/super.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/befs/super.c b/fs/befs/super.c
index 5ab75e8..79be409 100644
--- a/fs/befs/super.c
+++ b/fs/befs/
Fixing jornal to Journal.
Signed-off-by: Salah Triki
---
fs/befs/befs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/befs/befs.h b/fs/befs/befs.h
index 511d16d..55f3ea2 100644
--- a/fs/befs/befs.h
+++ b/fs/befs/befs.h
@@ -46,7 +46,7 @@ struct befs_sb_info {
/* S
flags field is usefull for validating the superblock state, so add this
field to befs_sb_info and read the state from the disk.
Signed-off-by: Salah Triki
---
fs/befs/befs.h | 3 +++
fs/befs/super.c | 2 ++
2 files changed, 5 insertions(+)
diff --git a/fs/befs/befs.h b/fs/befs/befs.h
index e0f
On 2016/8/5 22:04, zhongjiang wrote:
> From: zhong jiang
>
> when required_kernelcore decrease to zero, we should exit the loop in time.
> because It will waste time to scan the remainder node.
>
> Signed-off-by: zhong jiang
> ---
> mm/page_alloc.c | 10 +++---
> 1 file changed, 7 insertions
On Mon, 2016-08-08 at 11:48 -0400, robert.f...@collabora.com wrote:
> From: Robert Foss
>
> Implemented queued response handling. This queue is processed every time the
> WDM_READ flag is cleared.
>
> In case of a read error, userspace may not actually read the data, since the
> driver returns a
2016-08-09 17:32+0800, Yang Zhang:
> On 2016/8/9 2:16, Radim Krčmář wrote:
>> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
>> @@ -6995,16 +6982,21 @@ static int handle_vmon(struct kvm_vcpu *vcpu)
>> return 1;
>> }
>>
>> +if (cpu_has_vmx_msr_bitmap()) {
>> +
On 09/08/2016 at 14:03:35 +0200, Julia Lawall wrote :
>
>
> On Tue, 9 Aug 2016, Christophe JAILLET wrote:
>
> > It is likely that checking the result of 'pcf2123_write_reg' is expected
> > here.
> > Also fix a small style issue. The '{' at the beginning of the function
> > is misplaced.
>
> The
On Tue, 9 Aug 2016 10:16:00 +0200 (CEST)
Miroslav Benes wrote:
> I agree it is kind of shooting oneself in the foot bug, because explicit
> call to a sleeping function may not be the brightest thing to do. However
> I see two (closely related) issues with this.
>
> 1. It is a change in behavi
Am Dienstag, 9. August 2016, 13:36:17 schrieb Wolfram Sang:
> The core will do this for us now.
>
> Signed-off-by: Wolfram Sang
> ---
[...]
> diff --git a/drivers/i2c/busses/i2c-rk3x.c b/drivers/i2c/busses/i2c-rk3x.c
> index 2bc8b01153d619..3b87afe82f6394 100644
> --- a/drivers/i2c/busses/i2c-r
On Tue, Aug 09, 2016 at 01:22:30PM +0200, Thomas Gleixner wrote:
> From: Benedikt Spranger
>
> PCI and PCIBIOS probing only scans devices at function number 0/8/16/...
> Subdevices (e.g. multiqueue) have function numbers which are not a
> multiple of 8.
>
> Simple hypervisors (e.g. Jailhouse) pa
On Tue, 9 Aug 2016, Christophe JAILLET wrote:
> It is likely that checking the result of 'pcf2123_write_reg' is expected
> here.
> Also fix a small style issue. The '{' at the beginning of the function
> is misplaced.
They shouldn't be in the same patch. If you are wrong about the ret
issue, t
On 09.08.16 14:29, Grygorii Strashko wrote:
On 08/06/2016 01:48 PM, Ivan Khoronzhuk wrote:
No need to check number of handled packets, when in most cases (> 99%)
it's not 0. It can be 0 only in rare cases, even in this case
it's not bad to print just 0.
Signed-off-by: Ivan Khoronzhuk
---
dr
Kmemleak reports following false positive memory leaks for each sk
buffers allocated by CPSW (__netdev_alloc_skb_ip_align()) in
cpsw_ndo_open() and cpsw_rx_handler():
unreferenced object 0xea915000 (size 2048):
comm "systemd-network", pid 713, jiffies 4294938323 (age 102.180s)
hex dump (first
On Tue, Aug 9, 2016 at 5:23 AM, Rui Wang wrote:
> On Tuesday, Aug 9, 2016 4:23 AM, Bjorn Helgaas wrote:
>> On Sun, Jun 26, 2016 at 11:44:57AM +0800, Rui Wang wrote:
>> > v5: Remove #ifdef CONFIG_X86 from setup-bus.c, making it neutral to
>> archs.
>> > v4: Add comments explaining when to call acpi
On 09.08.16 14:34, Grygorii Strashko wrote:
On 08/06/2016 01:48 PM, Ivan Khoronzhuk wrote:
No need to check const slave num in runtime for every packet,
and ndev for slaves w/o ndev is anyway NULL. So remove redundant
check.
Signed-off-by: Ivan Khoronzhuk
---
drivers/net/ethernet/ti/cpsw.c
On 09/08/2016 at 13:58:27 +0200, Christophe JAILLET wrote :
> It is likely that checking the result of 'pcf2123_write_reg' is expected
> here.
> Also fix a small style issue. The '{' at the beginning of the function
> is misplaced.
>
> Fixes: 809b453b76e15 ("rtc: pcf2123: clean up writes to the rt
Hello Wolfram,
On Tue, Aug 09, 2016 at 01:36:17PM +0200, Wolfram Sang wrote:
> The core will do this for us now.
Would be nice to point out the relevant commit that changed the core in
the commit log.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König
It is likely that checking the result of 'pcf2123_write_reg' is expected
here.
Also fix a small style issue. The '{' at the beginning of the function
is misplaced.
Fixes: 809b453b76e15 ("rtc: pcf2123: clean up writes to the rtc chip")
Signed-off-by: Christophe JAILLET
---
drivers/rtc/rtc-pcf212
On Tue, Aug 09, 2016 at 06:30:03AM +, Pan, Miaoqing wrote:
> Agree with Jason's point, also understand Stephan's concern. The
> date rate can be roughly estimated by 'cat /dev/random |rngtest -c
> 1000', the average speed is .294Kibits/s. I will sent the patch
> to disable ath9k RNG by def
On Tue, Aug 9, 2016 at 11:23 AM, Jiri Kosina wrote:
> On Mon, 8 Aug 2016, Rafael J. Wysocki wrote:
>
>> From: Rafael J. Wysocki
>>
>> The low-level resume-from-hibernation code on x86-64 uses
>> kernel_ident_mapping_init() to create the temoprary identity mapping,
>> but that function assumes tha
Am 09.08.2016 um 08:10 schrieb Andreas Werner:
On Mon, Aug 08, 2016 at 04:35:34PM +0200, Wolfgang Grandegger wrote:
Am 08.08.2016 um 16:05 schrieb Andreas Werner:
On Mon, Aug 08, 2016 at 02:28:39PM +0200, Wolfgang Grandegger wrote:
---snip---
+
+ ndev = alloc_candev(sizeof(struct men_
On 08/09/2016 02:36 PM, Wolfram Sang wrote:
The core will do this for us now.
Signed-off-by: Wolfram Sang
---
For:
drivers/i2c/busses/i2c-davinci.c| 4 +---
drivers/i2c/busses/i2c-omap.c | 4 +---
Reviewed-by: Grygorii Strashko
--
regards,
-grygorii
Signed-off-by: Andre Przywara
---
.../devicetree/bindings/mailbox/arm-smc.txt| 53 ++
1 file changed, 53 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mailbox/arm-smc.txt
diff --git a/Documentation/devicetree/bindings/mailbox/arm-smc.txt
b/Docum
This mailbox driver implements a mailbox which signals transmitted data
via an ARM smc (secure monitor call) instruction. The mailbox receiver
is implemented in firmware and can synchronously return data when it
returns execution to the non-secure OS again.
An asynchronous receive path is not imple
Those two boards connect a microSD card slot to the MMC0 controller.
Add the dummy regulator and enable MMC0 to allow accessing the SD card.
The BananaPi M64 has an on-board eMMC chip connected to the MMC2
controller, but the existing MMC driver does not support this properly
yet, so keep this one
Support for variable frequency clocks is implemented in ARM Trusted
Firmware, which sits in SRAM and waits for SCPI requests.
Add the respective SMC mailbox node and a 512-byte chunk of SRAM to
allow SCPI calls to be handled by the firmware.
Signed-off-by: Andre Przywara
---
arch/arm64/boot/dts/
The MMC controllers in the Allwinner A64 SoC are somewhat compatible
with the versions used in other Allwinner SoCs.
Tell Linux about the three MMC clocks that the firmware implements and
add nodes to represent the MMC controllers.
The actual hardware is capable of new transfer modes, which the dri
Hi,
this is a proof-of-concept series to demonstrate the usage of firmware
driven clocks using the SCPI protocol for Allwinner SoCs.
This aims to replace the tricky and highly SoC specific clocks drivers
that every new Allwinner SoC seems to require.
The idea is to abstract the internal clock spec
601 - 700 of 900 matches
Mail list logo
