Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc:
Code obtained from
https://raw.githubusercontent.com/mightybigcar/synaptics-rmi4/jf/drivers/input/rmi4/rmi_smbus.c
and updated to match upstream. And fixed to make it work.
Signed-off-by: Benjamin Tissoires
Signed-off-by: Andrew Duggan
---
Patch to add Standard SD Host Controller Interface compliant
Synopsys sdhci-dwc controller driver.
Signed-off-by: Prabu Thangamuthu
---
Change log v5:
-Updated review comments.
Change log v4:
-Updated review comments to optimize the code.
Change log v3:
The i801 chip can handle the Host Notify feature since ICH 3 as mentioned
in
http://www.intel.com/content/dam/doc/datasheet/82801ca-io-controller-hub-3-datasheet.pdf
Enable the functionality unconditionally and propagate the alert
on each notification.
With a T440s and a Synaptics touchpad that
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc:
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc:
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc: r...@linutronix.de
Cc: "Paul E. McKenney"
Cc: Arjan van de Ven
---
Code obtained from
https://raw.githubusercontent.com/mightybigcar/synaptics-rmi4/jf/drivers/input/rmi4/rmi_smbus.c
and updated to match upstream. And fixed to make it work.
Signed-off-by: Benjamin Tissoires
Signed-off-by: Andrew Duggan
---
new in v5
no changes in v6
changes in v7:
- fixed
Patch to add Standard SD Host Controller Interface compliant
Synopsys sdhci-dwc controller driver.
Signed-off-by: Prabu Thangamuthu
---
Change log v5:
-Updated review comments.
Change log v4:
-Updated review comments to optimize the code.
Change log v3:
-Removed unused
The i801 chip can handle the Host Notify feature since ICH 3 as mentioned
in
http://www.intel.com/content/dam/doc/datasheet/82801ca-io-controller-hub-3-datasheet.pdf
Enable the functionality unconditionally and propagate the alert
on each notification.
With a T440s and a Synaptics touchpad that
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc: r...@linutronix.de
Cc: "Paul E. McKenney"
Cc: Arjan van de Ven
---
drivers/tty/metag_da.c |
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc: r...@linutronix.de
Cc: "Paul E. McKenney"
Cc: Arjan van de Ven
---
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc:
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc: r...@linutronix.de
Cc: "Paul E. McKenney"
Cc: Arjan van de Ven
---
This is the third version of the timer wheel rework series. The previous
versions can be found here:
V1: http://lkml.kernel.org/r/20160613070440.950649...@linutronix.de
V2: http://lkml.kernel.org/r/20160617121134.417319...@linutronix.de
The series is also available in git:
This is the third version of the timer wheel rework series. The previous
versions can be found here:
V1: http://lkml.kernel.org/r/20160613070440.950649...@linutronix.de
V2: http://lkml.kernel.org/r/20160617121134.417319...@linutronix.de
The series is also available in git:
We switched all users to initialize the timers as pinned and call
mod_timer(). Remove the now unused function.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
We switched all users to initialize the timers as pinned and call
mod_timer(). Remove the now unused function.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc: r...@linutronix.de
Cc: "Paul E. McKenney"
Cc: Arjan van de Ven
---
Some of the names are not longer correct and others are simply too long to
type. Clean it up before we switch the wheel implementation over to the new
scheme.
No functional change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic
Some of the names are not longer correct and others are simply too long to
type. Clean it up before we switch the wheel implementation over to the new
scheme.
No functional change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc:
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc:
We've converted most timeout related syscalls to hrtimers. sigtimedwait() did
not get this treatment. Convert it so we get a reasonable accuracy and remove
the user space exposure to the timer wheel properties.
Signed-off-by: Thomas Gleixner
Cc: Cyril Hrubis
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc: r...@linutronix.de
Cc: "Paul E. McKenney"
Cc: Arjan van de Ven
---
We've converted most timeout related syscalls to hrtimers. sigtimedwait() did
not get this treatment. Convert it so we get a reasonable accuracy and remove
the user space exposure to the timer wheel properties.
Signed-off-by: Thomas Gleixner
Cc: Cyril Hrubis
---
kernel/signal.c | 24
We want to move the timer migration from a push to a pull model. This requires
to store the pinned attribute of a timer in the timer itself. This must happen
at initialization time.
Add the helper macros for this.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
We want to move the timer migration from a push to a pull model. This requires
to store the pinned attribute of a timer in the timer itself. This must happen
at initialization time.
Add the helper macros for this.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc:
Required to figure out whether the entry is the only one in the hlist.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc:
Required to figure out whether the entry is the only one in the hlist.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc: r...@linutronix.de
Cc: "Paul E. McKenney"
Cc: Arjan van de Ven
---
include/linux/list.h | 10 ++
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc:
Introduce TPM_VTPM_PROXY_NO_SYSFS flag that prevents a vtpm_proxy driver
instance from having the typical sysfs entries that shows the state of the
TPM. The flag is to be set in the ioctl creating the vtpm_proxy device
pair and maps on a new chip flags TPM_CHIP_FLAG_NO_SYSFS.
This flag would be
The current timer wheel has some drawbacks:
1) Cascading
Cascading can be an unbound operation and is completely pointless in most
cases because the vast majority of the timer wheel timers are canceled or
rearmed before expiration.
2) No fast lookup of the next expiring timer
In
We want to store the array index in the flags space. 256k CPUs should be
enough for a while.
Signed-off-by: Thomas Gleixner
---
include/linux/timer.h | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
--- a/include/linux/timer.h
+++ b/include/linux/timer.h
We want to store the array index in the flags space. 256k CPUs should be
enough for a while.
Signed-off-by: Thomas Gleixner
---
include/linux/timer.h | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
--- a/include/linux/timer.h
+++ b/include/linux/timer.h
@@ -58,12 +58,12 @@
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc: r...@linutronix.de
Cc: "Paul E. McKenney"
Cc: Arjan van de Ven
---
Introduce TPM_VTPM_PROXY_NO_SYSFS flag that prevents a vtpm_proxy driver
instance from having the typical sysfs entries that shows the state of the
TPM. The flag is to be set in the ioctl creating the vtpm_proxy device
pair and maps on a new chip flags TPM_CHIP_FLAG_NO_SYSFS.
This flag would be
The current timer wheel has some drawbacks:
1) Cascading
Cascading can be an unbound operation and is completely pointless in most
cases because the vast majority of the timer wheel timers are canceled or
rearmed before expiration.
2) No fast lookup of the next expiring timer
In
On Fri, 24 Jun 2016 15:33:35 +0200,
Dmitry Vyukov wrote:
>
> On Fri, Jun 24, 2016 at 3:32 PM, Takashi Iwai wrote:
> > On Tue, 21 Jun 2016 20:26:48 +0200,
> > Dmitry Vyukov wrote:
> >>
> >> On Mon, Jun 6, 2016 at 4:11 PM, Takashi Iwai wrote:
> >> > On Sat, 04 Jun
From: Torsten Hilbrich
The value bytes comes from the filesystem which is about to be
mounted. We cannot trust that the value is always in the range
we expect it to be.
Check its value before using it to calculate the length for the
crc32_le call. It value must be
From: Anna-Maria Gleixner
After a NOHZ idle sleep the wheel must be forwarded to current jiffies. There
might be expired timers so the current code loops and checks the epxired
buckets for timers. This can take quite some time for long NOHZ idle periods.
The pending
On Fri, 24 Jun 2016 15:33:35 +0200,
Dmitry Vyukov wrote:
>
> On Fri, Jun 24, 2016 at 3:32 PM, Takashi Iwai wrote:
> > On Tue, 21 Jun 2016 20:26:48 +0200,
> > Dmitry Vyukov wrote:
> >>
> >> On Mon, Jun 6, 2016 at 4:11 PM, Takashi Iwai wrote:
> >> > On Sat, 04 Jun 2016 20:27:50 +0200,
> >> >
From: Torsten Hilbrich
The value bytes comes from the filesystem which is about to be
mounted. We cannot trust that the value is always in the range
we expect it to be.
Check its value before using it to calculate the length for the
crc32_le call. It value must be larger (or equal) sumoff + 4.
From: Anna-Maria Gleixner
After a NOHZ idle sleep the wheel must be forwarded to current jiffies. There
might be expired timers so the current code loops and checks the epxired
buckets for timers. This can take quite some time for long NOHZ idle periods.
The pending bitmask in the timer base
The wheel clock is stale when a cpu goes into a long idle sleep. This has the
side effect, that timers which are queued end up in the outer wheel
levels. That results in coarser granularity.
To solve this, we keep track of the idle state and forward the wheel clock
whenever it's possible.
Hi Andrew,
Please send the following patch to upstream (hopefully in this cycle).
It fixes a memory overrun issue due to incomplete sanity check of
on-disk super block size information, which can result in a kernel
panic, for instance, in the case where a non-nilfs volume is
accidentally mounted
The wheel clock is stale when a cpu goes into a long idle sleep. This has the
side effect, that timers which are queued end up in the outer wheel
levels. That results in coarser granularity.
To solve this, we keep track of the idle state and forward the wheel clock
whenever it's possible.
Hi Andrew,
Please send the following patch to upstream (hopefully in this cycle).
It fixes a memory overrun issue due to incomplete sanity check of
on-disk super block size information, which can result in a kernel
panic, for instance, in the case where a non-nilfs volume is
accidentally mounted
This was a failed attempt to optimize the timer expiry in idle, which was
disabled and never revisited. Remove the cruft.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc:
This was a failed attempt to optimize the timer expiry in idle, which was
disabled and never revisited. Remove the cruft.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc: r...@linutronix.de
Cc: "Paul E. McKenney"
Cc: Arjan van de
On Fri, 24 Jun 2016 15:48:53 +0200,
Dmitry Vyukov wrote:
>
> On Fri, Jun 24, 2016 at 3:33 PM, Takashi Iwai wrote:
> > On Tue, 21 Jun 2016 19:41:28 +0200,
> > Dmitry Vyukov wrote:
> >>
> >> On Mon, Jun 6, 2016 at 6:39 PM, Takashi Iwai wrote:
> >> > On Mon, 06 Jun
On Fri, 24 Jun 2016 15:48:53 +0200,
Dmitry Vyukov wrote:
>
> On Fri, Jun 24, 2016 at 3:33 PM, Takashi Iwai wrote:
> > On Tue, 21 Jun 2016 19:41:28 +0200,
> > Dmitry Vyukov wrote:
> >>
> >> On Mon, Jun 6, 2016 at 6:39 PM, Takashi Iwai wrote:
> >> > On Mon, 06 Jun 2016 18:29:25 +0200,
> >> >
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc:
Pinned timers must carry that attribute in the timer itself. No functional
change.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc: r...@linutronix.de
Cc: "Paul E. McKenney"
Cc: Arjan van de Ven
---
We now have implicit batching in the timer wheel. The slack is not longer
used. Remove it.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
From: Anna-Maria Gleixner
Move __run_timers() below __next_timer_interrupt() and next_pending_bucket()
in preparation for __run_timers() NOHZ optimization.
No functional change.
Signed-off-by: Anna-Maria Gleixner
Signed-off-by: Thomas
We now have implicit batching in the timer wheel. The slack is not longer
used. Remove it.
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc: r...@linutronix.de
Cc: "Paul E. McKenney"
Cc: Arjan van de Ven
---
block/genhd.c
From: Anna-Maria Gleixner
Move __run_timers() below __next_timer_interrupt() and next_pending_bucket()
in preparation for __run_timers() NOHZ optimization.
No functional change.
Signed-off-by: Anna-Maria Gleixner
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc:
From: Anna-Maria Gleixner
For further optimizations we need to seperate index calculation and
queueing. No functional change.
Signed-off-by: Anna-Maria Gleixner
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
From: Anna-Maria Gleixner
For further optimizations we need to seperate index calculation and
queueing. No functional change.
Signed-off-by: Anna-Maria Gleixner
Signed-off-by: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Frederic Weisbecker
Cc: Chris Mason
Cc: Eric Dumazet
Cc:
With the wheel forwading in place and with the HZ=1000 4ms folding we can
avoid running the softirq at all.
Signed-off-by: Thomas Gleixner
---
kernel/time/timer.c | 11 +++
1 file changed, 11 insertions(+)
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
@@
From: Anna-Maria Gleixner
The existing optimization for same expiry time in mod_timer() checks whether
the timer expiry time is the same as the new requested expiry time. In the old
timer wheel implementation this does not take the slack batching into account,
neither
With the wheel forwading in place and with the HZ=1000 4ms folding we can
avoid running the softirq at all.
Signed-off-by: Thomas Gleixner
---
kernel/time/timer.c | 11 +++
1 file changed, 11 insertions(+)
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
@@ -1599,7 +1599,18 @@
From: Anna-Maria Gleixner
The existing optimization for same expiry time in mod_timer() checks whether
the timer expiry time is the same as the new requested expiry time. In the old
timer wheel implementation this does not take the slack batching into account,
neither does the new implementation
Alexandre Belloni writes:
> Hi,
>
> On 24/06/2016 at 19:01:09 +0530, Raashid Muhammed wrote :
>> Add power led node and rename status led node.
>>
>
> Well, I'm ok with the change but this does more:
>
>> Signed-off-by: Raashid Muhammed
>> Reviewed-by: Vijay Kumar
Alexandre Belloni writes:
> Hi,
>
> On 24/06/2016 at 19:01:09 +0530, Raashid Muhammed wrote :
>> Add power led node and rename status led node.
>>
>
> Well, I'm ok with the change but this does more:
>
>> Signed-off-by: Raashid Muhammed
>> Reviewed-by: Vijay Kumar B.
>> ---
>>
Hi Nishanth,
On 06/24/2016 07:13 AM, Nishanth Menon wrote:
On 06/23/2016 07:28 PM, Guenter Roeck wrote:
By registering a cleanup function with devm_add_action(), we can
simplify the error path in the probe function and drop the remove
function entirely.
Signed-off-by: Guenter Roeck
Hi Nishanth,
On 06/24/2016 07:13 AM, Nishanth Menon wrote:
On 06/23/2016 07:28 PM, Guenter Roeck wrote:
By registering a cleanup function with devm_add_action(), we can
simplify the error path in the probe function and drop the remove
function entirely.
Signed-off-by: Guenter Roeck
I dont
On Fri, Jun 24, 2016 at 07:36:57PM +0800, Ming Lei wrote:
> >
> > This is not a theoretical problem.
> > At least int DRBD, and an unfortunately high IO concurrency wrt. the
> > "max-buffers" setting, without this patch we have a reproducible deadlock.
>
> Is there any log about the deadlock? And
On Fri, Jun 24, 2016 at 07:36:57PM +0800, Ming Lei wrote:
> >
> > This is not a theoretical problem.
> > At least int DRBD, and an unfortunately high IO concurrency wrt. the
> > "max-buffers" setting, without this patch we have a reproducible deadlock.
>
> Is there any log about the deadlock? And
SPI slave devices are not created when looking up driver for the slave
fails. Create a device anyway so it can be manually bound to a driver.
Signed-off-by: Michal Suchanek
---
drivers/spi/spi.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git
This allows binding spidev on any slave device by hand using sysfs
without adding superfluous compatibles or any other needless
complication.
Note that any slave driver that requires configuration will fail to
probe anyway. Only a driver that binds to anything can be bound
successfully.
SPI slave devices are not created when looking up driver for the slave
fails. Create a device anyway so it can be manually bound to a driver.
Signed-off-by: Michal Suchanek
---
drivers/spi/spi.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/drivers/spi/spi.c
This allows binding spidev on any slave device by hand using sysfs
without adding superfluous compatibles or any other needless
complication.
Note that any slave driver that requires configuration will fail to
probe anyway. Only a driver that binds to anything can be bound
successfully.
Hello,
This small patchset makes it possible to bind spidev manually to any SPI slave
without much hassle.
Thanks
Michal
Michal Suchanek (3):
spi: spidev: fix the check for spidev in dt
spi: of: allow instantiating slaves without a driver
drivers core: allow id match override when
The check is supposed to warn about spidev specified directly in
devicetree as compatible. This just does not work. I have a devicetree
with no compatible whatsoever and hacked my kernel so I can manually
bind spidev. This still triggers.
Also I have no idea how this could have build with !
Hello,
This small patchset makes it possible to bind spidev manually to any SPI slave
without much hassle.
Thanks
Michal
Michal Suchanek (3):
spi: spidev: fix the check for spidev in dt
spi: of: allow instantiating slaves without a driver
drivers core: allow id match override when
The check is supposed to warn about spidev specified directly in
devicetree as compatible. This just does not work. I have a devicetree
with no compatible whatsoever and hacked my kernel so I can manually
bind spidev. This still triggers.
Also I have no idea how this could have build with !
Hi Bjorn,
On Tue, Jun 21, 2016 at 6:49 PM, Bjorn Helgaas wrote:
> On Tue, Jun 21, 2016 at 06:41:00PM +0300, Valentine Barshak wrote:
>> On Tue, Jun 21, 2016 at 09:26:23AM -0500, Bjorn Helgaas wrote:
>> > On Tue, Jun 21, 2016 at 12:41:31PM +0200, Geert Uytterhoeven wrote:
>> >
Hi Bjorn,
On Tue, Jun 21, 2016 at 6:49 PM, Bjorn Helgaas wrote:
> On Tue, Jun 21, 2016 at 06:41:00PM +0300, Valentine Barshak wrote:
>> On Tue, Jun 21, 2016 at 09:26:23AM -0500, Bjorn Helgaas wrote:
>> > On Tue, Jun 21, 2016 at 12:41:31PM +0200, Geert Uytterhoeven wrote:
>> > > On Tue, Jun 7,
On Friday 10 June 2016 01:51 PM, Pavel Andrianov wrote:
> Hi!
>
> There is a potential data race in
> drivers/net/wireless/realtek/rtlwifi/rtl8188ee/rtl8188ee.ko.
>
> In the function rtl88ee_gpio_radio_on_off_checking the flag
> ppsc->rfchange_inprogress is set with a spinlock protection. In
On Friday 10 June 2016 01:51 PM, Pavel Andrianov wrote:
> Hi!
>
> There is a potential data race in
> drivers/net/wireless/realtek/rtlwifi/rtl8188ee/rtl8188ee.ko.
>
> In the function rtl88ee_gpio_radio_on_off_checking the flag
> ppsc->rfchange_inprogress is set with a spinlock protection. In
On 06/23/2016 07:28 PM, Guenter Roeck wrote:
By registering a cleanup function with devm_add_action(), we can
simplify the error path in the probe function and drop the remove
function entirely.
Signed-off-by: Guenter Roeck
I dont seem to have a cover letter to reply
On 06/23/2016 07:28 PM, Guenter Roeck wrote:
By registering a cleanup function with devm_add_action(), we can
simplify the error path in the probe function and drop the remove
function entirely.
Signed-off-by: Guenter Roeck
I dont seem to have a cover letter to reply to... but anyways..
Am 24.06.2016 um 15:17 schrieb Gustavo Padovan:
Hi Christian,
2016-06-24 Christian König :
Am 23.06.2016 um 17:29 schrieb Gustavo Padovan:
From: Gustavo Padovan
Hi all,
This is an attempt to improve fence support on Sync File. The
Am 24.06.2016 um 15:17 schrieb Gustavo Padovan:
Hi Christian,
2016-06-24 Christian König :
Am 23.06.2016 um 17:29 schrieb Gustavo Padovan:
From: Gustavo Padovan
Hi all,
This is an attempt to improve fence support on Sync File. The basic idea
is to have only sync_file->fence and store all
On Thu 23-06-16 20:52:21, Oleg Nesterov wrote:
> On 06/23, Linus Torvalds wrote:
> >
> > On Thu, Jun 23, 2016 at 10:03 AM, Oleg Nesterov wrote:
> > >
> > > Let me quote my previous email ;)
> > >
> > > And we can't free/nullify it when the parent/debuger reaps a
> > >
On Thu 23-06-16 20:52:21, Oleg Nesterov wrote:
> On 06/23, Linus Torvalds wrote:
> >
> > On Thu, Jun 23, 2016 at 10:03 AM, Oleg Nesterov wrote:
> > >
> > > Let me quote my previous email ;)
> > >
> > > And we can't free/nullify it when the parent/debuger reaps a
> > > zombie,
> > >
Current help text check only check a config option if it is followed
by another config.
Adding check for help text if the next entry is menuconfig, choice/
endchoice, comment, menu/endmenu, if/endif, source or end of file.
Signed-off-by: Yingjoe Chen
---
checkpatch
Current help text check only check a config option if it is followed
by another config.
Adding check for help text if the next entry is menuconfig, choice/
endchoice, comment, menu/endmenu, if/endif, source or end of file.
Signed-off-by: Yingjoe Chen
---
checkpatch Kconfig checking stuff again.
If a Kconfig config option doesn't specify 'default', the default
will be n. Adding 'default n' is unnecessary.
Add a test to warn about this.
Signed-off-by: Yingjoe Chen
---
scripts/checkpatch.pl | 7 +++
1 file changed, 7 insertions(+)
diff --git
If a Kconfig config option doesn't specify 'default', the default
will be n. Adding 'default n' is unnecessary.
Add a test to warn about this.
Signed-off-by: Yingjoe Chen
---
scripts/checkpatch.pl | 7 +++
1 file changed, 7 insertions(+)
diff --git a/scripts/checkpatch.pl
On 24/06/16 10:13, Jan Beulich wrote:
> Reads following writes with all address bits set to 1 should return all
> changeable address bits as one, not the BAR size (nor, as was the case
> for the upper half of 64-bit BARs, the high half of the region's end
> address). Presumably this didn't cause
On 24/06/16 10:13, Jan Beulich wrote:
> Reads following writes with all address bits set to 1 should return all
> changeable address bits as one, not the BAR size (nor, as was the case
> for the upper half of 64-bit BARs, the high half of the region's end
> address). Presumably this didn't cause
Refactoring code to use frequency table index instead of pstate_id.
This abstraction will make the code independent of the pstate values.
- No functional changes
- The highest frequency is at frequency table index 0 and the frequency
decreases as the index increases.
- Macros get_index() and
Refactoring code to use frequency table index instead of pstate_id.
This abstraction will make the code independent of the pstate values.
- No functional changes
- The highest frequency is at frequency table index 0 and the frequency
decreases as the index increases.
- Macros get_index() and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-4.7b-rc4-tag
xen: bug fixes for 4.7-rc4
- - Fix x86 PV dom0 crash during early boot on some hardware.
- - Fix two pciback bugs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-4.7b-rc4-tag
xen: bug fixes for 4.7-rc4
- - Fix x86 PV dom0 crash during early boot on some hardware.
- - Fix two pciback bugs
On 06/24/2016 07:10 PM, Alexandre Belloni wrote:
Hi,
On 24/06/2016 at 19:01:09 +0530, Raashid Muhammed wrote :
Add power led node and rename status led node.
Well, I'm ok with the change but this does more:
Signed-off-by: Raashid Muhammed
Reviewed-by: Vijay
On 06/24/2016 07:10 PM, Alexandre Belloni wrote:
Hi,
On 24/06/2016 at 19:01:09 +0530, Raashid Muhammed wrote :
Add power led node and rename status led node.
Well, I'm ok with the change but this does more:
Signed-off-by: Raashid Muhammed
Reviewed-by: Vijay Kumar B.
---
Add support for MCB bases FPGAs connected to the LPC or
non PCI Bus.
This driver currently supports the SC24 board. The FPGA
is connected to the LPC bus and is identified using the BIOS
DMI string.
Signed-off-by: Andreas Werner
---
drivers/mcb/Kconfig | 9 +++
Add support for MCB bases FPGAs connected to the LPC or
non PCI Bus.
This driver currently supports the SC24 board. The FPGA
is connected to the LPC bus and is identified using the BIOS
DMI string.
Signed-off-by: Andreas Werner
---
drivers/mcb/Kconfig | 9 +++
drivers/mcb/Makefile | 1 +
701 - 800 of 1424 matches
Mail list logo