On Fri, Mar 03, 2017 at 06:50:06PM -0300, Javier Martinez Canillas wrote:
> Hello Krzysztof,
>
> On 02/11/2017 05:14 PM, Krzysztof Kozlowski wrote:
> > In Odroid XU3 Lite board, the temperature levels reported for thermal
> > zone 0 were weird. In warm room:
> > /sys/class/thermal/thermal_zone
The following changes since commit bc49a7831b1137ce1c2dda1c57e3631655f5d2ae:
Merge branch 'akpm' (patches from Andrew) (2017-02-22 19:29:24 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/
tags/staging-4.11-rc1-part2
for you t
Add __printf compiler verification of format and arguments.
Fix fallout.
Signed-off-by: Joe Perches
---
drivers/scsi/qedf/qedf_dbg.h | 13 -
drivers/scsi/qedf/qedf_fip.c | 2 +-
drivers/scsi/qedf/qedf_io.c | 4 ++--
3 files changed, 11 insertions(+), 8 deletions(-)
diff --git a/d
On 02/15/17 15:31, Andrey Drobyshev wrote:
From: Alexander GQ Gerasiov
In case pps_dec_valid() is called from second_overflow() in the
absence of pps signal, there is no need to decrease pps_valid.
Signed-off-by: Alexander GQ Gerasiov
Acked-by: Rodolfo Giometti
On 02/15/17 15:31, Andrey Drobyshev wrote:
From: Nikita Edward Baruzdin
This commit is supposed to resolve the issue with hard lockups on systems using
jiffies as their clock source. Namely, it sets limits on number of iterations
clock source may remain unchanged (i. e. not being updated for on
On 02/24/17 21:23, Matt Ranostay wrote:
Issue is that x86 32-bit aligns to 4-bytes instead of 8-bytes
so this patchset works around the issue and corrects the data
returned in pps_fdata_compat.
Cc: Rodolfo Giometti
Cc: Moritz Fischer
Cc: George McCollister
Signed-off-by: Matt Ranostay
---
d
On Thu, Mar 02, 2017 at 06:23:19PM -0300, Sergio Prado wrote:
> We are getting a NULL pointer dereference when working with external
> interrupts on s3c24xx:
>
> Unable to handle kernel NULL pointer dereference at virtual address 00a8
> pgd = c0104000
> [00a8] *pgd=
> Internal erro
On 03/04/2017 04:23 AM, David Rientjes wrote:
> Initscripts can use the information (protection levels) from
> /proc/zoneinfo to configure vm.lowmem_reserve_ratio at boot.
>
> vm.lowmem_reserve_ratio is an array of ratios for each configured zone on
> the system. If a zone is not populated on an
On Fri, Mar 03, 2017 at 09:22:06AM +0900, Andi Shyti wrote:
> Hi Hoegeun,
>
> > Hoegeun Kwon (7):
> > arm64: dts: exynos: Add the burst and esc clock frequency properties
> > for exynos5433 dts
> > arm: dts: Add the burst and esc clock frequency properties for
> > exynos3250 dts
> >
Add SPI driver that initializes SPI regmap for the adxl345 core driver.
The driver supports the same functionality as I2C namely the x, y, z and
scale readings.
Signed-off-by: Eva Rachel Retuya
Reviewed-by: Andy Shevchenko
---
Changes from v5:
* Simplify configuration dependency to "depends on I
Add the device tree binding documentation for the ADXL345 3-axis digital
accelerometer.
Signed-off-by: Eva Rachel Retuya
Acked-by: Rob Herring
---
Change from v5:
* Add Rob's Acked-by tag
.../devicetree/bindings/iio/accel/adxl345.txt | 38 ++
1 file changed, 38 inserti
Convert the driver to use regmap instead of I2C-specific functions. This
is done in preparation for splitting this driver into core and
I2C-specific code as well as introduction of SPI driver.
Signed-off-by: Eva Rachel Retuya
Reviewed-by: Andy Shevchenko
---
Changes from v5:
* Re-order local var
Hi,
Thus wrote Bartlomiej Zolnierkiewicz (b.zolnier...@samsung.com):
> Do you mean that you want to have code adding bindings
> and its documentation in separate patches (because that
> is like it was before)?
ok, I'll send the next version as two patches again. Looks like we'll
need another ite
This patchset modifies the adxl345 to use regmap. In doing so, we can
easily introduce SPI support and let regmap handle the rest.
Recap of basic features: read_raw for x, y and z axes, scale. After
applying this series, driver now supports the SPI protocol and enumeration
of device via device tre
Move I2C-specific code into its own file and rely on regmap to access
registers. The core code provides access to x, y, z and scale readings.
Signed-off-by: Eva Rachel Retuya
Reviewed-by: Andy Shevchenko
---
Changes from v5:
* Simplify configuration dependency to "depends on INPUT_ADXL34X=n"
* R
On Thu, Mar 02, 2017 at 02:53:55AM +0100, Samuel Thibault wrote:
> This adds 16bit character support to most of the screen reading by
> extending characters to u16 throughout the code.
>
> Non-latin1 characters are assumed to be alphabetic type for now.
>
> non-latin1 vt_notifier_call-provided ch
Dobry den! :-)
> > > > Ok, I got the camera sensor to work. No subdevices support, so I don't
> > > > have focus (etc) working, but that's a start. I also had to remove
> > > > video-bus-switch support; but I guess it will be easier to use
> > > > video-multiplexer patches...
> > > >
> > > > I'l
Currently, sparse generates many warnings for the driver. This commit
changes the types of struct fields/function variables to match the
endianness at their assignment.
Signed-off-by: Ernestas Kulik
---
Changes from v1:
* Change the type of the variable being passed to ntohs() instead of casting
On Thu, Mar 02, 2017 at 02:53:55AM +0100, Samuel Thibault wrote:
> This adds 16bit character support to most of the screen reading by
> extending characters to u16 throughout the code.
>
> Non-latin1 characters are assumed to be alphabetic type for now.
>
> non-latin1 vt_notifier_call-provided ch
Use a single string literal as the fmt argument passed to dev_err()
instead of multiple string literals split with an embedded backslash
character.
Signed-off-by: Alexander Kapshuk
---
drivers/staging/fbtft/fb_ssd1331.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/
On Fri, 3 Mar 2017, Stephen Hemminger wrote:
> static inline u64 hv_read_tsc_page(const struct ms_hyperv_tsc_page *tsc_pg)
> {
> u64 scale, offset, cur_tsc;
> u32 start;
>
> /*
>* The protocol for reading Hyper-V TSC page is specified in Hypervisor
>* Top-Level Fu
On Fri, 2017-03-03 at 23:24-0800, Joe Perches wrote:
>
> More stuff the changelog doesn't show :(
>
> On Fri, 2017-03-03 at 22:58 +0200, Ernestas Kulik wrote:
> > This fixes type warnings generated by sparse, replaces instances of
> > ntohs() with be16_to_cpu() and removes unused fields in structs.
Hi,
Thus wrote Rob Herring (r...@kernel.org):
> On Mon, Feb 27, 2017 at 11:56:42AM +0100, Martin Kaiser wrote:
> > - fsl,pcr: LCDC PCR value
> > + A display node may optionally define
> > + - fsl,lauscr: LCDC AUS Mode Control Register value (only for imx21)
> Looks like we already got o
Hello Rodolfo,
I should say, that I found this solution is not the best. For example on
high speed PCs (I think over 3GHz) 5 iteration is not enough and module
stops working after several hours. That makes it not user-friendly,
cause user had to calibrate and set failure_iterations manually.
It w
From: Borislav Petkov
It doesn't really start a CPU but does a far jump to C code. So call it
that. Eliminate the unconditional JMP to it from secondary_startup_64()
but make the jump to C code piece part of secondary_startup_64()
instead.
Also, it doesn't need to be a global symbol either so ma
From: Borislav Petkov
... so that callees don't have to convert it and can use it directly.
Simplifies C code a bit. Cleanup comments and formatting in the
vicinity, while at it.
Also, document what phys_base really is.
No functionality change.
Signed-off-by: Borislav Petkov
---
arch/x86/ker
Dear Sir,
Did you recieved my mail?
I have sent it twice without a response.
Mr Masella Giuseppe
Since there's already two copies of this code, introduce a helper now
before we get a third instance.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/futex.c |5 +
kernel/locking/rtmutex.c| 12 +---
kernel/locking/rtmutex_common.h |1 +
3 files cha
The problem with returning -EAGAIN when the waiter state mismatches is
that it becomes very hard to proof a bounded execution time on the
operation. And seeing that this is a RT operation, this is somewhat
important.
While in practise it will be very unlikely to ever really take more
than one or t
By changing futex_lock_pi() to use rt_mutex_*_proxy_lock() we arrive
at a point where all wait_list modifications are done under both
hb->lock and wait_lock.
This closes the obvious interleave pattern between futex_lock_pi() and
futex_unlock_pi(), but not entirely so. See below:
Before:
futex_l
Currently futex-pi relies on hb->lock to serialize everything. Since
hb->lock is giving us problems (PI inversions among other things,
since on -rt hb lock itself is a rt_mutex), we want to break this up a
bit.
This patch reworks and documents the locking. Notably, it
consistently uses rt_mutex::w
There is a weird state in the futex_unlock_pi() path when it
interleaves with a concurrent futex_lock_pi() at the point where it
drops hb->lock.
In this case, it can happen that the rt_mutex wait_list and the
futex_q disagree on pending waiters, in particular rt_mutex will find
no pending waiters
There's a number of 'interesting' problems, all caused by holding
hb->lock while doing the rt_mutex_unlock() equivalient.
Notably:
- a PI inversion on hb->lock; and,
- a DL crash because of pointer instability.
Because of all the previous patches that:
- allow us to do rt_mutex_futex_unlock
Since the futex_q can dissapear the instruction after assigning NULL,
this really should be a RELEASE barrier. That stops loads from hitting
dead memory too.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/futex.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- a/kernel/futex.c
While working on the futex code, I stumbled over this potential
use-after-free scenario.
pi_mutex is a pointer into pi_state, which we drop the reference on in
unqueue_me_pi(). So any access to that pointer after that is bad.
Since other sites already do rt_mutex_unlock() with hb->lock held, see
Thomas spotted that fixup_pi_state_owner() can return errors and we
fail to unlock the rt_mutex in that case.
Reviewed-by: Darren Hart
Reported-by: Thomas Gleixner
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/futex.c |2 ++
1 file changed, 2 insertions(+)
--- a/kernel/futex.c
+++ b/ke
Hi all,
Here be the 5th iteration of these patches; which strive to unlock the rt_mutex
without holding hb->lock.
In total this patch-set is very much like the previous one (including the 'late'
fix) but it gets there in a slightly different -- and hopefully easier to
understand -- route.
The la
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/smsc/smc91x.c | 45 +++--
On 03/03/17 at 04:23pm, Borislav Petkov wrote:
> Ok,
>
> TBH, I still don't like adding yet another define and paying attention
> to whether I should use image size or mapping size. After your patch,
> KERNEL_IMAGE_SIZE is used to enforce the actual image size from
> exploding:
>
> arch/x86/inclu
On Fri, Mar 03, 2017 at 05:15:01PM +0100, Benjamin Tissoires wrote:
> > Firstly, the value reported by the device is still unusual and does not
> > correctly represent the state of the device.
>
> That's a little bit worrying. I still think the patch could be taken,
> but it would be interesting t
On Sat, Mar 04, 2017 at 11:11:32AM +0100, Philippe Reynes wrote:
>
> // lp->port = cmd->port;
Hi,
Review looks good. However, please also update the above comment as
well.
Thanks.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line
On Fri, Mar 03, 2017 at 03:01:23PM -0600, Brijesh Singh wrote:
> +merely enables SME (sets bit 23 of the MSR_K8_SYSCFG), then Linux can
> activate
> +memory encryption by default (CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=y)
> or
> +by supplying mem_encrypt=on on the kernel command line. However, i
Dear Sir,
Did you recieved my mail?
I have sent it twice without a response.
Mr Masella Giuseppe
These are unused and clutter up the code.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/locking/rtmutex-debug.c |9 ---
kernel/locking/rtmutex-debug.h |3 --
kernel/locking/rtmutex.c | 47 +++--
kernel/locking/rtmutex.h |2 -
4
Part of what makes futex_unlock_pi() intricate is that
rt_mutex_futex_unlock() -> rt_mutex_slowunlock() can drop
rt_mutex::wait_lock.
This means we cannot rely on the atomicy of wait_lock, which we would
like to do in order to not rely on hb->lock so much.
The reason rt_mutex_slowunlock() needs t
Hi Steve,
On Fri, Mar 03, 2017 at 02:43:51PM -0800, Steve Longerbeam wrote:
>
>
> On 03/03/2017 03:45 AM, Sakari Ailus wrote:
> >On Thu, Mar 02, 2017 at 03:07:21PM -0800, Steve Longerbeam wrote:
> >>
> >>
> >>On 03/02/2017 07:53 AM, Sakari Ailus wrote:
> >>>Hi Steve,
> >>>
> >>>On Wed, Feb 15, 2
Hi Charles,
2017-03-01 2:04 GMT+09:00 Charles Keepax :
> As the pinctrl is now added before the GPIOs are registered we need to
> manually calculate what the GPIO base will be, otherwise the base for
> each gpio_range will be set to zero. Fortunately the driver
> already assigns a GPIO base, in sa
Sort all devices in alps_model_data by signature and remove
command_mode_resp which is not used anymore.
Signed-off-by: Pali Rohár
---
drivers/input/mouse/alps.c | 56
drivers/input/mouse/alps.h |5
2 files changed, 25 insertions(+), 36 del
Like for other protocols create alps_v4_protocol_data and use it in
alps_identify() function.
Signed-off-by: Pali Rohár
---
drivers/input/mouse/alps.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/input/mouse/alps.c b/drivers/input/mouse/alps.c
index 72
Support for devices with ALPS_PROTO_V9 is not implemented yet but we can
detect these alps touchpads and warn users about it.
Signed-off-by: Pali Rohár
---
drivers/input/mouse/alps.c |9 +
drivers/input/mouse/alps.h |1 +
2 files changed, 10 insertions(+)
diff --git a/drivers/in
This patch series cleanup usage of alps_model_data table.
Changes since v1: Patches for ALPS_PROTO_V6 and ALPS_PROTO_V1 were
dropped and support for those touchpad are still in alps_model_data.
Pali Rohár (3):
Input: alps - move ALPS_PROTO_V4 out of alps_model_data table
Input: alps - warn ab
The ethtool api {get|set}_settings is deprecated.
We move this driver to new api {get|set}_link_ksettings.
As I don't have the hardware, I'd be very pleased if
someone may test this patch.
Signed-off-by: Philippe Reynes
---
Changelog:
v2:
- also update comment (feeback from Russel King)
driver
With the ultimate goal of keeping rt_mutex wait_list and futex_q
waiters consistent we want to split 'rt_mutex_futex_lock()' into finer
parts, such that only the actual blocking can be done without hb->lock
held.
This means we need to split rt_mutex_finish_proxy_lock() into two
parts, one that doe
futex_top_waiter() returns the top-waiter on the pi_mutex. Assinging
this to a variable 'match' totally obscures the code.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/futex.c | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
--- a/kernel/futex.c
+++ b
Since we're going to add more refcount fiddling, introduce
get_pi_state() to match the existing put_pi_state().
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/futex.c | 13 +
1 file changed, 9 insertions(+), 4 deletions(-)
--- a/kernel/futex.c
+++ b/kernel/futex.c
@@ -802,7 +802
[+Chanwoo]
2017-03-04 17:15 GMT+09:00 Krzysztof Kozlowski :
> On Thu, Mar 02, 2017 at 06:23:19PM -0300, Sergio Prado wrote:
>> We are getting a NULL pointer dereference when working with external
>> interrupts on s3c24xx:
>>
>> Unable to handle kernel NULL pointer dereference at virtual address 00
On Sat, Mar 04, 2017 at 06:10:37PM +0800, Baoquan He wrote:
> > BUT(!), don't take my word for it. Rather, do what the maintainers
> > propose. Who knows, they might have a much better idea.
>
> Sorry about that. Just think your words are very convincing on removing
> people's doubt if it's risky
Copy a patch prefix that everyone else has been using:
git log --oneline drivers/staging/media/platform/bcm2835/
The subject is too vague as well.
regards,
dan carpenter
Add function to enable/disable RTS line.
Signed-off-by: Sebastian Reichel
---
drivers/tty/serdev/core.c | 11 +++
drivers/tty/serdev/serdev-ttyport.c | 32
include/linux/serdev.h | 3 +++
3 files changed, 46 insertions(+)
diff --g
This will be used by Nokia's H4+ protocol, which
uses 2-byte aligned packets.
Signed-off-by: Sebastian Reichel
---
drivers/bluetooth/hci_h4.c| 17 +
drivers/bluetooth/hci_ldisc.c | 4
drivers/bluetooth/hci_uart.h | 3 +++
3 files changed, 24 insertions(+)
diff --git
Add bcm2048 node and its system clock to the N900 device tree file.
Apart from that a reference to the new clock has been added to
wl1251 (which uses it, too).
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/omap3-n900.dts | 23 +--
1 file changed, 21 insertions(+), 2
This adds a driver for the Nokia H4+ protocol, which is used
at least on the Nokia N9, N900 & N950.
Signed-off-by: Sebastian Reichel
---
.../devicetree/bindings/net/nokia-bluetooth.txt| 51 ++
drivers/bluetooth/Kconfig | 12 +
drivers/bluetooth/Makefile
Add method to get current CTS line state.
Signed-off-by: Sebastian Reichel
---
drivers/tty/serdev/core.c | 11 +++
drivers/tty/serdev/serdev-ttyport.c | 15 +++
include/linux/serdev.h | 6 ++
3 files changed, 32 insertions(+)
diff --git a/drivers/
From: Rob Herring
This adds library functions for serdev based BT drivers. This is largely
copied from hci_ldisc.c and modified to use serdev calls. There's a little
bit of duplication, but I avoided intermixing this as the ldisc code should
eventually go away.
Signed-off-by: Rob Herring
Cc: Ma
Hi, Andrew,
Sorry, I clicked the wrong button in my mail client, so forgot Ccing
mailing list. Sorry for duplicated mail.
On Sat, Mar 4, 2017 at 6:43 AM, Andrew Morton wrote:
> On Wed, 1 Mar 2017 22:38:09 +0800 "Huang, Ying" wrote:
>
>> Before using cluster lock in free_swap_and_cache(), the
The device driver may need to communicate with the UART
device while the Bluetooth device is closed (e.g. due
to interrupts).
Signed-off-by: Sebastian Reichel
---
drivers/bluetooth/hci_serdev.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git a/drivers/bluetooth/hc
Add method, which waits until the transmission buffer has been sent.
Signed-off-by: Sebastian Reichel
---
drivers/tty/serdev/core.c | 11 +++
drivers/tty/serdev/serdev-ttyport.c | 15 ++-
include/linux/serdev.h | 3 +++
3 files changed, 28 insertions(+
The UPF_BOOT_AUTOCONF flag is needed for proper
flow control support.
Signed-off-by: Sebastian Reichel
---
drivers/tty/serial/omap-serial.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/tty/serial/omap-serial.c b/drivers/tty/serial/omap-serial.c
index 6c6f82ad8d5c..a4734649a0f0
Dear Sir,
Did you recieved my mail?
I have sent it twice without a response.
Mr Masella Giuseppe
The Nokia N950 and N9 have a wl1271 (with nokia bootloader) bluetooth
module connected to second UART.
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/omap3-n950-n9.dtsi | 32
1 file changed, 32 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-n950-n9.d
Hi,
As the title suggest here is another try to get the Nokia bluetooth
supported mainline. The driver is based on the serdev work from Rob
Herring, which got merged into 4.11-rc1 (this patchset is based on
recent master branch from torvalds).
The driver was tested on N950 (I can connect to diffe
-bindings-add-assign-clock-property-in-u2phy-node/20170304-192646
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 4.9.0
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git
Am 03.03.2017 um 20:29 schrieb Kevin Hilman:
> Neil Armstrong writes:
>> On 03/02/2017 01:31 PM, Andreas Färber wrote:
>>> Am 01.03.2017 um 11:46 schrieb Neil Armstrong:
The same MALI-450 MP3 GPU is present in the GXBB and GXL SoCs.
[...]
The node is simply added in the meson-gxbb.dtsi f
On Sat, Mar 04, 2017 at 09:55:51AM +0100, Pavel Machek wrote:
> Dobry den! :-)
Huomenta! :-)
>
> > > > > Ok, I got the camera sensor to work. No subdevices support, so I don't
> > > > > have focus (etc) working, but that's a start. I also had to remove
> > > > > video-bus-switch support; but I g
tty_ldisc_ref_wait() checks tty->ldisc under tty->ldisc_sem.
But if ldisc==NULL it releases them sem and reloads
tty->ldisc without holding the sem. This is wrong and
can lead to returning non-NULL ldisc without protection.
Don't reload tty->ldisc second time.
Signed-off-by: Dmitry Vyukov
Cc: sy
Jiri Slaby writes:
> There is code duplicated over all architecture's headers for
> futex_atomic_op_inuser. Namely op decoding, access_ok check for uaddr,
> and comparison of the result.
>
> Remove this duplication and leave up to the arches only the needed
> assembly which is now in arch_futex_a
If tty_ldisc_open() fails in tty_set_ldisc(), it tries to go back
to the old discipline or N_TTY. But that can fail as well, in such
case it panics. This is not a graceful way to handle OOM.
Leave ldisc==NULL if all attempts fail instead.
Also use existing tty_ldisc_reinit() helper function instea
On Sat, Mar 04, 2017 at 12:51:12AM +, Abel Vesa wrote:
> diff --git a/arch/arm/kernel/entry-ftrace.S b/arch/arm/kernel/entry-ftrace.S
> index c73c403..93f9abb 100644
> --- a/arch/arm/kernel/entry-ftrace.S
> +++ b/arch/arm/kernel/entry-ftrace.S
> @@ -92,12 +92,78 @@
> 2: mcount_exit
> .endm
Hi Pavel,
On Thu, Mar 02, 2017 at 01:38:48PM +0100, Pavel Machek wrote:
> Hi!
>
> > > Ok, how about this one?
> > > omap3isp: add rest of CSI1 support
> > >
> > > CSI1 needs one more bit to be set up. Do just that.
> > >
> > > It is not as straightforward as I'd like, see the comments i
Commit 6a171b299379 ("serial: 8250_dw: Allow hardware flow control to be
used") recently broke the 8250_dw driver on platforms which don't select
HAVE_CLK, as dw8250_set_termios() gets confused by the behaviour of the
fallback HAVE_CLK=n clock API in linux/clk.h which pretends everything
is fine bu
On Fri, Mar 3, 2017 at 8:36 AM, Dmitry Vyukov wrote:
> On Thu, Mar 2, 2017 at 8:37 PM, Greg Kroah-Hartman
> wrote:
>>> >> This is hurting us badly.
>>> >
>>> > Really? How? Are you hitting this a lot? Why now and never before?
>>> > Are you really out of memory?
>>>
>>>
>>> This crashes our te
Hi Russell,
On Fri, Mar 03, 2017 at 11:06:45PM +, Russell King - ARM Linux wrote:
> On Thu, Mar 02, 2017 at 06:02:57PM +0200, Sakari Ailus wrote:
> > Hi Steve,
> >
> > On Wed, Feb 15, 2017 at 06:19:16PM -0800, Steve Longerbeam wrote:
> > > v4l2_pipeline_inherit_controls() will add the v4l2 co
On Fri, Mar 03, 2017 at 01:27:10PM +0100, Jiri Slaby wrote:
> diff --git a/arch/arm/include/asm/futex.h b/arch/arm/include/asm/futex.h
> index 6795368ad023..cc414382dab4 100644
> --- a/arch/arm/include/asm/futex.h
> +++ b/arch/arm/include/asm/futex.h
> @@ -128,20 +128,10 @@ futex_atomic_cmpxchg_ina
On 03/04/17 10:19, Alexander Gerasiov wrote:
Hello Rodolfo,
I should say, that I found this solution is not the best. For example on
high speed PCs (I think over 3GHz) 5 iteration is not enough and module
stops working after several hours. That makes it not user-friendly,
cause user had to calib
Am 28.02.2017 um 01:03 schrieb Rob Herring:
> On Thu, Feb 23, 2017 at 05:45:51PM +0100, Andreas Färber wrote:
>> Add initial device trees for the RTD1295 SoC and the Zidoo X9S TV box.
>>
>> The CPUs lack the enable-method property because the vendor device tree
>> uses a custom "rtk-spin-table" met
On 03/04/17 at 12:55pm, Borislav Petkov wrote:
> On Sat, Mar 04, 2017 at 06:10:37PM +0800, Baoquan He wrote:
> > > BUT(!), don't take my word for it. Rather, do what the maintainers
> > > propose. Who knows, they might have a much better idea.
> >
> > Sorry about that. Just think your words are ve
Hello,
This patch series adds 16bit unicode support to speakup, through three
patches:
- extend synth buffer to 16bit unicode characters
- convert screen reading to 16bit characters
- add unicode variant of /dev/softsynth
Samuel
--
Samuel
"...Unix, MS-DOS, and Windows NT (also known as the Goo
This extends the synth buffer slots to 16bit, so as to hold 16bit
unicode characters.
synth_buffer_getc and synth_buffer_peek now return 16bit characters.
Speech synthesizers which do not support characters beyond latin1 can
use the synth_buffer_skip_nonlatin1() helper to skip the non-latin1
chara
This adds /dev/softsynthu, along /dev/softsynth, which emits output in
UTF-8 encoding, thus allowing to support 16bit characters. Most of the
code is shared, only the read function has to behave differently in
latin1 and in unicode mode. Since Linux only supports 16bit characters,
we can just har
This adds 16bit character support to most of the screen reading by
extending characters to u16 throughout the code.
Non-latin1 characters are assumed to be alphabetic type for now.
non-latin1 vt_notifier_call-provided characters are not ignored any
more, and the 16bit character returned by get_ch
Hi Ingo,
Ping!
Could you please help have a look at thie patchset and give comments or
any suggestion?
Checked the git history, you have been taking care of the
KERNEL_IMAGE_SIZE value changing. Now Kees added his Reviewed-by, Boris
agreed on setting the size of space for kernel mapping to 1G b
On Sat, Mar 4, 2017 at 3:09 PM, James Hogan wrote:
> Commit 6a171b299379 ("serial: 8250_dw: Allow hardware flow control to be
> used") recently broke the 8250_dw driver on platforms which don't select
> HAVE_CLK, as dw8250_set_termios() gets confused by the behaviour of the
> fallback HAVE_CLK=n c
On Sat, Mar 04, 2017 at 10:56:23AM +0200, Ernestas Kulik wrote:
> Currently, sparse generates many warnings for the driver. This commit
> changes the types of struct fields/function variables to match the
> endianness at their assignment.
>
> Signed-off-by: Ernestas Kulik
> ---
> Changes from v1:
Hello,
I am getting the following use-after-free reports while running
syzkaller fuzzer on 86292b33d4b79ee03e2f43ea0381ef85f077c760 (but also
happened on 6dc39c50e4aeb769c8ae06edf2b1a732f3490913 and
c82be9d2244aacea9851c86f4fb74694c99cd874).
===
On Mon, 20 Feb 2017 12:19:24 -0700
Jim Davis wrote:
> Exception occurred:
> File "/usr/lib/python3.5/site-packages/docutils/writers/_html_base.py", line
> 671, in depart_document
> assert not self.context, 'len(context) = %s' % len(self.context)
> AssertionError: len(context) = 1
Just in c
If tty_ldisc_open() fails in tty_set_ldisc(), it tries to go back
to the old discipline or N_TTY. But that can fail as well, in such
case it panics. This is not a graceful way to handle OOM.
Leave ldisc==NULL if all attempts fail instead.
Also use existing tty_ldisc_reinit() helper function instea
After commit 0549bde0fcb1 ("of: fix of_node leak caused in
of_find_node_opts_by_path"), the following error may be
reported when running omap images.
OF: ERROR: Bad of_node_put() on /ocp@6800
CPU: 0 PID: 0 Comm: swapper Not tainted 4.10.0-rc7-next-20170210 #1
Hardware name: Generic OMAP3-GP (F
The device node returned by of_find_node_by_name() needs to be released
after it is no longer needed to avoid a device node leak.
Signed-off-by: Guenter Roeck
---
v3: Split patch into two parts
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletion
On 03/02/2017 09:31 AM, Alexandre Belloni wrote:
Because the only way to use the driver is to have a device tree enabling
it, pdev->dev.of_node will never be NULL. Remove the unnecessary check.
Signed-off-by: Alexandre Belloni
Reviewed-by: Guenter Roeck
---
drivers/watchdog/sama5d4_wdt.c
On 03/02/2017 09:31 AM, Alexandre Belloni wrote:
WDT_MR and WDT_CR must not updated within three slow clock periods after
the last ping (write to WDT_CR or WDT_MR). Ensure enough time has elapsed
before writing those registers.
wdt_write() waits for 4 periods to ensure at least 3 edges are seen b
1 - 100 of 299 matches
Mail list logo
