> On Nov 18, 2015, at 12:11 AM, Zhangjian (Bamvor)
> wrote:
>
> Hi, Yury
>
>> On 2015/11/18 5:16, Yury Norov wrote:
>> From: Philipp Tomsich
>>
>> To make life for tools (such as gdb) easier when dealing with ILP32
>> processes,
>> we report a proper subarchitecture for ILP32 in the ELF au
On Tue, Nov 17, 2015 at 01:01:09PM -0800, Paul E. McKenney wrote:
> On Tue, Nov 17, 2015 at 11:51:10AM +, Will Deacon wrote:
> > On Mon, Nov 16, 2015 at 01:58:49PM -0800, Linus Torvalds wrote:
> > > On Mon, Nov 16, 2015 at 8:24 AM, Will Deacon wrote:
> > > >
> > > > ... or we upgrade spin_unlo
On Wed, Nov 18, 2015 at 12:10:08PM +0100, Paolo Bonzini wrote:
> On 14/11/2015 11:37, Borislav Petkov wrote:
> > vendor = x86_vendor();
> > - family = x86_family();
> > + family = x86_family_cpuid();
>
> What about renaming x86_vendor() so that this looks like
>
> - vendor = x86_vendo
On 11/18, Sudip Mukherjee wrote:
On Tue, Nov 17, 2015 at 09:01:28PM +0100, Bogicevic Sasa wrote:
This fixes all "Comparison to NULL could be written like..."
messages from checkpatch.pl
Signed-off-by: Bogicevic Sasa
---
drivers/staging/wilc1000/coreconfigurator.c | 10 +-
1 file chang
On November 17, 2015 17:54, Rob Herring wrote:
> >> > +- dlg,micbias1-lvl : Voltage (mV) for Mic Bias 1
> >> > + [<1200>, <1600>, <1800>, <2000>, <2200>, <2400>, <2600>, <2800>,
> >> <3000>]
> >> > +- dlg,micbias2-lvl : Voltage (mV) for Mic Bias 2
> >> > + [<1200>, <1600>, <1800>, <2000>, <220
Christoph,
Given the discussion around this patch I think it would
be a good idea remove it from the patchset since it's not
mandatory for the CQ abstraction. I think that we should
take it with Steve to come up with a complete solution for
this bit.
Thoughts?
--
To unsubscribe from this list: s
On 11/18/15, Daniel Axtens wrote:
> HMIs (Hypervisor Management|Maintenance Interrupts) are a class of interrupt
> on POWER systems.
>
> HMI support has traditionally been exceptionally difficult to test. However
> Skiboot ships a tool that, with the correct magic numbers, will inject them.
>
> Th
On Wednesday 18 November 2015, Finn Thain wrote:
> Like my previous work on the NCR5380 drivers, this patch series has bug
> fixes, code cleanup and modernization. These drivers suffer from mistakes,
> poor style and neglect and this long series addresses the worst of it,
> covering all ten wrapper
On 18/11/2015 12:28, Borislav Petkov wrote:
>> On 14/11/2015 11:37, Borislav Petkov wrote:
>>> > > vendor = x86_vendor();
>>> > > - family = x86_family();
>>> > > + family = x86_family_cpuid();
>> >
>> > What about renaming x86_vendor() so that this looks like
>> >
>> > - v
This fixes all "comparison to NULL could be written like ..."
Signed-off-by: Bogicevic Sasa
---
drivers/staging/wilc1000/coreconfigurator.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/wilc1000/coreconfigurator.c
b/drivers/staging/wilc1000/corec
+Arnd
On 17/11/15 15:00, Robin Murphy wrote:
Hi Suravee,
On 28/10/15 22:50, Suravee Suthikulpanit wrote:
This patch move of_pci_dma_configure() to a more generic
pci_dma_configure(), which can be extended by non-OF code (e.g. ACPI).
This has no functional change.
Unfortunately, it appears t
On Wednesday 18 November 2015 11:07:26 Geert Uytterhoeven wrote:
> >
> > I've done a complete list of what the architectures (see
> > https://docs.google.com/spreadsheets/d/18GxXEHE2ywnSr-SPoGFd1ABz6wEM1ex-JMu5lEraaH8/
> > )
> >
> > We have these categories:
> >
> > 1. uses IPC_PARSE_VERSION with
From: Baolin Wang
> Sent: 18 November 2015 10:45
> On 18 November 2015 at 17:32, Andy Shevchenko
> wrote:
> > On Wed, Nov 18, 2015 at 4:15 AM, Baolin Wang wrote:
> >> On 17 November 2015 at 21:34, Andy Shevchenko
> >> wrote:
> >>> On Mon, Nov 16, 2015 at 9:05 AM, Baolin Wang
> >>> wrote:
> >
Cosmetic.
Do not define list_entry_next() and use list_next_entry()
from list.h.
Signed-off-by: Sergey Senozhatsky
---
drivers/misc/mic/scif/scif_dma.c | 27 +++
drivers/misc/mic/scif/scif_main.h | 1 +
2 files changed, 12 insertions(+), 16 deletions(-)
diff --git a/d
From: Will Deacon
> Sent: 18 November 2015 10:14
> On Tue, Nov 17, 2015 at 08:17:17PM +0100, Arnd Bergmann wrote:
> > On Tuesday 17 November 2015 17:12:37 Will Deacon wrote:
> > > On Tue, Nov 17, 2015 at 06:03:40PM +0100, Arnd Bergmann wrote:
> > > > On Tuesday 17 November 2015 16:44:53 Will Deacon
Cosmetic.
Do not define list_entry_next() and use list_next_entry()
from list.h.
Signed-off-by: Sergey Senozhatsky
---
net/ceph/messenger.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/net/ceph/messenger.c b/net/ceph/messenger.c
index 9981039..77ccca9 100644
--- a
On Thu, Nov 12, 2015 at 12:21:10PM -0800, Laura Abbott wrote:
> The permissions in mark_rodata_ro trigger a build error
> with STRICT_MM_TYPECHECKS. Fix this by introducing
> PAGE_KERNEL_ROX for the same reasons as PAGE_KERNEL_RO.
> From Ard:
>
> "PAGE_KERNEL_EXEC has PTE_WRITE set as well, making
Hi Ingo,
Thanks for looking into this.
On Wed, Nov 18, 2015 at 7:55 AM, Ingo Molnar wrote:
> Is this 'problem' a performance problem (code not being able to use the FPU
> occasionally and hence sporadically performing poorly), or some sort of actual
> stability/correctness problem?
More of the
Cosmetic.
Do not define list_entry_next() and use list_next_entry()
from list.h.
Signed-off-by: Sergey Senozhatsky
---
security/apparmor/apparmorfs.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/security/apparmor/apparmorfs.c b/security/apparmor/apparmorfs.c
in
On 2015-11-17 16:32, Seth Forshee wrote:
On Tue, Nov 17, 2015 at 03:54:50PM -0500, Austin S Hemmelgarn wrote:
On 2015-11-17 14:16, Seth Forshee wrote:
On Tue, Nov 17, 2015 at 02:02:09PM -0500, Austin S Hemmelgarn wrote:
On 2015-11-17 12:55, Al Viro wrote:
On Tue, Nov 17, 2015 at 11:25:51AM -0
This company already provided some products, so add them to the
vendor prefix list.
Signed-off-by: Stefan Wahren
---
.../devicetree/bindings/vendor-prefixes.txt|1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/de
On Wed, Nov 18, 2015 at 11:35:41AM +0100, Peter Zijlstra wrote:
> On Wed, Nov 18, 2015 at 09:36:22AM +0100, Ingo Molnar wrote:
> > What will such throttling do to latencies, as observed by user-space tasks?
> > What's
> > the typical expected frequency of the throttling frequency that you are
>
On Wed, Nov 18, 2015 at 12:11:25PM +, David Laight wrote:
> From: Will Deacon
> > Sent: 18 November 2015 10:14
> > On Tue, Nov 17, 2015 at 08:17:17PM +0100, Arnd Bergmann wrote:
> > > On Tuesday 17 November 2015 17:12:37 Will Deacon wrote:
> > > > On Tue, Nov 17, 2015 at 06:03:40PM +0100, Arnd
On Mon 16-11-15 19:35:14, Dave Hansen wrote:
>
> From: Dave Hansen
>
> get_user_pages_locked() appears to be for use when a caller needs
> to know that its lock on mmap_sem was invalidated by the gup
> call.
>
> But, get_vaddr_frames() is not one of those users. It
> unconditionally locks the
On Wednesday 18 November 2015 11:35:27 Andy Shevchenko wrote:
> On Fri, Nov 13, 2015 at 11:35 AM, Arnd Bergmann wrote:
> > On Friday 13 November 2015 03:10:13 Andy Shevchenko wrote:
> >> On Thu, Nov 12, 2015 at 4:14 PM, Arnd Bergmann wrote:
> >> > The dw_mmc driver stores the physical address of
On Wednesday 18 November 2015 12:00:32 Robin Murphy wrote:
> On 17/11/15 15:00, Robin Murphy wrote:
> > On 28/10/15 22:50, Suravee Suthikulpanit wrote:
> >> Signed-off-by: Suravee Suthikulpanit
> >> Acked-by: Rob Herring
> >> Acked-by: Bjorn Helgaas
> >> Reviewed-by: Hanjun Guo
> >> CC: Rafael
On Wed, 2015-11-18 at 08:45 +0100, SF Markus Elfring wrote:
> > You mean this likely() annotation of yours?
>
> How do you think about to express the software design pattern
> which is applied at the mentioned source code place by a dedicated
> preprocessor macro?
likely()/unlikely() are not alwa
Em Wed, Nov 18, 2015 at 07:32:38AM +0100, Ingo Molnar escreveu:
> So considering the relatively large diffstat and the fact that we are 3 days
> after
> the closing of the merge window, I think we should separate this into minimal
> fixes for perf/urgent, and more involved changes for v4.5.
Ok,
On 18 November 2015 at 20:05, David Laight wrote:
> From: Baolin Wang
>> Sent: 18 November 2015 10:45
>> On 18 November 2015 at 17:32, Andy Shevchenko
>> wrote:
>> > On Wed, Nov 18, 2015 at 4:15 AM, Baolin Wang
>> > wrote:
>> >> On 17 November 2015 at 21:34, Andy Shevchenko
>> >> wrote:
>> >
Em Wed, Nov 18, 2015 at 03:40:09PM +0900, Masami Hiramatsu escreveu:
> Hi,
>
> Here is a series to fix some memory leaks and refcount
> leaks on map and dso. This also includes the refcnt APIs
> with backtrace debugging feature.
Cool, I wonder if this could be usable in the kernel proper... Is th
On 2015-11-17 17:01, Seth Forshee wrote:
On Tue, Nov 17, 2015 at 09:05:42PM +, Al Viro wrote:
On Tue, Nov 17, 2015 at 03:39:16PM -0500, Austin S Hemmelgarn wrote:
This is absolutely insane, no matter how much LSM snake oil you slatter on
the whole thing. All of a sudden you are exposing a
W dniu 18.11.2015 o 00:58, Javier Martinez Canillas pisze:
> Since the multi_v7_defconfig is used to build an image for different
> platforms, the options should be enabled as module whenever possible.
>
> Signed-off-by: Javier Martinez Canillas
>
> ---
> The patch was tested on an Exynos5800 Pe
On Wed, Nov 18, 2015 at 12:27:04PM +, Morten Rasmussen wrote:
> On Wed, Nov 18, 2015 at 11:35:41AM +0100, Peter Zijlstra wrote:
> > On Wed, Nov 18, 2015 at 09:36:22AM +0100, Ingo Molnar wrote:
> > > What will such throttling do to latencies, as observed by user-space
> > > tasks? What's
> > >
Hi everybody,
and thanks a lot for your work.
I'm using my main laptop (no virtualized environment) with Kasan
enabled. Kernel it's the Linus latest commit,¹ plus a few pulls
from different git trees (BTRFS, drm-intel, ecc.). You can find
a detailed list in the attached file: added_
The simple_strtoul function is marked as obsolete.
This patch replace it by kstrtou8.
Signed-off-by: LABBE Corentin
---
drivers/i2c/busses/i2c-taos-evm.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-taos-evm.c
b/drivers/i2c/busses/i2c-taos-ev
Hello
Changes since v2
- removed err variable
- fix a spelling issue
Changes since v1
- drop the return code of kstrtou8 and return -EPROTO
as suggested by Jean Delvare
- Added a comment on the return code drop
Regards
LABBE Corentin (1):
i2c: taos-evm: replace simple_strtoul by kstrtou8
On Wed, Nov 18, 2015 at 11:17:25AM +, John Keeping wrote:
> The SPICE protocol considers the position of a cursor to be the location
> of its active pixel on the display, so the cursor is drawn with its
> top-left corner at "(x - hot_spot_x, y - hot_spot_y)" but the DRM cursor
> position gives
发自我的 iPhone
> 在 2015年11月18日，下午8:44，Arnaldo Carvalho de Melo 写道：
>
> Em Wed, Nov 18, 2015 at 07:32:38AM +0100, Ingo Molnar escreveu:
>> So considering the relatively large diffstat and the fact that we are 3 days
>> after
>> the closing of the merge window, I think we should separate this int
Simplify the code with list_first_entry_or_null().
Signed-off-by: Geliang Tang
---
block/blk-throttle.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/block/blk-throttle.c b/block/blk-throttle.c
index 2149a1d..db2dbf1 100644
--- a/block/blk-throttle.c
+++ b/block/
- On Nov 18, 2015, at 1:51 AM, masami hiramatsu pt
masami.hiramatsu...@hitachi.com wrote:
> Hi Mathieu, Steven,
>
> From: Steven Rostedt [mailto:rost...@goodmis.org]
>>
>>On Tue, 17 Nov 2015 16:35:35 + (UTC)
>>Mathieu Desnoyers wrote:
>>
>>> Hi,
>>>
>>> I notice that trace_kprobe.c does
On Wed, Nov 18, 2015 at 1:13 PM, Sergey Senozhatsky
wrote:
> Cosmetic.
>
> Do not define list_entry_next() and use list_next_entry()
> from list.h.
>
> Signed-off-by: Sergey Senozhatsky
> ---
> net/ceph/messenger.c | 8 +++-
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/
On Tuesday 17 November 2015 16:54:16 Arnd Bergmann wrote:
> +#include
>
My randconfig test setup has now found the typo above. Resending the
fixed version.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.o
This patch adds glue driver for DWC3 core in Xilinx ZynqMP SOC.
DWC3 glue layer is hardware layer around Synopsys DesignWare
USB3 core. Its purpose is to supply Synopsys IP with required clocks
and interface it with the rest of the SoC.
Signed-off-by: Subbaraya Sundeep Bhatta
---
drivers/usb/dwc
The Exynos5420 Peach Pit Chromebook has a Marvell WiFi SDIO chip which
can't neither be removed nor be detected. But the node isn't marked
as non-removable and instead has the broken-cd DT property.
This causes the device to be removed when the system enters into a
suspend state and the following
The Exynos5800 Peach Pi Chromebook has a Marvell WiFi SDIO chip which
can't neither be removed nor be detected. But the node isn't marked
as non-removable and instead has the broken-cd DT property.
This causes the device to be removed when the system enters into a
suspend state and the following w
Hello Krzysztof and Kukjin,
This is a resend of a series posted a month ago [0] that use the correct
card detection properties in the DTS for Exynos Chromebooks but that was
never picked.
The patches have no changed, the only difference is that I'm including
all the Reviewed-by and Tested-by tags
The eMMC is non-removable so is marked with the non-removable DT
property to avoid having to redetect it after a suspend/resume.
But it also has the broken-cd property which is wrong since only
one of the DT properties for card detection should be used.
Also remove the card-detect-delay property
The eMMC is non-removable so is marked with the non-removable DT
property to avoid having to redetect it after a suspend/resume.
But it also has the broken-cd property which is wrong since only
one of the DT properties for card detection should be used.
Also remove the card-detect-delay property
The eMMC is non-removable so mark it using the non-removable DT
property to avoid having to redetect it after a suspend/resume.
Also remove the card-detect-delay property that is not needed with
non-removable.
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Tomeu Vizoso
Tested-by: Tomeu Vi
On (11/18/15 14:13), Ilya Dryomov wrote:
[..]
>
> Someone beat you to it ;)
>
> https://github.com/ceph/ceph-client/commit/76b4a27faebb369c1c50df01ef08b614a2854fc5
Oh, OK then :) Thanks!
-ss
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
The Exynos5250 Snow Chromebooks have a Marvell WiFi SDIO chip which
can't neither be removed nor be detected. But the node isn't marked
as non-removable and instead has the broken-cd DT property.
This causes the device to be removed when the system enters into a
suspend state and the following war
The current kthread worker users call flush() and stop() explicitly.
This function drains the worker, stops it, and frees the kthread_worker
struct in one call.
It is supposed to be used together with create_kthread_worker*() that
allocates struct kthread_worker.
Also note that drain() correctly
kthread_create_on_node() implements a bunch of logic to create
the kthread. It is already called by kthread_create_on_cpu().
We are going to extend the kthread worker API and will
need to call kthread_create_on_node() with va_list args there.
This patch does only a refactoring and does not modify
There are situations when we need to modify the delay of a delayed kthread
work. For example, when the work depends on an event and the initial delay
means a timeout. Then we want to queue the work immediately when the event
happens.
This patch implements mod_delayed_kthread_work() as inspired wor
kthread_create_on_cpu() was added by the commit 2a1d446019f9a5983e
("kthread: Implement park/unpark facility"). It is currently used
only when enabling new CPU. For this purpose, the newly created
kthread has to be parked.
The CPU binding is a bit tricky. The kthread is parked when the CPU
has not
There is an attempt to print debug messages when the kthread is waken
and when it goes into sleep. It does not work well because the spin lock
does not guard all manipulations with the thread state.
I did not find a way how to print a message when the kthread really
goes into sleep. Instead, I add
Em Wed, Nov 18, 2015 at 09:06:58PM +0800, pi3orama escreveu:
>
>
> 发自我的 iPhone
>
> > 在 2015年11月18日，下午8:44，Arnaldo Carvalho de Melo 写道：
> >
> > Em Wed, Nov 18, 2015 at 07:32:38AM +0100, Ingo Molnar escreveu:
> >> So considering the relatively large diffstat and the fact that we are 3
> >> days
This patch allows to make kthread worker freezable via a new @flags
parameter. It will allow to avoid an init work in some kthreads.
It currently does not affect the function of kthread_worker_fn()
but it might help to do some optimization or fixes eventually.
I currently do not know about any ot
Kthreads are currently implemented as an infinite loop. Each
has its own variant of checks for terminating, freezing,
awakening. In many cases it is unclear to say in which state
it is and sometimes it is done a wrong way.
The plan is to convert kthreads into kthread_worker or workqueues
API. It a
Kthreads are currently implemented as an infinite loop. Each
has its own variant of checks for terminating, freezing,
awakening. In many cases it is unclear to say in which state
it is and sometimes it is done a wrong way.
The plan is to convert kthreads into kthread_worker or workqueues
API. It a
Kthreads are currently implemented as an infinite loop. Each
has its own variant of checks for terminating, freezing,
awakening. In many cases it is unclear to say in which state
it is and sometimes it is done a wrong way.
The plan is to convert kthreads into kthread_worker or workqueues
API. It a
Kthreads are currently implemented as an infinite loop. Each
has its own variant of checks for terminating, freezing,
awakening. In many cases it is unclear to say in which state
it is and sometimes it is done a wrong way.
The plan is to convert kthreads into kthread_worker or workqueues
API. It a
This patch removes a code duplication. It does not modify
the functionality.
Signed-off-by: Petr Mladek
CC: Zhang Rui
CC: Eduardo Valentin
CC: Jacob Pan
CC: linux...@vger.kernel.org
---
drivers/thermal/intel_powerclamp.c | 45 +-
1 file changed, 20 insertio
Kthreads are currently implemented as an infinite loop. Each
has its own variant of checks for terminating, freezing,
awakening. In many cases it is unclear to say in which state
it is and sometimes it is done a wrong way.
The plan is to convert kthreads into kthread_worker or workqueues
API. It a
Kthreads are currently implemented as an infinite loop. Each
has its own variant of checks for terminating, freezing,
awakening. In many cases it is unclear to say in which state
it is and sometimes it is done a wrong way.
The plan is to convert kthreads into kthread_worker or workqueues
API. It a
Remove code duplication and use the new try_lock_kthread_work()
function in flush_kthread_work() as well.
Signed-off-by: Petr Mladek
---
kernel/kthread.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff --git a/kernel/kthread.c b/kernel/kthread.c
index dbd090466e2a..f7caa
Kthreads are currently implemented as an infinite loop. Each
has its own variant of checks for terminating, freezing,
awakening. In many cases it is unclear to say in which state
it is and sometimes it is done a wrong way.
The plan is to convert kthreads into kthread_worker or workqueues
API. It a
This is a minor cleanup to make the s3c2412-i2s and s3c24xx-i2s
drivers independent of the mach/dma.h header file and to allow
removing the dependency on the specific dmaengine driver in the
next patch.
As a side not, only the s3c24xx-i2s driver seems to still be
used, while the definition of the
Kthreads are currently implemented as an infinite loop. Each
has its own variant of checks for terminating, freezing,
awakening. In many cases it is unclear to say in which state
it is and sometimes it is done a wrong way.
The plan is to convert kthreads into kthread_worker or workqueues
API. It a
We are going to use kthread workers more widely and sometimes we will need
to make sure that the work is neither pending nor running.
This patch implements cancel_*_sync() operations as inspired by
workqueues. Well, we are synchronized against the other operations
via the worker lock, we use del_t
We are going to use kthread_worker more widely and delayed works
will be pretty useful.
The implementation is inspired by workqueues. It uses a timer to
queue the work after the requested delay. If the delay is zero,
the work is queued immediately.
In compare with workqueues, each work is associa
Nothing currently prevents a work from queuing for a kthread worker
when it is already running on another one. This means that the work
might run in parallel on more workers. Also some operations, e.g.
flush or drain are not reliable.
This problem will be even more visible after we add cancel_kthr
flush_kthread_worker() returns when the currently queued works are proceed.
But some other works might have been queued in the meantime.
This patch adds drain_kthread_work() that is inspired by drain_workqueue().
It returns when the queue is completely empty and warns when it takes too
long.
The
Kthread workers are currently created using the classic kthread API,
namely kthread_run(). kthread_worker_fn() is passed as the @threadfn
parameter.
This patch defines create_kthread_worker() and
create_kthread_worker_on_cpu() functions that hide implementation details.
They enforce using kthread
Use PFN_DOWN() in should_add_memory_movable() to keep the consistency
of this file.
Signed-off-by: Geliang Tang
---
mm/memory_hotplug.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index 67d488a..7c44ff7 100644
--- a/mm/memory_hotp
Viresh Kumar writes:
> On 17-11-15, 12:06, Punit Agrawal wrote:
>> Register passive cooling devices when initialising cpufreq on
>> big.LITTLE systems. If the device tree provides a dynamic power
>> coefficient for the CPUs then the bound cooling device will support
>> the extensions that allow i
Hello,
On 11/18/2015 10:23 AM, Javier Martinez Canillas wrote:
> The eMMC is non-removable so mark it using the non-removable DT
> property to avoid having to redetect it after a suspend/resume.
>
> Also remove the card-detect-delay property that is not needed with
> non-removable.
>
> Signed-of
timer_pending() checks whether the list of callbacks is empty.
Each callback is removed from the list before it is called,
see call_timer_fn() in __run_timers().
Sometimes we need to make sure that the callback has finished.
For example, if we want to free some resources that are accessed
by the c
My intention is to make it easier to manipulate and maintain kthreads.
Especially, I want to replace all the custom main cycles with a
generic one. Also I want to make the kthreads sleep in a consistent
state in a common place when there is no work.
My first attempt was with a brand new API (itera
This patch adds binding doc for Xilinx DWC3 glue driver.
Signed-off-by: Subbaraya Sundeep Bhatta
---
.../devicetree/bindings/usb/dwc3-xilinx.txt| 33 ++
1 file changed, 33 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/dwc3-xilinx.txt
diff --
Commit 0c5b2b915a58 ("reset: Mark function as static and remove unused
function in core.c") removed the only user of the device pointer in
struct reset_control. As it is now unused, remove it.
Signed-off-by: Philipp Zabel
---
drivers/reset/core.c | 7 +--
1 file changed, 1 insertion(+), 6 de
Simplify the code with list_first_entry_or_null().
Signed-off-by: Geliang Tang
---
fs/locks.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/fs/locks.c b/fs/locks.c
index 86c9467..d2ee8e3 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -1505,12 +1505,10 @@ void lease_
The crash is observed when a service is being disabled host side while
userspace daemon is connected to the device:
[ 90.244859] general protection fault: [#1] SMP
...
[ 90.800082] Call Trace:
[ 90.800082] [] __fput+0xc8/0x1f0
[ 90.800082] [] fput+0xe/0x10
...
[ 90.800082] []
As a preparation to reusing outmsg_lock to protect test-and-set openrations
on 'mode' rename it the more general 'lock'.
Signed-off-by: Vitaly Kuznetsov
---
drivers/hv/hv_utils_transport.c | 14 +++---
drivers/hv/hv_utils_transport.h | 2 +-
2 files changed, 8 insertions(+), 8 deletions
When Hyper-V host asks us to remove some util driver by closing the
appropriate channel there is no easy way to force the current file
descriptor holder to hang up but we can start to respond -EBADF to all
operations asking it to exit gracefully.
As we're setting hvt->mode from two separate contex
inmsg should be freed in case of on_msg() failure to avoid memory leak.
Preserve the error code from on_msg().
Signed-off-by: Vitaly Kuznetsov
---
Changes since v1:
- Preserve the error code from on_msg(). [Dan Carpenter]
---
drivers/hv/hv_utils_transport.c | 7 ---
1 file changed, 4 inserti
Changes since v1:
- Don't re-introduce memory leak in hvt_op_write(), preserve the error
code from on_msg() [Dan Carpenter]
Original description:
I'm observing a crash when a utility driver is disabled host side (e.g.
'Guest services' is disabled live) when we have userspace daemon
connected:
Since 'struct clocksource' is cacheline_aligned, gcc must insert
a lot of padding between reg and clksrc in 'struct clocksource_mmio'
(for example, L1_CACHE_BYTES = 64 on ARMv7).
Storing reg within 'struct clocksource' removes unnecessary padding,
and reg can then be grouped with other hot dat
On 11/17/2015 05:17 PM, Nathan Zimmer wrote:
> When running the SPECint_rate gcc on some very large boxes it was noticed
> that the system was spending lots of time in mpol_shared_policy_lookup.
> The gamess benchmark can also show it and is what I mostly used to chase
> down the issue since the se
Marc Gonzalez writes:
> Since 'struct clocksource' is cacheline_aligned, gcc must insert
> a lot of padding between reg and clksrc in 'struct clocksource_mmio'
> (for example, L1_CACHE_BYTES = 64 on ARMv7).
>
> Storing reg within 'struct clocksource' removes unnecessary padding,
> and reg can
Simplify the code with list_first_entry_or_null().
Signed-off-by: Geliang Tang
---
mm/pgtable-generic.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/mm/pgtable-generic.c b/mm/pgtable-generic.c
index 69261d4..c311a2e 100644
--- a/mm/pgtable-generic.c
+++ b/mm/pgtab
On Tue, Nov 17, 2015 at 11:17 PM, Hongzhou Yang
wrote:
> Since Linux gpio framework return 0 for output, 1 for input.
> But HW use 0 stands for input, and 1 stands for output.
> So use negative to correct it.
>
> And gpio_chip.get is used to get input value, no need to get
> output value, so remo
Hi Philipp,
[auto build test WARNING on: v4.4-rc1]
[also build test WARNING on: next-20151118]
url:
https://github.com/0day-ci/linux/commits/Philipp-Zabel/reset-remove-unused-device-pointer-from-struct-reset_control/20151118-214443
config: x86_64-randconfig-x012-11181928 (attached as .config
On Wed, Nov 18, 2015 at 12:58 AM, William Breathitt Gray
wrote:
> To prevent confusion, and to match the existing coding style used in
> other GPIO drivers, symbol names within the 104-idio-16 GPIO driver
> should be lowercase.
>
> Signed-off-by: William Breathitt Gray
> Reviewed-by: Alexandre C
On Tue, Nov 17, 2015 at 09:16:28AM -0800, Bart Van Assche wrote:
> How about renaming blk_iopoll into blk_poll ? That way the name still
> refers to the block layer. And although the current implementation performs
> polling from IRQ context future implementations maybe will allow polling
> from
On Tue, Nov 17, 2015 at 09:52:58AM -0800, Bart Van Assche wrote:
> On 11/13/2015 05:46 AM, Christoph Hellwig wrote:
>> + * context and does not ask from completion interrupts from the HCA.
>
> Should this perhaps be changed into "for" ?
Yes.
>
>> + */
>> +void
Looks good,
Reviewed-by: Christoph Hellwig
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Wed, Nov 18, 2015 at 10:56:00AM +0100, Miroslav Benes wrote:
> On Mon, 16 Nov 2015, Chris J Arges wrote:
>
> > @@ -281,29 +243,26 @@ static int klp_write_object_relocations(struct module
> > *pmod,
> > return -EINVAL;
> >
> > for (reloc = obj->relocs; reloc->name; reloc++) {
On Tue, Nov 17, 2015 at 11:38:48AM -0800, Bart Van Assche wrote:
> On 11/13/2015 05:46 AM, Christoph Hellwig wrote:
>> [ ... ]
>
> This patch contains two logical changes:
> - Conversion to the new CQ API.
> - Removal of the ib_srpt_compl thread.
>
> Had it been considered to implement these change
On Wed, Nov 18, 2015 at 01:49:46PM +0100, Peter Zijlstra wrote:
> On Wed, Nov 18, 2015 at 12:27:04PM +, Morten Rasmussen wrote:
> > On Wed, Nov 18, 2015 at 11:35:41AM +0100, Peter Zijlstra wrote:
> > > On Wed, Nov 18, 2015 at 09:36:22AM +0100, Ingo Molnar wrote:
> > > > What will such throttlin
201 - 300 of 1043 matches
Mail list logo
