[PATCH 3/8 V2] staging: rts5208: fix comment blocks style in rtsx_chip.h

This patch fixes the following checkpatch.pl warning in rtsx_chip.h: WARNING: Block comments use a trailing */ on a separate line Signed-off-by: Sergio Paracuellos --- drivers/staging/rts5208/rtsx_chip.h | 52 +++-- 1 file changed,

Re: [PATCH] usb: gadget: udc: atmel: fix endpoint name

Le 16/09/2016 à 10:36, Nicolas Ferre a écrit : > Le 15/09/2016 à 17:07, Alexandre Belloni a écrit : >> Since commit c32b5bcfa3c4 ("ARM: dts: at91: Fix USB endpoint nodes"), >> atmel_usba_udc fails with: >> >> [ cut here ] >> WARNING: CPU: 0 PID: 0 at

[PATCH] kcov: do not instrument lib/stackdepot.c

There's no point in collecting coverage from lib/stackdepot.c, as it is not a function of syscall inputs. Disabling kcov instrumentation for that file will reduce the coverage noise level. Signed-off-by: Alexander Potapenko --- lib/Makefile | 1 + 1 file changed, 1

[LKP] Tips to append base tree info by git-format-patch

Hi, Here's a tip for people who've been bothered by messages sent by kbuild bot like below: [auto build test ERROR on net/master] [also build test ERROR on v4.8-rc3 next-20160825] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] It means that

Re: [PATCH] mm: warn about allocations which stall for too long

