On Sun, Dec 17, 2017 at 03:07:55AM +0530, Harsh Shandilya wrote:
> Ran checkpatch across the entire drivers/android
> directory and fixed all relevant warnings. Summary
> of changes done:
>
> -> Convert all symbolic permissions into their
> octal equivalents.
> -> Use "%s", __func__ in loggi
On Sat, 2017-12-16 at 23:44 +, Colin King wrote:
> From: Colin Ian King
>
> Trivial fix to spelling mistake in dev_dbg debug message. Also
> add in a missing comma.
>
> Signed-off-by: Colin Ian King
Ack
Thanks
Tomas
From: devesh pradhan
Fixed a "foo * bar" and add tab coding style issue
Signed-off-by: devesh pradhan
---
mm/filemap.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/mm/filemap.c b/mm/filemap.c
index a49702445ce0..e14d62876980 100644
--- a/mm/filemap.c
+++ b/mm
The performance of some aead tfm providers is affected by
the amount of parallelism possible with the processing.
Introduce an async aead concurrent multiple buffer
processing speed test to be able to test performance of such
tfm providers.
Signed-off-by: Gilad Ben-Yossef
---
crypto/tcrypt.c |
The multi buffer concurrent requests ahash speed test only
supported the cycles mode. Add support for the so called
jiffies mode that test performance of bytes/sec.
We only add support for digest mode at the moment.
Signed-off-by: Gilad Ben-Yossef
---
crypto/tcrypt.c | 112 +
The performance of some skcipher tfm providers is affected by
the amount of parallelism possible with the processing.
Introduce an async skcipher concurrent multiple buffer
processing speed test to be able to test performance of such
tfm providers.
Signed-off-by: Gilad Ben-Yossef
---
crypto/tcr
The AEAD speed test pretended to support decryption, however that support
was broken as decryption requires a valid auth field which the test did
not provide.
Fix this by running the encryption path once with inout/output sgls
switched to calculate the auth field prior to performing decryption
spe
The performance of some crypto tfm providers is affected by
the amount of parallelism possible with the processing.
We already had some support for speed test of multiple concurrent
requests, dubbed multi buffer, in ahash speed tests.
For multiple buffers speed tests, the number of buffers, or
requests, used actually sets the level of parallelism a tfm
provider may utilize to hide latency. The existing number
(of 8) is good for some software based providers but not
enough for many HW providers with deep FIFOs.
Add a module para
The multi buffer ahash speed test was allocating multiple
buffers for use with the multiple outstanding requests
it was starting but never actually using them (except
to free them), instead using a different single statically
allocated buffer for all requests.
Fix this by actually using the alloca
* Andy Lutomirski wrote:
> > Is this tree looking good to you standalone?
>
> I think this stuff is looking okay, although I'm a bit mystified by
> the whole merge base thing. But if the backporters and Linus like it,
> then whatever.
To explain the merge base thing: considering that v4.14 is
Hi Marek,
On Wed, 11 Oct 2017 23:34:33 +0200
Marek Vasut wrote:
> On 10/11/2017 03:54 PM, Arnd Bergmann wrote:
> > The map_word_() functions, dating back to linux-2.6.8, try to perform
> > bitwise operations on a 'map_word' structure. This may have worked
> > with compilers that were current the
Hello!
I was trying to investigate why all my old kernels can't be booted on my
relatively new machine. Kernels 4.10+ naturally boot - I use 4.14.3 right now -
but old kernels die early ...
After some digging I found this
https://patchwork.kernel.org/patch/9311567/
Patch talk about family 12h,
This patchset removes some warnings generated by checkpatch
for cleanup of the rtl8723bs driver. Also some additional
cleanups are introduced in the *[1/4] and *[3/4] patches
to make the code according to the kernel coding style.
Shreeya Patel (4):
Staging: rtl8723bs: Replace true with x and fa
Replace true and false keywords with "x" and "!x"
respectively to follow the kernel coding style.
Signed-off-by: Shreeya Patel
---
drivers/staging/rtl8723bs/hal/sdio_ops.c | 30 ++
1 file changed, 14 insertions(+), 16 deletions(-)
diff --git a/drivers/staging/rtl8723
Change names of some variables and functions to conform
to the kernel coding style.
Signed-off-by: Shreeya Patel
---
drivers/staging/rtl8723bs/hal/sdio_ops.c | 714 +++
1 file changed, 357 insertions(+), 357 deletions(-)
diff --git a/drivers/staging/rtl8723bs/hal/sdi
Change the conditional operator to assignment as it is
not a conditional statement.
Signed-off-by: Shreeya Patel
---
drivers/staging/rtl8723bs/hal/sdio_ops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/hal/sdio_ops.c
b/drivers/staging/rtl8723bs/
If "x" is compared to NULL, use "!x" instead of it, so
as to follow the kernel coding style.
Signed-off-by: Shreeya Patel
---
drivers/staging/rtl8723bs/hal/sdio_ops.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/staging/rtl8723bs/hal/sdio_ops.c
On Fri, 8 Dec 2017 18:41:46 +0100
Stefan Brüns wrote:
> iio_push_to_buffers_with_timestamp expects a void pointer, so the cast
> is both unnecessary and misleading.
>
> Signed-off-by: Stefan Brüns
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play wit
On Fri, 8 Dec 2017 18:41:47 +0100
Stefan Brüns wrote:
> The timestamp is inserted into the buffer after the sample data by
> iio_push_to_buffers_with_timestamp, document the space requirement for
> the timestamp.
>
> Signed-off-by: Stefan Brüns
Applied and pushed out as testing for the autobuil
On Sun, 2017-12-17 at 15:07 +0530, Shreeya Patel wrote:
> Replace true and false keywords with "x" and "!x"
> respectively to follow the kernel coding style.
[]
> diff --git a/drivers/staging/rtl8723bs/hal/sdio_ops.c
> b/drivers/staging/rtl8723bs/hal/sdio_ops.c
[]
> @@ -191,8 +191,8 @@ static u32
test_sort.c perform array-based and linked list sort test. Code allows to
compile either as a loadable modules or builtin into the kernel.
Current code is not allow to unload the test_sort.ko module after
successful completion.
This patch add support to unload the "test_sort.ko" module.
Signed-o
On Sun, 2017-12-17 at 01:45 -0800, Joe Perches wrote:
> On Sun, 2017-12-17 at 15:07 +0530, Shreeya Patel wrote:
> >
> > Replace true and false keywords with "x" and "!x"
> > respectively to follow the kernel coding style.
> []
> >
> > diff --git a/drivers/staging/rtl8723bs/hal/sdio_ops.c
> > b/dr
Hi Anthony,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051
commit: 842ff286166e8512450573f6b6eb5e04e626a07f Input: add support for HiDeep
touchscreen
date: 5 weeks ago
con
On Wed, 13 Dec 2017 00:48:40 +0100
Stefan Brüns wrote:
> On Tuesday, December 12, 2017 9:15:30 PM CET Jonathan Cameron wrote:
> > On Sun, 10 Dec 2017 21:53:42 +0100
> >
> > Stefan Brüns wrote:
> > > On Sunday, December 10, 2017 6:27:33 PM CET Jonathan Cameron wrote:
> > > > On Fri, 8 Dec 20
Wei Wang wrote:
> > But passing GFP_NOWAIT means that we can handle allocation failure. There is
> > no need to use preload approach when we can handle allocation failure.
>
> I think the reason we need xb_preload is because radix tree insertion
> needs the memory being preallocated already (it c
lib/rbtree_test.c code allows to compile either as a loadable modules or
builtin into the kernel.
Current code returns -EAGAIN on successful termination from module_init.
Such a fail will directly unload the module and hence there is no scope
to execute rbtree_test_exit on module_exit.
This patch
2017-12-17 17:56 GMT+08:00 syzbot
:
> Hello,
>
> syzkaller hit the following crash on
> 41d8c16909ebda40f7b4982a7f5e2ad102705ade
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is attached.
>
Hi Linus,
here are 4 fixes for the watchdog device drivers.
Please pull.
Kind regards,
Wim.
The following changes since commit f3b5ad89de16f5d42e8ad36fbdf85f705c1ae051:
Merge tag 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma (2017-12-16 13:43:08
-0800)
are availabl
On Sat, Dec 16, 2017 at 10:24:31PM +0100, Thomas Gleixner wrote:
> From: Andy Lutomirski
>
> Shrink vmalloc space from 16384TiB to 12800TiB to enlarge the hole starting
> at 0xff90 to be a full PGD entry.
>
> A subsequent patch will use this hole for the pagetable isolation LDT
> ali
On Sat, Dec 16, 2017 at 10:24:32PM +0100, Thomas Gleixner wrote:
> From: Andy Lutomirski
>
> With PTI enabled, the LDT must be mapped in the usermode tables somewhere.
> The LDT is per process, i.e. per mm.
>
> An earlier approach mapped the LDT on context switch into a fixmap area,
> but that's
lib/percpu_test.c code allows to compile either as a loadable modules or
builtin into the kernel.
Current code returns -EAGAIN on successful termination from module_init.
Such a fail will directly unload the module and hence there is no scope
to execute percpu_test_exit on module_exit.
Signed-off
On Sat, 16 Dec 2017, Andy Lutomirski wrote:
> On Fri, Dec 15, 2017 at 8:07 AM, Ingo Molnar wrote:
> I few things I noticed in the PTI tree:
>
> "x86/mm/pti: Map ESPFIX into user space" has a leftover pr_err().
> Sorry, my bad, I've spent *way* too long looking at this crap to
> retain my sanity.
> -Original Message-
> From: Tetsuo Handa [mailto:penguin-ker...@i-love.sakura.ne.jp]
> Sent: Sunday, December 17, 2017 6:22 PM
> To: Wang, Wei W ; wi...@infradead.org
> Cc: virtio-...@lists.oasis-open.org; linux-kernel@vger.kernel.org; qemu-
> de...@nongnu.org; virtualizat...@lists.linux
On Fri, 8 Dec 2017 18:41:49 +0100
Stefan Brüns wrote:
> The conversion time can be up to 16 seconds (8 ms per channel, 2 channels,
> 1024 times averaging).
>
> Signed-off-by: Stefan Brüns
Applied
> ---
>
> drivers/iio/adc/ina2xx-adc.c | 8 +---
> 1 file changed, 5 insertions(+), 3 deletio
On Tue, 12 Dec 2017 20:21:14 +
Jonathan Cameron wrote:
> On Sun, 10 Dec 2017 21:47:37 +0100
> Stefan Brüns wrote:
>
> > On Sunday, December 10, 2017 6:31:57 PM CET Jonathan Cameron wrote:
> > > On Fri, 8 Dec 2017 18:41:50 +0100
> > >
> > > Stefan Brüns wrote:
> > > > The iio timesta
Hello,
I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a
NAND flash. While I could get OpenWRT to work flawlessly on it using
kernel 4.4, mainline 4.14.6 fails with a lot of such messages :
pxa3xx-nand f10d.flash: Wait time out!!!
Looking a bit closer, I found that i
Hello
I noticed my system is less stable after upgrade from kernel 4.13 to
4.14.6 yesterday. There was a soft CPU lockup, hard CPU lockup and one
kernel panic while shutting down the system, all on the same day. There
was little diagnostic information collected at the time, but since then
I've en
Hi Willy,
On Sun, 17 Dec 2017 13:05:03 +0100
Willy Tarreau wrote:
> Hello,
>
> I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a
> NAND flash. While I could get OpenWRT to work flawlessly on it using
> kernel 4.4, mainline 4.14.6 fails with a lot of such messages :
>
>
On Wed, 13 Dec 2017 15:00:39 +0100
Crt Mori wrote:
> There is no option to perform 64bit integer sqrt on 32bit platform.
> Added stronger typed int_sqrt64 enables the 64bit calculations to
> be performed on 32bit platforms. Although int_sqrt() is a rough
> approximation, the same algorithm is use
On Wed, 13 Dec 2017 18:10:34 +0100
Andreas Klinger wrote:
> Return value in hx711_reset() should indicate status of dout otherwise the
> calling function is reporting an error as false positive
>
> If there are two reads too close to each other, then the second one will
> never succeed. This hap
On Wed, 13 Dec 2017 18:10:11 +0100
Andreas Klinger wrote:
> Add buffer to device data struct and add trigger function
>
> Data format is quite simple:
> voltage - channel 0 32 Bit
> voltage - channel 1 32 Bit
> timestamp 64 Bit
>
> Using both channels at the sa
On Fri, 15 Dec 2017 08:59:23 +0100
Maciej Purski wrote:
> Calibration register is used for calculating current register in
> hardware according to datasheet:
> current = shunt_volt * calib_register / 2048 (ina 226)
> current = shunt_volt * calib_register / 4096 (ina 219)
>
> Fix calib_register v
cc devicet...@vger.kernel.org
On 12/14/2017 10:35 PM, Jacek Anaszewski wrote:
> On 12/11/2017 05:27 PM, Rob Herring wrote:
>> On Mon, Dec 4, 2017 at 4:43 AM, Pavel Machek wrote:
>>> Hi!
>>>
Label property was imposed a uniqueness requirement, which was erroneous,
since ePAPR defines it
On Sat, 2017-12-16 at 15:17 +1100, NeilBrown wrote:
> On Wed, Dec 13 2017, Jeff Layton wrote:
>
> > On Thu, 2017-12-14 at 09:04 +1100, NeilBrown wrote:
> > > On Wed, Dec 13 2017, Jeff Layton wrote:
> > >
> > > > +/*
> > > > + * The change attribute (i_version) is mandated by NFSv4 and is mostly
Hi Boris!
On Sun, Dec 17, 2017 at 01:33:55PM +0100, Boris Brezillon wrote:
> You should have a look at this thread [1], and in case you don't want
> to read everything,
I've read it entirely, it was very instructive!
> you can just test the solution proposed here [2].
>
> [1]http://linux-mtd.in
This has happend again, and hopefully the report is not as mangled as
the previous one. I was also trying to start "systemctl status", only
once this time. The kernel build is different because I've just disabled
RCU tracing/debugging options. One more thing, this kernel was built with gcc
7.2.1
2017-12-17 0:32 GMT+08:00 Bruno Wolff III :
> On Fri, Dec 15, 2017 at 13:51:22 -0600,
> Bruno Wolff III wrote:
>>
>>
>> I do not know what is different. Do you have any ideas? Most likely I
>> won't be able to test any more kernels until Monday (unless I can use most
>> of my most recent build ov
On Saturday, December 16, 2017 3:22 AM, Matthew Wilcox wrote:
> On Fri, Dec 15, 2017 at 10:49:15AM -0800, Matthew Wilcox wrote:
> > Here's the API I'm looking at right now. The user need take no lock;
> > the locking (spinlock) is handled internally to the implementation.
Another place I saw your
Hello,
On Sat, Dec 16, 2017 at 6:51 PM, Stephen Hemminger
wrote:
> It makes sense to organize the config if you dont break old configs.
> It would be more logical to group and treat all para-virtualized guest
> support in same way. Hyper-V should be next to KVM and Xen.
I agree, I can try to wo
On 17 December 2017 at 10:17, Willy Tarreau wrote:
> Hi Boris!
>
> On Sun, Dec 17, 2017 at 01:33:55PM +0100, Boris Brezillon wrote:
>> You should have a look at this thread [1], and in case you don't want
>> to read everything,
>
> I've read it entirely, it was very instructive!
>
>> you can just
On 17 December 2017 at 09:05, Willy Tarreau wrote:
> Hello,
>
> I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a
> NAND flash. While I could get OpenWRT to work flawlessly on it using
> kernel 4.4, mainline 4.14.6 fails with a lot of such messages :
>
> pxa3xx-nand f10d00
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.x86/pti.entry
head: 6891282dd3ab7fead975ed52d0f7f8da37ab96a5
commit: c2bc66082e1048c7573d72e62f597bdc5ce13fea [10/39] locking/barriers: Add
implicit smp_read_barrier_depends() to READ_ONCE()
config: h8300-h8300h-sim_defconf
On Sun, 17 Dec 2017 11:27:51 -0300
Ezequiel Garcia wrote:
> On 17 December 2017 at 09:05, Willy Tarreau wrote:
> > Hello,
> >
> > I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a
> > NAND flash. While I could get OpenWRT to work flawlessly on it using
> > kernel 4.4, mainli
On Sun, Dec 17, 2017 at 03:53:05PM +0100, Boris Brezillon wrote:
> On Sun, 17 Dec 2017 11:27:51 -0300
> Ezequiel Garcia wrote:
>
> > On 17 December 2017 at 09:05, Willy Tarreau wrote:
> > > Hello,
> > >
> > > I recently bought a Linksys WRT1900ACS which hosts an Armada 385 and a
> > > NAND flash
* Ingo Molnar wrote:
> > was supposed to be a synchronization point, but if you do
> >
> > git diff 9a818d1a3235..9a818d1a3235^
> >
> > it isn't actually synchronized. It's *almost* synchronized, but not
> > quite. How did those cherry-picks that were already upstream end up
> > causing *c
Linus,
Please pull the latest WIP.x86-pti.base.prep-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.x86-pti.base.prep-for-linus
# HEAD: 1784f9144b143a1e8b19fe94083b040aa559182b drivers/misc/intel/pti:
Rename the header file to free up the namespace
Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
A single bugfix which prevents arbitrary sigev_notify values in
posix-timers.
Thanks,
tglx
-->
Thomas Gleixner (1)
On Sun, Dec 17, 2017 at 04:00:43PM +0100, Willy Tarreau wrote:
> > > Any idea why this issue is on v4.14, but not observed on v4.4?
> >
> > I have absolutely no idea.
>
> Warning, the 4.4 in openwrt very likely is heavily patched! That's also
> why I'm moving to mainline instead (to know what I'm
On Sun, Dec 17, 2017 at 12:41:42PM +0100, Thomas Gleixner wrote:
> > X86_BUG_CPU_SECURE_MODE_PTI should be added to DISABLED_FEATURES or
> > DISABLED_BUGS or whatever if it's not configured in, which will reduce
> > bloat. Borislav, that's kind of up your alley, since I don't think
> > the appropr
Linus,
Please pull the latest WIP.x86-pti.base-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.x86-pti.base-for-linus
# HEAD: 2aeb07365bcd489620f71390a7d2031cd4dfb83e x86/mm/kasan: Don't use
vmemmap_populate() to initialize shadow
Note, this tree s
Wang, Wei W wrote:
> > Wei Wang wrote:
> > > > But passing GFP_NOWAIT means that we can handle allocation failure.
> > > > There is no need to use preload approach when we can handle allocation
> > > > failure.
> > >
> > > I think the reason we need xb_preload is because radix tree insertion
> > >
Linus,
Please pull the latest WIP.x86-pti.entry-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
WIP.x86-pti.entry-for-linus
# HEAD: 6cbd2171e89b13377261d15e64384df60ecb530e x86/cpufeatures: Make CPU
bugs sticky
The main changes here are Andy Lutomirski
On Sat, Dec 16, 2017 at 10:46:05PM -0500, Nicolas Pitre wrote:
> Date: Fri, 10 Nov 2017 15:57:21 +0100
> From: Arnd Bergmann
> Subject: [PATCH] cramfs: fix MTD dependency
>
> With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
>
> fs/cramfs/inode.o: In function `cramfs_mount':
> in
On 14/12/2017 10:32 PM, Dmitry Torokhov wrote:
On Thu, Dec 14, 2017 at 12:15 PM, Casey Leedom wrote:
Thanks Dmitry! I've asked Komali to test it against the problem that she
reported internally. She or I will get back to you on that testing ASAP.
I see that we've now moved on to 4.1
On 17 December 2017 at 12:00, Willy Tarreau wrote:
> On Sun, Dec 17, 2017 at 03:53:05PM +0100, Boris Brezillon wrote:
>> On Sun, 17 Dec 2017 11:27:51 -0300
>> Ezequiel Garcia wrote:
>>
>> > On 17 December 2017 at 09:05, Willy Tarreau wrote:
>> > > Hello,
>> > >
>> > > I recently bought a Linksys
On Sun, Dec 17, 2017 at 21:43:50 +0800,
weiping zhang wrote:
Hi, thanks for testing, I think you first reproduce this issue(got WARNING
at device_add_disk) by your own build, then add my debug patch.
No, the first log (that Laura copied) was from the Fedora bug and it was
from a Fedora kerne
On Sun, 17 Dec 2017, Pravin Shedge wrote:
lib/rbtree_test.c code allows to compile either as a loadable modules or
builtin into the kernel.
Current code returns -EAGAIN on successful termination from module_init.
Such a fail will directly unload the module and hence there is no scope
to execute
On Sat, Dec 16, 2017 at 07:31:33PM +0100, Philippe Ombredanne wrote:
> Please consider using the new SPDX tags per Thomas doc patches [1],
> and already adopted by other Intel contributors
> Thanks!
> [1] https://lkml.org/lkml/2017/12/4/934
Hi, sure, I can do this. I'm sorry that I missed your ema
On 04:45-20171217, Jassi Brar wrote:
> On Sun, Dec 17, 2017 at 3:19 AM, Nishanth Menon wrote:
> > On 08:21-20171213, Lokesh Vutla wrote:
> >>
> >>
> >> On Saturday 02 December 2017 03:52 PM, Nishanth Menon wrote:
> >> > Switch to SPDX licen
+Alexander
On Sun, Dec 17, 2017 at 08:55:57PM +0800, Fengguang Wu wrote:
> Hello,
>
> FYI this happens in mainline kernel 4.15.0-rc3.
> It looks like a new regression.
>
> It occurs in 4 out of 28 boots.
>
> [ 166.090516]
> ==
>
On Sun, Dec 17, 2017 at 12:53:36PM -0300, Ezequiel Garcia wrote:
> If not too much to ask, this is the test that I believe is needed.
> You seem to have a setup ready, hence why I'm asking you, if
> possible, to give it a shot.
>
> (1) Scrub the BBT from the NAND. Or scrub the whole NAND.
> You ca
On Friday, December 15, 2017 8:59:23 AM CET Maciej Purski wrote:
> Calibration register is used for calculating current register in
> hardware according to datasheet:
> current = shunt_volt * calib_register / 2048 (ina 226)
> current = shunt_volt * calib_register / 4096 (ina 219)
>
> Fix calib_reg
On Sat, Dec 16, 2017 at 08:59:06PM +0100, Javier Martinez Canillas wrote:
> On 12/15/2017 01:03 PM, Jarkko Sakkinen wrote:
> > Hi
> >
> > Some basic questions about DT, which I'm not expert of.
> >
> > On Mon, Dec 04, 2017 at 06:39:16PM +0100, Javier Martinez Canillas wrote:
> >> The commit 21dc0
On Sun, 17 Dec 2017, Fengguang Wu wrote:
> Hello,
>
> FYI this happens in mainline kernel 4.15.0-rc3.
> It looks like a new regression.
>
> It occurs in 23 out of 36 boots.
>
> [ 38.592360] LUN: removable file: (no medium)
> [ 38.593442] no file given for LUN0
> [ 38.594589] g_mass_storag
Heya Linus,
Here are the fixes for this time round consisting of fixes in bunch and
driver and dmatest module.
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the git repository at:
git://git.infradead
On Sat, Dec 16, 2017 at 11:47 PM, syzbot
wrote:
> Hello,
>
> syzkaller hit the following crash on
> 6084b576dca2e898f5c101baef151f7bfdbb606d
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console output is
On 17/12/2017 5:29 PM, Tariq Toukan wrote:
On 14/12/2017 10:32 PM, Dmitry Torokhov wrote:
On Thu, Dec 14, 2017 at 12:15 PM, Casey Leedom
wrote:
Thanks Dmitry! I've asked Komali to test it against the problem
that she reported internally. She or I will get back to you on that
testing
Hi Alexandre,
With very small amount of code in arch/mips this series looks really nice.
On 8 December 2017 at 21:16, Alexandre Belloni
wrote:
> Hi,
>
> This patch series adds initial support for the Microsemi MIPS SoCs. It
> is currently focusing on the Microsemi Ocelot (VSC7513, VSC7514).
>
>
alloc_super() one is this window regression, lazytime thing
is older...
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/
This fixes "utmi_phy_clk_enable: timeout waiting for phy to stabilize"
error message.
Signed-off-by: Dmitry Osipenko
---
Change log:
v2: Increased delay for the poll retry from 1us to 2000ms, thanks to
Thierry Reding for the suggestion.
drivers/usb/phy/phy-tegra-usb.c | 14 +---
Tegra's PHY driver has a mix of pr_err() and dev_err(), let's switch to
dev_err() and use common errors message formatting across the driver for
consistency.
Signed-off-by: Dmitry Osipenko
---
Change log:
v2: Removed function names as per Thierry's suggestion.
drivers/usb/phy/phy-tegra-usb
Currently tegra-phy driver is built only when ehci-tegra is. Add own
Kconfig entry for tegra-phy so that drivers other than ehci-tegra (like
ChipIdea) could work without ehci-tegra.
Signed-off-by: Dmitry Osipenko
---
Change log:
v2: Added missed USB_ULPI dependency to USB_TEGRA_PHY.
driver
Previously tegra-phy driver was built only when ehci-tegra was, now
tegra-phy has its own Kconfig entry. Remove the USB_PHY dependencies
from ehci-tegra's Kconfig since they aren't useful anymore.
Signed-off-by: Dmitry Osipenko
---
drivers/usb/host/Kconfig | 3 ---
1 file changed, 3 deletions(-)
UTMI pads are shared by USB controllers and reset of UTMI pads is shared
with the reset of USB1 controller. Currently reset of UTMI pads is done by
the EHCI driver and ChipIdea UDC works because EHCI driver always happen
to be probed first. Move reset controls from ehci-tegra to tegra-phy in
order
Am 04.12.2017 um 21:18 schrieb Dan Carpenter:
On Mon, Dec 04, 2017 at 08:59:35PM +0200, Marcus Wolf wrote:
Am 04.12.2017 um 12:33 schrieb Dan Carpenter:
On Sun, Dec 03, 2017 at 04:17:26PM +0100, Simon Sandström wrote:
diff --git a/drivers/staging/pi433/pi433_if.h b/drivers/staging/pi433/pi43
On Sat, Dec 09, 2017 at 05:24:24PM +0100, Christophe Leroy wrote:
> CHECK lib/usercopy.c
> lib/usercopy.c:26:13: warning: incorrect type in argument 1 (different
> address spaces)
> lib/usercopy.c:26:13:expected void const volatile [noderef]
> *
> lib/usercopy.c:26:13:got void *to
> l
On Fri, Dec 15, 2017 at 5:48 PM, Dan Williams wrote:
> On Fri, Dec 15, 2017 at 6:09 AM, Christoph Hellwig wrote:
>> We can just pass this on instead of having to do a radix tree lookup
>> without proper locking 2 levels into the callchain.
>>
>> Signed-off-by: Christoph Hellwig
>
> Yeah, the loo
On Fri, Dec 15, 2017 at 6:09 AM, Christoph Hellwig wrote:
> This is a pretty big function, which should be out of line in general,
> and a no-op stub if CONFIG_ZONE_DEVICЕ is not set.
>
> Signed-off-by: Christoph Hellwig
> Reviewed-by: Logan Gunthorpe
[..]
> +/**
> + * get_dev_pagemap() - take a
host1x_syncpt_wait() takes timeout value in jiffies, but DRM passes it in
milliseconds.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/drm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/tegra/drm.c b/drivers/gpu/drm/tegra/drm.c
index bb98336fa8d
HW reset isn't actually broken on Tegra20, but there is a dependency on
first display controller to be taken out of reset for the second to be
enabled successfully.
Signed-off-by: Dmitry Osipenko
---
Change log:
v2: Got rid of global variable and now use driver_find_device() instead.
drive
Commit 7772fdaef939 ("drm/tegra: Support ARGB and ABGR formats") broke
DRM's MODE_ADDFB IOCTL on Tegra20/30, because it uses XRGBA format if
requested FB depth is 24bpp. As a result, Xorg doesn't work anymore with
both modesetting and opentegra drivers. On all Tegra's each plane has a
blending conf
Older Tegra's do not support RGBA format for the cursor, but instead
overlay plane could be used for it. Since there is no much use for the
overlays on a regular desktop and HW-accelerated cursor is much nicer
than the jerky SW cursor, let's trade one overlay plane for the cursor.
Signed-off-by: D
On Fri, Dec 15, 2017 at 6:09 AM, Christoph Hellwig wrote:
> Change the calling convention so that get_dev_pagemap always consumes the
> previous reference instead of doing this using an explicit earlier call to
> put_dev_pagemap in the callers.
>
> The callers will still need to put the final refe
iommu_map_sg() doesn't return a error value, but a size of the requested
IOMMU mapping or zero in case of error.
Signed-off-by: Dmitry Osipenko
---
drivers/gpu/drm/tegra/gem.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/tegra/gem.c b/drivers/
On Fri, Dec 15, 2017 at 6:09 AM, Christoph Hellwig wrote:
> All callers are gone now.
>
> Signed-off-by: Christoph Hellwig
> ---
Nice,
Reviewed-by: Dan Williams
On 11.12.2017 16:27, Mauro Carvalho Chehab wrote:
> Em Tue, 10 Oct 2017 23:34:45 +0200
> "Maciej S. Szmigiero" escreveu:
>
>> This commit adds pin to pad mapping and output format configuration support
>> in CX2584x-series chips to cx25840 driver.
>>
>> This functionality is then used to allow di
> The change is good.
> The commit message would better simply describe the problem instead
> of describing the symptom. For example, something like:
> The function _copy_to_user() is used to copy to address space.
> As such, the destination pointer should be annotated with
> '__u
On Fri, Dec 15, 2017 at 6:09 AM, Christoph Hellwig wrote:
> __radix_tree_insert already checks for duplicates and returns -EEXIST in
> that case, so remove the duplicate (and racy) duplicates check.
>
> Signed-off-by: Christoph Hellwig
> Reviewed-by: Logan Gunthorpe
> ---
> kernel/memremap.c |
This series adds support for analog part of Medion 95700 in the cxusb
driver.
What works:
* Video capture at various sizes with sequential fields,
* Input switching (TV Tuner, Composite, S-Video),
* TV and radio tuning,
* Video standard switching and auto detection,
* Radio mode switching (stereo
1 - 100 of 414 matches
Mail list logo
