On Sat, Nov 21, 2015 at 1:37 PM, Edwin Velds wrote:
> This patch implements force feedback support for the Logitech G920 Driving
> Force
> Racing Wheel.
>
> This patch is based on the basic G920 support patch by Simon Wood:
> http://www.spinics.net/lists/linux-input/msg42174.html
>
> The first
On arm64, kstop_machine which is hugely disruptive to a running
system is not needed to convert nops to ftrace calls or back,
because that modifed code is a single 32bit instructions which
is impossible to cross cache (or page) boundaries, and the used str
instruction is single-copy atomic.
Cc:
Add the support of Hisilicon Hi3519 debug uart.
Signed-off-by: Jiancheng Xue
---
arch/arm/Kconfig.debug | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
index 259c0ca..4d2ae2a 100644
--- a/arch/arm/Kconfig.debug
+++
enable ARCH_HI3519 in hisi_defconfig
Signed-off-by: Jiancheng Xue
---
arch/arm/configs/hisi_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/hisi_defconfig b/arch/arm/configs/hisi_defconfig
index b2e340b..321d020 100644
--- a/arch/arm/configs/hisi_defconfig
+++
add dts files for hi3519-demb board
Signed-off-by: Jiancheng Xue
---
arch/arm/boot/dts/Makefile| 2 +
arch/arm/boot/dts/hi3519-demb.dts | 55
arch/arm/boot/dts/hi3519.dtsi | 129 ++
3 files changed, 186 insertions(+)
create
Hi3519 SOC is mainly used for ip camera and sport dv
solutions.
Signed-off-by: Jiancheng Xue
---
arch/arm/mach-hisi/Kconfig | 9 +
arch/arm/mach-hisi/hisilicon.c | 9 +
2 files changed, 18 insertions(+)
diff --git a/arch/arm/mach-hisi/Kconfig b/arch/arm/mach-hisi/Kconfig
The CRG(Clock and Reset Generator) module provides
clock and reset signals for other modules in hi3519 soc.
Signed-off-by: Jiancheng Xue
---
.../devicetree/bindings/clock/hi3519-clock.txt | 46 +++
drivers/clk/hisilicon/Makefile | 1 +
Hello,
Hi3519 soc is mainly used for ip camera and sport DV solutions. This patchset
adds initial support
for Hi3519 soc. It includes clock driver, arch configuration, device tree and
debug uart configuration.
It has been tested on hi3519 reference board.
Spi-nor flash driver and other
this patch enables the ethX for D02 board on hip05-d02.dts. otherwise it
cannot find hns ethX by ifconfig -a.
Signed-off-by: yankejian
---
arch/arm64/boot/dts/hisilicon/hip05-d02.dts | 16
1 file changed, 16 insertions(+)
diff --git
when linux start up, we get the log below:
"Hi-HNS_MDIO 803c.mdio: no syscon hisilicon,peri-c-subctrl
mdio_bus mdio@803c: mdio sys ctl reg has not maped "
the source code about the subctrl is dealled with syscon, but dts doesn't.
it cause such fault. so this patch adds the syscon
this patchset fixes the bug that eth can't initial successful. because the
the dts files doesn't match the source code.
yankejian (3):
dts: hisi: enables the ethX for D02 board
dts: hisi: fixes no syscon error when init mdio
arm64: hip05-d02: Document devicetree bindings for Hisilicon D02
On 11/27/2015 8:06 PM, Frank Rowand wrote:
> On 7/6/2015 1:26 PM, Pali Rohár wrote:
>> This patch series converts some legacy ATAGs into DT and provide them to
>> userspace. It is needed for userspace applications which needs some
>> informations from legacy bootloaders which are not DT
Michal Hocko wrote:
> for write while write but the probability is reduced considerably wrt.
Is this "while write" garbage?
> Users of mmap_sem which need it for write should be carefully reviewed
> to use _killable waiting as much as possible and reduce allocations
> requests done with the lock
On 7/6/2015 1:26 PM, Pali Rohár wrote:
> This patch series converts some legacy ATAGs into DT and provide them to
> userspace. It is needed for userspace applications which needs some
> informations from legacy bootloaders which are not DT compatible.
>
> Patch series is for now without DT
On Wed, Nov 25, 2015 at 9:02 AM, Eric Dumazet wrote:
> From: Eric Dumazet
>
> Once TX has been enabled on a NIC, it is illegal to access skb,
> as this skb might have been freed by another cpu, from TX completion
> handler.
>
> Signed-off-by: Eric Dumazet
> Reported-by: Mark Rutland
>
On 2015/11/28 2:57, Oleg Nesterov wrote:
On 11/26, Oleg Nesterov wrote:
OK. I do not know what exactly do you mean, perhaps if you fix this problem
the race between fork and attach goes away and in this case the fix I sent
is not needed?
Otherwise please consider this series.
Slightly
commit fdf6d7e7cf448b9482062d73a48895afaf38a458
Author: Jordan Hargrave
Date: Fri Nov 27 20:39:59 2015 -0600
Fix spacing
Check invalid slot entry according to spec
commit 8a7fe87241b93c72cfd6ef818a680a2c7fc2f1c7
Author: Jordan Hargrave
Date: Thu Nov 26 15:57:24 2015 -0600
Save
tty_mutex is a core, system-wide lock; there is no reason for any
code outside the tty core to have direct access.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_io.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index
tty_read_raw_data() and tty_signal() no longer exist; remove
declarations.
Signed-off-by: Peter Hurley
---
include/linux/tty.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/include/linux/tty.h b/include/linux/tty.h
index 9e3231e..584bf4c 100644
--- a/include/linux/tty.h
+++
On Fri, Nov 27, 2015 at 09:44:45AM +0100, Krzysztof Opasiak wrote:
>
>
> On 11/26/2015 06:29 PM, Greg KH wrote:
> >On Thu, Nov 26, 2015 at 10:19:29AM +0100, Krzysztof Opasiak wrote:
> >>
> >>
> >>On 11/25/2015 04:45 PM, Emilio López wrote:
> >>>Hi everyone,
> >>>
> >>>This patch introduces a new
Reduce global tty symbols; move and rename tty_ldisc_begin() as
n_tty_init() and redefine the N_TTY ldisc ops as file scope.
Signed-off-by: Peter Hurley
---
drivers/tty/n_tty.c | 12
drivers/tty/tty_io.c| 2 +-
drivers/tty/tty_ldisc.c | 6 --
include/linux/tty.h |
Access to tty->tty_files list is always per-tty, never for all ttys
simultaneously. Replace global tty_files_lock spinlock with per-tty
->files_lock. Initialize when the ->tty_files list is inited, in
alloc_tty_struct().
Signed-off-by: Peter Hurley
---
drivers/tty/tty_io.c | 25
Move is_ignored() to drivers/tty/tty_io.c and re-declare in file
scope.
Signed-off-by: Peter Hurley
---
drivers/tty/n_tty.c | 6 --
drivers/tty/tty_io.c | 6 ++
include/linux/tty.h | 1 -
3 files changed, 6 insertions(+), 7 deletions(-)
diff --git a/drivers/tty/n_tty.c
The TTY_DEBUG macro is not used; remove.
Signed-off-by: Peter Hurley
---
include/linux/tty.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/linux/tty.h b/include/linux/tty.h
index 8f16d52..168f198 100644
--- a/include/linux/tty.h
+++ b/include/linux/tty.h
@@ -335,7 +335,6 @@ struct
Hi Greg,
This patch series is part of the ongoing effort to cleanup and reduce the
kernel tty interface; specifically removing undefined function declarations,
unused macros, encapsulating global data, undefining unused exports,
limiting functions and data to file scope, etc.
Regards,
Peter
tty_driver_remove_tty() is only local-scope; declare as static.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_io.c | 2 +-
include/linux/tty.h | 2 --
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index fe2ed1a..64978ca 100644
---
tty_init_termios() never returns an error; re-declare as void. Remove
unnecessary error handling from callers. Remove extern declarations
of tty_free_termios() and free_tty_struct() and re-declare in file
scope.
Signed-off-by: Peter Hurley
---
drivers/tty/pty.c| 15 +++
Evaluate the conditions which prevent this tty being the controlling
terminal in one place, just before setting the controlling terminal.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_io.c | 17 -
1 file changed, 8 insertions(+), 9 deletions(-)
diff --git
The tty driver remove() method is used exclusively by the BSD and Unix98
pty drivers to release the tty index; the BSD drivers clear the tty tables
for the pty pair @index, while the Unix98 drivers free the devpts index.
Although the remove() method is intended as the symmetric operation to the
The tty lock/unlock code does not belong in the special lockfunc section
which is treated specially by stack backtraces.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 16 +++-
drivers/tty/tty_mutex.c | 8
include/linux/tty.h | 8
3 files changed,
The tty core invokes the optional driver shutdown() just before
the optional driver remove() (shutdown() has access to the termios
and remove() does not). Because pty drivers must prevent the default
remove() action, the Unix98 pty drivers define a dummy remove() function.
Instead, release the
Extract the driver lookup and reopen-or-initialize logic into helper
function tty_open_by_driver(). No functional change.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_io.c | 98 +++-
1 file changed, 50 insertions(+), 48 deletions(-)
diff --git
A small window exists where a tty reopen will observe the tty
just prior to imminent teardown (tty->count == 0); in this case, open()
returns EIO to userspace.
Instead, retry the open after checking for signals and yielding;
this interruptible retry loop allows teardown to commence and initialize
release_tty() leaks the ldisc instance when called directly (rather
than when releasing the file descriptor from tty_release()).
Since tty_ldisc_release() clears tty->ldisc, releasing the ldisc
instance at tty teardown if tty->ldisc is non-null is not in danger
of double-releasing the ldisc.
Allow a signal to interrupt the wait for a tty reopen; eg., if
the tty has starting final close and is waiting for the device to
drain.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_io.c| 8 +++-
drivers/tty/tty_mutex.c | 8
include/linux/tty.h | 1 +
3 files changed, 16
BSD pty drivers are cross-linked at driver initialization and linked pairs
must have the same tty index; use this information to simplify clearing
the driver tables.
Signed-off-by: Peter Hurley
---
drivers/tty/pty.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
Hi Greg,
This patch series implements two important improvements to tty open()
behavior: interruptible open() and automatic retry when tty teardown
has already commenced.
Interruptible open() allows signals to cancel the open wait if stalled
waiting for tty teardown to complete.
Automatic retry
free_tty_struct() is never called with NULL tty; the two call sites
would already have faulted on earlier access.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_io.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/tty/tty_io.c b/drivers/tty/tty_io.c
index 153b7b8..76e4ae0 100644
On 2015/11/27 20:02, Joerg Roedel wrote:
> On Fri, Nov 20, 2015 at 10:25:08AM +0800, Chen Feng wrote:
>> +config HI6220_IOMMU
>> +bool "Hi6220 IOMMU Support"
>> +depends on ARM64
>> +select IOMMU_API
>> +select IOMMU_IOVA
>> +help
>> + Enable IOMMU Driver for hi6220 SoC.
On 11/27/2015 05:13 AM, Geert Uytterhoeven wrote:
> If an earlycon console driver needs to acquire the uart_port.lock
> spinlock for serial console output, and CONFIG_DEBUG_SPINLOCK=y:
>
> BUG: spinlock bad magic on CPU#0, swapper/0
> lock: sci_ports+0x0/0x3480, .magic: , .owner:
Hi Rob,
On Sat, Nov 28, 2015 at 5:30 AM, Rob Herring wrote:
> On Thu, Nov 26, 2015 at 10:47:26PM +0900, Chanwoo Choi wrote:
>> This patch adds the documentation for generic exynos bus frequency
>> driver.
>>
>> Signed-off-by: Chanwoo Choi
>> ---
>>
On 2015/11/27 19:49, Joerg Roedel wrote:
> On Fri, Nov 20, 2015 at 10:25:06AM +0800, Chen Feng wrote:
>> eg:
>> struct iommu_domain *domain = iommu_domain_alloc(bus);
>> iommu_attach_device(domain, dev);
>> struct iova_domain *iovad = (struct iova_domain *)m_dev->archdata.iommu;
>> struct iova *
Hi Arnaldo,
On Fri, Nov 27, 2015 at 04:57:21PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Nov 27, 2015 at 04:56:27PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Sat, Nov 28, 2015 at 02:32:37AM +0900, Namhyung Kim escreveu:
> > > Currently when perf fails to process samples for some
Hi Matiasl
Just to let you know this patch and previous version both cannot
address 'register device with supported manager may blocked while
holding the lock' issue.
2015-11-28 3:41 GMT+08:00 Matias Bjørling :
> On 11/27/2015 01:04 PM, Wenwei Tao wrote:
>>
>> Hi Matias
>> Previous version patch
On 11/27/2015 08:20 PM, Peter Hurley wrote:
> It would really help if you included the syzkaller-generated applet with
> the bug reports; state previously established by the applet can be
> crucial in understanding why the call stack looks the way it does.
>
> Also, every generated applet that
On 2015/11/28 9:10, Arnaldo Carvalho de Melo wrote:
Em Fri, Nov 27, 2015 at 08:47:38AM +, Wang Nan escreveu:
bpf__config_obj() is introduced as a core API to config BPF object
after loading. One configuration option of maps is introduced. After
this patch BPF object can accept
From: Namhyung Kim
If user gives a filter, perf marks the corresponding column elided and
omits the output. But it should process and aggregates samples using
the field, otherwise samples will be aggregated as if the column was not
there resulted in incorrect output.
For example, I'd like to
From: Arnaldo Carvalho de Melo
When PERF_COUNT_SW_BPF_OUTPUT was added to the kernel we should've
added it to tools/perf, where it is used just to list events.
This ended up causing a segfault in commands like "perf list stall".
Fix it by adding that new software counter.
A patch to robustify
From: Wang Nan
Following patches are going to introduce BPF object level configuration
to enable setting values into BPF maps. To avoid confusion, this patch
renames existing 'config' in bpf-loader.c to 'program config'. Following
patches would introduce 'object config'.
Signed-off-by: Wang Nan
From: Michael Petlan
The --kernel option of perf buildid-list tool should show the running
kernel buildid. The functionality has been lost during other changes of
the related code.
The build_id__sprintf() function should return length of the build-id
string, but it was the length of the
From: Arnaldo Carvalho de Melo
Hi Ingo,
Please consider applying,
- Arnaldo
The following changes since commit 3f3b1a46bfdbce97dd3f9594d8a95db82baa554b:
Merge tag 'perf-core-for-mingo' of
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core
(2015-11-27 08:28:44
From: Wang Nan
This patch collects name of maps in BPF object files and saves them into
'maps' field in 'struct bpf_object'. 'bpf_object__get_map_by_name' is
introduced to retrive fd and definitions of a map through its name.
Signed-off-by: He Kuang
Cc: Alexei Starovoitov
Cc: He Kuang
Cc:
From: Namhyung Kim
When perf report on TUI was called with -S symbol filter, it should
update nr entries even if min_pcnt is 0. IIRC the reason was to update
nr entries after applying minimum percent threshold. But if symbol
filter was given on command line (with -S option), it should use
From: Jiri Olsa
The 'perf test unwind' is failing because it forgot to create the kernel
maps, fix it.
After the patch:
# perf test unwind
40: Test dwarf unwind : Ok
Reported-and-Tested-by: Arnaldo Carvalho de Melo
Signed-off-by: Jiri Olsa
Cc: David Ahern
Cc: Masami Hiramatsu
From: Wang Nan
This patch collects more information from maps sections in BPF object
files into 'struct bpf_object', enables later patches access those
information (such as the type and size of the map).
In this patch, a new handler 'struct bpf_map' is extracted in parallel
with bpf_object and
From: Namhyung Kim
Currently when perf fails to process samples for some reason, it doesn't
show any message about the failure. This is very inconvenient for users
especially on TUI as screen is reset after the failure.
Reported-by: Ingo Molnar
Signed-off-by: Namhyung Kim
Cc: David Ahern
From: Arnaldo Carvalho de Melo
When a43eec304259 ("bpf: introduce bpf_perf_event_output() helper") added
PERF_COUNT_SW_BPF_OUTPUT we ended up with a new entry in the event_symbols_sw
array that wasn't initialized, thus set to NULL, fix print_symbol_events()
to check for that case so that we
On 2015/11/28 9:20, Wangnan (F) wrote:
On 2015/11/28 9:10, Arnaldo Carvalho de Melo wrote:
Em Fri, Nov 27, 2015 at 08:47:38AM +, Wang Nan escreveu:
bpf__config_obj() is introduced as a core API to config BPF object
after loading. One configuration option of maps is introduced. After
On 11/27/2015 07:28 PM, Paul Bolle wrote:
> (A few quick notes follow. The hope here is basically that my display of
> ignorance might trigger others to speak up while I'm still pondering on
> this bug.)
>
> On vr, 2015-11-27 at 13:15 -0500, Sasha Levin wrote:
>> On 11/27/2015 12:57 PM, Paul
Em Fri, Nov 27, 2015 at 08:47:38AM +, Wang Nan escreveu:
> bpf__config_obj() is introduced as a core API to config BPF object
> after loading. One configuration option of maps is introduced. After
> this patch BPF object can accept configuration like:
>
> maps:my_map:value=1234
>
>
Em Sat, Nov 28, 2015 at 02:32:39AM +0900, Namhyung Kim escreveu:
> When perf report on TUI was called with -S symbol filter, it should
> update nr entries even if min_pcnt is 0. IIRC the reason was to update
> nr entries after applying minimum percent threshold. But if symbol
> filter was given
Em Sat, Nov 28, 2015 at 02:32:38AM +0900, Namhyung Kim escreveu:
> If user gives a filter, perf marks the corresponding column elided and
> omits the output. But it should process and aggregates samples using
> the field, otherwise samples will be aggregated as if the column was not
> there
Hi Linus,
The following changes since commit 1ec218373b8ebda821aec00bb156a9c94fad9cd4:
Linux 4.4-rc2 (2015-11-22 16:45:59 -0800)
are available in the git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.4-2
for you to fetch changes up to
On Fri, Nov 27, 2015 at 10:40 AM, Emil Velikov wrote:
> On 27 November 2015 at 15:10, Daniel Vetter wrote:
>> It only leads to bloodshed and tears - we don't bother to restore a
>> working legacy vga hw setup.
>>
>> On haswell with the new dynamic power well code this leads to even
>> more
(A few quick notes follow. The hope here is basically that my display of
ignorance might trigger others to speak up while I'm still pondering on
this bug.)
On vr, 2015-11-27 at 13:15 -0500, Sasha Levin wrote:
> On 11/27/2015 12:57 PM, Paul Bolle wrote:
> > On vr, 2015-11-27 at 10:19 -0500, Sasha
On Fri, Nov 27, 2015 at 07:21:06PM +0900, Masahiro Yamada wrote:
> Hi,
>
>
> If I add "earlycon" to the kernel parameter, the log message
> on the earlycon is also displayed to the regular console.
> In other words, the same log messages are displayed twice.
>
> I noticed this problem on
On Fri, Nov 27, 2015 at 03:23:33PM +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 11/27/2015 1:38 PM, Rasmus Villemoes wrote:
>
> >This file already uses pr_debug in a few places; this converts the
> >remaining printks.
>
>Are you aware that printk(KERN_DEBUG, ...) and pr_debug() are not
>
Hi Florian,
On 15-11-27 10:39 AM, Florian Fainelli wrote:
Le 26/11/2015 11:59, Scott Branden a écrit :
Add support for switching defconfig between big and little endian CPU.
Various CPU types have ability to select big and little endian
CPU in the kernel configuration.
"make beconfig" will
Hi Arnd,
Thanks for comment - I forgot to directly add you to CC list so was
going to add you in a couple days if you didn't find this patch proposal.
Response below.
On 15-11-27 07:59 AM, Arnd Bergmann wrote:
On Thursday 26 November 2015 11:59:55 Scott Branden wrote:
@@ -151,6 +159,8 @@
On Fri, 27 Nov 2015, Arnd Bergmann wrote:
> I don't mind creating the /proc/atags compatibility hack from the kernel
> for a DT based N700 kernel, as long as we limit it as much as we can
> to the machines that need it. Leaving a board file for the N700 in place
> that contains the procfs code
RX DMA tail data handling doesn't work correctly in many cases with
current implementation. It happens because SPI core was setup
to generates both RX watermark level and RX DATA TAIL events
incorrectly. SPI transfer triggering for DMA also done in wrong way.
SPI client wants to transfer 70 words
DMA transfer for SPI was limited to up to 8 bits word size until now.
Sync in SPI burst size and DMA bus width is necessary to correctly
support other BPW supported by HW.
Signed-off-by: Anton Bondarenko
---
drivers/spi/spi-imx.c | 133 ++
1 file
A number of patches to impove or add the implementation
for the spi-imx driver related to Freescale IMX51, IMX53 and IMX6.
It would also possible some of patches can be applied for other
Freescale controllers using spi-imx driver but could not be tested
due to lack of hardware.
Changes since V3:
Similar to other controller type checks add check function for
IMX51. This also includes IMX53 and IMX6.
Signed-off-by: Anton Bondarenko
---
drivers/spi/spi-imx.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-imx.c b/drivers/spi/spi-imx.c
index
Fixed timeout value can fire while transaction is ongoing. This may happen
because there are no strict requirements on SPI transaction duration.
Dynamic timeout value is generated based on SCLK and transaction size.
There is also 4 * SCLK delay between TX bursts related to CS change.
If SPI device supports DMA mode, but DMA controller is not yet
available due to e.g. a delay in the corresponding kernel module
initialization, retry to initialize SPI driver later on instead of
falling back into PIO only mode.
Signed-off-by: Vladimir Zapolskiy
Signed-off-by: Anton Bondarenko
On SDMA initialization return exactly the same error, which is
reported by dma_request_slave_channel_reason(), it is a preceding
change to defer SPI DMA initialization, if SDMA module is not yet
available.
Signed-off-by: Vladimir Zapolskiy
Signed-off-by: Anton Bondarenko
---
Support for ECSPI loopback for IMX51,IMX53 and IMX6Q using TEST register.
Signed-off-by: Mohsin Kazmi
Signed-off-by: Anton Bondarenko
---
drivers/spi/spi-imx.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/drivers/spi/spi-imx.c b/drivers/spi/spi-imx.c
On Fri, Nov 27, 2015 at 10:25:55AM +0100, Rafał Miłecki wrote:
> On 26 November 2015 at 09:05, Rafał Miłecki wrote:
> > So far struct spi_nor was using just a pointer to struct mtd_info so it
> > wasn't needed to have it fully defined there. After recent change we
> > embed whole struct so we
vmxnet3_drv does check dma_addr with dma_mapping_error()
after mapping dma memory. The patch adds the checks and
tries to handle failures.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/net/vmxnet3/vmxnet3_drv.c | 71
On Fri, Nov 27, 2015 at 02:44:50PM -0600, Rob Herring wrote:
> On Fri, Nov 27, 2015 at 12:37:50PM +, Mark Brown wrote:
> > On Thu, Nov 26, 2015 at 03:57:00PM +0900, Milo Kim wrote:
> > > This binding describes LM3631 and LM3632 regulator properties.
> > Please use subject lines matching the
The following changes since commit 1ec218373b8ebda821aec00bb156a9c94fad9cd4:
Linux 4.4-rc2 (2015-11-22 16:45:59 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/fixes-for-linus
for you to fetch changes up to
The chars_in_buffer() line discipline method serves no functional
purpose, other than as a (dubious) debugging aid for mostly bit-rotting
drivers. Despite being documented as an optional method, every caller
is unconditionally executed (although conditionally compiled).
Furthermore, direct
The open-coded tty_wakeup()s are attempts to workaround fixed bugs
in the line discipline write_wakeup() method. Replace with tty_wakeup().
Cc: Lidza Louina
Cc: Daeseok Youn
Cc: Mark Hounschell
Signed-off-by: Peter Hurley
---
drivers/staging/dgap/dgap.c | 28 ++--
As the #warning indicates, the open-coded ldisc reset was always not ok.
Not only is this code long dead, but now it would have no effect as
the ldisc is destroyed when this driver's close() method returns; remove.
Signed-off-by: Peter Hurley
---
drivers/tty/serial/68328serial.c | 12
As the function documentation for tty_ldisc_ref_wait() notes, it is
only callable from a tty file_operations routine; otherwise there
is no guarantee the ref won't be NULL.
The key difference with the VT's paste_selection() is that is an ioctl,
where __speakup_paste_selection() is completely
After the ldisc is released, but before the tty is destroyed, the termios
is saved (in tty_free_termios()); this termios is restored if a new
tty is created on next open(). However, the line discipline is always
reset, which is not obvious in the current method. Instead, reset
as part of the
tty_ldisc_get() returns ERR_PTR() values if unsuccessful, not NULL;
fix function header documentation.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/drivers/tty/tty_ldisc.c b/drivers/tty/tty_ldisc.c
ioctl(TIOCGETD) retrieves the line discipline id directly from the
ldisc because the line discipline id (c_line) in termios is untrustworthy;
userspace may have set termios via ioctl(TCSETS*) without actually
changing the line discipline via ioctl(TIOCSETD).
However, directly accessing the
tty_ldisc_kill() sets tty->ldisc to NULL; _not_ to N_TTY with a valid
but unopened ldisc. Fix function header documentation.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/tty/tty_ldisc.c
In preparation of destroying line discipline on hangup, fix
ldisc core operations to properly handle when the tty's ldisc is
NULL.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 16
1 file changed, 12 insertions(+), 4 deletions(-)
diff --git
tty file_operations (read/write/ioctl) wait for the ldisc reference
indefinitely (until ldisc lifetime events, such as hangup or TIOCSETD,
finish). Since hangup now destroys the ldisc and does not instance
another copy, file_operations must now be prepared to receive a NULL
ldisc reference from
tty->ldisc is a ptr to struct tty_ldisc, but unfortunately 'ldisc' is
also used as a parameter or local name to refer to the line discipline
index value (ie, N_TTY, N_GSM, etc.); instead prefer the name used
by the line discipline registration/ref counting functions.
Signed-off-by: Peter Hurley
Combined declaration/initialization statements that perform
substantial or important operations are confusing if separated from
the main body by newline; refactor if necessary and remove the newline.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 11 ++-
1 file changed, 2
At tty hangup, the line discipline instance is reinitialized by
closing the current ldisc instance and opening a new instance.
This operation is complicated by error recovery: if the attempt
to reinit the current line discipline fails, the line discipline
is reset to N_TTY (which should not but
In preparation for destroying the line discipline instance on hangup,
move tty_ldisc_kill() to eliminate needless forward declarations.
No functional change.
Signed-off-by: Peter Hurley
---
drivers/tty/tty_ldisc.c | 32 +++-
1 file changed, 19 insertions(+), 13
Currently, when the tty is hungup, the ldisc is re-instanced; ie., the
current instance is destroyed and a new instance is created. The purpose
of this design was to guarantee a valid, open ldisc for the lifetime of
the tty.
However, now that tty buffers are owned by and have lifetime equivalent
The N_HCI ldisc does not define a flush_buffer() ldisc method, so
the check when opening the ldisc is always false.
Cc: Marcel Holtmann
Cc: Johan Hedberg
Cc:
Signed-off-by: Peter Hurley
---
drivers/bluetooth/hci_ldisc.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git
Although n_tty_check_unthrottle() has a valid ldisc reference (since
the tty core gets the ldisc ref in tty_read() before calling the line
discipline read() method), it does not have a valid ldisc reference to
the "other" pty of a pty pair. Since getting an ldisc reference for
tty->link
The N_NCI ldisc does not define a flush_buffer() ldisc method, so
the check when opening the ldisc is always false.
Cc: Lauro Ramos Venancio
Cc: Aloisio Almeida Jr
Cc: Samuel Ortiz
Cc: "David S. Miller"
Cc:
Signed-off-by: Peter Hurley
---
net/nfc/nci/uart.c | 9 +
1 file changed, 1
1 - 100 of 1026 matches
Mail list logo
