Analog Devices ADG792A/G is a triple 4:1 mux.
Reviewed-by: Jonathan Cameron
Signed-off-by: Peter Rosin
---
drivers/mux/Kconfig | 12
drivers/mux/Makefile | 1 +
drivers/mux/mux-adg792a.c | 140 ++
3 files changed, 153 insertions(+)
Extend the inkern api with functions for reading and writing ext_info
of iio channels.
Acked-by: Jonathan Cameron
Signed-off-by: Peter Rosin
---
drivers/iio/inkern.c | 60
include/linux/iio/consumer.h | 37 +++
2 files
On Mon, Mar 27, 2017 at 04:14:25PM +0200, Benjamin Gaignard wrote:
>2017-03-27 15:47 GMT+02:00 William Breathitt Gray :
>> On Mon, Mar 27, 2017 at 11:43:23AM +0200, Benjamin Gaignard wrote:
>>>One of the features of STM32 trigger hardware block is a quadrature
>>>encoder that can counts up/down dep
Hi,
On Sun, Mar 26, 2017 at 08:34:23PM -0700, Tony Lindgren wrote:
> There's a funny typo where IRQ_NONE is used instead of IRQF_TRIGGER_NONE
> for request_threaded_irq(). Let's fix it before it gets copied elsewhere.
>
> Fixes: dd3bf50b35e3 ("rtc: cpcap: new rtc driver")
> Cc: Sebastian Reichel
Everything else is indented with two spaces, so fix the odd one out.
Acked-by: Jonathan Cameron
Signed-off-by: Peter Rosin
---
Documentation/driver-model/devres.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/driver-model/devres.txt
b/Documentation/driver-
On Fri, Mar 24, 2017 at 4:19 PM, Geert Uytterhoeven
wrote:
> Hi Andy,
>
> On Fri, Mar 24, 2017 at 3:29 PM, Andy Shevchenko
> wrote:
>> On Fri, 2017-03-24 at 15:19 +0100, Geert Uytterhoeven wrote:
>>> On Fri, Mar 24, 2017 at 3:06 PM, Andy Shevchenko
>>> wrote:
>>> > It looks like panel.c belongs
On Fri, 24 Mar 2017, Jacek Anaszewski wrote:
> On 03/24/2017 09:47 AM, Sebastian Reichel wrote:
> > This fixes compilation for files, that try to include the
> > cpcap header in alphabetically sorted #include lists.
> >
> > Acked-by: Pavel Machek
> > Acked-by: Tony Lindgren
> > Signed-off-by: Se
On Fri, Mar 24, 2017 at 04:53:01AM +0100, luca abeni wrote:
> From: Luca Abeni
>
> Instead of decreasing the runtime as "dq = -Uact dt" (eventually
> divided by the maximum utilization available for deadline tasks),
> decrease it as "dq = -(1 - Uinact) dt", where Uinact is the "inactive
> utiliza
On Fri, 24 Mar 2017, Daniel Thompson wrote:
> On 24/03/17 16:42, Daniel Thompson wrote:
> > On 22/03/17 17:21, Geert Uytterhoeven wrote:
> > > Commit 7613c922315e308a ("backlight: pwm_bl: Move the checks for initial
> > > power state to a separate function") not just moved some code, but made
> >
On Mon, 27 Mar 2017 11:55:52 +0200
Arnd Bergmann wrote:
> On Mon, Mar 27, 2017 at 11:25 AM, kbuild test robot wrote:
> > Hi Deepa,
> >
> > [auto build test WARNING on tip/perf/core]
> > [also build test WARNING on v4.11-rc4 next-20170327]
> > [if your patch
Hi Jeffy,
> Currrently we are disabling this wake irq after receiving it. If this
> happens before we finish suspend and the pm event check is disabled,
> the system will continue suspending, and this irq would not work again.
>
> We may need to abort system suspend to avoid that.
>
> Signed-off
Hi,
On 23/03/17 11:12, Byungchul Park wrote:
> When cpudl_find() returns any among free_cpus, the cpu might not be
> closer than others, considering sched domain. For example:
>
>this_cpu: 15
>free_cpus: 0, 1,..., 14 (== later_mask)
>best_cpu: 0
>
>topology:
>
>0 --+
>
On Mon, Mar 27, 2017 at 03:46:47PM +0200, Peter Rosin wrote:
> On 2017-03-27 15:06, Johan Hovold wrote:
> > On Mon, Mar 27, 2017 at 02:17:48PM +0200, Peter Rosin wrote:
> >> Comparing a size_t with less than zero is always false as size_t
> >> is unsigned. So, change the type of the variable to ssi
On Sat, Mar 25, 2017 at 12:31 AM, Oza Pawandeep wrote:
> it jumps to the parent node without examining the child node.
> also with that, it throws "no dma-ranges found for node"
> for pci dma-ranges.
>
> this patch fixes device node traversing for dma-ranges.
What's the DT look like that doesn't
This patch fix a minor coding style issue.
Signed-off-by: sfaragnaus
---
drivers/staging/xgifb/XGI_main_26.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/xgifb/XGI_main_26.c
b/drivers/staging/xgifb/XGI_main_26.c
index d938da3..b450c74 100644
--- a/drivers/staging/xgifb/XG
On 24/03/2017 19:22, Marc Zyngier wrote:
> You cannot directly use a pointer to a u32 in any of the bitmap
> operations. You need to copy the value to an unsigned long, and
> apply the bitmap op on that.
On my platform, find_first_zero_bit() resolves to
int _find_first_zero_bit_le(const void *
The display backend on sun5i shares the same interrupt line as the
display frontend. Add it.
Signed-off-by: Chen-Yu Tsai
---
This won't directly apply to old releases. We may want to backport
them though?
---
arch/arm/boot/dts/sun5i.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch
Hi Maxime,
As promised, here is the patch adding the interrupt line for the display
backend to the sun5i shared dtsi, and another one adding it to the device
tree bindings.
The display backend has an undocumented (in the user manual) interrupt
that, according to vendor code, is raised when the cu
* Bin Liu [170327 06:22]:
> On Mon, Mar 27, 2017 at 02:53:27PM +0200, Moreno Bartalucci wrote:
> > > Il giorno 25 mar 2017, alle ore 08:21, Lars Melin ha
> > > scritto:
> > >
> > >>
> > >> The usb device has been disconnected, why it still cares about VBUS
> > >> power?
> > >
> > > Morphing d
The display backend has an interrupt line. Add it to the device tree
binding.
Signed-off-by: Chen-Yu Tsai
---
Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/sunxi/sun4i-drm.txt
b/Docum
On Mon, 27 Mar 2017 14:38:16 +0200
Paolo Bonzini wrote:
> VFIO is better and everyone should have switched to it. If they
> haven't, they will now. :)
>
> Signed-off-by: Paolo Bonzini
> ---
> arch/x86/kvm/Kconfig| 12 -
> arch/x86/kvm/Makefile |2 -
> arch/x86/kvm/assigned
2017-03-27 15:55 GMT+02:00 William Breathitt Gray :
> On Mon, Mar 27, 2017 at 11:43:24AM +0200, Benjamin Gaignard wrote:
>>Device counting could be controlled by the level or the edges of
>>a trigger.
>>in_count0_enable_mode attibute allow to set the control mode.
>>
>>Signed-off-by: Benjamin Gaign
Hi Rob,
On 27/03/17 15:34, Rob Herring wrote:
> On Sat, Mar 25, 2017 at 12:31 AM, Oza Pawandeep wrote:
>> it jumps to the parent node without examining the child node.
>> also with that, it throws "no dma-ranges found for node"
>> for pci dma-ranges.
>>
>> this patch fixes device node traversing
On Mon, 27 Mar 2017, Mason wrote:
> On 24/03/2017 19:22, Marc Zyngier wrote:
>
> > You cannot directly use a pointer to a u32 in any of the bitmap
> > operations. You need to copy the value to an unsigned long, and
> > apply the bitmap op on that.
>
> On my platform, find_first_zero_bit() resolve
Hello,
I've got the following use-after-free report on
linux-next/65b2dc38291f9f27e5ec3b804d6eb3b5f79a3ce4.
==
BUG: KASAN: use-after-free in debug_spin_unlock
kernel/locking/spinlock_debug.c:97 [inline]
BUG: KASAN: use-after-free in
Hi Peter,
On Mon, 27 Mar 2017 16:03:41 +0200
Peter Zijlstra wrote:
> On Fri, Mar 24, 2017 at 04:53:02AM +0100, luca abeni wrote:
>
> > +static inline
> > +void __dl_update(struct dl_bw *dl_b, s64 bw)
> > +{
> > + struct root_domain *rd = container_of(dl_b, struct
> > root_domain, dl_bw);
> >
On Mon 27-03-17 12:36:17, kernel test robot wrote:
> FYI, we noticed the following commit:
>
> commit: 0ee0efcf7c7968fb045454f621b5681e94b2c288 ("fsnotify: Move queueing of
> mark for destruction into fsnotify_put_mark()")
> https://git.kernel.org/cgit/linux/kernel/git/jack/linux-fs.git for_testi
On Mon, Mar 27, 2017 at 4:16 PM, Paul E. McKenney
wrote:
> On Mon, Mar 27, 2017 at 02:36:35PM +0200, Dmitry Vyukov wrote:
>> On Tue, Mar 14, 2017 at 5:21 PM, Paul E. McKenney
>> wrote:
>> > On Tue, Mar 14, 2017 at 12:47:02AM -0700, Lance Roy wrote:
>> >> I am not sure how the rcu_scheduler_active
Hi Steve,
[auto build test WARNING on ljones-mfd/for-mfd-next]
[also build test WARNING on v4.11-rc4 next-20170327]
[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/Steve-Twiss/Documentation
gt; > [also build test WARNING on v4.11-rc4 next-20170327]
>> > [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/Deepa-Dinama
On x86-32, with CONFIG_FIRMWARE and multiple CPUs, if you enable
function graph tracing and then suspend to RAM, it will triple fault and
reboot when it resumes.
The first fault happens when booting a secondary CPU:
startup_32_smp()
load_ucode_ap()
prepare_ftrace_return()
ftrace_graph
Hello,
There’s three way to perform an invalid memory access :
The attempt to execute/jump at an invalid address.
The attempt to read at an invalid address.
The attempt to write at an invalid address.
Determining the execute case with rt_sigaction is easy : the last value
of eip match the valu
On Mon, 27 Mar 2017 16:26:33 +0200
Peter Zijlstra wrote:
> On Fri, Mar 24, 2017 at 04:53:01AM +0100, luca abeni wrote:
> > From: Luca Abeni
> >
> > Instead of decreasing the runtime as "dq = -Uact dt" (eventually
> > divided by the maximum utilization available for deadline tasks),
> > decrease
On Mon, 27 Mar 2017 13:28:28 +0530
Ravi Bangoria wrote:
> SDT marker argument is in N@OP format. N is the size of argument and
> OP is the actual assembly operand. OP is arch dependent component and
> hence it's parsing logic also should be placed under tools/perf/arch/.
>
> Signed-off-by: Ravi
Unless they are connected through unifying, they don't support it,
so remove one error in the logs.
Signed-off-by: Benjamin Tissoires
---
changes in v3:
- moved up in the series
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers
Register 0xB5 should be handled specially no matter what function is
used. This allows to retrieve the serial and the Quad ID from
hid-logitech-hidpp directly.
Signed-off-by: Benjamin Tissoires
---
changes in v3:
- fixed 0xb5 to handle any incoming parameters
no changes in v2
---
drivers/hid/
Unifying devices are different from others because they can probed
while not connected. So we need to talk to the receiver to get some
extra information like the device name and the serial.
Instead of having conditionals while attempting to read the device name
from HID++ 2.0, have a special init
This way, upower can add a simple udev rule to decide whether or not
it should use the internal unifying support or just the generic kernel
one.
Signed-off-by: Benjamin Tissoires
---
no changes in v3
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 20
1 file chang
Le lundi 27 mars 2017 à 10:45 +0200, Hans Verkuil a écrit :
> > > timestamp and sequence are only set for CAPTURE, not OUTPUT. Is
> > > that correct?
> >
> > Correct. I can add sequence for the OUTPUT queue too, but I have no
> > idea how that sequence is used by userspace.
>
> You set V4L2_BUF_F
Looks like all users don't care about a disconnect.
Simplify the various variant_connect() and put the connect state check
at the beginning.
For delayed input devices, make sure we go through all other connect
values (protocol, battery) before bailing out.
Signed-off-by: Benjamin Tissoires
---
The Solar Keyboard uses a different feature to report the battery level.
Signed-off-by: Benjamin Tissoires
---
changes in v3:
- fixed online status
changes in v2:
* update state according to lux information
* do not update Lux if the event does not contain lux information
---
drivers/hid/hid-
Better forwarding the device name, manufacturer and serial to upower.
Note that serial is still empty, it will be filled in a later patch
in this series.
Signed-off-by: Benjamin Tissoires
---
changes in v3:
- moved up in the series
changes in v2:
* model stripped of Logitech
* vendor Logitech
Do not pollute the quirks bits field which is public API
with elements that are queried from the device.
Move the 2 battery capabilities into the new field.
Signed-off-by: Benjamin Tissoires
---
new in v3
---
drivers/hid/hid-logitech-hidpp.c | 10 ++
1 file changed, 6 insertions(+), 4
Battery events are reported through HID++, so we need to be sure
the report ID is the HID++ one.
Without this, we might receive keyboard events that looks just like
battery events with wrong data and which will confuse user space.
Signed-off-by: Benjamin Tissoires
---
new in v3
---
drivers/hi
Hi,
this is finally a rework of the series that provides kernel power_supply
for hidpp devices.
This will allow upower to not handle those devices anymore and to have more
immediate reportng of the device to the system.
I have splitted the series to not support non unifying receivers here. I got
When a device reconnects, there is a high chance its power supply has
been changed (for a battery replacement for instance). Just forward
the battery state here.
Signed-off-by: Benjamin Tissoires
---
changes in v3:
- moved up in the series
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c
Also enable battery reporting for HID++ 1.0 devices through 2 registers:
0x07: battery status -> reports only 4 levels (critical, low, good, full)
0x0D: battery mileage -> reports true pourcentage
Signed-off-by: Benjamin Tissoires
---
changes in v3:
- differentiate between level and mileage
- b
Simple check to add, huge improvement :)
Signed-off-by: Benjamin Tissoires
---
no changes in v3
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-hidpp.c
index 4aaf237..1cda2
Dear Josh,
On 03/27/17 16:54, Josh Poimboeuf wrote:
On x86-32, with CONFIG_FIRMWARE and multiple CPUs, if you enable
function graph tracing and then suspend to RAM, it will triple fault and
reboot when it resumes.
The first fault happens when booting a secondary CPU:
startup_32_smp()
load_u
The creation of the power_supply should not be in a HID++ 2.0 specific
function.
Signed-off-by: Benjamin Tissoires
---
changes in v3:
- moved up in the series
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 94 ++--
1 file changed, 43 insertions(+),
From: Bastien Nocera
Without a scope defined, UPower assumes that the battery provides
power to the computer it's connected to, like a laptop battery or a UPS.
Tested-by: Peter Hutterer
Signed-off-by: Bastien Nocera
Signed-off-by: Benjamin Tissoires
---
no changes in v3
changes in v2:
* fi
The power_supply term for the percentage is capacity. Capacity level
can be given when non accurate mileage is provided by the device, so
better stick to the terms used in power_supply.
Signed-off-by: Benjamin Tissoires
---
new in v3
---
drivers/hid/hid-logitech-hidpp.c | 55 ++
When ONLINE isn't set, upower should ignore the battery capacity,
so there is no need to overload it with some random values.
Signed-off-by: Benjamin Tissoires
---
completely reworked in v3:
- store a online field in hidpp->battery to be able to fine control
the value
- provide POWER_SUPPLY_S
CAPACITY LEVEL allows to forward rough information on the battery mileage.
HID++ 2.0 devices will either report percentage or levels, so better
forwarding this information to the user space.
The M325 supports only 2 levels: 'Full' and 'Critical'. With mileage,
it will report either 90% or 5%, whic
hidpp->name can't be null.
Only HID++ 2.0 and above device supports the query.
Signed-off-by: Benjamin Tissoires
---
changes in v3:
- moved up in the series
new in v2
---
drivers/hid/hid-logitech-hidpp.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/driver
Or the device just answers a valid feature '0'.
Signed-off-by: Benjamin Tissoires
---
changes in v3:
- moved up in the series
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitec
On 27/03/2017 16:46, Dmitry Vyukov wrote:
>
> Paul McKenney writes:
>
> ===
> Hmmm... I am not seeing a call to cleanup_srcu_struct() for the
> ->track_srcu field of the kvm_page_track_notifier_head structure.
> Or is this structure immortal, so that it is never cleaned up?
> Or am I just blin
* Kishon Vijay Abraham I [170326 23:27]:
> On Thursday 23 March 2017 05:16 AM, Tony Lindgren wrote:
> > +static const struct phy_ops ops = {
> > + .owner = THIS_MODULE,
> > +};
>
> Given that this phy doesn't have any phy_ops, Is there a reason for
> registering
> this phy with the ph
Hi Boris,
On 03/24/2017 12:12 PM, Borislav Petkov wrote:
}
+static inline int __init early_set_memory_decrypted(void *addr,
+ unsigned long size)
+{
+ return 1;
return 1 when !CONFIG_AMD_MEM_ENCRYPT ?
The non-early var
From: Pablo Neira Ayuso
> Sent: 27 March 2017 13:08
> On Sat, Mar 25, 2017 at 06:19:47PM +0530, Arushi Singhal wrote:
> > This patch removes multiple assignments.
> > Done using coccinelle.
> > @@
> > identifier i1,i2;
> > constant c;
> > @@
> > - i1=i2=c;
> > + i1=c;
> > + i2=c;
>
> You have to e
On Tue, Mar 28, 2017 at 04:39:25PM +0800, Changpeng Liu wrote:
> Currently virtio-blk driver does not provide discard feature flag, so the
> filesystems which built on top of the block device will not send discard
> command. This is okay for HDD backend, but it will impact the performance
> for SSD
On 3/22/2017 10:53 AM, bod...@mellanox.com wrote:
From: Bodong Wang
Sometimes it is not desirable to probe the virtual functions after
SRIOV is enabled. This can save host side resource usage by VF
instances which would be eventually probed to VMs.
Add a new PCI sysfs interface "sriov_probe_vf
On Sat, Mar 25, 2017 at 12:31 AM, Oza Pawandeep wrote:
> it is possible that PCI device supports 64-bit DMA addressing,
> and thus it's driver sets device's dma_mask to DMA_BIT_MASK(64),
> however PCI host bridge may have limitations on the inbound
> transaction addressing. As an example, consider
On Mon, 27 Mar 2017 13:28:29 +0530
Ravi Bangoria wrote:
> SDT marker argument is in N@OP format. Here OP is arch dependent
> component. Add powerpc logic to parse OP and convert it to uprobe
> compatible format.
Looks good to me.
Acked-by: Masami Hiramatsu
BTW, using regex to parse this short
> > 2 --
> > 1 file changed, 2 deletions(-)
>
> Ugh, Alan, what's going on here, I thought you fixed this?
I sent you a patch that removed the arrays entirely and turned it into
a single string as well as removing the define. Not quite sure what
happened but I've resynched to -next and I'll send
Hello Dmitry,
On 03/23/2017 06:45 PM, Dmitry Torokhov wrote:
> On Thu, Mar 23, 2017 at 04:14:56PM -0300, Javier Martinez Canillas wrote:
>> Hello Dmitry,
>>
>> On 02/22/2017 11:40 AM, Javier Martinez Canillas wrote:
>>> The driver doesn't have a struct of_device_id table but supported devices
>>>
On 27/03/2017 16:46, Thomas Gleixner wrote:
> On Mon, 27 Mar 2017, Mason wrote:
>
>> On 24/03/2017 19:22, Marc Zyngier wrote:
>>
>>> You cannot directly use a pointer to a u32 in any of the bitmap
>>> operations. You need to copy the value to an unsigned long, and
>>> apply the bitmap op on that.
On 24/03/17 18:00, Christoffer Dall wrote:
On Mon, Mar 20, 2017 at 06:26:42PM +, Suzuki K Poulose wrote:
In order to perform an operation on a gpa range, the hyp iterates
the hyp ?
To be precise "the host" ?
over each page in a user memory slot for the given range. This is
inefficien
Both atmel-ebi and atmel-sdram are maintained as part of the Atmel ARM
SoCs.
Signed-off-by: Alexandre Belloni
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c45c02bc6082..6531d239db6b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -,6 +
Le 27/03/2017 à 17:21, Alexandre Belloni a écrit :
> Both atmel-ebi and atmel-sdram are maintained as part of the Atmel ARM
> SoCs.
>
> Signed-off-by: Alexandre Belloni
Acked-by: Nicolas Ferre
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAIN
On x86-32, with CONFIG_FIRMWARE and multiple CPUs, if you enable
function graph tracing and then suspend to RAM, it will triple fault and
reboot when it resumes.
The first fault happens when booting a secondary CPU:
startup_32_smp()
load_ucode_ap()
prepare_ftrace_return()
ftrace_graph
On 27/03/2017 16:42, Alex Williamson wrote:
> Yes, it's been deprecated since v4.2. I'd suggest also updating
> Documentation/virtual/kvm/api.txt.
Good point:
diff --git a/Documentation/virtual/kvm/api.txt
b/Documentation/virtual/kvm/api.txt
index fd106899afd1..9c886307268c 100644
--- a/Docum
On Mon, 27 Mar 2017 17:01:53 +0200
Paul Menzel wrote:
> > + /*
> > +* When resuming from suspend-to-ram, this function can be indirectly
> > +* called from early CPU startup code while the CPU is in real mode,
> > +* which would fail miserably. Make sure the stack pointer is a
> >
[+Al,Darren to comment on _DSD review process]
On Mon, Mar 27, 2017 at 12:24:45PM +, Gabriele Paoloni wrote:
> Hi Marc Many thanks for your comments
>
> > -Original Message-
> > From: linuxarm-boun...@huawei.com [mailto:linuxarm-boun...@huawei.com]
> > On Behalf Of Marc Zyngier
> > Se
On Mon, 27 Mar 2017 16:53:09 +0200
Arnd Bergmann wrote:
> > Actually, I believe that "%zd" will work. It's made to work with size_t
> > which is long long on 32 and long on 64.
>
> size_t is always 'long', not 'long long'. We have %pad for dma_addr_t
> which may be 'long' or 'long long', but
On Fri, Mar 24, 2017 at 02:47:09PM +0300, Kirill A. Shutemov wrote:
>
> From d2f416a3ee3e5dbb10e59d0b374d382fdc4ba082 Mon Sep 17 00:00:00 2001
> From: "Kirill A. Shutemov"
> Date: Fri, 24 Mar 2017 14:13:05 +0300
> Subject: [PATCH] mm: Fix false-positive VM_BUG_ON() in
> page_cache_{get,add}_spec
On Mon, Mar 27, 2017 at 4:45 PM, none wrote:
> Hello,
>
> There’s three way to perform an invalid memory access :
>
> The attempt to execute/jump at an invalid address.
> The attempt to read at an invalid address.
> The attempt to write at an invalid address.
>
> Determining the execute case with
On Wed, 22 Mar 2017 23:07:27 +0900
Masahiro Yamada wrote:
> This will be filled by nand_scan_ident() later.
>
> Signed-off-by: Masahiro Yamada
> ---
>
> Changes in v2: None
>
> drivers/mtd/nand/denali.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/mtd/nand/denali.c b/driv
Hi Nicolas,
2017-03-27 18:45 GMT+09:00 Nicolas Dichtel :
>> I wanted to leave comments/questions on 10/11,
>> but I could not find 10/11 in my mailbox. I do not know why.
> Note that you can download the mail from the kbuild patchwork, open it with
> your
> email client and do a reply ;-)
I too
On Mon, Mar 27, 2017 at 5:30 PM, Steven Rostedt wrote:
> On Mon, 27 Mar 2017 16:53:09 +0200
>> We could probably introduce a %pts format string for timespec64
>> and have that pretty-printed.
>
> Hmm, probably don't want a %p as that suggests its a pointer, which it
> should not be. Unless we pass
2017-03-27 21:20 GMT+09:00 Nicolas Dichtel :
>
>
> Patches #1 and #2 are just cleanup: some exported headers were still under
> a non-uapi directory. Patch #3 is a fix to avoid exporting a file that was
> not under an uapi directory.
> After these three patches, all exported headers are under an ua
On (03/26/17 22:47), Samuel Thibault wrote:
> commit bbeddf52adc1 ("printk: move braille console support into
> separate braille.[ch] files") introduced _braille_console_setup()
> to outline the braille initialization code. There was however some
> confusion over the value it was supposed to retur
This patch converts tpm_tis to use of the new tpm class ops
request_locality, and relinquish_locality.
With the move to using the callbacks, release_locality is changed so
that we now release the locality even if there is no request pending.
This required some changes to the tpm_tis_core_init cod
On Sat, Mar 25, 2017 at 12:52:58PM +0300, Ivan Safonov wrote:
> DIV_ROUND_UP is bit useful than series of "/" and "%" operations.
> Replace "/%" sequence with DIV_ROUND_UP macro.
>
> Signed-off-by: Ivan Safonov
Applied. Thanks.
-Bin.
> ---
> Changes in v2:
> - little style fix
>
> drivers/us
On Mon, 2017-03-27 at 15:37 +0200, Stefan Wahren wrote:
> In order to share common functions between QCA7000 SPI and UART
> protocol
> driver the qca_common needs to be a separate kernel module.
Maybe "qca_eth_common"? There are many things Qualcomm, slightly fewer
things Qualcomm Atheros, and "q
From: Kan Liang
Currently, there is no way to measure the time cost in System management
mode (SMM) by perf.
Intel perfmon supports FREEZE_WHILE_SMM bit in IA32_DEBUGCTL. Once it sets,
the PMU core counters will freeze on SMI handler. But it will not have an
effect on free running counters. E.g.
From: Kan Liang
Having msr_set/clear_bit on many cpus or given CPU can avoid extra
unnecessory IPIs and simplify MSR content manipulation, when it only
needs to flip a bit.
There is already msr_set/clear_bit, but missing the _on_cpu and _on_cpus
version.
Signed-off-by: Kan Liang
---
arch/x86/i
From: Kan Liang
Currently, the SMIs are visible to all performance counters. Because
many users want to measure everything including SMIs. But in some
cases, the SMI cycles should not be count. For example, to calculate
the cost of SMI itself. So a knob is needed.
When setting FREEZE_WHILE_SMM b
On 24/03/2017 19:47, Marc Zyngier wrote:
> On 23/03/17 17:03, Mason wrote:
>
>> On 23/03/2017 15:22, Marc Zyngier wrote:
>>
>>> On 23/03/17 13:05, Mason wrote:
>>>
+ writel_relaxed(status, pcie->msi_status); /* clear IRQs */
>>>
>>> Why isn't this your irq_ack method instead of open-coding i
- Original Message -
> From: "Fam Zheng"
> To: linux-kernel@vger.kernel.org
> Cc: "Martin K. Petersen" , f...@redhat.com,
> linux-s...@vger.kernel.org, "James E.J.
> Bottomley"
> Sent: Monday, March 27, 2017 10:18:31 AM
> Subject: [PATCH] sd: Consider max_xfer_blocks if opt_xfer_blocks
On Mon, 27 Mar 2017 17:35:13 +0200
Arnd Bergmann wrote:
> On Mon, Mar 27, 2017 at 5:30 PM, Steven Rostedt wrote:
> > On Mon, 27 Mar 2017 16:53:09 +0200
> >> We could probably introduce a %pts format string for timespec64
> >> and have that pretty-printed.
> >
> > Hmm, probably don't want a %
On Monday, March 13, 2017 10:05:09 PM CEST Alban wrote:
> The current binding only cover PCI devices so extend it for SoC devices.
>
> Most SoC platforms use an MTD partition for the calibration data
> instead of an EEPROM. The qca,no-eeprom property was added to allow
> loading the EEPROM content
On Thu, 23 Mar 2017 05:07:20 +0900
Masahiro Yamada wrote:
> Collect multi NAND fixups into a helper function instead of
> scattering them in denali_init().
>
> I am rewording the comment block to clearly explain what is called
> "multi device".
I will take the patch (and the next one too), but
On Mon, Mar 27, 2017 at 12:38 AM, Andrew Donnellan
wrote:
> On 01/02/17 07:24, Kees Cook wrote:
>>
>> From: Emese Revfy
>>
>> The kernel already has a mechanism to free up code and data memory that
>> is only used during kernel or module initialization. This plugin will
>> teach the compiler to
On Mon, Mar 27, 2017 at 04:56:51PM +0200, Luca Abeni wrote:
> > > +u64 grub_reclaim(u64 delta, struct rq *rq, u64 u)
> > > {
> > > + u64 u_act;
> > > +
> > > + if (rq->dl.this_bw - rq->dl.running_bw > (1 << 20) - u)
> > > + u_act = u;
> > > + else
> > > + u_act = (1 << 20) - rq->d
> Il giorno 27 mar 2017, alle ore 16:30, Tony Lindgren ha
> scritto:
>
> […]
> I wonder if the following test patch allows the mode changing
> devices to been properly found? Of course it's just for testing,
> and scanning for devices takes now 5 seconds.. But it might
> provide clues why musb
On Mon, 2017-03-27 at 16:59 +0200, Benjamin Tissoires wrote:
> Hi,
>
> this is finally a rework of the series that provides kernel
> power_supply
> for hidpp devices.
>
> This will allow upower to not handle those devices anymore and to
> have more
> immediate reportng of the device to the system
Às 7:19 AM de 3/23/2017, Niklas Cassel escreveu:
> On 03/22/2017 04:47 PM, Joao Pinto wrote:
>> Hi Niklas,
>>
>> Às 2:43 PM de 3/21/2017, Niklas Cassel escreveu:
>>> From: Niklas Cassel
>>>
>>> Fix the following crash, seen in dwc/pcie-artpec6.
>>>
>>> Unable to handle kernel NULL pointer derefe
On 03/27/2017 05:14 PM, Petr Mladek wrote:
On Mon 2017-03-20 13:03:00, Aleksey Makarov wrote:
[..]
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index fd752f0c8ef1..462036e7a767 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -1909,8 +1909,28 @@ static int
On 25/03/17 18:23, Leo Yan wrote:
Coresight includes debug module and usually the module connects with CPU
debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has
description for related info in "Part H: External Debug".
Chapter H7 "The Sample-based Profiling Extension" introduces
401 - 500 of 902 matches
Mail list logo
