On 08/29/2016 10:49 AM, Takashi Iwai wrote:
Gah, then it was a different one. Obviously I overlooked your patch
during my vacation. Will put it to the queue.
But, this message should appear only once in the recent version. Does
it still annoy as appearing repeatedly at all...?
Hi Takash
Hi Andrew,
On Aug 26 2016 or thereabouts, Andrew Duggan wrote:
> Resending as plain text
>
> Hi Benjamin,
>
> This patch causes standard clickpads without extended buttons to not work.
> I'll explain some more below.
>
> On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
> >From: Lyude Paul
> >
On 30/08/16 16:10, Seth Forshee wrote:
> On Tue, Aug 30, 2016 at 04:00:03PM +0100, David Vrabel wrote:
>> On 29/08/16 16:03, Seth Forshee wrote:
>>> Mounting proc in user namespace containers fails if the xenbus
>>> filesystem is mounted on /proc/xen because this directory fails
>>> the "permanentl
On Tue, Aug 30, 2016 at 04:43:30PM +0200, Petr Mladek wrote:
> On Mon 2016-08-29 11:16:28, Christopher Arges wrote:
> > On Mon, Aug 29, 2016 at 05:23:30PM +0200, Petr Mladek wrote:
> > > On Fri 2016-08-26 13:50:27, Chris J Arges wrote:
> > > > It can be useful to execute hook functions whenever a l
On 08/30/2016 03:58 AM, Shawn Guo wrote:
> On Tue, Aug 09, 2016 at 02:59:39PM -0700, York Sun wrote:
>> Add DDR memory controller nodes to enable EDAC driver.
>>
>> Signed-off-by: York Sun
>
> The patch subject is too general. I changed it to "arm64: dts: Add DDR
> memory controller for Layerscap
Mounting proc in user namespace containers fails if the xenbus
filesystem is mounted on /proc/xen because this directory fails
the "permanently empty" test. proc_create_mount_point() exists
specifically to create such mountpoints in proc but is currently
proc-internal. Export this interface to modu
On 30 August 2016 at 07:55, Jonathan Liu wrote:
> If the enable-gpios property of a simple panel in device tree is set,
> the GPIO is not toggled on/off because of missing calls to
> drm_panel_prepare and drm_panel_unprepare.
>
> Signed-off-by: Jonathan Liu
> ---
> drivers/gpu/drm/sun4i/sun4i_rg
On Wednesday, 2016-08-24 16:33 Joe Perches wrote:
> Many email addresses in MAINTAINERS no longer work so many
> sections in
> MAINTAINERS could likely be considered either
> obsolete or unmaintained.
Whereas I agree it's helpful to purge dysfunctional adresses...
> These M: entries in MAINTAINER
I tried these scenarios:
1. Booted the system without the bbswitch module. The nouveau module
was loaded and is responsible for the power management of the GPU.
The graphical session freezes after some minutes...
2. Booted the system without bbswitch and with nouveau blacklisted.
Manuall
Hello Heikki,
On Tue, Aug 30, 2016 at 11:22:27AM +0300, Heikki Krogerus wrote:
> >
> > If you are only interested in accessory mode support, maybe we don't need
> > the 'type' attribute at all. We could make the 'accessory' attribute always
> > visible and display one of "none", "Audio", "Debug",
Hi Stephen,
2016-08-25 2:16 GMT+02:00 Stephen Boyd :
> On 08/23, Marcin Wojtas wrote:
>> Original commit, which added support for Armada CP110 system controller
>> used global variables for storing all clock information. It worked
>> fine for Armada 7k SoC, with single CP110 block. After dual-CP11
On 8/30/2016 3:58 AM, Peter Zijlstra wrote:
On Mon, Aug 29, 2016 at 12:40:32PM -0400, Chris Metcalf wrote:
On 8/29/2016 12:33 PM, Peter Zijlstra wrote:
On Tue, Aug 16, 2016 at 05:19:27PM -0400, Chris Metcalf wrote:
+ /*
+* Request rescheduling unless we are in full dynticks mode.
On Tue, 2016-08-30 at 17:19 +0200, Anders Larsen wrote:
> On Wednesday, 2016-08-24 16:33 Joe Perches wrote:
> > Many email addresses in MAINTAINERS no longer work so many
> > sections in MAINTAINERS could likely be considered either
> > obsolete or unmaintained.
> Whereas I agree it's helpful to pu
From: Voker57
Add device tree definitions for Qualcomm Cryptography engine and its BAM
Signed-off-by: Iaroslav Gridin
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 42 +
1 file changed, 42 insertions(+)
diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
b/arch/ar
x/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rewrite
Tagged thusly:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
rxrpc-rewrite-20160830-1
David
---
David Howells (2):
rxrpc: Fix a potential NULL-pointer deref in rxrpc_abort_calls
rxrpc: Pass st
Pass struct socket * to more rxrpc kernel interface functions. They should
be starting from this rather than the socket pointer in the rxrpc_call
struct if they need to access the socket.
I have left:
rxrpc_kernel_is_data_last()
rxrpc_kernel_get_abort_code()
rxrpc_kernel_
The call pointer in a channel on a connection will be NULL if there's no
active call on that channel. rxrpc_abort_calls() needs to check for this
before trying to take the call's state_lock.
Signed-off-by: David Howells
---
net/rxrpc/conn_event.c | 26 +++---
1 file chang
Oops. Please ignore this, I just sent the first and last patches, not the
range :-(
David
Heikki,
On Tue, Aug 30, 2016 at 01:04:37PM +0300, Heikki Krogerus wrote:
> Hi Oliver,
>
> On Tue, Aug 30, 2016 at 11:32:01AM +0200, Oliver Neukum wrote:
> > On Mon, 2016-08-29 at 15:36 +0300, Heikki Krogerus wrote:
> > > +What: /sys/class/typec//current_data_role
> > > +Date: Ju
The call pointer in a channel on a connection will be NULL if there's no
active call on that channel. rxrpc_abort_calls() needs to check for this
before trying to take the call's state_lock.
Signed-off-by: David Howells
---
net/rxrpc/conn_event.c | 26 +++---
1 file chang
x/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rewrite
Tagged thusly:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
rxrpc-rewrite-20160830-1
David
---
David Howells (8):
rxrpc: Fix a potential NULL-pointer deref in rxrpc_abort_calls
rxrpc: Calls
We should #include linux/random.h to use get_random().
Signed-off-by: David Howells
---
fs/afs/main.c |1 +
1 file changed, 1 insertion(+)
diff --git a/fs/afs/main.c b/fs/afs/main.c
index 35de0c04729f..0b187ef3b5b7 100644
--- a/fs/afs/main.c
+++ b/fs/afs/main.c
@@ -14,6 +14,7 @@
#include
Use call->peer rather than call->conn->params.peer as call->conn may become
NULL.
Signed-off-by: David Howells
---
net/rxrpc/call_event.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/net/rxrpc/call_event.c b/net/rxrpc/call_event.c
index 02fe4a4b60d9..de72de66
Add a trace event for debuging rxrpc_call struct usage.
Signed-off-by: David Howells
---
include/trace/events/rxrpc.h | 39 ++
net/rxrpc/ar-internal.h | 19 ++---
net/rxrpc/call_accept.c |5 +-
net/rxrpc/call_event.c | 11 ++---
net/rxrpc/call_objec
Condense the terminal states of a call state machine to a single state,
plus a separate completion type value. The value is then set, along with
error and abort code values, only when the call is transitioned to the
completion state.
Helpers are provided to simplify this.
Signed-off-by: David Ho
On Tue, 30 Aug 2016 19:50:20 +0800
Baolin Wang wrote:
> Hi,
>
> On 22 August 2016 at 12:23, Baolin Wang wrote:
> > For system debugging, we usually want to know who sets one alarm timer, the
> > time of the timer, when the timer started and fired and so on. Thus adding
> > tracepoints can help
Remove one #ifndef'd-out variable and a couple of excessive blank lines.
Signed-off-by: David Howells
---
fs/afs/cmservice.c |6 --
1 file changed, 6 deletions(-)
diff --git a/fs/afs/cmservice.c b/fs/afs/cmservice.c
index 85737e96ab8b..ca32d891bbc3 100644
--- a/fs/afs/cmservice.c
+++ b
From: Voker57
These initialization are missing and causing bam not to init
Signed-off-by: Iaroslav Gridin
---
drivers/dma/qcom/bam_dma.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/drivers/dma/qcom/bam_dma.c b/drivers/dma/qcom/bam_dma.c
index 03c4eb3..faae0c8 1006
Pass struct socket * to more rxrpc kernel interface functions. They should
be starting from this rather than the socket pointer in the rxrpc_call
struct if they need to access the socket.
I have left:
rxrpc_kernel_is_data_last()
rxrpc_kernel_get_abort_code()
rxrpc_kernel_
Provide a function so that kernel users, such as AFS, can ask for the peer
address of a call:
void rxrpc_kernel_get_peer(struct rxrpc_call *call,
struct sockaddr_rxrpc *_srx);
In the future the kernel service won't get sk_buffs to look inside.
Further, this allows
On Tue, Aug 30, 2016 at 11:25 AM, Roland Singer
wrote:
> I tried these scenarios:
>
> 1. Booted the system without the bbswitch module. The nouveau module
>was loaded and is responsible for the power management of the GPU.
>The graphical session freezes after some minutes...
>
> 2. Booted
On Mon 2016-08-29 12:12:49, Chris Metcalf wrote:
> When doing an nmi backtrace of many cores, most of which are idle,
> the output is a little overwhelming and very uninformative. Suppress
> messages for cpus that are idling when they are interrupted and just
> emit one line, "NMI backtrace for N
Hi Lee,
Thanks for reviewing.
On Tue, 30 Aug 2016, Lee Jones wrote:
> On Fri, 26 Aug 2016, Peter Griffin wrote:
>
> > slim core is used as a basis for many IPs in the STi
> > chipsets such as fdma and demux. To avoid duplicating
> > the elf loading code in each device driver a slim
> > rproc dr
On 30 August 2016 at 16:25, Roland Singer wrote:
> I tried these scenarios:
>
> 1. Booted the system without the bbswitch module. The nouveau module
>was loaded and is responsible for the power management of the GPU.
>The graphical session freezes after some minutes...
>
> 2. Booted the sy
On Tue, Aug 30, 2016 at 11:44 AM, Ilia Mirkin wrote:
> On Tue, Aug 30, 2016 at 11:25 AM, Roland Singer
> wrote:
>> I tried these scenarios:
>>
>> 1. Booted the system without the bbswitch module. The nouveau module
>>was loaded and is responsible for the power management of the GPU.
>>The
On Tue, Aug 30, 2016 at 8:56 PM, Maxime Ripard
wrote:
> Hi,
>
> On Tue, Aug 30, 2016 at 08:22:23PM +0800, Chen-Yu Tsai wrote:
>> The KMS helpers (drm_atomic_helper_check_modeset/mode_fixup) pass
>> encoder->bridge directly to drm_bridge_mode_fixup, which expects a
>> valid pointer, or NULL (in whi
Don't expose skbs to in-kernel users, such as the AFS filesystem, but
instead provide a notification hook the indicates that a call needs
attention and another that indicates that there's a new call to be
collected.
This makes the following possibilities more achievable:
(1) Call refcounting can
reception for AFS.
The patch can be found here also:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rewrite
Tagged thusly:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
rxrpc-rewrite-20160830-2
David
---
David
On 26/08/16 18:44, Stephen Boyd wrote:
> On 08/26, Paul Burton wrote:
>> diff --git a/Documentation/devicetree/bindings/clock/img,boston-clock.txt
>> b/Documentation/devicetree/bindings/clock/img,boston-clock.txt
>> new file mode 100644
>> index 000..c01ea60
>> --- /dev/null
>> +++ b/Documenta
This set of patches fixes QCE digest code, preventing lockups and incorrect
results.
From: Voker57
Current code avoids supplying scatterlist containing more data than used
to DMA. This leads to dropping data from scatterlists which would
leave some for next run.
Signed-off-by: Iaroslav Gridin
---
drivers/crypto/qce/sha.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/driv
From: Voker57
If total data amount to hash is zero, we cannot submit it to QCE,
since it locks up on zero-sized updates. So, return pre-computed
SHA256/SHA1 hash.
Signed-off-by: Iaroslav Gridin
---
drivers/crypto/qce/sha.c | 27 ---
1 file changed, 24 insertions(+), 3 de
From: Voker57
Calling QCE finalization when hash have already been finalized causes
a lockup. Avoid it by introducing finalized flag.
Signed-off-by: Iaroslav Gridin
---
drivers/crypto/qce/sha.c | 6 ++
drivers/crypto/qce/sha.h | 1 +
2 files changed, 7 insertions(+)
diff --git a/drivers/cr
From: Voker57
Zero-sized updates lock QCE, so ensure there's always some data left
for the final update, up to blocksize.
Signed-off-by: Iaroslav Gridin
---
drivers/crypto/qce/sha.c | 30 --
1 file changed, 20 insertions(+), 10 deletions(-)
diff --git a/drivers/cryp
Guennadi Liakhovetski writes:
> Hi Robert,
>
> On Mon, 29 Aug 2016, Robert Jarzmik wrote:
>
>> Remove the soc_camera adherence. Mostly the change removes the power
>> manipulation provided by soc_camera, and instead :
>> - powers on the sensor when the s_power control is activated
>> - powers o
Hello, Linus.
Two fixes for cgroup.
* There still was a hole in enforcing cpuset rules, fixed by Li.
* Recent switch to global percpu_rwseom for threadgroup locking
revealed a couple issues in how percpu_rwsem is implemented and used
by cgroup. Balbir found that the read locking section was
On 28 August 2016 at 16:00, Madhavan Srinivasan
wrote:
> Patchset to extend PERF_SAMPLE_REGS_INTR to include
> platform specific PMU registers.
>
> Patchset applies cleanly on tip:perf/core branch
>
> It's a perennial request from hardware folks to be able to
> see the raw values of the pmu regist
Hello, Linus.
Two libata driver specific fixes for v4.8-rc4. Nothing too scary.
Thanks.
The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc:
Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel
On 30/08/2016 17:53, Iaroslav Gridin wrote:
> From: Voker57
>
> If total data amount to hash is zero, we cannot submit it to QCE,
> since it locks up on zero-sized updates. So, return pre-computed
> SHA256/SHA1 hash.
> Signed-off-by: Iaroslav Gridin
> ---
> drivers/crypto/qce/sha.c | 27 +++
Hi Guodong,
On 25/08/2016 04:00, Guodong Xu wrote:
> To support display in Debian on HiKey, cma heap is used to allocate
> graphic buffers. The default size of CMA is 16 MB which is not enough.
>
> Increase the default CMA size to 128 MB.
>
> cc: Fathi Boudra
> cc: John Stultz
> cc: Xinliang L
On (08/29/16 14:31), Aaron Lu wrote:
>
> The global zero page is used to satisfy an anonymous read fault. If
> THP(Transparent HugePage) is enabled then the global huge zero page is used.
> The global huge zero page uses an atomic counter for reference counting
> and is allocated/freed dynamically
On Mon, Aug 29, 2016 at 11:36 PM, Christoph Hellwig wrote:
> On Mon, Aug 29, 2016 at 04:20:43PM -0700, Andy Lutomirski wrote:
>> The "Set Features" command (section 5.15) Figure 103 says:
>>
>> If using PRPs, this field shall not be a pointer to a PRP List as the
>> data buffer may not cross more
On Thu, Aug 25, 2016 at 3:32 AM, Mickaël Salaün wrote:
> Hi,
>
> This series is a proof of concept to fill some missing part of seccomp as the
> ability to check syscall argument pointers or creating more dynamic security
> policies. The goal of this new stackable Linux Security Module (LSM) calle
Baoyou Xie writes:
> On 29 August 2016 at 23:31, Rafał Miłecki wrote:
>
> On 29 August 2016 at 14:39, Baoyou Xie wrote:
> > We get 1 warning when build kernel with W=1:
> > drivers/net/wireless/broadcom/brcm80211/brcmfmac/tracepoint.c:23:6:
> warning: no previous prototype for '
This patch makes it possible to use the current filter
framework with address filters. That way address filters for
HW tracers such as CoreSight and IntelPT can be communicated
to the kernel drivers.
CC: Alexander Shishkin
Signed-off-by: Mathieu Poirier
---
Changes for V2:
- Rebased to v4.8-r
Hi Ted,
On 2016/8/30 3:08, Theodore Ts'o wrote:
> On Mon, Aug 29, 2016 at 10:55:47PM +0800, Chao Yu wrote:
>> Hi Ted, Jaegeuk,
>>
>> Since encryption functionality in ext4/f2fs was exported to vfs as fscrypot
>> module, more filesystems can use it, I'm not sure, maybe other fs will
>> traverse
>>
On 16/08/16 11:02, Vincent Guittot wrote:
> On 19 July 2016 at 14:40, Juri Lelli wrote:
> > ARM systems may be configured to have cpus with different power/performance
> > characteristics within the same chip. In this case, additional information
> > has to be made available to the kernel (the sch
On 29/08/16 08:55, Felipe Balbi wrote:
>
> Hi,
>
> Felipe Ferreri Tonello writes:
>>> Felipe Ferreri Tonello writes:
> "Felipe F. Tonello" writes:
>> The default_length parameter of alloc_ep_req was not really necessary
>> and gadget drivers would almost always create an inline f
On 28 August 2016 at 16:00, Madhavan Srinivasan
wrote:
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index 274288819829..e16bf4d057d1 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -5371,16 +5371,24 @@ u64 __attribute__((weak)) perf_arch_reg_value(struct
> pe
patch can be found here also:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rewrite
Tagged thusly:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
rxrpc-rewrite-20160830-2v2
David
---
David Howells (1):
rxrpc: Do
From: Sergey Senozhatsky
__printk_nmi_flush() can be called from nmi_panic(), therefore it has to
test whether it's executed in NMI context and thus must route the messages
through deferred printk() or via direct printk(). Except for two places
where __printk_nmi_flush() does unconditional direct
Hi Jaegeuk,
On 2016/8/30 0:45, Jaegeuk Kim wrote:
> Hi Chao,
>
> On Sun, Aug 28, 2016 at 09:20:46PM +0800, Chao Yu wrote:
>> From: Chao Yu
>>
>> tests/generic/251 of fstest suit complains us with below message:
>>
>> [ cut here ]
>> invalid opcode: [#1] PREEMPT SMP
>
We get some warnings when building kernel with W=1:
drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf117.c:222:1: warning: no previous
prototype for 'gf117_grctx_generate_main' [-Wmissing-prototypes]
drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxnv50.c:255:1: warning: no previous
prototype for 'nv50_grctx
This patch adds PMU driver specific configuration to the parser
infrastructure by preceding any term with the '@' letter. As such
doing something like:
perf record -e some_event/@cfg1,@cfg2=config/ ...
will see 'cfg1' and 'cfg2=config' being added to the list of evsel config
terms. Token 'cfg1'
Original blurb:
---
This patchset adds the possiblity of specifying PMU driver configuration
directly from the perf command line. Anything that falls within the
event specifiers '/.../' and that is preceded by the '@' symbol is
treated as a configurable. Two formats are supported, @c
Adding the required mechanic allowing 'perf list pmu' to
discover coresight ETM/PTM tracers.
Signed-off-by: Mathieu Poirier
Acked-by: Adrian Hunter
Acked-by: Jiri Olsa
---
MAINTAINERS| 1 +
tools/perf/Makefile.config | 11 +++
tools/perf/arch/arm/util/Build |
Coresight ETMs are IP blocks used to perform HW assisted tracing
on a CPU core. This patch introduce the required auxiliary API
functions allowing the perf core to interact with a tracer.
Signed-off-by: Mathieu Poirier
Acked-by: Adrian Hunter
---
MAINTAINERS | 4 +
to
On 08/22/2016 10:35 AM, Alexey Brodkin wrote:
> With commit e3d09ec8126f ("tools lib traceevent: Export dynamic symbols
> used by traceevent plugins") we started to add "--dynamic-list" in
> LDFLAGS. One side-effect of that was inability to build really
> statically-linked perf.
>
> I.e. even if "L
On Fri, Aug 26, 2016 at 03:56:40PM +0100, Peter Griffin wrote:
> config STM32_DMA
> bool "STMicroelectronics STM32 DMA support"
> depends on ARCH_STM32
> @@ -567,7 +580,6 @@ config ZX_DMA
> help
> Support the DMA engine for ZTE ZX296702 platform devices.
>
> -
unrelat
Sorry about this, stgit mail is playing silly devils and not inserting the
patch numbers if there's a cover letter but only one patch:-/
David
On Tue, Aug 30, 2016 at 7:53 AM, Dan Williams wrote:
> On Mon, Aug 29, 2016 at 7:37 PM, Darrick J. Wong
> wrote:
>> On Mon, Aug 29, 2016 at 06:50:05PM -0700, Dan Williams wrote:
>>> [ Adding Darrick on the off chance that this triggers an "aha, of
>>> course it does!" ]
>>
>> Aha! Of course it d
Currently, there is no mechanism to filter events based on containers.
perf -G can be used, but it will not filter events for the containers
created after perf is invoked, making it difficult to assess/analyze
performance issues of multiple containers at once. This limitation can
be overcome, if th
With the introduction of container identifier entry in sample data,
perf sample data can now be analyzed with regard to containers. This
patch adds cid entry related support in perf tool.
Shown below is the output of perf report, sorted based on cid, on a
system that was running three containers a
This patch adds a PMU callback so that drivers can process the
command line configuration elements found in evsel::config_terms.
The callback is then used in various places where events can be
specified.
Signed-off-by: Mathieu Poirier
Acked-by: Jiri Olsa
---
tools/perf/builtin-record.c | 9 +++
Using the PMU::set_drv_config() callback to enable the CoreSight
sink that will be used for the trace session.
Signed-off-by: Mathieu Poirier
Acked-by: Jiri Olsa
---
tools/perf/arch/arm/util/cs-etm.c | 56 +++
tools/perf/arch/arm/util/cs-etm.h | 3 +++
tools
Hi Vincent,
On 16/08/16 10:20, Vincent Guittot wrote:
> Hi Juri,
>
>
> On 19 July 2016 at 14:40, Juri Lelli wrote:
[...]
> > +static int
> > +init_cpu_capacity_callback(struct notifier_block *nb,
> > + unsigned long val,
> > + void *data)
> >
On Tue, Aug 30, 2016 at 8:32 AM, Chris Metcalf wrote:
> On 8/30/2016 3:58 AM, Peter Zijlstra wrote:
>>
>> On Mon, Aug 29, 2016 at 12:40:32PM -0400, Chris Metcalf wrote:
>>>
>>> On 8/29/2016 12:33 PM, Peter Zijlstra wrote:
On Tue, Aug 16, 2016 at 05:19:27PM -0400, Chris Metcalf wrote:
>>>
alloc_ordered_workqueue() with WQ_MEM_RECLAIM set, replaces
deprecated create_singlethread_workqueue(). This is the identity
conversion.
The workqueue "wq" queues multiple work items viz
&bond->mcast_work, &nnw->work, &bond->mii_work, &bond->arp_work,
&bond->alb_work, &bond->mii_work, &bond->ad_wo
The workqueue "pegasus_workqueue" queues a single work item per pegasus
instance and hence it doesn't require execution ordering. Hence,
alloc_workqueue has been used to replace the deprecated
create_singlethread_workqueue instance.
The WQ_MEM_RECLAIM flag has been set to ensure forward progress u
Hi,
On Mon, Aug 29, 2016 at 6:02 AM, Peter Zijlstra wrote:
>
> On Mon, Aug 29, 2016 at 12:03:09PM +0200, Peter Zijlstra wrote:
> > @@ -1802,8 +1802,18 @@ event_sched_out(struct perf_event *event,
> >
> > event->tstamp_stopped = tstamp;
> > event->pmu->del(event, 0);
> > - event->o
The workqueue "led_wq" queues a single work item &led_task and hence
doesn't require ordering. It is involved in managing when and which
chassis LCD/LED gets updated and hence, is not being used on a memory
reclaim path. Hence, it has been converted to use system_wq.
System workqueues have been ab
The workqueue "creg_wq" queues a single work item viz
&card->creg_ctrl.done_work and hence it doesn't require execution
ordering. Hence, alloc_workqueue has been used to replace the
deprecated create_singlethread_workqueue instance.
The workqueue "event_wq" queues a single work item viz &card->eve
On Tue, Aug 30, 2016 at 09:25:45AM -0700, Dan Williams wrote:
> On Tue, Aug 30, 2016 at 7:53 AM, Dan Williams
> wrote:
> > On Mon, Aug 29, 2016 at 7:37 PM, Darrick J. Wong
> > wrote:
> >> On Mon, Aug 29, 2016 at 06:50:05PM -0700, Dan Williams wrote:
> >>> [ Adding Darrick on the off chance that
On 16-08-30 22:02:47, Bhaktipriya Shridhar wrote:
> The workqueue "pegasus_workqueue" queues a single work item per pegasus
> instance and hence it doesn't require execution ordering. Hence,
> alloc_workqueue has been used to replace the deprecated
> create_singlethread_workqueue instance.
>
> The
From: Colin Ian King
port is deferenced before it is null sanity checked, hence
we potentially have a null pointer dereference bug. Instead,
initialise trl_enabled from port->fcs->bfa after we are sure
port is not null.
Signed-off-by: Colin Ian King
---
drivers/scsi/bfa/bfa_fcs_lport.c | 4 ++-
On 8/30/2016 6:37 AM, Bjorn Helgaas wrote:
On Mon, Aug 29, 2016 at 05:37:09PM -0700, Ray Jui wrote:
Hi Bjorn,
On 8/24/2016 10:54 AM, Bjorn Helgaas wrote:
[+cc Ray, Scott, Jon, bcm-kernel-feedback-list]
On Wed, Aug 24, 2016 at 03:07:52PM +0800, Ley Foon Tan wrote:
On Mon, Aug 22, 2016 at 11
On Wed, Aug 24, 2016 at 10:13:27AM +0200, Mike Looijmans wrote:
> Add devicetree property for early initialization of the fan controller
> to prevent overheating, for example when resetting the board while the
> fan was completely turned off.
>
> Signed-off-by: Mike Looijmans
> ---
> Documentati
From: Ankitprasad Sharma
Some modules, like i915.ko, needs to detect when certain ACPI features are
active inorder to prevent corruption on contended resources.
In particular, use of BIOS RapidStart Technology may corrupt the contents of
the reserved graphics memory, due to unalarmed hibernation.
Jaegeuk Kim writes:
> Hello,
>
> On Sat, Aug 27, 2016 at 10:13:34AM +0800, Fengguang Wu wrote:
>> Hi Jaegeuk,
>>
>> > > >> > - [lkp] [f2fs] b93f771286: aim7.jobs-per-min -81.2% regression
>> > > >> >
>> > > >> > The disk is 4 12G ram disk, and setup RAID0 on them via mdadm. The
>> > > >> > step
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Sunday, August 21, 2016 2:05 PM
> To: Kershner, David A
>
> On Fri, Jun 10, 2016 at 11:23:56PM -0400, David Kershner wrote:
> > visorbus is currently located at drivers/staging/visorbus,
> > this patch moves
Hi Boris,
> We recently faced some problems when using an BT uart chip interfaced
> through the H5 proto (rtk_h5). Here are the logs of the 2 different
> issues we had when closing the line discipline (actually, restoring
> the previous one) [1][2]. I know the kernel is Tainted in those logs,
> bu
The workqueue "dm_bufio_wq" queues a single work item &dm_bufio_work and
hence it doesn't require execution ordering. Hence, alloc_workqueue has
been used to replace the deprecated create_singlethread_workqueue instance.
The WQ_MEM_RECLAIM flag has been set since md / dm are block multi disk
drive
Hi Boris,
> hci_uart_tty_close() is cancelling any pending write work, but some
> hci_uart_proto implementations might re-schedule this work after its
> cancellation (by calling hci_uart_tx_wakeup()).
>
> Make sure the write work is not re-scheduled in our back while we're
> closing the device.
>
Hi Boris,
> The H5 timer should not be rescheduled while we are closing the device,
> otherwise it's defeating the del_timer_sync() call done in h5_close().
>
> Signed-off-by: Boris Brezillon
> ---
> drivers/bluetooth/hci_h5.c | 7 ++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> dif
On Tue 30 Aug 05:34 PDT 2016, Lee Jones wrote:
Thanks for your review Lee.
> On Fri, 26 Aug 2016, Peter Griffin wrote:
[..]
> > diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig
> > index 1a8bf76a..06765e0 100644
> > --- a/drivers/remoteproc/Kconfig
> > +++ b/drivers/remoteproc
Hi Boris,
> The HCI_UART_TX_WAKEUP flag checking is racy and some HCI_UART_TX_WAKEUP
> events can be lost.
>
> Signed-off-by: Boris Brezillon
> ---
> drivers/bluetooth/hci_ldisc.c | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/bluetooth/hci_ldisc.c b/drivers/blueto
On Tue, Aug 23, 2016 at 12:48:11AM -0400, Sinan Kaya wrote:
> spin_lock_init(&lldev->lock);
> - tasklet_init(&lldev->rst_task, hidma_ll_abort, (unsigned long)lldev);
??
This is not described in changlog? If you are not using in anywhere else,
then rst_task variable should be removed to
Hi Linus,
The following changes since commit 694d0d0bb2030d2e36df73e2d23d5770511dbc8d:
Linux 4.8-rc2 (2016-08-14 19:11:36 -0700)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.8-3
for you to fetch changes up to 98b0f80c2396224b
On 08/30, Peter Zijlstra wrote:
> On Tue, Aug 30, 2016 at 03:04:27PM +0200, Oleg Nesterov wrote:
> > On 08/30, Peter Zijlstra wrote:
> > >
> > > /*
> > >* Ensure we load p->on_rq _after_ p->state, otherwise it would
> > >* be possible to, falsely, observe p->on_rq == 0 and get stuck
> > >
Heikki,
On Tue, Aug 30, 2016 at 11:22:27AM +0300, Heikki Krogerus wrote:
>
> How about if I add the "supports_usb_power_delivery" attribute for the
> partners instead to give some details about them. Any objections?
>
After looking into the code again, I assume the idea is to have the existing
s
401 - 500 of 842 matches
Mail list logo