Michal Hocko wrote: > @@ -3659,6 +3661,15 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int > order, > else > no_progress_loops++; > > + /* Make sure we know about allocations which stall for too long */ > + if (!(gfp_mask & __GFP_NOWARN) && time_after(jiffies,

Re: [PATCH v3 1/2] mm, proc: Fix region lost in /proc/self/smaps

On Fri 23-09-16 15:50:51, Michal Hocko wrote: > On Fri 23-09-16 21:12:33, Robert Ho wrote: [...] > > @@ -786,7 +791,7 @@ static int show_smap(struct seq_file *m, void *v, int > > is_pid) > >"KernelPageSize: %8lu kB\n" > >"MMUPageSize:%8lu kB\n" > >

Re: [PATCH] kcov: do not instrument lib/stackdepot.c

On Fri, Sep 23, 2016 at 4:29 PM, Alexander Potapenko wrote: > There's no point in collecting coverage from lib/stackdepot.c, as it is > not a function of syscall inputs. Disabling kcov instrumentation for > that file will reduce the coverage noise level. > > Signed-off-by:

[PATCH 12/16] perf intel-pt: Add a helper function for processing AUXTRACE_INFO

Add a helper function 'intel_pt_has()' to make it easier to determine which members the AUXTRACE_INFO event contains. Signed-off-by: Adrian Hunter --- tools/perf/util/intel-pt.c | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git

[PATCH 13/16] perf intel-pt: Record address filter in AUXTRACE_INFO event

The address filter is needed to help decode the trace, so store it in the AUXTRACE_INFO event. Signed-off-by: Adrian Hunter --- tools/perf/arch/x86/util/intel-pt.c | 51 ++--- tools/perf/util/intel-pt.h | 3 +-- 2 files changed,

[PATCH 15/16] perf intel-pt: Enable decoder to handle TIP.PGD with missing IP

When address filters are used, the decoder must detect the end of a filter region (or a branch into a tracestop region) by matching Packet Generation Disabled (TIP.PGD) packets against the object code using the IP given in the packet. However, due to errata SKL014 "Intel PT TIP.PGD May Not Have

[PATCH 14/16] perf intel-pt: Read address filter from AUXTRACE_INFO event

Read the address filter from the AUXTRACE_INFO event in preparation for using it to assist in decoding. Signed-off-by: Adrian Hunter --- tools/perf/util/intel-pt.c | 51 ++ 1 file changed, 51 insertions(+) diff --git

[PATCH 16/16] perf intel-pt: Fix decoding when there are address filters

Due to errata SKL014 "Intel PT TIP.PGD May Not Have Target IP Payload", the Intel PT decoder needs to match address filters against TIP.PGD packets. Parse the address filters and implement the decoder's 'pgd_ip()' callback to match the IP against the filter regions. Signed-off-by: Adrian Hunter

[PATCH 09/16] perf intel-pt: Fix snapshot overlap detection decoder errors

Fix occasional decoder errors decoding trace data collected in snapshot mode. Snapshot mode can take successive snapshots of trace which might overlap. The decoder checks whether there is an overlap but only looks at the current and previous buffer. However buffers that do not contain

[PATCH 03/16] perf script: Fix vanished idle symbols

Patch "perf symbols: Mark if a symbol is idle in the library" causes idle symbols to vanish from perf script output. That is because print functions suppress symbols marked as 'idle'. However, suppression of 'idle' functions is only used by 'perf top' and 'perf top' does not use the print

[PATCH 02/16] perf tools: Fix MMAP event synthesis broken by MAP_HUGETLB change

Patch "perf record: Mark MAP_HUGETLB when synthesizing mmap events") breaks MMAP event synthesis. The executable name comparison will match any name if the length is zero, resulting in all the user space maps becoming anonymous. This is particularly noticeable with system-wide traces. Example:

[PATCH 08/16] perf tools: Increase debug level of SDT debug messages

Two SDT debug messages can occur for every DSO which is too noisy. Consequently, increase debug level of SDT messages. Signed-off-by: Adrian Hunter --- tools/perf/util/build-id.c | 4 ++-- tools/perf/util/probe-file.c | 2 +- 2 files changed, 3 insertions(+), 3

[PATCH 0/5] ACPI / gpio: Updates to properties

Hi, This series brings couple of useful GPIO related properties from Device Tree to ACPI _DSD device properties: - Names for GPIO lines - GPIO hogging - Holes in GPIO property lists We are using these to get Intel Galileo better supported in the mainline kernel (but these may be useful

Re: [RFC PATCH v3] docs-rst: user: add MAINTAINERS

On Fri, 23 Sep 2016 12:07:33 -0300 Mauro Carvalho Chehab wrote: > including MAINTAINERS using ReST is tricky, because all > maintainer's entries are like: So I'm generally in favor of moving things over to RST, but I have to ask: what's the payoff for doing that with

[RFC PATCH v3] docs-rst: user: add MAINTAINERS

including MAINTAINERS using ReST is tricky, because all maintainer's entries are like: FOO SUBSYSTEM: M: My Name L: mailing@list S: Maintained F: foo/bar On ReST, this would be displayed on a single line. Using alias, like |M|, |L|, ... won't solve, as an alias in Sphinx doesn't accept

Re: [PATCH 07/19] ahci: st: Remove STiH416 dt example

On Wed, Sep 14, 2016 at 02:27:45PM +0100, Peter Griffin wrote: > This platform is being removed from the kernel so remove > the dt example. > > Signed-off-by: Peter Griffin > Cc: > Cc: > Cc: > --- >

[PATCH net-next 12/15] rxrpc: Add data Tx tracepoint and adjust Tx ACK tracepoint

Add a tracepoint to log transmission of DATA packets (including loss injection). Adjust the ACK transmission tracepoint to include the packet serial number and to line this up with the DATA transmission display. Signed-off-by: David Howells ---

[PATCH net-next 10/15] rxrpc: Don't call the tx_ack tracepoint if don't generate an ACK

rxrpc_send_call_packet() is invoking the tx_ack tracepoint before it checks whether there's an ACK to transmit (another thread may jump in and transmit it). Fix this by only invoking the tracepoint if we get a valid ACK to transmit. Further, only allocate a serial number if we're going to

[PATCH net-next 04/15] rxrpc: Should be using ktime_add_ms() not ktime_add_ns()

ktime_add_ms() should be used to add the resend time (in ms) rather than ktime_add_ns(). Signed-off-by: David Howells --- net/rxrpc/call_event.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/rxrpc/call_event.c b/net/rxrpc/call_event.c index

[PATCH net-next 11/15] rxrpc: Add a tracepoint for the call timer

Add a tracepoint to log call timer initiation, setting and expiry. Signed-off-by: David Howells --- include/trace/events/rxrpc.h | 36 net/rxrpc/ar-internal.h | 13 - net/rxrpc/call_event.c |7 ---

[PATCH RT 8/9] fs/dcache: incremental fixup of the retry routine

3.12.63-rt85-rc2 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior It has been pointed out by tglx that on UP the non-RT task could spin its entire time slice because the lock owner is preempted.

[PATCH RT 6/9] net: add a lock around icmp_sk()

3.12.63-rt85-rc2 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior It looks like the this_cpu_ptr() access in icmp_sk() is protected with local_bh_disable(). To avoid missing serialization in -RT I

[PATCH RT 4/9] scsi/fcoe: Fix get_cpu()/put_cpu_light() imbalance in fcoe_recv_frame()

3.12.63-rt85-rc2 stable review patch. If anyone has any objections, please let me know. -- From: Mike Galbraith During master->rt merge, I stumbled across the buglet below. Fix get_cpu()/put_cpu_light() imbalance. Cc: stable...@vger.kernel.org

[PATCH RT 9/9] Linux 3.12.63-rt85-rc2

3.12.63-rt85-rc2 stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (Red Hat)" --- localversion-rt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/localversion-rt b/localversion-rt index

[PATCH RT 3/9] sched: lazy_preempt: avoid a warning in the !RT case

3.12.63-rt85-rc2 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Steven Rostedt ---

Re: [PATCH 4.4 000/118] 4.4.22-stable review

On Fri, Sep 23, 2016 at 05:11:48PM +0200, Greg Kroah-Hartman wrote: > On Fri, Sep 23, 2016 at 06:25:33AM -0700, Guenter Roeck wrote: > > On 09/23/2016 01:08 AM, Greg Kroah-Hartman wrote: > > > On Thu, Sep 22, 2016 at 08:01:35PM -0700, Guenter Roeck wrote: > > > > e5767a13d7cb ("cxl: use

[PATCH RT 2/8] timers: wakeup all timer waiters without holding the base lock

3.10.103-rt115-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior There should be no need to hold the base lock during the wakeup. There should be no boosting involved, the wakeup list has its own

[PATCH RT 8/8] Linux 3.10.103-rt115-rc1

3.10.103-rt115-rc1 stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (Red Hat)" --- localversion-rt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/localversion-rt b/localversion-rt index

[PATCH RT 4/8] net: add back the missing serialization in ip_send_unicast_reply()

3.10.103-rt115-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Some time ago Sami Pietikainen reported a crash on -RT in ip_send_unicast_reply() which was later fixed by Nicholas Mc Guire

[PATCH RT 7/9] fs/dcache: resched/chill only if we make no progress

3.12.63-rt85-rc2 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Upstream commit 47be61845c77 ("fs/dcache.c: avoid soft-lockup in dput()") changed the condition _when_ cpu_relax() / cond_resched()

[PATCH RT 0/9] Linux 3.12.63-rt85-rc2

Dear RT Folks, This is the RT stable review cycle of patch 3.12.63-rt85-rc2. Please scream at me if I messed something up. Please test the patches too. The -rc release will be uploaded to kernel.org and will be deleted when the final release is out. This is just a review release (or release

[PATCH RT 6/8] fs/dcache: resched/chill only if we make no progress

3.10.103-rt115-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Upstream commit 47be61845c77 ("fs/dcache.c: avoid soft-lockup in dput()") changed the condition _when_ cpu_relax() /

[PATCH RT 7/8] fs/dcache: incremental fixup of the retry routine

3.10.103-rt115-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior It has been pointed out by tglx that on UP the non-RT task could spin its entire time slice because the lock owner is preempted.

Re: [PATCH RT 0/9] Linux 3.12.63-rt85-rc2

On Fri, 23 Sep 2016 11:28:26 -0400 Steven Rostedt wrote: > Dear RT Folks, > > This is the RT stable review cycle of patch 3.12.63-rt85-rc2. Bah, it's suppose to be rc1. The patch has the change correct, even though its subject is wrong as well. -- Steve

[PATCH RT 5/8] net: add a lock around icmp_sk()

3.10.103-rt115-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior It looks like the this_cpu_ptr() access in icmp_sk() is protected with local_bh_disable(). To avoid missing serialization in -RT I

[PATCH RT 1/9] timers: wakeup all timer waiters

3.12.63-rt85-rc2 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior The base lock is dropped during the invocation if the timer. That means it is possible that we have one waiter while timer1 is

[PATCH RT 1/8] timers: wakeup all timer waiters

3.10.103-rt115-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior The base lock is dropped during the invocation if the timer. That means it is possible that we have one waiter while timer1 is

[PATCH RT 0/8] Linux 3.10.103-rt115-rc1

Dear RT Folks, This is the RT stable review cycle of patch 3.10.103-rt115-rc1. Please scream at me if I messed something up. Please test the patches too. The -rc release will be uploaded to kernel.org and will be deleted when the final release is out. This is just a review release (or release

[PATCH RT 5/9] net: add back the missing serialization in ip_send_unicast_reply()

3.12.63-rt85-rc2 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Some time ago Sami Pietikainen reported a crash on -RT in ip_send_unicast_reply() which was later fixed by Nicholas Mc Guire

[PATCH RT 2/9] timers: wakeup all timer waiters without holding the base lock

3.12.63-rt85-rc2 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior There should be no need to hold the base lock during the wakeup. There should be no boosting involved, the wakeup list has its own

Re: [PATCH 1/1] lib/ioremap.c: avoid endless loop under ioremapping page unaligned ranges

On 2016/9/23 22:42, Tejun Heo wrote: > Hello, > > On Wed, Sep 21, 2016 at 12:19:53PM +0800, zijun_hu wrote: >> From: zijun_hu >> >> endless loop maybe happen if either of parameter addr and end is not >> page aligned for kernel API function ioremap_page_range() >> >> in order

Re: [PATCH] sched/fair: Do not decay new task load on first enqueue

Hi Matt, On 23 September 2016 at 13:58, Matt Fleming wrote: > Since commit 7dc603c9028e ("sched/fair: Fix PELT integrity for new > tasks") ::last_update_time will be set to a non-zero value in > post_init_entity_util_avg(), which leads to p->se.avg.load_avg being >

Patchwork [1/1] staging: ks7010: Attempt to structure and format to standards

Mostly code formatting, unapologetically a stepping stone for a potential refactoring with a knowledge seeking, following complete disclosure, ultimate goal. In case this fails, my backup plan is to have the world's record for the quickest kernel patch dismissal, either way it's a win. diff

Re: [dm-devel] [RFC][PATCH] dm: Remove dm_bufio_cond_resched()

On 09/23/16 00:34, Peter Zijlstra wrote: Is anybody still using PREEMPT_NONE? Most workloads also care about latency to some extend. Lots of code has explicit cond_resched() and doesn't worry. From a SLES11 system: $ grep PREEMPT_NONE /boot/config-3.0.101-0.47.67-default CONFIG_PREEMPT_NONE=y

Re: [RFC PATCH 07/11] pci: controller: designware: Add EP mode support

On Wed, Sep 14, 2016 at 10:42:03AM +0530, Kishon Vijay Abraham I wrote: > Add endpoint mode support to designware driver. This uses the > EP Core layer introduced recently to add endpoint mode support. > *Any* function driver can now use this designware device > to achieve the EP functionality. >

[PATCH 5/5] ACPI / gpio: Allow holes in list of GPIOs for a device

Make it possible to have an empty GPIOs in a GPIO list for device. For example a SPI master may use both GPIOs and native pins as chip selects and we need to be able to distinguish between the two. This makes it mandatory to have exactly 3 arguments for GPIOs and then converts gpiolib to use of

[PATCH 1/5] ACPI / documentation: Use recommended name in GPIO property names

The recommended property name for all kinds of GPIOs is to end it with "-gpios" even if there is only one GPIO. Update the documentation to follow this fact. Signed-off-by: Mika Westerberg --- Documentation/acpi/gpio-properties.txt | 10 +- 1 file

Re: [PATCH 1/1] lib/ioremap.c: avoid endless loop under ioremapping page unaligned ranges

On 2016/9/23 22:27, Michal Hocko wrote: > On Fri 23-09-16 22:14:40, zijun_hu wrote: >> On 2016/9/23 21:33, Michal Hocko wrote: >>> On Fri 23-09-16 21:00:18, zijun_hu wrote: On 09/23/2016 08:42 PM, Michal Hocko wrote: no, it don't work for many special case for example,

[PATCH 3/5] ACPI / gpio: Add hogging support

GPIO hogging means that the GPIO controller can "hog" and configure certain GPIOs without need for a driver or userspace to do that. This is useful in open-connected boards where BIOS cannot possibly know beforehand which devices will be connected to the board. This adds GPIO hogging mechanism to

Re: [PATCH] usb: gadget: udc: atmel: fix endpoint name

On Fri, Sep 23, 2016 at 04:20:45PM +0200, Nicolas Ferre wrote: > Le 16/09/2016 à 10:36, Nicolas Ferre a écrit : > > Le 15/09/2016 à 17:07, Alexandre Belloni a écrit : > >> Since commit c32b5bcfa3c4 ("ARM: dts: at91: Fix USB endpoint nodes"), > >> atmel_usba_udc fails with: > >> > >> [

Re: Patchwork [1/1] staging: ks7010: Attempt to structure and format to standards

On Fri, Sep 23, 2016 at 04:28:11PM +0200, Marcel Xubuntu wrote: > Mostly code formatting, unapologetically a stepping stone for a potential > refactoring with a knowledge seeking, following complete disclosure, > ultimate goal. > In case this fails, my backup plan is to have the world's record for

Re: [PATCH v6 4/4] tracing: Histogram for delayed hrtimer offsets

On 09/09/2016 03:30 PM, Thomas Gleixner wrote: > On Thu, 8 Sep 2016, Binoy Jayan wrote: >> On 8 September 2016 at 12:40, Thomas Gleixner wrote: > [..] + latency = ktime_to_ns(ktime_sub(basenow, + ktime_to_ns(timer->praecox) ? +

Re: [PATCHv2 3/5] staging:android:ion: Fix blank line issues

On Fri, Sep 23, 2016 at 04:26:28PM +0300, Yannis Damigos wrote: > On Fri, Sep 23, 2016 at 3:17 PM, Greg KH wrote: > > On Fri, Sep 23, 2016 at 11:05:15AM +0300, giannis.dami...@gmail.com wrote: > >> From: Yannis Damigos > >> > >> This patch

Re: [PATCH 19/19] reset: sti: softreset: Remove obsolete platforms from dt binding doc.

On Wed, Sep 14, 2016 at 02:27:57PM +0100, Peter Griffin wrote: > STiH415/6 SoC support is being removed from the kernel. > This patch updates the sti dt softreset bindings and > removes references to these obsolete platforms. > > Signed-off-by: Peter Griffin > Cc:

Re: [PATCH 4.4 000/118] 4.4.22-stable review

On Fri, Sep 23, 2016 at 06:25:33AM -0700, Guenter Roeck wrote: > On 09/23/2016 01:08 AM, Greg Kroah-Hartman wrote: > > On Thu, Sep 22, 2016 at 08:01:35PM -0700, Guenter Roeck wrote: > > > e5767a13d7cb ("cxl: use pcibios_free_controller_deferred() when removing > > > vPHBs") > > > does not apply

Re: [PATCH 18/19] stmmac: dwmac-sti: Remove obsolete STi platforms

On Wed, Sep 14, 2016 at 02:27:56PM +0100, Peter Griffin wrote: > This patch removes support for STiH415/6 SoC's from the > dwmac-sti driver and dt binding doc, as support for these > platforms is being removed from the kernel. It also removes > STiD127 related code, which has never actually been

Re: [PATCH 1/2] armv8: aarch32: Execute 32-bit Linux for LayerScape platforms

On 23/09/16 15:44, Arnd Bergmann wrote: > On Friday, September 23, 2016 3:24:12 PM CEST Robin Murphy wrote: >> On 23/09/16 15:01, Stuart Yoder wrote: >> Otherwise you can >> always simply run your own shim at EL2 to drive an AArch32 EL1 (it'll >> need to trap and translate subsequent SMC calls for

Re: [PATCH 02/19] phy: stih41x-usb: Remove usb phy driver and dt binding documentation.

On Wed, Sep 14, 2016 at 02:27:40PM +0100, Peter Griffin wrote: > This phy is only used on STiH415/6 based silicon, and support for > these SoC's is being removed from the kernel. > > Signed-off-by: Peter Griffin > Cc: > --- >

Re: [RFC PATCH 1/6] perf: Move mlock accounting to ring buffer allocation

On Fri, Sep 23, 2016 at 05:27:22PM +0300, Alexander Shishkin wrote: > > Afaict there's no actual need to hide the AUX buffer for this sampling > > stuff; the user knows about all this and can simply mmap() the AUX part. > > Yes, you're right here. We could also re-use the AUX record, adding a >

Re: [PATCH 0/2] Ajust lockdep static allocations

On Fri, Sep 23, 2016 at 10:15:46AM -0500, Babu Moger wrote: > >> Correct, We can't boot with lockdep. Sorry I did not make that clear. > >>We have a limit on static size of the kernel. > >This stuff should be in .bss not .data. It should not affect the static > >size at all. Or am I

Re: [PATCH v18 6/6] ARM: socfpga: fpga bridge driver support

Hi! Alan Tull writes: > Supports Altera SOCFPGA bridges: > * fpga2sdram > * fpga2hps > * hps2fpga > * lwhps2fpga > > Allows enabling/disabling the bridges through the FPGA > Bridge Framework API functions. > > The fpga2sdram driver only supports enabling and disabling > of the ports that

Re: GPU-DRM-QXL: Move three assignments in qxl_device_init()

>> I am trying to improve various open issues also in Linux source files. >> > That the fact that you see issues (in these particular cases) while > others do not I guess that the discussed "story" affects more challenges in communication and different opinions about where to invest software

Re: [RFC PATCH 2/3] PM / Domains: Add support for devices with multiple domains

Hi Jon, On Fri, Sep 23, 2016 at 2:57 PM, Jon Hunter wrote: > On 21/09/16 15:57, Geert Uytterhoeven wrote: >> On Wed, Sep 21, 2016 at 4:37 PM, Jon Hunter wrote: >>> On 21/09/16 09:53, Geert Uytterhoeven wrote: On Tue, Sep 20, 2016 at 12:28 PM, Jon

Re: [RFC/PATCH] usb: misc: Add a driver for TC7USB40MU

On Wed, Sep 14, 2016 at 01:55:02AM -0700, Stephen Boyd wrote: > Quoting Stephen Boyd (2016-09-13 18:42:46) > > On the db410c 96boards platform we have a TC7USB40MU[1] on the > > board to mux the D+/D- lines from the SoC between a micro usb > > "device" port and a USB hub for "host" roles. Upon a

Re: [tip:sched/core] sched/core: Avoid _cond_resched() for PREEMPT=y

On Fri, Sep 23, 2016 at 10:44:42AM +0200, Peter Zijlstra wrote: > On Thu, Sep 22, 2016 at 01:28:17PM -0700, Paul E. McKenney wrote: > > On Thu, Sep 22, 2016 at 08:42:28PM +0200, Peter Zijlstra wrote: > > > On Thu, Sep 22, 2016 at 02:25:01PM -0400, Mikulas Patocka wrote: > > > > I've found a

[PATCH 01/16] perf record: Fix documentation 'event_sources' -> 'event_source'

Change '/sys/bus/event_sources' to the correct path which is '/sys/bus/event_source'. Signed-off-by: Adrian Hunter --- tools/perf/Documentation/perf-record.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

Crypto Fixes for 4.8

Hi Linus: This push fixes a regression RSA that was only half-fixed earlier in the cycle. It also fixes an older regression that breaks the keyring subsystem. Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus Herbert Xu (2): KEYS: Fix skcipher

[PATCH] kcov: properly check if we are in an interrupt

in_interrupt() returns a nonzero value when we are either in an interrupt or have bh disabled via local_bh_disable(). Since we are interested in only ignoring coverage from actual interrupts, do a proper check of whether we are really in an interrupt. Signed-off-by: Andrey Konovalov

Re: [PATCH 0/2] Ajust lockdep static allocations

On 9/23/2016 9:34 AM, Peter Zijlstra wrote: On Fri, Sep 23, 2016 at 09:04:42AM -0500, Babu Moger wrote: On 9/23/2016 2:12 AM, Peter Zijlstra wrote: On Thu, Sep 22, 2016 at 11:43:34AM -0700, Babu Moger wrote: These patches adjust the static allocations for lockdep data structures used for

Re: [PATCH] mm: warn about allocations which stall for too long

On Fri 23-09-16 23:36:22, Tetsuo Handa wrote: > Michal Hocko wrote: > > @@ -3659,6 +3661,15 @@ __alloc_pages_slowpath(gfp_t gfp_mask, unsigned int > > order, > > else > > no_progress_loops++; > > > > + /* Make sure we know about allocations which stall for too long */ > > +

Re: [patch v5] i2c: mux: mellanox: add driver

On 2016-09-13 22:37, vad...@mellanox.com wrote: > From: Vadim Pasternak > > This driver allows I2C routing controlled through CPLD select registers on > a wide range of Mellanox systems (CPLD Lattice device). > MUX selection is provided by digital and analog HW. Analog part

[PATCH net-next 13/15] rxrpc: Add a tracepoint to log injected Rx packet loss

Add a tracepoint to log received packets that get discarded due to Rx packet loss. Signed-off-by: David Howells --- include/trace/events/rxrpc.h | 21 + net/rxrpc/input.c| 11 +-- 2 files changed, 26 insertions(+), 6 deletions(-)

[PATCH net-next 14/15] rxrpc: Add tracepoint for ACK proposal

Add a tracepoint to log proposed ACKs, including whether the proposal is used to update a pending ACK or is discarded in favour of an easlier, higher priority ACK. Whilst we're at it, get rid of the rxrpc_acks() function and access the name array directly. We do, however, need to validate the

[PATCH net-next 09/15] rxrpc: Pass the last Tx packet marker in the annotation buffer

When the last packet of data to be transmitted on a call is queued, tx_top is set and then the RXRPC_CALL_TX_LAST flag is set. Unfortunately, this leaves a race in the ACK processing side of things because the flag affects the interpretation of tx_top and also allows us to start receiving reply

[PATCH net-next 06/15] rxrpc: Need to start the resend timer on initial transmission

When a DATA packet has its initial transmission, we may need to start or adjust the resend timer. Without this we end up relying on being sent a NACK to initiate the resend. Signed-off-by: David Howells --- net/rxrpc/ar-internal.h |1 + net/rxrpc/call_event.c |2

[PATCH net-next 05/15] rxrpc: Use before_eq() and friends to compare serial numbers

before_eq() and friends should be used to compare serial numbers (when not checking for (non)equality) rather than casting to int, subtracting and checking the result. Signed-off-by: David Howells --- net/rxrpc/input.c |2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH 0/2] Ajust lockdep static allocations

On 9/23/2016 10:04 AM, Peter Zijlstra wrote: On Fri, Sep 23, 2016 at 09:50:52AM -0500, Babu Moger wrote: Why can't you boot? You have that little memories? 4MB doesn't seem like a worthwhile amount of memory. Also, you didn't say. This seems a somewhat crucial point. Correct, We can't

Re: [PATCH v5 6/6] regulator: core: Prevent falling too fast

On Wed, Sep 14, 2016 at 09:52:10AM -0700, Matthias Kaehlcke wrote: > From: Douglas Anderson > > On some boards it is possible that transitioning the regulator downwards > too fast will trigger the over voltage protection (OVP) on the > regulator. This is because until the

[PATCH net-next 08/15] rxrpc: Fix call timer

Fix the call timer in the following ways: (1) If call->resend_at or call->ack_at are before or equal to the current time, then ignore that timeout. (2) If call->expire_at is before or equal to the current time, then don't set the timer at all (possibly we should queue the call).

[PATCH net-next 03/15] rxrpc: Make sure sendmsg() is woken on call completion

Make sure that sendmsg() gets woken up if the call it is waiting for completes abnormally. Signed-off-by: David Howells --- net/rxrpc/ar-internal.h |1 + 1 file changed, 1 insertion(+) diff --git a/net/rxrpc/ar-internal.h b/net/rxrpc/ar-internal.h index

[PATCH net-next 01/15] rxrpc: Preset timestamp on Tx sk_buffs

Set the timestamp on sk_buffs holding packets to be transmitted before queueing them because the moment the packet is on the queue it can be seen by the retransmission algorithm - which may see a completely random timestamp. If the retransmission algorithm sees such a timestamp, it may retransmit

[PATCH net-next 00/15] rxrpc: Bug fixes and tracepoints

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-20160923 David --- David Howells (15): rxrpc: Preset timestamp on Tx sk_buffs rxrpc: Don't

Re: [PATCH V3 01/10] Documentation: DT: qcom_hidma: update binding for MSI

On Thu, Sep 15, 2016 at 01:22:37PM -0400, Sinan Kaya wrote: > Adding a new binding for qcom,hidma-1.1 to distinguish HW supporting > MSI interrupts from the older revision. > > Signed-off-by: Sinan Kaya > --- > Documentation/devicetree/bindings/dma/qcom_hidma_mgmt.txt | 13

[PATCH 6/8 V2] staging: rts5208: fix line style warnings in spi.c

This patch fixes the following checkpatch.pl warning in spi.c: WARNING: line over 80 characters Signed-off-by: Sergio Paracuellos --- drivers/staging/rts5208/spi.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/rts5208/spi.c

[PATCH 8/8 V2] staging: rts5208: fix style warnings in xd.c

This patch fixes the following checkpatch.pl warning in xd.c: WARNING: else is not generally useful after a break or return It also makes code more uniform with the new changes Signed-off-by: Sergio Paracuellos --- drivers/staging/rts5208/xd.c | 38

Re: strace lockup when tracing exec in go

On Fri 23-09-16 16:07:24, Oleg Nesterov wrote: > On 09/23, Michal Hocko wrote: > > > > On Fri 23-09-16 15:21:02, Oleg Nesterov wrote: > > > > > > This change is simply wrong no matter what. > > > > I've just tried to extend the existing > > > > /* > > * Tracers may want to know about even

Re: [RFC PATCH 1/6] perf: Move mlock accounting to ring buffer allocation

Peter Zijlstra writes: > On Fri, Sep 23, 2016 at 02:27:21PM +0300, Alexander Shishkin wrote: >> In order to be able to allocate perf ring buffers in non-mmap path, we >> need to make sure we can still account the memory to the user and that >> they don't exceed their mlock

Re: [PATCH] drm/i2c: tda998x: don't register the connector

On Fri, Sep 23, 2016 at 03:13:15PM +0200, Daniel Vetter wrote: On Fri, Sep 23, 2016 at 01:52:49PM +0100, Brian Starkey wrote: On Fri, Sep 23, 2016 at 12:58:46PM +0200, Daniel Vetter wrote: > On Fri, Sep 23, 2016 at 11:34 AM, Liviu Dudau wrote: > > rmmod-ing the hdlcd

[PATCH 07/16] perf record: Add support for using symbols in address filters

Symbols come from either the DSO or /proc/kallsyms for the kernel. Details of the functionality can be found in Documentation/perf-record.txt. Signed-off-by: Adrian Hunter --- tools/perf/Documentation/perf-record.txt | 55 ++- tools/perf/builtin-record.c |

[PATCH 00/16] perf tools: Add support for using symbols in address filters

Hi Here are some patches that add support for using symbols in address filters. There are also some fixes for other things that I came across during testing. Finally there are patches for Intel PT, mainly to fix an issue with address filters, but also these two: perf intel-pt: Fix

[PATCH 04/16] perf record: Rename label 'out_symbol_exit'

In preparation for fixing the error paths, rename label 'out_symbol_exit' to be 'out' because that error path can be used irrespective of whether symbols (or anything else) has been initialized. Signed-off-by: Adrian Hunter --- tools/perf/builtin-record.c | 10

[PATCH 4/5] ACPI / property: Allow holes in reference properties

DT allows holes or empty phandles for references. This is used for example in SPI subsystem where some chip selects are native and others are regular GPIOs. In ACPI _DSD we currently do not support this but instead the preceding reference "consumes" all following integer arguments. For example we

[PATCH 2/5] ACPI / gpio: Add support for naming GPIOs

DT has property 'gpio-line-names' to name GPIO lines the controller has if present. Use this very same property in ACPI as well to provide nice names for the GPIOS. Signed-off-by: Mika Westerberg --- Documentation/acpi/gpio-properties.txt | 21 +

RE: [PATCH V3 2/4] ARM64 LPC: LPC driver implementation on Hip06

Hi Arnd > -Original Message- > From: Arnd Bergmann [mailto:a...@arndb.de] > Sent: 23 September 2016 14:43 > To: Gabriele Paoloni > Cc: zhichang.yuan; linux-arm-ker...@lists.infradead.org; > devicet...@vger.kernel.org; lorenzo.pieral...@arm.com; miny...@acm.org; >

Re: [PATCH 01/19] phy: phy-miphy365x: Remove miphy365 driver and dt binding documentation.

On Wed, Sep 14, 2016 at 02:27:39PM +0100, Peter Griffin wrote: > This phy is only used on STiH415/6 based silicon, and support for > these SoC's is being removed from the kernel. > > Signed-off-by: Peter Griffin > Cc: > --- >

Re: [PATCH v5 5/6] regulator: core: Add support for a fixed delay after voltage changes

On Wed, Sep 14, 2016 at 09:52:09AM -0700, Matthias Kaehlcke wrote: > The target voltage is not necessarily reached inmediately after > requesting a regulator to change the voltage. In some cases the > ramp_delay can be used to calculate the stabilisation time, in others > there is no direct

<    1   2   3   4   5   6   7   8   9   10   >