On Fri, Dec 22, 2017 at 05:43:50PM +0100, Thomas Gleixner wrote:
> On Fri, 22 Dec 2017, Juergen Gross wrote:
>
> > The patch in the tip tree with commit 506bcdf68b07a0335751e1fe8be37
> > ("x86/pti: Add the pti= cmdline option and documentation") is completely
> > wrong: cmdline_find_option() will
On Tue, Dec 19, 2017 at 11:48:02PM -0800, 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
On 2017-12-13 23:47, Sam Ravnborg wrote:
Hi Andreas.
On Mon, Dec 11, 2017 at 03:58:10PM +0100, Andreas Larsson wrote:
This probes for CASA support, that is commonly present in LEON
processors, and when available, uses the CASA instruction for atomic
operations rather than the spinlock based
On Fri, Dec 22, 2017 at 09:25:53AM -0500, J. Bruce Fields wrote:
> On Fri, Dec 22, 2017 at 09:29:15AM +, Reshetova, Elena wrote:
> >
> > On Wed, Nov 29, 2017 at 01:15:43PM +0200, Elena Reshetova wrote:
> > > atomic_t variables are currently used to implement reference
> > > counters with the
On Fri, Dec 22, 2017 at 09:45:41AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.108 release.
> There are 78 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On 12/22/2017 05:12 PM, Konrad Rzeszutek Wilk wrote:
On Mon, Dec 11, 2017 at 10:45:27AM +0200, Oleksandr Andrushchenko wrote:
ping
..snip..
This is implemented as a change to the sndif protocol [8] and allows
[8]
On Fri, Dec 22, 2017 at 3:03 PM, Paul Moore wrote:
> On Fri, Dec 22, 2017 at 4:14 AM, Dmitry Vyukov wrote:
>> On Thu, Dec 21, 2017 at 9:40 PM, Paul Moore wrote:
>>> On Wed, Dec 20, 2017 at 2:48 AM, syzbot
>>>
On 21 December 2017 at 21:47, Richard Ruigrok wrote:
> Please tested-by
> Tested on Centiq, applied on v4.15-rc4.
> This fixes the regression introduced in 4.13 where the capsule is no longer
> passed in contiguous virtual memory.
>
> On 12/19/2017 3:49 AM, Ge Song
On Fri, Dec 22, 2017 at 08:48:33AM -0700, Nathan Chancellor wrote:
> On Fri, Dec 22, 2017 at 09:45:41AM +0100, Greg Kroah-Hartman wrote:
>
> Merged, compiled, and flashed onto my Pixel 2 XL and OnePlus 5.
>
> No initial issues noticed in general usage or dmesg.
Wonderful, thanks for testing and
On Fri, Dec 22, 2017 at 05:48:45PM +0200, Oleksandr Andrushchenko wrote:
>
> On 12/22/2017 05:12 PM, Konrad Rzeszutek Wilk wrote:
> > On Mon, Dec 11, 2017 at 10:45:27AM +0200, Oleksandr Andrushchenko wrote:
> > > ping
> > ..snip..
> > > > > This is implemented as a change to the sndif protocol
On Fri, Dec 22, 2017 at 03:49:25PM +0100, Michal Hocko wrote:
> On Mon 18-12-17 15:53:20, Michal Hocko wrote:
> > On Fri 01-12-17 08:23:27, Seth Forshee wrote:
> > > On Mon, Sep 25, 2017 at 02:58:25PM +0200, Michal Hocko wrote:
> > > > On Thu 21-09-17 00:40:34, Seth Forshee wrote:
> > [...]
> > >
Bpftool determines it's own version based on the kernel
version, which is picked from the linux/version.h header.
It's strange to use the version of the installed kernel
headers, and makes much more sense to use the version
of the actual source tree, where bpftool sources are.
Fix this by
> On Dec 21, 2017, at 3:51 PM, NeilBrown wrote:
>
> On Thu, Dec 21 2017, Chuck Lever wrote:
>
>> Hi Neil-
>>
>>
>>> On Dec 20, 2017, at 9:57 PM, NeilBrown wrote:
>>>
>>>
>>> When an i_op->getattr() call is made on an NFS file
>>> (typically from a 'stat'
From: Colin Ian King
The function __tee_shm_alloc is local to the source and does
not need to be in global scope, so make it static.
Cleans up sparse warning:
symbol '__tee_shm_alloc' was not declared. Should it be static?
Signed-off-by: Colin Ian King
On 12/21/2017 07:09 PM, Anshuman Khandual wrote:
> I had presented a proposal for NUMA redesign in the Plumbers Conference this
> year where various memory devices with different kind of memory attributes
> can be represented in the kernel and be used explicitly from the user space.
> Here is the
On Wednesday, December 20, 2017 12:58 PM, Felix Brack wrote:
>
> This patch adds a LCD driver supporting the OTM3225A LCD SoC
> from ORISE Technology. This device can drive TFT LC panels having a
> resolution of 240x320 pixels. After initializing the OTM3225A using
> it's SPI interface it
The sysfs documentation for sht3x devices should be with the rest of the
interfaces in Documentation/ABI. The motivation behind this is that
documentation should be where the user expects it to be, rather than
where the developer expects it to be.
ABI documentation requires a specific format and
On Sun, Dec 17, 2017 at 09:50:01PM -0800, syzbot wrote:
>
> syzbot will keep track of this bug report.
> Once a fix for this bug is merged into any tree, reply to this email with:
> #syz fix: exact-commit-title
> If you want to test a patch for this bug, please reply with:
> #syz test:
On Fri, Dec 22, 2017 at 04:11:16PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Dec 22, 2017 at 04:46:28AM -0800, kernelci.org bot wrote:
> > stable-rc/linux-4.14.y boot: 136 boots: 12 failed, 111 passed with 12
> > offline, 1 untried/unknown (v4.14.8-159-gc2a94d1a6095)
> >
> > Full Boot Summary:
From: Thomas Gleixner
The members migrate_enable and nohz_active in the timer/hrtimer per CPU
bases have been introduced to avoid accessing global variables for these
decisions.
Still that results in a (cache hot) load and conditional branch, which can
be avoided by using
On Fri, Dec 22, 2017 at 4:48 PM, Dmitry Vyukov wrote:
On Wed, Dec 20, 2017 at 2:48 AM, syzbot
wrote:
> Hello,
>
> syzkaller hit the following crash on
>
On Fri, Dec 22, 2017 at 02:05:21PM +0800, Chunyan Zhang wrote:
> On 22 December 2017 at 07:26, Rob Herring wrote:
> > On Thu, Dec 21, 2017 at 02:25:02PM +0800, Chunyan Zhang wrote:
> >> + - regulator-suspend-microvolt: the default voltage which regulator
> >> + should
On Fri, 2017-12-22 at 08:43 -0600, Steve Magnani wrote:
> Jan,
>
> Re: [PATCH v4 00/19] fs: rework and optimize i_version handling in filesystems
>
> On 12/22/2017 06:05 AM, Jeff Layton wrote:
>
> > The inode->i_version field is supposed to be a value that changes
> > whenever there is any data
On Fri, Dec 22, 2017 at 04:08:39PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Dec 22, 2017 at 09:44:45AM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.14.9 release.
> > There are 159 patches in this series, all will be posted as a response
> > to this
On Fri, 2017-12-22 at 10:53 +0100, Christian Borntraeger wrote:
> any quick ideas?
Hello Christian,
Was commit afc567a4977b ("dm table: fix regression from improper
dm_dev_internal.count
refcount_t conversion") included in your test kernel?
Bart.
Eugen,
On Fri, Dec 22, 2017 at 4:07 PM, Eugen Hristev
wrote:
> This is the implementation of the Microchip SAMA5D2 SOC resistive
> touchscreen driver.
> --- /dev/null
> +++ b/drivers/input/touchscreen/sama5d2_rts.c
> @@ -0,0 +1,287 @@
> +/*
> + * Microchip
It was <2017-12-22 pią 14:34>, when Philippe Ombredanne wrote:
> Łukasz,
>
> On Fri, Dec 22, 2017 at 2:23 PM, Łukasz Stelmach
> wrote:
>> Add support for True Random Number Generator found in Samsung Exynos
>> 5250+ SoCs.
>>
>> Signed-off-by: Łukasz Stelmach
On Wed, Dec 06, 2017 at 10:19:39PM +0530, Pravin Shedge wrote:
> These duplicate includes have been found with scripts/checkincludes.pl but
> they have been removed manually to avoid removing false positives.
>
> Signed-off-by: Pravin Shedge
>
On 2017-12-22 00:38, Javier Martinez Canillas wrote:
> Hello Peter,
>
> On Fri, Dec 22, 2017 at 12:07 AM, Peter Rosin wrote:
>> On 2017-12-21 21:27, Javier Martinez Canillas wrote:
>>> Hello Peter,
>>>
>>> On Thu, Dec 21, 2017 at 5:20 PM, Peter Rosin wrote:
From: Thomas VanSelus
The Elapsed Time Counter (ETC) registers are not buffered for reading.
If a 250ms tick occurs while data is being read out, the result can be
a combination of old and new values. This can occur at the byte level
(giving a time in the future) or the
This patch leverages the fact that all DS1682 registers are unsigned to
merge two return paths into one. It also introduces val_le as used in
ds1682_store() to merge two endianness conversions into one.
Signed-off-by: Aaron Sierra
---
drivers/misc/ds1682.c | 18
[+Cc keyri...@vger.kernel.org]
On Fri, Dec 22, 2017 at 07:55:01AM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 9035a8961b504d0997369509ab8c6b1f0a4ee33d
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> compiler: gcc (GCC) 7.1.1 20170620
>
On Sun, Dec 10, 2017 at 05:31:01AM -0800, syzbot wrote:
>
> syzbot will keep track of this bug report.
> Once a fix for this bug is merged into any tree, reply to this email with:
> #syz fix: exact-commit-title
> If you want to test a patch for this bug, please reply with:
> #syz test:
---
kernel: 4.4.108-rc1
git repo: https://git.linaro.org/lkft/arm64-stable-rc.git
git tag: 4.4.108-rc1-hikey-20171222-84
git commit: b8f2eb356f221e556c994ffa669f17b9ed885ecf
git describe: 4.4.108-rc1-hikey-20171222-84
Test details:
https://qa-reports.linaro.org/lkft/linar
On Fri, Dec 22, 2017 at 05:13:44PM +0530, Vinod Koul wrote:
> On Fri, Dec 22, 2017 at 09:33:44AM +0100, Greg Kroah-Hartman wrote:
> > On Fri, Dec 22, 2017 at 01:56:56PM +0530, Vinod Koul wrote:
>
> > > Hey Greg,
> > >
> > > So I have spent couple of days on this but don't have a solution.
> > >
On 21 December 2017 at 13:47, PrasannaKumar Muralidharan
wrote:
> Hi Ard,
>
> On 21 December 2017 at 17:52, Ard Biesheuvel
> wrote:
>> On 21 December 2017 at 10:20, Arnd Bergmann wrote:
>>> On Wed, Dec 20, 2017 at 10:46 PM,
Hello Chris,
On Fri, 22 Dec 2017 12:19:04 +1300
Chris Packham wrote:
> From: Kalyan Kinthada
>
> The Armada-370 based SoCs support arbitration between the NAND Flash
> interface and NOR (i.e. devbus) on the same chip
On Fri, Dec 22, 2017 at 10:48 AM, Dmitry Vyukov wrote:
> On Fri, Dec 22, 2017 at 3:03 PM, Paul Moore wrote:
>> On Fri, Dec 22, 2017 at 4:14 AM, Dmitry Vyukov wrote:
>>> On Thu, Dec 21, 2017 at 9:40 PM, Paul Moore
On Fri, Dec 22, 2017 at 09:45:26AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.72 release.
> There are 104 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On 12/22/2017 05:58 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Dec 22, 2017 at 05:48:45PM +0200, Oleksandr Andrushchenko wrote:
On 12/22/2017 05:12 PM, Konrad Rzeszutek Wilk wrote:
On Mon, Dec 11, 2017 at 10:45:27AM +0200, Oleksandr Andrushchenko wrote:
ping
..snip..
This is implemented as
On Fri, Dec 22, 2017 at 08:41:54AM -0600, Eric W. Biederman wrote:
> Alexey Dobriyan writes:
> > unshare
> > fork
> > alloc_pid in level 1 succeeds
> > alloc_pid in level 0 fails, ->idr_next is 2
> > fork
> > alloc pid 2
> > exit
> >
> > Reliable reproducer and
Hi,
On 22/12/2017 at 17:07:21 +0200, Eugen Hristev wrote:
> Add the resistive touchscreen device, and the cell numbers to the
> ADC device.
>
> Signed-off-by: Eugen Hristev
> ---
> arch/arm/boot/dts/sama5d2.dtsi | 12 +++-
> 1 file changed, 11
Dear RT folks!
I'm pleased to announce the v4.14.8-rt9 patch set.
Changes since v4.14.8-rt8:
- Tom Zanussi's "tracing: Inter-event (e.g. latency) support" patch
has been updated to v8.
- The hrtimer-softirq rewrite by Anna-Maria has been updated to v4
(last I claimed I updated to
* Santosh Shilimkar [171222 02:01]:
> On 12/21/2017 3:12 PM, Tony Lindgren wrote:
> > * Stephen Rothwell [171221 21:48]:
> > > Hi Tony,
> > >
> > > Today's linux-next merge of the omap tree got a conflict in:
> > >
> > >
The patch in the tip tree with commit 506bcdf68b07a0335751e1fe8be37
("x86/pti: Add the pti= cmdline option and documentation") is completely
wrong: cmdline_find_option() will return -1 in case the otion isn't
found and the len of the argument in case it has been found.
Juergen
drivers/md/faulty.c has been renamed to md-faulty.c after
following commit merged int to the main line.
935fe0983e09f4f7331ebf5ea4ae2124f6e9f9e8 .
But the file name in fault-injection.txt has not been changed.
Now the actual file name and document are in sync.
Signed-off-by: Masanari Iida
Add support for True Random Number Generator found in Samsung Exynos
5250+ SoCs.
Signed-off-by: Łukasz Stelmach
Reviewed-by: Krzysztof Kozlowski
---
Changes since v4:
- SPDX license header instead of the traditional blurb.
- MODULE_LICENSE("GPL v2")
On Fri, Dec 22, 2017 at 5:03 PM, Paul Moore wrote:
> wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> 6084b576dca2e898f5c101baef151f7bfdbb606d
>> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master
>> compiler:
On Fri, Dec 22, 2017 at 03:51:11PM +0100, Thomas Gleixner wrote:
> Paul was observing weird stalls which are hard to reproduce and decode. We
> were finally able to reproduce and decode the wreckage on RT.
>
> The following series addresses the issues and hopefully nails the root
> cause
On Fri, Dec 22, 2017 at 03:56:03PM +, Mark Brown wrote:
> On Thu, Dec 21, 2017 at 09:05:43PM +, Trent Piepho wrote:
> > On Thu, 2017-12-21 at 14:03 -0600, Kyle Roeschley wrote:
> > > Add a sysfs interface to instantiate and delete SPI devices using the
> > > spidev driver. This can be used
This is a follow-up to commit a5ba91c380b8 ("regmap: debugfs: emit a
debug message when locking is disabled"). I figured that a user may
see this message, grep the code, come to this place and he still won't
know why we actually disabled debugfs.
Add a comment explaining the reason.
On Friday, December 22, 2017 8:48:22 AM CET Linus Walleij wrote:
> On Fri, Dec 22, 2017 at 2:17 AM, Andrew Cooks
> wrote:
> > On 21/12/17 23:02, Christian Lamparter wrote:
>
> >> Just a FYI: due to these difficulties with getting a gpio driver
> >> upstream, Alan
On Fri, Dec 22, 2017 at 06:47:41PM +0100, Javier Martinez Canillas wrote:
> The data field for the entries in the device tables are set but not used.
>
> Signed-off-by: Javier Martinez Canillas
>
>
> Changes in v2:
> - Also empty spaces (suggested by Jason Gunthorpe).
>
>
From: Colin Ian King
In the case that shm->pages fails to allocate, the current exit
error path will try to put_page on a null shm->pages and cause
a null pointer dereference when accessing shm->pages[n]. Fix this
by only performing the put_page and kfree on shm->pages
From: Colin Ian King
Lock glob->lru_lock is locked before the while loop and also
locked again at the end of the while loop; it appears that the
lock at the end of the while loop is a double lock that should
be removed. CoverityScan picked this up with the introduction
From: Steven Rostedt (VMware)
While doing some debugging, I kicked off the stacktrace trigger, to see
what was doing stacktraces in my code (it was causing a lot of noise in
my function traces).
I ran:
# trace-cmd record -p function -l save_stack_trace -l
On Fri, Dec 22, 2017 at 09:45:41AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.108 release.
> There are 78 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
* Kishon Vijay Abraham I [171222 06:06]:
> Hi Rob,
>
> On Thursday 21 December 2017 12:27 AM, Rob Herring wrote:
> > On Tue, Dec 19, 2017 at 02:28:22PM +0530, Kishon Vijay Abraham I wrote:
> >> Add syscon properties required for configuring PCIe in x2 lane mode.
> >>
> >>
On Fri, Dec 22, 2017 at 11:58:08AM +0100, Dmitry Vyukov wrote:
...
> > Same with this one, perhaps related to / fixed by:
> > http://patchwork.ozlabs.org/patch/850957/
> >
>
>
>
> Looking at the log, this one seems to be an infinite loop in SCTP code
> with console output in it. Kernel is
On Wed, Dec 20, 2017 at 12:35:35PM +0100, Javier Martinez Canillas wrote:
> The driver maps the I/O memory address to control the LPC bus CLKRUN_EN,
> but on the error path the memory is accessed by the .clk_enable handler
> after this was already unmapped. So only unmap the I/O memory region if
>
On Thu, Dec 21, 2017 at 03:13:39PM -0800, Azhar Shaikh wrote:
> Commit 3c1701339284353c41 ("tpm: Keep CLKRUN enabled throughout
> the duration of transmit_cmd()") added code which accessed
> chip->ops, even after it was set to NULL in tpm_del_char_device(),
> called from tpm_chip_unregister() in
Em Mon, 18 Dec 2017 09:14:50 -0800
Nick Desaulniers escreveu:
> These were leftover from:
> commit 469ffe083665 ("[media] tda18271c2dd: Remove the CHK_ERROR macro")
> and
> commit 58d5eaec9f87 ("[media] drxd: Don't use a macro for CHK_ERROR ...")
> that programmatically
On Fri, Dec 22, 2017 at 07:12:35PM +0100, Jann Horn wrote:
> This checks that it is not possible to bypass the total stack size check in
> update_stack_depth() by calling a function that uses a large amount of
> stack memory *before* using a large amount of stack memory in the caller.
>
>
On 22/12/17 17:23, Jingoo Han wrote:>> diff --git
a/drivers/video/backlight/otm3225a.c
b/drivers/video/backlight/otm3225a.c
new file mode 100644
index 000..0de75f8
--- /dev/null
+++ b/drivers/video/backlight/otm3225a.c
@@ -0,0 +1,210 @@
+/*
+ * Driver for ORISE Technology OTM3225A SOC for
On Fri, Dec 22, 2017 at 08:48:28AM +0100, Greg Kroah-Hartman wrote:
> I've reverted this from 4.4 and 4.9-stable, but note that this was
Thanks!
> included in 4.14-rc1, so something needs to be done in Linus's tree to
> resolve this issue, otherwise people will hit this as a regression when
>
On Fri, Dec 22, 2017 at 02:06:07PM +0100, Michal Hocko wrote:
>On Fri 22-12-17 13:41:22, Greg KH wrote:
>> On Fri, Dec 22, 2017 at 10:34:07AM +0100, Michal Hocko wrote:
>> > On Fri 22-12-17 09:46:33, Greg KH wrote:
>> > > 4.14-stable review patch. If anyone has any objections, please let me
>> >
On Fri, Dec 22, 2017 at 06:56:16PM +0100, Michal Hocko wrote:
>On Fri 22-12-17 17:40:10, Sasha Levin wrote:
>> On Fri, Dec 22, 2017 at 02:06:07PM +0100, Michal Hocko wrote:
>> >On Fri 22-12-17 13:41:22, Greg KH wrote:
>> >> On Fri, Dec 22, 2017 at 10:34:07AM +0100, Michal Hocko wrote:
>> >> > On
This checks that it is not possible to bypass the total stack size check in
update_stack_depth() by calling a function that uses a large amount of
stack memory *before* using a large amount of stack memory in the caller.
Currently, the first added testcase causes a rejection as expected, but
the
On Fri, Dec 22, 2017 at 4:37 AM, Alexei Starovoitov
wrote:
> On Fri, Dec 22, 2017 at 02:14:45AM +0100, Jann Horn wrote:
>> Hi!
>>
>> I saw the recently-added support for multiple functions in a single
>> program in BPF. I've stumbled over something that looks like it
On Fri 22-12-17 18:07:23, Sasha Levin wrote:
> On Fri, Dec 22, 2017 at 06:56:16PM +0100, Michal Hocko wrote:
> >On Fri 22-12-17 17:40:10, Sasha Levin wrote:
> >> On Fri, Dec 22, 2017 at 02:06:07PM +0100, Michal Hocko wrote:
> >> >On Fri 22-12-17 13:41:22, Greg KH wrote:
> >> >> On Fri, Dec 22,
Hi Mike
On Thu, Dec 21, 2017 at 1:40 AM, Mike Kravetz wrote:
> On 12/20/2017 04:26 PM, Andrew Morton wrote:
>> On Wed, 20 Dec 2017 16:10:51 +0100 Michal Hocko wrote:
>>
>>> On Wed 20-12-17 15:15:50, Marc-André Lureau wrote:
Hi
On Wed,
On Fri, Dec 22, 2017 at 01:18:41PM -0500, Steven Rostedt wrote:
> From: Steven Rostedt (VMware)
>
> While doing some debugging, I kicked off the stacktrace trigger, to see
> what was doing stacktraces in my code (it was causing a lot of noise in
> my function traces).
>
> I
On Fri, Dec 22, 2017 at 05:02:54PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Dec 22, 2017 at 09:45:26AM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.72 release.
> > There are 104 patches in this series, all will be posted as a response
> > to this
> I'm OK with that.
>
> Do you need any more info on the specifics of the machine I'm using?
>
> (Note: I'm not currently aware of any BIOS updates for it. If this is
> ultimately a BIOS problem I wouldn't know what sort of report to file, or how
> to file it anyway...)
>
> Thanks,
> James
I
On Fri, Dec 22, 2017 at 5:38 PM, Łukasz Stelmach wrote:
> It was <2017-12-22 pią 14:34>, when Philippe Ombredanne wrote:
>> Łukasz,
>>
>> On Fri, Dec 22, 2017 at 2:23 PM, Łukasz Stelmach
>> wrote:
>>> Add support for True Random Number Generator
On Fri, 22 Dec 2017 12:30:24 -0600
Josh Poimboeuf wrote:
> I'm officially on vacation but I got a chance to look at this myself a
> few minutes ago. This looks mostly right. In theory, you should able
> to mark those as functions by changing END to ENDPROC. Then you won't
On Wed, Dec 20, 2017 at 07:26:03PM +0100, Javier Martinez Canillas wrote:
> On 12/20/2017 07:10 PM, Jason Gunthorpe wrote:
> > On Wed, Dec 20, 2017 at 03:19:19PM +, Shaikh, Azhar wrote:
> >>> This flag is only used to warn if CLKRUN_EN wasn't disabled on Braswell
> >>> systems, but the only
On Wed, Dec 20, 2017 at 12:43:39PM +0100, Hans de Goede wrote:
> Note I'm just reading along here, but I'm wondering if both the TPM
> and now also some PS/2 controllers need CLK_RUN to be disabled,
> why don't we just disable it once permanently and be done with it?
>
> It seems that on machines
On 12/21/2017 07:39 PM, Stephen Boyd wrote:
On 12/20, Stephen Boyd wrote:
On 12/20, David Lechner wrote:
On 12/20/2017 02:33 PM, David Lechner wrote:
So, the question I have is: what is the actual "correct" behavior of
spin_trylock_irqsave()? Is it really supposed to always return true
when
On Fri, Dec 22, 2017 at 10:12:40AM -0600, Seth Forshee wrote:
> On Fri, Dec 22, 2017 at 03:49:25PM +0100, Michal Hocko wrote:
> > On Mon 18-12-17 15:53:20, Michal Hocko wrote:
> > > On Fri 01-12-17 08:23:27, Seth Forshee wrote:
> > > > On Mon, Sep 25, 2017 at 02:58:25PM +0200, Michal Hocko wrote:
Hi Roman,
2017-12-22 16:11 UTC+ ~ Roman Gushchin
> Bpftool build is broken with binutils version 2.28 and later.
Could you check the binutils version? I believe it changed in 2.29
instead of 2.28. Could you update your commit log and subject
accordingly, please?
> The cause is
This commit adds GPIO driver for Winbond Super I/Os.
Currently, only W83627UHG model (also known as Nuvoton NCT6627UD) is
supported but in the future a support for other Winbond models, too, can
be added to the driver.
A module parameter "gpios" sets a bitmask of GPIO ports to enable (bit 0 is
NAK, ttm_bo_cleanup_refs() is dropping the lock.
Your backtrace is cause by an issue I've fixed this morning on
amd-staging-drm-next.
Regards,
Christian.
Am 22.12.2017 um 19:03 schrieb Colin King:
From: Colin Ian King
Lock glob->lru_lock is locked before the
On Fri, Dec 22, 2017 at 04:28:07PM -0200, Marcelo Ricardo Leitner wrote:
> On Fri, Dec 22, 2017 at 11:58:08AM +0100, Dmitry Vyukov wrote:
> ...
> > > Same with this one, perhaps related to / fixed by:
> > > http://patchwork.ozlabs.org/patch/850957/
> > >
> >
> >
> >
> > Looking at the log,
Hi,
On Fri, Dec 22, 2017 at 09:46:56AM +0100, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Greg Kroah-Hartman
>
> This reverts commit
The data field for the entries in the device tables are set but not used.
Signed-off-by: Javier Martinez Canillas
---
Changes in v2:
- Also empty spaces (suggested by Jason Gunthorpe).
drivers/char/tpm/tpm_i2c_infineon.c | 12 ++--
1 file changed, 6 insertions(+),
On Fri, Dec 22, 2017 at 09:46:13AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.90 release.
> There are 38 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me
On Fri 22-12-17 17:40:10, Sasha Levin wrote:
> On Fri, Dec 22, 2017 at 02:06:07PM +0100, Michal Hocko wrote:
> >On Fri 22-12-17 13:41:22, Greg KH wrote:
> >> On Fri, Dec 22, 2017 at 10:34:07AM +0100, Michal Hocko wrote:
> >> > On Fri 22-12-17 09:46:33, Greg KH wrote:
> >> > > 4.14-stable review
On Fri, Dec 22, 2017 at 10:56:04PM +0530, Aishwarya Pant wrote:
> The sysfs documentation for sht3x devices should be with the rest of the
> interfaces in Documentation/ABI. The motivation behind this is that
> documentation should be where the user expects it to be, rather than
> where the
On Fri, Dec 22, 2017 at 04:54:41PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Dec 22, 2017 at 04:08:39PM +0100, Greg Kroah-Hartman wrote:
> > On Fri, Dec 22, 2017 at 09:44:45AM +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 4.14.9 release.
> > > There
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 by
adding
On Wed, Dec 20, 2017 at 12:35:36PM +0100, Javier Martinez Canillas wrote:
> This flag is only used to warn if CLKRUN_EN wasn't disabled on Braswell
> systems, but the only way this can happen is if the code is not correct.
>
> So it's an unnecessary check that just makes the code harder to read.
Łukasz,
On Fri, Dec 22, 2017 at 5:48 PM, Łukasz Stelmach wrote:
> Add support for True Random Number Generator found in Samsung Exynos
> 5250+ SoCs.
>
> Signed-off-by: Łukasz Stelmach
> Reviewed-by: Krzysztof Kozlowski
> ---
>
On Wed, Dec 20, 2017 at 12:35:37PM +0100, Javier Martinez Canillas wrote:
> The coding style says "use just one data declaration per line (no commas
> for multiple data declarations)" so follow this convention.
>
> Suggested-by: Jarkko Sakkinen
> Signed-off-by:
On Thursday, December 21, 2017 2:18:01 PM CET Dong Aisheng wrote:
> Hi Rafael,
>
> On Thu, Sep 14, 2017 at 02:40:32PM -0700, Viresh Kumar wrote:
> > On 31-08-17, 19:43, Dong Aisheng wrote:
> > > Use clk_bulk_get to ease the driver clocks handling.
> > >
> > > Cc: "Rafael J. Wysocki"
On Mon, Dec 18, 2017 at 9:51 AM, wrote:
> From: Patrick Bruenn
>
> rtc-mxc_v2 driver will add support for the i.MX53 SRTC
>
> Note: we keep the 'srtc' label to avoid duplicate with imx53-m53.dtsi
>
> Signed-off-by: Patrick Bruenn
On Wed, Dec 20, 2017 at 12:35:38PM +0100, Javier Martinez Canillas wrote:
> Commit 5e572cab92f0 ("tpm: Enable CLKRUN protocol for Braswell systems")
> added logic in the TPM TIS driver to disable the Low Pin Count CLKRUN
> signal during TPM transactions.
>
> Unfortunately this breaks other
On Fri, Dec 22, 2017 at 03:32:53PM +0100, Vincent Guittot wrote:
> > The only thing I could come up with is running a timer for this :/ That
> > would keep the ILB thing running until all load is decayed (have a patch
> > for that somewhere).
>
> IMHO running a timer doesn't sound really great
I
On 22/12/2017 10:32 PM, Dongsu Park wrote:
> From: Seth Forshee
>
> When looking up a block device by path no permission check is
> done to verify that the user has access to the block device inode
> at the specified path. In some cases it may be necessary to
> check
As we have option in u-boot to set CPU mask for running linux,
we want to pass information to kernel about CPU cores should
be brought up.
So we patch kernel dtb in u-boot to set CPUs status.
On linux boot we setup cpu possible mask according to status
field in each cpu node. It is generic
701 - 800 of 1842 matches
Mail list logo