Hi all,
Today's linux-next merge of the kvm-arm tree got conflicts in:
arch/arm64/include/asm/kvm_host.h
arch/arm64/kvm/hyp/switch.c
between commit:
55e3748e8902 ("arm64: KVM: Add ARCH_WORKAROUND_2 support for guests")
from the arm64 tree and commits:
fa89d31c5306 ("KVM: arm64:
On 2018-06-01 15:02, Joel Fernandes wrote:
On Fri, Jun 01, 2018 at 12:07:48PM +0900, Byungchul Park wrote:
On 2018-05-25 14:13, Byungchul Park wrote:
On 2018-05-09 15:33, Byungchul Park wrote:
On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
Sorry for the huge delay
On Fri, Jun 01, 2018 at 12:07:48PM +0900, Byungchul Park wrote:
>
>
> On 2018-05-25 14:13, Byungchul Park wrote:
> >
> >
> > On 2018-05-09 15:33, Byungchul Park wrote:
> > > On Thu, Jan 11, 2018 at 10:07:16AM +0100, Peter Zijlstra wrote:
> > > >
> > > >
> > > > Sorry for the huge delay on
On Mon, Jan 08, 2018 at 03:14:41PM +0900, byungchul park wrote:
> Currently, migrating tasks to cpu0 unconditionally happens when the
> heap is empty, since cp->elements[].cpu was initialized to 0(=cpu0).
> We have to distinguish between the empty case and cpu0 to avoid the
> unnecessary
On Thu, May 31, 2018 at 11:12:55PM -0700, Joel Fernandes wrote:
> On Mon, Jan 08, 2018 at 03:14:41PM +0900, byungchul park wrote:
> > Currently, migrating tasks to cpu0 unconditionally happens when the
> > heap is empty, since cp->elements[].cpu was initialized to 0(=cpu0).
> > We have to
On Thu, May 31, 2018 at 09:48:23PM +0200, Sabin Mihai Rapan wrote:
> In the first patch series I forgot to CC linux-kernel@vger.kernel.org and
> assumed (wrongly) that the patch series will be ignored.
> In an attempt to fix that, I sent the second patch series with proper
> CC added. I should
Hi Bjorn,
Thanks for this much needed consolidation.
On 5/23/2018 10:50 AM, Bjorn Andersson wrote:
> Shared between all Hexagon V5 based remoteprocs is the handling of the 5
> interrupts and the SMP2P stop request, so break this out into a separate
> function in order to allow these drivers to
Hi Bjorn,
On 5/23/2018 10:50 AM, Bjorn Andersson wrote:
> Migrate the Hexagon V5 PAS (ADSP) driver to using the newly extracted
> helper functions. The use of the handover callback does introduce latent
> disabling of proxy resources. But apart from this there should be no
> change in
On Thu, May 31, 2018 at 09:07:24AM -0500, Rob Herring wrote:
> On Thu, May 31, 2018 at 5:23 AM, Matti Vaittinen
> wrote:
> > On Thu, May 31, 2018 at 10:17:17AM +0300, Matti Vaittinen wrote:
> >> On Wed, May 30, 2018 at 10:01:29PM -0500, Rob Herring wrote:
> >> > On Wed, May 30, 2018 at 11:42:03AM
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in:
arch/arm64/include/asm/cpufeature.h
between commits:
a43ae4dfe56a ("arm64: Add 'ssbd' command-line option")
c32e1736ca03 ("arm64: ssbd: Add global mitigation state accessor")
647d0519b53f ("arm64: ssbd: Restore
On Wed, May 23, 2018 at 04:26:04PM +0800, Huang, Ying wrote:
> From: Huang Ying
>
> Hi, Andrew, could you help me to check whether the overall design is
> reasonable?
>
> Hi, Hugh, Shaohua, Minchan and Rik, could you help me to review the
> swap part of the patchset? Especially [02/21],
On Fri, May 25, 2018 at 01:08:38AM +0100, David Howells wrote:
> Make it possible to clone a mount tree with a new pair of open flags that
> are used in conjunction with O_PATH:
>
> (1) O_CLONE_MOUNT - Clone the mount or mount tree at the path.
>
> (2) O_NON_RECURSIVE - Don't clone
Hi Greg,
Today's linux-next merge of the driver-core tree got a conflict in:
include/linux/device.h
between commit:
3d6ce86ee794 ("drivers: remove force dma flag from buses")
from the dma-mapping tree and commit:
8c97a46af04b ("driver core: hold dev's parent lock when needed")
from
On Wed, 2018-04-25 at 13:26 +0300, Mika Westerberg wrote:
> On Tue, Apr 24, 2018 at 06:05:12PM +0300, Andy Shevchenko wrote:
> > According to documentation the function has 2 bits for reset
> > while iDMA 64-bit has only one.
> >
> > Rename it accordingly. Note, there is no functional change
Prepare for migrating swapper_pg_dir, introduce new_swapper_pg_dir
to save virtual address of swapper_pg_dir.
Signed-off-by: Jun Yao
---
arch/arm64/include/asm/mmu_context.h | 2 +-
arch/arm64/include/asm/pgtable.h | 1 +
arch/arm64/mm/kasan_init.c | 2 +-
arch/arm64/mm/mmu.c
To defense KSMA, we need to migrate tramp_pg_dir and swapper_pg_dir
together. Make them adjacent to avoid modifying tramp_(un)map_kernel.
Signed-off-by: Jun Yao
---
arch/arm64/kernel/entry.S | 4 ++--
arch/arm64/kernel/vmlinux.lds.S | 9 +
2 files changed, 7 insertions(+), 6
Introduce __pa_swapper_pg_dir to save physical address of
swapper_pg_dir. And pass it as an argument to __enable_mmu().
Signed-off-by: Jun Yao
---
arch/arm64/include/asm/mmu_context.h | 4 +---
arch/arm64/include/asm/pgtable.h | 1 +
arch/arm64/kernel/cpufeature.c | 2 +-
Currently, The offset between swapper_pg_dir and _text is
fixed. When attackers know the address of _text(no KASLR or
breaking KASLR), they can caculate the address of
swapper_pg_dir. Then KSMA(Kernel Space Mirroring Attack) can
be applied.
The principle of KSMA is to insert a carefully
On Thu, May 31, 2018 at 05:30:24PM +, Dilger, Andreas wrote:
> On May 31, 2018, at 18:54, Greg Kroah-Hartman
> wrote:
> >
> > On Tue, May 29, 2018 at 10:21:45AM -0400, James Simmons wrote:
> >> From: "John L. Hammond"
> >>
> >> Pre 2.10.1 MDTs will crash when they receive a listxattr
Add driver for serial-connected u-blox GNSS receivers.
Note that the driver uses the generic GNSS serial implementation and
therefore essentially only manages power abstracted into three power
states: ACTIVE, STANDBY, and OFF.
For u-blox receivers with a main supply and no enable-gpios, this
Add driver for serial-connected SiRFstar-based GNSS receivers.
These devices typically boot into hibernate mode from which they can be
woken using a pulse on the ON_OFF input pin. Once active, a pulse on the
same ON_OFF pin is used to put the device back into hibernate mode. The
current state can
Add a "type" device attribute and a "GNSS_TYPE" uevent variable which
can be used to determine the type of a GNSS receiver. The currently
identified types reflect the protocol(s) supported by a receiver:
"NMEA" NMEA 0183
"SiRF" SiRF Binary
"UBX" UBX
Note that both
Add binding for SiRFstar-based GNSS receivers.
Note that while four compatible-strings are initially added representing
devices which differ in which I/O interfaces they support, they
otherwise essentially share the same feature set.
Pin and supply names vary slightly, as do some recommended
Hi David,
On 05/26/2018 06:38 AM, David Collins wrote:
>
>> +[1] = _mx,
>> +[2] = _mx_ao,
>> +[3] = _cx,
>> +[4] = _cx_ao,
>> +[5] = _lmx,
>> +[6] = _lcx,
>> +[7] = _gfx,
>> +[8] = _mss,
>> +};
>> +
>> +static const struct rpmhpd_desc sdm845_desc = {
>> +
Hi Dan,
Today's linux-next merge of the nvdimm tree got a conflict in:
drivers/dax/super.c
between commits:
ba23cba9b3bd ("fs: allow per-device dax status checking for filesystems")
80660f20252d ("dax: change bdev_dax_supported() to support boolean returns")
from the xfs tree and
Now the hwlock core has supplied new function to get a specific hwlock id
by one hwlock name, which is more clear for users. So change to use
of_hwspin_lock_get_id_byname().
Signed-off-by: Baolin Wang
---
drivers/spi/spi-sprd-adi.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On (06/01/18 10:53), Petr Mladek wrote:
> [...]
>
> > So I'd say that most likely the following scenarios can suffer:
> >
> > - NMI comes in, sets loglevel to X, printk-s some data, restores the
> > loglevel back to Y
> > - IRQ comes in [like sysrq, etc] comes in and does the same thing
> > -
> -Original Message-
> From: Tejun Heo [mailto:hte...@gmail.com] On Behalf Of 't...@kernel.org'
> Sent: Wednesday, May 30, 2018 1:26 AM
> To: Hatayama, Daisuke
> Cc: 'gre...@linuxfoundation.org' ; Okajima,
> Toshiyuki ;
> linux-kernel@vger.kernel.org; 'ebied...@aristanetworks.com'
>
>
On Fri, Jun 1, 2018 at 3:42 AM, Kees Cook wrote:
> Make sure that the memory allocators are behaving as expected in the face
> of overflows.
> #include
> #include
> #include
> +#include
> +#include
> +#include
A nit, can we keep it in order?
--
With Best Regards,
Andy Shevchenko
Hi Bjorn,
On 5/23/2018 10:50 AM, Bjorn Andersson wrote:
> Migrate the MSS remoteproc driver to use the newly extracted helper
> functions.
>
> Signed-off-by: Bjorn Andersson
> ---
> drivers/remoteproc/Kconfig | 4 +
> drivers/remoteproc/qcom_q6v5_pil.c | 157
On Thu, May 31, 2018 at 9:05 PM, Eric W. Biederman
wrote:
> Nagarathnam Muthusamy writes:
>
>> Ping? Any additional comments on this patch?
>
> Konstantin's v5 no.
>
> I am uncomfortable with unnecessary flexibility. I don't want to
> encourage the increased usage of pids to identify
The LKP robot found a 27% will-it-scale/page_fault3 performance regression
regarding commit e27be240df53("mm: memcg: make sure memory.events is
uptodate when waking pollers").
What the test does is:
1 mkstemp() a 128M file on a tmpfs;
2 start $nr_cpu processes, each to loop the following:
2.1
On 2018-06-01 15:18, Joel Fernandes wrote:
On Thu, May 31, 2018 at 11:12:55PM -0700, Joel Fernandes wrote:
On Mon, Jan 08, 2018 at 03:14:41PM +0900, byungchul park wrote:
Currently, migrating tasks to cpu0 unconditionally happens when the
heap is empty, since cp->elements[].cpu was
On Thu, May 31, 2018 at 09:51:05PM -0700, Zhenzhong Duan wrote:
> Free useless ucode_patch entry when it's replaced.
>
> Signed-off-by: Zhenzhong Duan
> ---
> arch/x86/kernel/cpu/microcode/intel.c | 10 +-
> 1 files changed, 9 insertions(+), 1 deletions(-)
>
> diff --git
On 06/01/2018 03:46 AM, Steve Longerbeam wrote:
>
>
> On 05/31/2018 12:37 PM, Marek Vasut wrote:
>> On 05/31/2018 08:52 PM, Steve Longerbeam wrote:
>>>
>>> On 05/31/2018 11:35 AM, Marek Vasut wrote:
On 05/31/2018 08:32 PM, Steve Longerbeam wrote:
> Hi Marek,
>
>
> On
On Fri, 1 Jun 2018 00:16:32 +0200
Stefan Agner wrote:
> Add Reed-Solomon (RS) to the enumeration of ECC algorithms.
>
> Signed-off-by: Stefan Agner
Reviewed-by: Boris Brezillon
> ---
> drivers/mtd/nand/raw/nand_base.c | 1 +
> include/linux/mtd/rawnand.h | 1 +
> 2 files changed, 2
On Mon, May 28, 2018 at 07:40:19PM +0800, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed a +23.0% improvement of vm-scalability.throughput due to
> commit:
>
>
> commit: 309fe96bfc0ae387f53612927a8f0dc3eb056efd ("mm, memcontrol: implement
> memory.swap.events")
>
On Fri, Jun 01, 2018 at 05:08:25PM +1000, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the driver-core tree got a conflict in:
>
> include/linux/device.h
>
> between commit:
>
> 3d6ce86ee794 ("drivers: remove force dma flag from buses")
>
> from the dma-mapping tree
On Thu 31-05-18 14:16:34, David Rientjes wrote:
> On Thu, 31 May 2018, Michal Hocko wrote:
>
> > > It's not a random timeout, it's sufficiently long such that we don't oom
> > > kill several processes needlessly in the very rare case where oom
> > > livelock
> > > would actually prevent the
On Thu, May 31, 2018 at 1:06 PM, Gao Xiang wrote:
> Hi all,
>
> Read-only file systems are used in many cases, such as read-only storage
> media.
> We are now focusing on the Android device which several read-only partitions
> exist.
> Due to limited read-only solutions, a new read-only file
On Wed, May 30, 2018 at 12:17:56PM -0700, Kees Cook wrote:
> In the quest to remove all stack VLA usage from the kernel[1], this
> allocates the maximum size expected for all possible attrs and adds
> sanity-checks at both registration and usage to make sure nothing
> gets out of sync.
>
> [1]
>
[added linux-api]
On Fri, May 25, 2018 at 3:08 AM, David Howells wrote:
> Make it possible to clone a mount tree with a new pair of open flags that
> are used in conjunction with O_PATH:
>
> (1) O_CLONE_MOUNT - Clone the mount or mount tree at the path.
>
> (2) O_NON_RECURSIVE - Don't clone
On Tue, May 29, 2018 at 10:21:58AM -0400, James Simmons wrote:
> From: Dmitry Eremin
>
> Change goto label out to err.
Again, this says what it does, not why.
Hi Sergey,
>> but the problem is real.
>
>Yep, could be. But not exactly the way it is described in the commit
>messages and the patch does not fully address the problem.
>
>The patch assumes that all those events happen sequentially. While
>in reality they can happen in parallel on different
On Fri, 2018-06-01 at 09:35 +0800, Ian Kent wrote:
> On Thu, 2018-05-31 at 17:13 -0700, Andrew Morton wrote:
> > On Wed, 30 May 2018 17:18:55 +0800 Ian Kent wrote:
> >
> > > > I actually had an alternative approach that I tried out successfully
> > > > but discarded as being too different from
Amir Goldstein wrote:
> Reject O_NON_RECURSIVE without O_CLONE_MOUNT?
Yes, I should add that.
> I am not sure what are the consequences of opening O_PATH with old kernel
> and getting an open file, can't think of anything bad.
> Can the same be claimed for O_PATH|O_CLONE_MOUNT?
Yes, actually,
On Fri 2018-06-01 13:40:50, Sergey Senozhatsky wrote:
> On (05/31/18 14:21), Petr Mladek wrote:
> > >
> > > Upstream printk has no printing kthread. And we also run
> > > printk()->console_unlock() with disabled preemption.
> >
> > Yes, the comment was wrong
>
> Yes, that was the only thing I
On Fri 2018-06-01 10:53:56, Petr Mladek wrote:
> On Fri 2018-06-01 13:40:50, Sergey Senozhatsky wrote:
> > On (05/31/18 14:21), Petr Mladek wrote:
> > > >
> > > > Upstream printk has no printing kthread. And we also run
> > > > printk()->console_unlock() with disabled preemption.
> > >
> > >
On 01.06.2018 01:16, Stefan Agner wrote:
> Add support for the NAND flash controller found on NVIDIA
> Tegra 2 SoCs. This implementation does not make use of the
> command queue feature. Regular operations/data transfers are
> done in PIO mode. Page read/writes with hardware ECC make
> use of the
On 01/06/18 09:08, Jun Yao wrote:
Currently, The offset between swapper_pg_dir and _text is
fixed. When attackers know the address of _text(no KASLR or
breaking KASLR), they can caculate the address of
swapper_pg_dir. Then KSMA(Kernel Space Mirroring Attack) can
be applied.
The principle of
On 31-05-18 17:34, Stephen Boyd wrote:
Quoting Mike Looijmans (2018-05-31 07:03:55)
The si544 driver had a rounding problem that using the result of clk_round_rate
may set the clock to yet another rate, for example:
clk_round_rate(19500) = 19499
clk_round_rate(19499) = 19498
First of all - Thanks for looking at this!
On Thu, May 31, 2018 at 08:10:39AM -0700, Stephen Boyd wrote:
> Quoting Matti Vaittinen (2018-05-30 01:43:19)
> > diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> > index 41492e980ef4..4b045699bb5e 100644
> > --- a/drivers/clk/Kconfig
> > +++
On Fri, Jun 1, 2018 at 6:23 AM, Kai-Heng Feng
wrote:
> There are two new events generated by dell-wmi, rfkill and fn-lock, from
> Dell Systems.
>
> When Fn-lock hotkey gets pressed to switch to function mode:
> [85951.591542] dell_wmi: Unknown key with type 0x0010 and code 0xe035
> pressed
>
Switch to bitmap_zalloc() to show clearly what we are allocating.
Besides that it returns pointer of bitmap type instead of opaque void *.
Signed-off-by: Andy Shevchenko
---
drivers/input/keyboard/gpio_keys.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
A lot of code become ugly because of open coding allocations for bitmaps.
Introduce three helpers to allow users be more clear of intention
and keep their code neat.
Signed-off-by: Andy Shevchenko
---
include/linux/bitmap.h | 16
1 file changed, 16 insertions(+)
diff --git
On Wed, May 30, 2018 at 2:38 AM, Masahiro Yamada
wrote:
> 2018-05-28 21:23 GMT+09:00 Masahiro Yamada :
>> 2018-05-28 18:21 GMT+09:00 Masahiro Yamada :
>
> I pushed this series to the for-next branch.
> Unless a significant problem is reported,
> I'd like to merge this series in the upcoming MW.
On Tue, May 29, 2018 at 10:21:47AM -0400, James Simmons wrote:
> From: Amir Shehata
>
> Move from num_possible_cpus() to nr_cpu_ids.
This says what you did, not _why_ you did it. If these functions are
really identical, why do we have both of them? :)
greg k-h
Hi Yogesh,
On 30.05.2018 16:24, Boris Brezillon wrote:
Hi Yogesh,
On Wed, 30 May 2018 13:50:51 +
Yogesh Narayan Gaur wrote:
Hi Frieder,
Thanks for migrating the fsl-quadspi.c driver on the new SPI
framework. This patch is using dynamic LUT approach to create the LUT
at run time instead
On Fri, Jun 01, 2018 at 12:25:43AM +0530, Sankalp Negi wrote:
> This patch fixes following checkpatch.pl issues:
>
> WARNING : line over 80 characters
> ERROR : code indent should use tabs where possible
> WARNING : no spaces at the start of a line
> ERROR : switch and case should be at the
Am Freitag, 1. Juni 2018, 11:11:21 CEST schrieb Gao Xiang:
> > In which sense is it extendable?
>
> Actually, the meaning of an enhanced (means not just read-only, but with the
> scalable
> on-disk layout, compression, or fs-verify in the future) read-only file
> system is emphasized.
ah ok.
Hi Boris,
On 30.05.2018 17:10, Boris Brezillon wrote:
On Wed, 30 May 2018 15:14:34 +0200
Frieder Schrempf wrote:
The FSL QSPI driver was moved to the SPI framework and it now
acts as a SPI controller. Therefore the subnodes need to set
spi-[rx/tx]-bus-width = <4>, so quad mode is used just
Hi Jia-Ju,
On Fri, Jun 1, 2018 at 2:59 AM, Jia-Ju Bai wrote:
> On 2018/6/1 5:13, Steven Rostedt wrote:
>> On Thu, 31 May 2018 18:42:48 +0200
>> Geert Uytterhoeven wrote:
>>> On Thu, May 31, 2018 at 5:19 PM, Stephen Boyd wrote:
Quoting Linus Torvalds (2018-05-31 07:32:10)
> On Thu, May
Printk format "%pCr" will be removed soon, as clk_get_rate() must not be
called in atomic context.
Replace it by printing the variable that already holds the clock rate.
Note that calling clk_get_rate() is safe here, as the code runs in task
context.
Signed-off-by: Geert Uytterhoeven
---
On Fri, Jun 1, 2018 at 11:24 AM, Stefan Hajnoczi wrote:
> Ping?
>
> Archive link in case I broke email threading:
> https://marc.info/?l=linux-fsdevel=152719324102009=2
Thanks for the patch. Should already be fixed in:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-next
"%pCr" formats the current rate of a clock, and calls clk_get_rate().
The latter obtains a mutex, hence it must not be called from atomic
context.
Remove support for this rarely-used format, as vsprintf() (and e.g.
printk()) must be callable from any context.
Any remaining out-of-tree users will
Hi all,
"%pCr" formats the current rate of a clock, and calls clk_get_rate().
The latter obtains a mutex, hence it must not be called from atomic
context. As vsprintf() (and e.g. printk()) must be callable from any
context, it's better to remove support for this (rarely-used) format.
On Mon, May 14, 2018 at 10:06:22AM +0200, Linus Walleij wrote:
> As we augmented the regulator core to accept a GPIO descriptor instead
> of a GPIO number, we can augment the fixed GPIO regulator to look up
> and pass that descriptor directly from device tree or board GPIO
> descriptor look up
Hello,
On (06/01/18 14:12), Vaneet Narang wrote:
> > CPU0CPU1
> >
> > set console verbose
> >
> > dump_backtrace()
> > {
> > // for (;;) print frames
> > printk("%pS\n", frame0);
> > printk("%pS\n", frame1);
> > printk("%pS\n", frame2);
> > printk("%pS\n",
On Fri, Jun 01, 2018 at 11:33:11AM +0200, Pavel Machek wrote:
> Hi!
>
> > This series adds a new subsystem for GNSS receivers (e.g. GPS
> > receivers).
> >
> > While GNSS receivers are typically accessed using a UART interface they
> > often also support other I/O interfaces such as I2C, SPI and
On Fri, Jun 01, 2018 at 11:35:11AM +0200, Thierry Reding wrote:
> > cfg.ena_gpio_invert = !config->enable_high;
> Change this line to:
> cfg.ena_gpio_invert = false;
> fixes the regression and is pretty much the implementation of my above
> suggestion to ignore enable-active-high,
On Thu, May 31, 2018 at 11:26:54PM -0700, Christoph Hellwig wrote:
> On Fri, May 25, 2018 at 01:08:38AM +0100, David Howells wrote:
> > Make it possible to clone a mount tree with a new pair of open flags that
> > are used in conjunction with O_PATH:
> >
> > (1) O_CLONE_MOUNT - Clone the mount
Hi,
On Thursday 31 May 2018 06:59 PM, Tero Kristo wrote:
> On 31/05/18 13:14, Faiz Abbas wrote:
>> Hi,
>>
>> On Thursday 31 May 2018 09:33 AM, Rob Herring wrote:
>>> On Wed, May 30, 2018 at 07:41:30PM +0530, Faiz Abbas wrote:
Add clkctrl data for the m_can clocks and register it within the
Naoya Horiguchi writes:
> On Wed, May 23, 2018 at 04:26:04PM +0800, Huang, Ying wrote:
>> From: Huang Ying
>>
>> Hi, Andrew, could you help me to check whether the overall design is
>> reasonable?
>>
>> Hi, Hugh, Shaohua, Minchan and Rik, could you help me to review the
>> swap part of the
On Fri, 1 Jun 2018 00:16:33 +0200
Stefan Agner wrote:
> Allow to define a NAND chip as a boot device. This can be helpful
> for the selection of the ECC algorithm and strength in case the boot
> ROM supports only a subset of controller provided options.
>
> Signed-off-by: Stefan Agner
On Fri, 1 Jun 2018 00:16:34 +0200
Stefan Agner wrote:
> This adds the devicetree binding for the Tegra 2 NAND flash
> controller.
>
> Signed-off-by: Lucas Stach
> Signed-off-by: Stefan Agner
> ---
> .../bindings/mtd/nvidia-tegra20-nand.txt | 64 +++
> 1 file changed, 64
On Fri, 01 Jun 2018 00:35:18 +0200,
Bo Chen wrote:
>
> When 'kzalloc()' fails in 'snd_hda_attach_pcm_stream()', a new pcm instance is
> created without setting its operators via 'snd_pcm_set_ops()'. Following
> operations on the new pcm instance can trigger kernel null pointer
> dereferences
>
On Fri, 2018-05-18 at 14:51 +0100, Lee Jones wrote:
> On Tue, 24 Apr 2018, Andy Shevchenko wrote:
>
> > According to documentation REMAP register has to be programmed in
> > either DMA or PIO mode of the slice.
> >
> > Move the DMA capability check below to let REMAP register be
> > programmed
>
Hi Stephen,
On 01/06/18 07:23, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the kvm-arm tree got conflicts in:
>
> arch/arm64/include/asm/kvm_host.h arch/arm64/kvm/hyp/switch.c
>
> between commit:
>
> 55e3748e8902 ("arm64: KVM: Add ARCH_WORKAROUND_2 support for
> guests")
This series adds a new subsystem for GNSS receivers (e.g. GPS
receivers).
While GNSS receivers are typically accessed using a UART interface they
often also support other I/O interfaces such as I2C, SPI and USB, while
yet other devices use iomem or even some form of remote-processor
messaging
Switch to bitmap_zalloc() to show clearly what we are allocating.
Besides that it returns pointer of bitmap type instead of opaque void *.
Signed-off-by: Andy Shevchenko
---
drivers/input/evdev.c | 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git
On Tue, May 29, 2018 at 10:21:47AM -0400, James Simmons wrote:
> From: Amir Shehata
>
> Move from num_possible_cpus() to nr_cpu_ids.
Nit, when doing a "v2" of a patch, in a series that is not all "v2", put
the moniker after the patch number. Otherwise it does not sort properly
in anyone's
On Tue, May 29, 2018 at 10:21:51AM -0400, James Simmons wrote:
> From: Amir Shehata
>
> On systems with large number of NUMA nodes and cores it is easy
> to incorrectly configure their use with Lustre. Provide debugfs
> files which can help track down any issues.
>
> Signed-off-by: Amir Shehata
Am 31.05.2018 um 18:57 schrieb Bjorn Andersson:
On Thu 31 May 04:45 PDT 2018, Greg Kroah-Hartman wrote:
On Thu, May 31, 2018 at 01:21:56PM +0200, Sebastian Gottschall wrote:
Am 28.05.2018 um 12:05 schrieb Greg Kroah-Hartman:
4.16-stable review patch. If anyone has any objections, please
On Sat, May 26, 2018 at 09:10:19AM +0100, John Whitmore wrote:
> Missed these in the last pass. Coding style does not require blank line after
> opening brace of a function.
This should have been merged with the previous patch :(
On Sat, May 26, 2018 at 09:10:18AM +0100, John Whitmore wrote:
> Coding style requires blank line after definitions and function definition,
> blank lines removed. Correction of some indentation.
Do not change indentation in the same patch you should only be doing
blank line removal or adding in.
Hi Richard,
On 2018/6/1 15:48, Richard Weinberger wrote:
> On Thu, May 31, 2018 at 1:06 PM, Gao Xiang wrote:
>> Hi all,
>>
>> Read-only file systems are used in many cases, such as read-only storage
>> media.
>> We are now focusing on the Android device which several read-only partitions
>>
On Thu, May 31, 2018 at 1:12 AM, Peter Hutterer
wrote:
> Hi Dmitry,
>
> On Thu, Aug 10, 2017 at 05:44:59PM -0700, Dmitry Torokhov wrote:
>> According to Microsoft specification [1] for Precision Touchpads (and
>> Touchscreens) the devices use "confidence" reports to signal accidental
>> touches,
On Fri, Jun 01, 2018 at 11:35:11AM +0200, Thierry Reding wrote:
> On Mon, May 14, 2018 at 10:06:22AM +0200, Linus Walleij wrote:
> > As we augmented the regulator core to accept a GPIO descriptor instead
> > of a GPIO number, we can augment the fixed GPIO regulator to look up
> > and pass that
Hi Mark,
Thanks for the comments.
On 2018/5/31 18:52, Mark Rutland wrote:
> On Thu, May 31, 2018 at 08:41:45PM +0800, Dongjiu Geng wrote:
>> +#ifdef CONFIG_ACPI_APEI_SEI
>> +static LIST_HEAD(ghes_sei);
>> +
>> +/*
>> + * Return 0 only if one of the SEI error sources successfully reported an
The vector_alloc tracepont reversed the reserved and ret aggs, that made
the trace print wrong. Exchange them.
Signed-off-by: Dou Liyang
---
arch/x86/include/asm/trace/irq_vectors.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/trace/irq_vectors.h
On Thu, May 31, 2018 at 08:56:52PM +, Nadav Amit wrote:
> Nadav Amit wrote:
>
> > Nadav Amit wrote:
> >
> >> Ping. Please consider it for inclusion for rc4.
> >>
> >> Nadav Amit wrote:
> >>
> >>> From: Gil Kupfer
> >>>
> >>> The balloon.page field is used for two different purposes if
Migrate swapper_pg_dir and tramp_pg_dir. And their virtual addresses
do not correlate with kernel's address.
Signed-off-by: Jun Yao
---
arch/arm64/mm/mmu.c | 70 +++--
1 file changed, 42 insertions(+), 28 deletions(-)
diff --git a/arch/arm64/mm/mmu.c
On Tue, May 29, 2018 at 10:21:40AM -0400, James Simmons wrote:
> From: James Simmons
>
> Recently lustre support has been expanded to extreme machines with as
> many as a 1000+ cores. On the other end lustre also has been ported
> to platforms like ARM and KNL which have uniquie NUMA and core
On Tue, May 29, 2018 at 10:21:48AM -0400, James Simmons wrote:
> From: Amir Shehata
>
> This patch adds NUMA node support.
Really? It looks like you just added an empty data structure pointer
that doesn't really do anything at all.
Where are you reading the host memory NUMA information from?
On Tue, May 29, 2018 at 10:21:53AM -0400, James Simmons wrote:
> int cfs_cpt_set_nodemask(struct cfs_cpt_table *cptab,
> - int cpt, nodemask_t *mask);
> + int cpt, const nodemask_t *mask);
This is not a coding style change. It is a semi-functional
Hi Rob Herring,
Thank you for the review.
Please find my answers inline..
On Thu, May 31, 2018 at 10:18 PM, Rob Herring wrote:
> On Mon, May 28, 2018 at 11:11:22AM +0530, Srinath Mannam wrote:
>> From: Pramod Kumar
>>
>> Add binding document for supported thermal implementation
>> in Stingray.
This patch make sure printing of log on console if loglevel
at time of storing log is less than current console loglevel.
@why
In SMP printk can work asynchronously, logs can be missed on console
because it checks current log level at time of console_unlock,
not at time of storing logs.
func()
{
Hi,
The main new feature of this patch-set is the Energy Model framework we
discussed at OSPM. The core of it and the APIs are all implemented in
patch 03/10, so this is really where I was hoping to get some feedback.
Is the overall idea of this framework reasonable ? What do you think
about the
On Thu, May 31, 2018 at 11:28:58AM +0800, David Wang wrote:
> Newer Centaur support CMCI mechanism, which is compatible with INTEL CMCI.
>
> Signed-off-by: David Wang
> ---
> arch/x86/Kconfig | 12
> arch/x86/kernel/cpu/mcheck/mce.c | 6 ++
> 2 files changed,
On (06/01/18 11:09), Petr Mladek wrote:
> > [...]
> >
> > > So I'd say that most likely the following scenarios can suffer:
> > >
> > > - NMI comes in, sets loglevel to X, printk-s some data, restores the
> > > loglevel back to Y
> > > - IRQ comes in [like sysrq, etc] comes in and does the
1 - 100 of 1040 matches
Mail list logo
