On 2017-10-03 12:49:19 [-0300], Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> diff --git a/drivers/infiniband/hw/hfi1/pio.c
> b/drivers/infiniband/hw/hfi1/pio.c
> index 615be68e40b3..3a30bde9a07b 100644
> --- a/drivers/infiniband/hw/hfi1/pio.c
> +++ b/drivers/infiniband/hw
On Mon 11 Sep 17:32 PDT 2017, fengl...@codeaurora.org wrote:
> From: Fenglin Wu
>
> GPIO is expected to be disabled iff PIN_CONFIG_BIAS_HIGH_IMPEDANCE is
> configured. Update is_enabled flag in config_set() so that it can
> reflect GPIO status correctly. Also modify EN_CTL register based on
> is
On 2017-10-03 12:49:20 [-0300], Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> The hfi1 driver calls request_threaded_irq with two parameters:
>
> handler = receive_context_interrupt;
> thread = receive_context_thread;
> request_threaded_irq(me->msix.vecto
On Thu, Oct 05, 2017 at 05:51:56PM +0200, Pali Rohár wrote:
> On Thursday 05 October 2017 17:42:14 Greg KH wrote:
> > > > > --- /dev/null
> > > > > +++ b/include/uapi/linux/wmi.h
> > > > > @@ -0,0 +1,10 @@
> > > > > +#ifndef _UAPI_LINUX_WMI_H
> > > > > +#define _UAPI_LINUX_WMI_H
> > > > > +
> > > >
> -Original Message-
> From: Greg KH [mailto:g...@kroah.com]
> Sent: Thursday, October 5, 2017 2:23 AM
> To: Limonciello, Mario
> Cc: dvh...@infradead.org; Andy Shevchenko ;
> LKML ; platform-driver-...@vger.kernel.org;
> Andy Lutomirski ; quasi...@google.com;
> pali.ro...@gmail.com; r...@
On 10/03, Jürg Billeter wrote:
>
> My use case is to provide a way for a process to spawn a child and
> ensure that no descendants survive when that child dies. Avoiding
> runaway processes is desirable in many situations. My motivation is
> very lightweight (nested) sandboxing (every process is
Does the patch below fix the warning for you?
--
>From 28aae7104425433d39e6142adcd5b88dc5b0ad5f Mon Sep 17 00:00:00 2001
From: Christoph Hellwig
Date: Thu, 5 Oct 2017 18:31:02 +0200
Subject: block: use DECLARE_COMPLETION_ONSTACK in submit_bio_wait
This way we get our lockdep annotations right in
On Thursday 05 October 2017 16:28:40 mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Greg KH [mailto:g...@kroah.com]
> > Sent: Thursday, October 5, 2017 2:23 AM
> > To: Limonciello, Mario
> > Cc: dvh...@infradead.org; Andy Shevchenko ;
> > LKML ; platform-driver-...@vger
> -Original Message-
> From: Greg KH [mailto:g...@kroah.com]
> Sent: Thursday, October 5, 2017 2:33 AM
> To: Limonciello, Mario
> Cc: dvh...@infradead.org; Andy Shevchenko ;
> LKML ; platform-driver-...@vger.kernel.org;
> Andy Lutomirski ; quasi...@google.com;
> pali.ro...@gmail.com; r...@
Hi Paul,
On Tue, Oct 03, 2017 at 12:11:10PM -0700, Paul E. McKenney wrote:
> On Fri, Sep 29, 2017 at 05:33:49PM +0100, Will Deacon wrote:
> > On Fri, Sep 29, 2017 at 09:29:39AM -0700, Paul E. McKenney wrote:
> > > On Fri, Sep 29, 2017 at 10:08:43AM +0100, Will Deacon wrote:
> > > > Ok, but where d
On 10/04, Michal Hocko wrote:
>
> On Wed 04-10-17 23:12:38, Baoquan He wrote:
> > if (total_size) {
> > total_size = ELF_PAGEALIGN(total_size);
> > - map_addr = vm_mmap(filep, addr, total_size, prot, flags, off);
> > - if (!BAD_ADDR(map_addr))
> > -
On Thu 05-10-17 10:54:01, Johannes Weiner wrote:
> On Thu, Oct 05, 2017 at 03:14:19PM +0200, Michal Hocko wrote:
> > On Wed 04-10-17 16:04:53, Johannes Weiner wrote:
> > [...]
> > > That will silently ignore what the user writes to the memory.oom_group
> > > control files across the system's cgroup
On Thu, Oct 05, 2017 at 06:16:23PM +0200, Thomas Gleixner wrote:
> On Thu, 5 Oct 2017, Julia Cartwright wrote:
>
> > On Thu, Oct 05, 2017 at 11:55:39AM -0400, Steven Rostedt wrote:
> > > On Thu, 5 Oct 2017 10:37:59 -0500
> > > Julia Cartwright wrote:
> > >
> > > > On Thu, Oct 05, 2017 at 05:27:3
On Thu, Oct 05, 2017 at 04:28:40PM +, mario.limoncie...@dell.com wrote:
> > -Original Message-
> > From: Greg KH [mailto:g...@kroah.com]
> > Sent: Thursday, October 5, 2017 2:23 AM
> > To: Limonciello, Mario
> > Cc: dvh...@infradead.org; Andy Shevchenko ;
> > LKML ; platform-driver-...
On 05/10/17 16:43, Ed Blake wrote:
> On 05/10/17 16:26, James Hogan wrote:
>> On Thu, Oct 05, 2017 at 03:48:53PM +0100, Ed Blake wrote:
>>> I'm not sure how this is supposed to work, but the issue seems to be
>>> that without this patch the parent irq isn't being masked. This is
>>> causing the pa
On Thu 05-10-17 18:33:20, Oleg Nesterov wrote:
> On 10/04, Michal Hocko wrote:
> >
> > On Wed 04-10-17 23:12:38, Baoquan He wrote:
> > > if (total_size) {
> > > total_size = ELF_PAGEALIGN(total_size);
> > > - map_addr = vm_mmap(filep, addr, total_size, prot, flags, off);
> > > -
Currently, RPMSG_VIRTIO can only be enabled if some other kconfig
option selects it. This does not allow it to be enabled for
virtualized systems where Virtio RPMSG is available over Virtio
MMIO or PCI transport.
This patch updates RPMSG_VIRTIO kconfig option so that we can
enable the VirtIO RPMSG
Hi John,
First, my apologies for calling it a "hack." I just went back and looked at the
commit history and this is first-class stuff... and you explained it very well
(including the NTP interaction) in the commit message. I'm pretty sure I
read this before, but I reckon most of it went over my he
On systems where multiple chassis are reset asynchronously, and thus
the TSC counters are started asynchronously, the offset needed to
convert to TSC to ART would be different. Disable ART in that case
and rely on the TSC counters to supply the accurate time.
Signed-off-by: Mike Travis
Reviewed-
Hi Thomas,
On Thu, Oct 5, 2017 at 4:01 AM, Thomas Gleixner wrote:
> > The SoC we use backs the monotonic clock (sched_clock_register()) with a
>
> Again. monotonic clock != sched clock. The clocksource which feeds the
> monotonic timekeeper clock is registered via clocksource_register() & al.
So
Add a flag to indicate and process that TSC counters are on chassis
that reset at different times during system startup. Therefore which
TSC ADJUST values should be zero is not predictable.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Russ Anderson
Reviewed-by: Andrew
If the TSC has already been determined to be unstable, then checking
TSC ADJUST values is a waste of time and generates unnecessary error
messages.
Signed-off-by: Mike Travis
Reviewed-by: Dimitri Sivanich
Reviewed-by: Russ Anderson
Reviewed-by: Peter Zijlstra
---
arch/x86/kernel/tsc_sync.c |
The UV BIOS goes to considerable effort to get the TSC synchronization
accurate across the entire system. Included in that are multiple chassis
that can have 32+ sockets. The architecture does support an external
high resolution clock to aid in maintaining this synchronization.
The resulting TS
Prior to the TSC ADJUST MSR being available, the method to set TSC's in
sync with each other naturally caused a small skew between cpu threads.
This was NOT a firmware bug at the time so introducing a whole avalanche
of alarming warning messages might cause unnecessary concern and customer
complain
Insert a check early in UV system startup that checks whether BIOS was
able to obtain satisfactory TSC Sync stability. If not, it usually
is caused by an error in the external TSC clock generation source.
In this case the best fallback is to use the builtin hardware RTC
as the kernel will not be a
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Thursday, October 5, 2017 11:28 AM
> To: Pali Rohár
> Cc: Limonciello, Mario ;
> gno...@lxorguk.ukuu.org.uk; dvh...@infradead.org;
> andy.shevche...@gmail.com; linux-kernel@vger.kernel.org; platform-driver-
>
The RPMSG_VIRTIO is now user selectable option so we explicitly
select it in multi_v7_defconfig. Till now RPMSG_VIRTIO was
selected by ST_REMOTEPROC=m in multi_v7_defconfig.
Signed-off-by: Anup Patel
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch
Em Thu, Oct 05, 2017 at 09:17:44AM -0500, Julia Cartwright escreveu:
> On Tue, Oct 03, 2017 at 12:49:19PM -0300, Arnaldo Carvalho de Melo wrote:
> > +++ b/drivers/infiniband/hw/hfi1/pio.c
> > @@ -1421,7 +1421,7 @@ struct pio_buf *sc_buffer_alloc(struct send_context
> > *sc, u32 dw_len,
> > /*
From: Paul Bolle
Date: Thu, 05 Oct 2017 09:58:56 +0200
> Hi Kees,
>
> On Wed, 2017-10-04 at 17:52 -0700, Kees Cook wrote:
>> Also uses kzmalloc to replace open-coded field assignments to NULL and zero.
>
> If I'm allowed to whine (chances that I'm allowed to do that are not so great
> as Dave t
On Tue, Oct 03, 2017 at 02:36:42AM -0400, Jon Masters wrote:
> On 09/29/2017 04:56 AM, Will Deacon wrote:
>
> > The full fix isn't just cosmetic; it's also addressing the wider problem
> > of unannotated racing page table accesses outside of the specific failure
> > case we've run into.
>
> Let u
Loading the pmd without holding the pmd_lock exposes us to races with
concurrent updaters of the page tables but, worse still, it also allows
the compiler to cache the pmd value in a register and reuse it later on,
even if we've performed a READ_ONCE in between and seen a more recent
value.
In the
On Thu, Oct 5, 2017 at 2:13 AM, Sebastian Ott wrote:
> On Wed, 4 Oct 2017, Kees Cook wrote:
>> In preparation for unconditionally passing the struct timer_list pointer to
>> all timer callbacks, switch to using the new timer_setup() and from_timer()
>> to pass the timer pointer explicitly.
>
>> -v
> -Original Message-
> From: Andy Shevchenko [mailto:andy.shevche...@gmail.com]
> Sent: Thursday, October 5, 2017 12:34 AM
> To: Limonciello, Mario
> Cc: dvh...@infradead.org; LKML ; Platform Driver
> ; Andy Lutomirski ;
> quasi...@google.com; Pali Rohár ; Rafael J. Wysocki
> ; mj...@googl
On Wed, Oct 4, 2017 at 2:14 PM, Rob Herring wrote:
> On Fri, Sep 22, 2017 at 03:24:11PM -0700, Tim Harvey wrote:
>> Signed-off-by: Tim Harvey
>
Hi Rob, thanks for the review!
I will add a commit message, vendor prefix to non-standard props, and
remove '_' in the next revision.
>
>> +
>> +Optio
On Thu, 5 Oct 2017, Kees Cook wrote:
> On Thu, Oct 5, 2017 at 2:13 AM, Sebastian Ott
> wrote:
> > On Wed, 4 Oct 2017, Kees Cook wrote:
> >> In preparation for unconditionally passing the struct timer_list pointer to
> >> all timer callbacks, switch to using the new timer_setup() and from_timer()
Two errors found their way into the timer callback conversions that
weren't noticed with x86 allmodconfig.
Reported-by: kernel test robot
Signed-off-by: Kees Cook
---
This should apply cleanly on top of tip/timers/core
---
drivers/hsi/clients/ssi_protocol.c | 2 +-
drivers/s390/net/lcs.c
On Wed, Oct 4, 2017 at 11:22 PM, Takashi Iwai wrote:
> On Thu, 05 Oct 2017 02:53:36 +0200,
> Kees Cook wrote:
>>
>> In preparation for unconditionally passing the struct timer_list pointer to
>> all timer callbacks, switch to using the new timer_setup() and from_timer()
>> to pass the timer pointe
On Thu, 05 Oct 2017 19:17:16 +0200,
Kees Cook wrote:
>
> On Wed, Oct 4, 2017 at 11:22 PM, Takashi Iwai wrote:
> > On Thu, 05 Oct 2017 02:53:36 +0200,
> > Kees Cook wrote:
> >>
> >> In preparation for unconditionally passing the struct timer_list pointer to
> >> all timer callbacks, switch to usin
On 10/05, Arnd Bergmann wrote:
> The ARM allmodconfig build fails in linux-next, since one
Which version of linux-next? I merged a patch for this already
and pushed it out a day or two ago.
> clk interface was accidentally never exported but is now
> used by an mmc driver:
>
--
Qualcomm Innova
On Thu, Oct 05, 2017 at 02:47:15PM +, mario.limoncie...@dell.com wrote:
> > >
> > > So I believe it should be a mandatory runtime dependency due to needing
> > > the symbol dell_wmi_get_interface_version. Depmod should be handling
> > > this then no?
> >
> > This was nagging me all night, and
On Wed, Oct 4, 2017 at 11:47 PM, Johannes Berg
wrote:
> On Wed, 2017-10-04 at 17:49 -0700, Kees Cook wrote:
>> In preparation for unconditionally passing the struct timer_list
>> pointer to all timer callbacks, switch to using the new timer_setup()
>> and from_timer() to pass the timer pointer exp
On Thu, Oct 5, 2017 at 12:49 AM, Christophe LEROY
wrote:
>
>
> Le 05/10/2017 à 05:45, Kees Cook a écrit :
>>
>> When available, CONFIG_KERNEL_RWX should be default-enabled.
>
>
> On PPC32, this option implies deactivating BATs and/or LTLB mapping of the
> linear kernel address space, hence a signi
On 10/05, Viresh Kumar wrote:
> The routine is named incorrectly since the first attempt as there is
> nothing like a put_opp() helper. We wanted to unregister the set_opp()
> helper here and so it should rather be named as
> dev_pm_opp_unregister_set_opp_helper().
>
> Signed-off-by: Viresh Kumar
> -Original Message-
> From: Darren Hart [mailto:dvh...@infradead.org]
> Sent: Thursday, October 5, 2017 12:22 PM
> To: Limonciello, Mario
> Cc: andy.shevche...@gmail.com; linux-kernel@vger.kernel.org; platform-
> driver-...@vger.kernel.org; l...@kernel.org; quasi...@google.com;
> pali.ro.
On Thu, Oct 5, 2017 at 6:45 AM, Joonas Lahtinen
wrote:
> On Wed, 2017-10-04 at 17:54 -0700, Kees Cook wrote:
>> In preparation for unconditionally passing the struct timer_list pointer to
>> all timer callbacks, switch to using the new timer_setup() and from_timer()
>> to pass the timer pointer ex
Hi Alex,
> -Original Message-
> From: Alexandre TORGUE
> Sent: Thursday, October 05, 2017 9:02 AM
> To: Vikas MANOCHA ; linux-kernel@vger.kernel.org
> Cc: Patrice CHOTARD
> Subject: Re: [PATCH 0/3] Arm: dts: stm32: remove extra compatible uart string
>
> Hi Vikas
>
>
> On 09/29/2017 12
On Thu, 2017-10-05 at 11:41 +0200, Borislav Petkov wrote:
> On Tue, Oct 03, 2017 at 08:54:09PM -0700, Ricardo Neri wrote:
> >
> > Even though memory addresses are unsigned, the operands used to compute the
> > effective address do have a sign. This is true for ModRM.rm, SIB.base,
> > SIB.index as
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly. This requires adding a pointer back
to the sta_info since container_of() can't resolve the sta_info.
Cc: Joh
On Thu, Oct 05, 2017 at 06:26:28PM +0200, Greg KH wrote:
> On Thu, Oct 05, 2017 at 05:51:56PM +0200, Pali Rohár wrote:
> > On Thursday 05 October 2017 17:42:14 Greg KH wrote:
> > > > > > --- /dev/null
> > > > > > +++ b/include/uapi/linux/wmi.h
> > > > > > @@ -0,0 +1,10 @@
> > > > > > +#ifndef _UAPI
This is still spitting:
lib/dlock-list.c: In function âcpu2idx_initâ:
lib/dlock-list.c:75:16: error: incompatible types when assigning to type
âcpumask_var_tâ from type âstruct cpumask *â
sibling_mask = topology_sibling_cpumask(cpu);
^
lib/dlock-list.c:76:7: warning:
On Thu, Oct 05, 2017 at 05:11:15PM +0200, Wolfram Sang wrote:
>
> > Sorry for the delay. Looks all good to me (as I'd expect from Gunter...)
> >
> > Reviewed-by: Jean Delvare
>
> Thanks, Jean!
>
> Guenter: I will queue it to for-current, when I am back home. Does it
> need a stable tag?
>
I w
Hi Marc,
On 10/05/2017 05:43 AM, Marc Zyngier wrote:
> On 20/09/17 04:21, Shanker Donthineni wrote:
>> A new feature Range Selector (RS) has been added to GIC specification
>> in order to support more than 16 CPUs at affinity level 0. New fields
>> are introduced in SGI system registers (ICC_SGI0R
On Thu, Oct 5, 2017 at 7:56 AM, Jens Axboe wrote:
> On 10/04/2017 06:49 PM, Kees Cook wrote:
>> In preparation for unconditionally passing the struct timer_list pointer to
>> all timer callbacks, switch to using the new timer_setup() and from_timer()
>> to pass the timer pointer explicitly.
>>
>>
On Thu, 5 Oct 2017, Christoph Hellwig wrote:
> On Wed, Oct 04, 2017 at 04:47:52PM -0400, Nicolas Pitre wrote:
> > The only downside so far is the lack of visibility from user space to
> > confirm it actually works as intended. With the vma splitting approach
> > you clearly see what gets directl
On Mon, Oct 02, 2017 at 09:33:12PM -0400, Jérémy Lefaure wrote:
> On Mon, 2 Oct 2017 15:22:24 -0400
> bfie...@fieldses.org (J. Bruce Fields) wrote:
>
> > Mainly I'd just like to know which you're asking for. Do you want me to
> > apply this, or to ACK it so someone else can? If it's sent as a se
On Thu, Oct 05, 2017 at 03:12:46PM +, mario.limoncie...@dell.com wrote:
> > > diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
> > > index f0b97cb8e449..ef597f440d2e 100644
> > > --- a/drivers/platform/x86/Kconfig
> > > +++ b/drivers/platform/x86/Kconfig
> > > @@ -93,13
acme/linux into perf/urgent
(2017-09-29 19:31:46 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-urgent-for-mingo-4.14-20171005
for you to fetch changes up to c1fbc0cf81f1c464f5fda322c1104d4bb1da6711:
perf callchain: Compar
From: Ravi Bangoria
Two functions from different binaries can have same start address. Thus,
comparing only start address in match_chain() leads to inconsistent
callchains. Fix this by adding a check for dsos as well.
Ex, https://www.spinics.net/lists/linux-perf-users/msg04067.html
Reported-by:
On Thu, Oct 5, 2017 at 5:27 PM, Hans de Goede wrote:
> Hi,
>
> On 05-10-17 16:23, Andy Shevchenko wrote:
>>
>> On Thu, Oct 5, 2017 at 5:20 PM, Hans de Goede wrote:
>>>
>>> It seems that the WMI GUID used by the PEAQ 2-in-1 WMI hotkeys is not
>>> as unique as a GUID should be and is used on some o
On 05/10/17 18:49, Shanker Donthineni wrote:
> Hi Marc,
>
> On 10/05/2017 05:43 AM, Marc Zyngier wrote:
>> On 20/09/17 04:21, Shanker Donthineni wrote:
>>> A new feature Range Selector (RS) has been added to GIC specification
>>> in order to support more than 16 CPUs at affinity level 0. New field
On Thu, 2017-10-05 at 10:07 +0300, Gilad Ben-Yossef wrote:
> On Wed, Oct 4, 2017 at 10:12 PM, wrote:
> > There is no need to create a local pointer variable "dev" and
> > pass it various API's, instead use plat_dev which is enumerated
> > by platform core on successful probe.
[]
> I'm sorry but I
2017-10-04 12:28+0200, Arnd Bergmann:
> The rework of the posted interrupt handling broke building without
> support for the local APIC:
>
> ERROR: "boot_cpu_physical_apicid" [arch/x86/kvm/kvm-intel.ko] undefined!
>
> That configuration is probably not particularly useful anyway, so
> we can avoi
Gabriel,
On Thu, 5 Oct 2017, Gabriel Beddingfield wrote:
> On Thu, Oct 5, 2017 at 4:01 AM, Thomas Gleixner wrote:
> > i.e. the 32bit rollover of the clocksource. So, if the clocksource->read()
> > function returns a full 64bit counter value, then it must have protection
> > against observing the
On 10/05/2017 01:40 PM, Davidlohr Bueso wrote:
> This is still spitting:
>
> lib/dlock-list.c: In function ‘cpu2idx_init’:
> lib/dlock-list.c:75:16: error: incompatible types when assigning to
> type ‘cpumask_var_t’ from type ‘struct cpumask *’
> sibling_mask = topology_sibling_cpumas
2017-10-01 21:42 GMT+09:00 Julia Lawall :
> This semantic patch detects duplicate arrays declared using BQ27XXX_DATA
> within a single structure. It is currently specific to the file
> drivers/power/supply/bq27xxx_battery.c.
>
> Signed-off-by: Julia Lawall
>
> ---
Applied to linux-kbuild/misc.
T
On Thu, Oct 05, 2017 at 08:52:33PM +0530, Himanshu Jha wrote:
> There are various instances where a function used in file say for eg
> int func_align (void* a)
> is used and it is defined in align.h
> But many files don't *directly* include align.h and rather include
> any other header which includ
Hi,
On 05-10-17 19:59, Andy Shevchenko wrote:
On Thu, Oct 5, 2017 at 5:27 PM, Hans de Goede wrote:
Hi,
On 05-10-17 16:23, Andy Shevchenko wrote:
On Thu, Oct 5, 2017 at 5:20 PM, Hans de Goede wrote:
It seems that the WMI GUID used by the PEAQ 2-in-1 WMI hotkeys is not
as unique as a GUID
Hi All,
This is a resend with Kai Heng Feng added to the Cc. Kai can you please
test this patch. This patch replaces yours, as many devices seem to be
affected so a whitelist is the better approach here.
Regards,
Hans
It seems that the WMI GUID used by the PEAQ 2-in-1 WMI hotkeys is not
as unique as a GUID should be and is used on some other devices too.
This is causing spurious key-press reports on these other devices.
This commits adds a DMI check to the PEAQ 2-in-1 WMI hotkeys driver to
ensure that it is ac
Like other Plantronics devices, P610 does not support sample
rate reading. Apply sample rate quirk to it.
BugLink: https://bugs.launchpad.net/bugs/1719853
Signed-off-by: Kai-Heng Feng
---
sound/usb/quirks.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/usb/quirks.c b/sound/usb/quirk
2017-10-04 03:08+, Jeremy Cline:
> Make kvm_stat support Python 3 by changing the use of "print" to a
> function rather than a statement, switching from "iteritems" and
> "iterkeys" (removed in Python 3) to "items" and "keys" respectively,
> and decoding bytes to strings when dealing with text.
mempool_destroy() already checks for a NULL value being passed in, this
eliminates duplicate checks.
This was caught by running make coccicheck M=block/ on linus' tree on commit
77ede3a014a32746002f7889211f0cecf4803163 (current head as of this patch).
Signed-off-by: Tim Hansen
---
block/bio-i
erf-urgent-for-mingo-4.14-20170928' of
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent
> (2017-09-29 19:31:46 +0200)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
> tags/perf-ur
On Thu, Oct 5, 2017 at 9:04 PM, Hans de Goede wrote:
> On 05-10-17 19:59, Andy Shevchenko wrote:
>> On Thu, Oct 5, 2017 at 5:27 PM, Hans de Goede wrote:
>> ... however, the patch can't be dropped.
>>
>> Either me, or you in v2 need to revert it. Tell me what you prefer here.
> Isn't the whole p
Counters are IIO devices that are exposed via a generic counter
interface consisting of one or more counter signals (IIO_SIGNAL) linked
to one or more counter values (IIO_COUNT).
This patch introduces the IIO_SIGNAL constant which represents a counter
device signal line. Additionally, a new "count
There have been some significant implementation changes for this version
of the patchset. Here's a brief summary of the updates:
- Inline comments throughout the industrial-counter.c file; this
should help clarify some of the code and aid in the review of the
system architecture
- Simplif
This patch introduces the IIO generic counter interface for supporting
counter devices. The generic counter interface serves as a catch-all to
enable rudimentary support for devices that qualify as counters. More
specific and apt counter interfaces may be developed on top of the
generic counter int
This patch adds standard documentation for the userspace sysfs
atrributes of the IIO Generic Counter Interface.
Signed-off-by: William Breathitt Gray
---
.../testing/sysfs-bus-iio-generic-counter-sysfs| 63 ++
1 file changed, 63 insertions(+)
create mode 100644
Document
2017-10-05 07:35-0700, Wanpeng Li:
> From: Wanpeng Li
>
> The description in the Intel SDM of how the divide configuration
> register is used: "The APIC timer frequency will be the processor's bus
> clock or core crystal clock frequency divided by the value specified in
> the divide configuration
This patch adds high-level documentation about the IIO Generic Counter
Interface.
Signed-off-by: William Breathitt Gray
---
Documentation/driver-api/iio/generic-counter.txt | 526 +++
1 file changed, 526 insertions(+)
create mode 100644 Documentation/driver-api/iio/generic-c
This patch introduces the dummy counter driver. The dummy counter driver
serves as a reference implementation of a driver that utilizes the
Generic Counter interface.
Writing individual '1' and '0' characters to the Signal attributes
allows a user to simulate a typical Counter Signal input stream
This patch adds support for the IIO generic counter interface to the
104-QUAD-8 driver. The existing 104-QUAD-8 device interface should not
be affected by this patch; all changes are intended as supplemental
additions as perceived by the user.
IIO Counter Signals are defined for all quadrature inp
On Thu, Oct 5, 2017 at 6:58 AM, Jozsef Kadlecsik
wrote:
> Hi,
>
> On Wed, 4 Oct 2017, Kees Cook wrote:
>
>> In preparation for unconditionally passing the struct timer_list pointer
>> to all timer callbacks, switch to using the new timer_setup() and
>> from_timer() to pass the timer pointer explic
Added functionality to read LPIT table, which provides:
- Sysfs interface to read residency counters via
/sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us
/sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us
Here the count "low_power_idle_cpu_residency_us" shows the ti
Commit-ID: c1fbc0cf81f1c464f5fda322c1104d4bb1da6711
Gitweb: https://git.kernel.org/tip/c1fbc0cf81f1c464f5fda322c1104d4bb1da6711
Author: Ravi Bangoria
AuthorDate: Thu, 5 Oct 2017 14:42:34 +0530
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 5 Oct 2017 10:52:54 -0300
perf callchain
On Thu, Oct 05, 2017 at 01:43:31PM +1100, Michael Ellerman wrote:
> Thomas Meyer writes:
> > On Tue, Oct 03, 2017 at 08:18:14PM +1100, Michael Ellerman wrote:
> ...
> >>
> >> I've switched it to using one of the toolchains from Free Electrons,
> >> which is built with glibc, and that seems to be
On Thu, Oct 5, 2017 at 9:04 PM, Hans de Goede wrote:
> It seems that the WMI GUID used by the PEAQ 2-in-1 WMI hotkeys is not
> as unique as a GUID should be and is used on some other devices too.
>
> This is causing spurious key-press reports on these other devices.
>
> This commits adds a DMI che
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer explicitly. This introduces a pointer back to the
struct ip_set, which is used instead of the struct timer_list .data fie
On Thu, Oct 05, 2017 at 06:25:14PM +0200, Peter Zijlstra wrote:
> On Thu, Oct 05, 2017 at 09:19:09AM -0700, Paul E. McKenney wrote:
> >
> > Yes, the ordering does need to be visible to uninvolved CPUs, so
> > release-acquire is not necessarily strong enough.
>
> Why? Because I'm not at all seeing
On Thu, Oct 5, 2017 at 6:02 PM, wrote:
>> > - if (strncmp(obj->string.pointer, "DELL WMI", 8) != 0)
>> > - dev_warn(&wdev->dev, "Dell descriptor buffer has invalid
>> > signature
>> (%8ph)\n",
>> > + if (strncmp(obj->string.pointer, "DELL WMI", 8) != 0) {
>> > +
On Thu, 05 Oct 2017 20:04:06 +0200,
Kai-Heng Feng wrote:
>
> Like other Plantronics devices, P610 does not support sample
> rate reading. Apply sample rate quirk to it.
>
> BugLink: https://bugs.launchpad.net/bugs/1719853
>
> Signed-off-by: Kai-Heng Feng
Hrm, maybe we should ignore all Plantro
Hello Thomas,
Thanks for your comments.
Thomas Gleixner writes:
> On Wed, 4 Oct 2017, Thiago Jung Bauermann wrote:
>
>> It turns out that not all paths calling arch_update_cpu_topology hold
>> cpu_hotplug_lock, but that's ok because those paths aren't supposed to race
>> with any concurrent ho
On Thu, 5 Oct 2017, Daniel Vetter wrote:
> On Thu, Oct 05, 2017 at 06:19:30PM +0200, Thomas Gleixner wrote:
> > On Thu, 5 Oct 2017, Daniel Vetter wrote:
> > > On Thu, Oct 05, 2017 at 05:23:20PM +0200, Thomas Gleixner wrote:
> > > > Aside of that, is it really required to use stomp_machine() for thi
On 10/05/2017 11:49 AM, Kees Cook wrote:
> On Thu, Oct 5, 2017 at 7:56 AM, Jens Axboe wrote:
>> On 10/04/2017 06:49 PM, Kees Cook wrote:
>>> In preparation for unconditionally passing the struct timer_list pointer to
>>> all timer callbacks, switch to using the new timer_setup() and from_timer()
>
On Tue, 3 Oct 2017, Frank Rowand wrote:
> On 10/03/17 11:46, Nicolas Pitre wrote:
> > On Tue, 3 Oct 2017, Rob Herring wrote:
> >
> >> For static DT usecases, we don't need the disabled nodes and can skip
> >> unflattening. This saves a significant amount of RAM in memory constrained
> >> cases. I
On 10/05/17 04:07, Johannes Berg wrote:
> On Thu, 2017-10-05 at 12:00 +0100, David Howells wrote:
>>
>> Only validly signed wifi databases may be use.
s/use/used/
> We don't even have this yet, and when we do, we want this to be the
> case for typical configurations regardless of lockdown.
--
The raid10 driver can't be built with clang since it uses a variable
length array in a structure (VLAIS):
drivers/md/raid10.c:4583:17: error: fields must have a constant size:
'variable length array in structure' extension will never be supported
Allocate the r10bio struct with kmalloc instead
On Thu, Oct 05, 2017 at 01:53:05PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Oct 05, 2017 at 09:17:44AM -0500, Julia Cartwright escreveu:
> > On Tue, Oct 03, 2017 at 12:49:19PM -0300, Arnaldo Carvalho de Melo wrote:
> > > +++ b/drivers/infiniband/hw/hfi1/pio.c
> > > @@ -1421,7 +1421,7 @@ str
The alt_max_short() macro in asm/alternative.h does not work as
intended, leading to nasty bugs. E.g. alt_max_short("1", "3")
evaluates to 3, but alt_max_short("3", "1") evaluates to 1 -- not
exactly the maximum of 1 and 3.
In fact, I had to learn it the hard way by crashing my kernel in not
so fu
compat_statfs64 structure has some 32-bit and some 64-bit fields, so
64d2ab32e "vfs: fix put_compat_statfs64() does not handle errors" fixed
32-bit overflow checks not being performed, but accidentally enabled
checks for f_files and f_ffree that are 64-bit and cannot have overflow.
Now checks for b
501 - 600 of 958 matches
Mail list logo
