On 09.02.19 at 11:35, Andy Shevchenko wrote:
On Sat, Feb 9, 2019 at 12:08 AM Andrew Morton wrote:
On Fri, 8 Feb 2019 21:45:21 +0200 Andy Shevchenko
wrote:
On Tue, Oct 30, 2018 at 5:22 PM David Engraf wrote:
Unpacking an external initrd may fail e.g. not enough memory. This leads
to an
On (02/08/19 13:55), Steven Rostedt wrote:
[..]
> > + if (len) {
> > + /*
> > +* Order the stores above in vsnprintf() vs the store of the
> > +* space below which joins the two strings. Note this doesn't
> > +* make the code truly race free because
On 9/02/19 1:29 AM, Alexei Starovoitov wrote:
> On Thu, Feb 07, 2019 at 01:19:01PM +0200, Adrian Hunter wrote:
>> Subject to memory pressure and other limits, retain executable code, such
>> as JIT-compiled bpf, in memory instead of freeing it immediately it is no
>> longer needed for execution.
On 2/9/2019 8:31 AM, Wen Yang wrote:
> The of_find_device_by_node() takes a reference to the underlying device
> structure, we should release that reference.
>
> Fixes: 35af64038623 ("crypto: caam - Check for CAAM block presence before
> registering with crypto layer")
> Signed-off-by: Wen Yang
On Mon, Feb 11, 2019 at 11:09:15AM +0400, kpark3...@gmail.com wrote:
> From: Sahara
I need a "real" name here, one you use to sign legal documents please.
> Especially when a linked tty is used such as pty, the linked tty
> port's buf works have not been cancelled while master tty port's
> buf
* Peter Zijlstra wrote:
> On Thu, Feb 07, 2019 at 01:19:01PM +0200, Adrian Hunter wrote:
> > Subject to memory pressure and other limits, retain executable code, such
> > as JIT-compiled bpf, in memory instead of freeing it immediately it is no
> > longer needed for execution.
> >
> > While
Hello Heiner,
>Hi Maxime,
>
>Andrew and me are working on Aquantia PHY support and he handed over
>to me a patch series which includes parts of the first version of your
>series. Having said that I'm especially interested in your patches
>5 and 6. Because your series is somewhat bigger and there
On Mon, Feb 11, 2019 at 07:40:52AM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> In commit
>
> 344c0152d878 ("selftests: firmware: fix verify_reqs() return value")
>
> Fixes tag
>
> Fixes: a6a9be9270c87 ("selftests: firmware: return Kselftest Skip code for
> for skipped tests")
>
> has
On (02/11/19 09:35), Mike Rapoport wrote:
> On Sun, Feb 10, 2019 at 10:34:11PM -0800, Randy Dunlap wrote:
> > From: Randy Dunlap
> >
> > Fix markup warning by quoting the '*' character with a backslash.
> >
> > Documentation/vm/slub.rst:71: WARNING: Inline emphasis start-string without
> >
* Alexander Shishkin wrote:
> On Denverton's integration of the Intel(R) Trace Hub (for a reference
> and overview see Documentation/trace/intel_th.txt) the reported size of
> one of its resources (RTIT_BAR) doesn't match its actual size, which
> leads to overlaps with other devices'
Add two bits XLF_5LEVEL and XLF_5LEVEL_ENABLED for 5-level kernel.
Bit XLF_5LEVEL indicates if 5-level related code is contained
in this kernel.
Bit XLF_5LEVEL_ENABLED indicates if CONFIG_X86_5LEVEL=y is set.
They are being used in later patch to check if kexec/kdump kernel
is loaded in right
* Waiman Long wrote:
> On 02/07/2019 02:51 PM, Davidlohr Bueso wrote:
> > On Thu, 07 Feb 2019, Waiman Long wrote:
> >> 30 files changed, 1197 insertions(+), 1594 deletions(-)
> >
> > Performance numbers on numerous workloads, pretty please.
> >
> > I'll go and throw this at my mmap_sem
Hi all,
Changes since 20190208:
The drm-misc tree still has its build failure so I used a supplied
merge fix patch.
The apparmor tree lost its build failure.
The phy-next tree gained conflicts against the net-next tree.
The scsi-mkp tree gained conflicts against Linus' and the block trees.
On Sun, Feb 10, 2019 at 8:23 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:74e96711e337 Merge tag 'platform-drivers-x86-v5.0-2' of gi..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=11225b2740
> kernel config:
On Sun, Feb 10, 2019 at 01:00:20PM +0100, Christian Zigotzky wrote:
> I tested the whole series today. The kernels boot and the P.A. Semi
> Ethernet works! :-) Thanks a lot!
>
> I also tested it in a virtual e5500 QEMU machine today. Unfortunately the
> kernel crashes.
This looks like a patch I
On Sun, Feb 10, 2019 at 10:34:11PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix markup warning by quoting the '*' character with a backslash.
>
> Documentation/vm/slub.rst:71: WARNING: Inline emphasis start-string without
> end-string.
>
> Signed-off-by: Randy Dunlap
> Cc:
Hi Michael,
Thanks for looking into this and summarizing in detail.
> > This patch series has implementation for "virtio pmem".
> > "virtio pmem" is fake persistent memory(nvdimm) in guest
> > which allows to bypass the guest page cache. This also
> > implements a VIRTIO based
* Hugo Lefeuvre wrote:
> introduce wait_event_freezable_hrtimeout, an interruptible and freezable
> version of wait_event_hrtimeout.
>
> This helper will allow for simplifications in staging/android/vsoc.c, among
> others.
>
> Signed-off-by: Hugo Lefeuvre
> ---
> Changes in v2:
> - No
On Sat, Feb 9, 2019 at 12:29 AM Lorenzo Pieralisi
wrote:
>
> Apologies, I have dropped the ball on this one.
>
> On Wed, Jan 02, 2019 at 02:16:48PM +0800, Ley Foon Tan wrote:
> > Add PCIe Root Port support for Stratix 10 device.
> >
> > Main differences:
> > - HIP interface to access Root Port
On Sat, 9 Feb 2019 01:15:22 +0100
Miguel Ojeda wrote:
> On module unload/remove, we need to ensure that work does not run
> after we have freed resources. Concretely, cancel_delayed_work()
> may return while the callback function is still running.
>
> From kernel/workqueue.c:
>
> The work
On Mon, Feb 11, 2019 at 12:08:32AM +0100, Kristian Fiskerstrand wrote:
> On 1/23/19 9:50 AM, Domenico Andreoli wrote:
> > Ben Finney writes:
> >> Domenico Andreoli writes:
[...]
> >>> the only knot left is now the license of hash.h
> >>>
> >>> This file is also present in the kernel [0] with
Hi Christoph,
Mario successfully tested a kernel from your Git [1] on his T2080rdb today.
Link to the log:
https://gitlab.com/oshw-powerpc-notebook/T2080customizations/blob/master/kernel/dma_fix/kernel_dma_fix_log.txt
He wrote:
Please, note that all of the above kernel runs just fine with the
Change cpu clock name from ca57 to ca72 since MT8173 does use cortex-a72.
Signed-off-by: Seiya Wang
---
drivers/clk/mediatek/clk-mt8173.c | 4 ++--
include/dt-bindings/clock/mt8173-clk.h | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git
* Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> f6783319737f ("sched/fair: Fix insertion in rq->leaf_cfs_rq_list")
>
> Fixes tag
>
> Fixes: 9c2791f936ef ("Fix hierarchical order in rq->leaf_cfs_rq_list")
>
> has these problem(s):
>
> - Subject does not match target commit
The cpu type of cpu2 and cpu3 should be cortex-a72, not cortex-a57.
Signed-off-by: Seiya Wang
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
Hi Stuart
On 2019-02-10 23:51, Stuart Menefy wrote:
> When debugging suspend problems on Exynos 5260, I had a large number
> of debugging prints going to the serial port after interrupts
> had been disabled but before the timer interrupt was shutdown. This
> was long enough for a timer tick to
* Waiman Long wrote:
> On 02/10/2019 09:00 PM, Waiman Long wrote:
> > As the generic rwsem-xadd code is using the appropriate acquire and
> > release versions of the atomic operations, the arch specific rwsem.h
> > files will not be that much faster than the generic code as long as the
> >
From: Sahara
Especially when a linked tty is used such as pty, the linked tty
port's buf works have not been cancelled while master tty port's
buf work has been cancelled. Since release_one_tty and flush_to_ldisc
run in workqueue threads separately, when pty_cleanup happens and
link tty port is
Hi Linus,
please pull s390 fixes for 5.0-rc7
The following changes since commit f17b5f06cb92ef2250513a1e154c47b78df07d40:
Linux 5.0-rc4 (2019-01-27 15:18:05 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-5.0-3
for you
Thanks for reviewing. I was in vacation, sorry for late reply.
On 01/29/19 at 09:05pm, Thomas Gleixner wrote:
> On Fri, 25 Jan 2019, Baoquan He wrote:
>
> > Add two bit fields XLF_5LEVEL and XLF_5LEVEL_ENABLED for 5-level kernel.
>
> These are not bit fields. These are simple bits.
Indeed,
Commit 52cf93e63ee6 ("HID: i2c-hid: Don't reset device upon system resume")
fixes the resume behavior of several devices. However, this breaks the
resume on the ELAN2097, used on Dell Inspiron laptops, with the same flood
of messages:
[27009.817110] i2c_hid i2c-ELAN2097:00: i2c_hid_get_input:
Hi Hean-Loong, Ong
Patch looks good to me, but there is a few trivial
things I spotted while browsing the code.
See below.
Sam
> +++ b/drivers/gpu/drm/ivip/Makefile
> @@ -0,0 +1,7 @@
> +#
> +# Makefile for the drm device driver. This driver provides support for the
> +# Direct
Softly reset registers values on module probe
Signed-off-by: Kirill Marinushkin
---
sound/soc/codecs/pcm3060.c | 8
1 file changed, 8 insertions(+)
diff --git a/sound/soc/codecs/pcm3060.c b/sound/soc/codecs/pcm3060.c
index 6714aa8d9026..543cb86fd764 100644
---
ADC and DAC can be clocked from separate or same sources CLK1 and CLK2.
By default, ADC is clocked from CLK1, and DAC - from CLK2.
This commits allows sound cards to selest a proper clock source during
`hw_params()` via `snd_soc_dai_set_sysclk()`. It makes possible to have a
single clock source
>-Original Message-
>From: Shawn Guo
>Sent: 2019年2月11日 13:39
>To: Peng Ma
>Cc: ax...@kernel.dk; mark.rutl...@arm.com; Andy Tang
>; devicet...@vger.kernel.org;
>linux-kernel@vger.kernel.org; Leo Li ;
>linux-...@vger.kernel.org; robh...@kernel.org;
>linux-arm-ker...@lists.infradead.org
> From: Mikulas Patocka
> Sent: Monday, February 04, 2019 7:28 PM
> On Thu, 31 Jan 2019, Huaisheng Ye wrote:
>
> > From: Huaisheng Ye
> >
> > This patch set could be used for dm-writecache when use persistent
> > memory as cache data device.
> >
> > Patch 1 and 2 go towards removing unused
Hi all,
Today's linux-next merge of the akpm tree got a conflict in:
arch/mips/mm/c-r4k.c
between commit:
3315b6b336c8 ("MIPS: Delete unused flush_cache_sigtramp()")
from the mips tree and commit:
"arch/mips/mm/c-r4k.c: do not use mmap_sem for gup_fast()"
from the akpm tree.
I fixed
On 2019/2/5 2:15, Alexander Duyck wrote:
> From: Alexander Duyck
>
> Because the implementation was limiting itself to only providing hints on
> pages huge TLB order sized or larger we introduced the possibility for free
> pages to slip past us because they are freed as something less then
>
On Wed, Feb 06, 2019 at 04:17:25PM +0300, Mika Westerberg wrote:
> We can't be sure the paths are actually properly deactivated when a
> tunnel is restarted after resume.
Why can't we be sure? Please provide proper reasoning.
> So instead of marking all paths as
> inactive we go ahead and
On Thu, 2019-02-07 at 15:52 +, Marc Zyngier wrote:
> On 07/02/2019 15:47, Marc Zyngier wrote:
> > On 07/02/2019 15:20, Matthias Brugger wrote:
> >>
> >>
> >> On 24/01/2019 09:07, Erin Lo wrote:
> >>> From: Seiya Wang
> >>>
> >>> To support partitioned PPIs, 4 interrupt parameters should be
From: Randy Dunlap
Fix markup warning by quoting the '*' character with a backslash.
Documentation/vm/slub.rst:71: WARNING: Inline emphasis start-string without
end-string.
Signed-off-by: Randy Dunlap
Cc: Christoph Lameter
Cc: Sergey Senozhatsky
---
Documentation/vm/slub.rst |2 +-
1
From: Randy Dunlap
Fix markup warnings by inserting blank lines.
Also correct one typo.
Documentation/laptops/lg-laptop.rst:2: WARNING: Explicit markup ends without a
blank line; unexpected unindent.
Documentation/laptops/lg-laptop.rst:16: WARNING: Unexpected indentation.
From: Randy Dunlap
Fix markup warning: insert a blank line before the list.
Documentation/driver-api/gpio/board.rst:209: WARNING: Unexpected indentation.
Signed-off-by: Randy Dunlap
Cc: Linus Walleij
Cc: Bartosz Golaszewski
Cc: linux-g...@vger.kernel.org
---
Hi All,
Any comments on this series ??
Regards,
Anup
Le 11/02/2019 à 01:21, Benjamin Herrenschmidt a écrit :
On Fri, 2019-02-08 at 12:52 +, Christophe Leroy wrote:
/*
+ * MSR_KERNEL is > 0x8000 on 4xx/Book-E since it include MSR_CE.
+ */
+.macro __LOAD_MSR_KERNEL r, x
+.if \x >= 0x8000
+ lis \r, (\x)@h
+ ori \r, \r, (\x)@l
From: Randy Dunlap
Fix markup warning: insert a blank line before the hint.
Documentation/driver-api/dmaengine/dmatest.rst:63: WARNING: Unexpected
indentation.
Signed-off-by: Randy Dunlap
Cc: Andy Shevchenko
Cc: Vinod Koul
Cc: dmaeng...@vger.kernel.org
---
On Wed, Feb 06, 2019 at 04:17:23PM +0300, Mika Westerberg wrote:
> We need to be able to walk from one port to another when we are creating
> paths where there are multiple switches between two ports. For this
> reason introduce a new function tb_port_get_next() and a new macro
>
+ ath10k
Stephen Rothwell writes:
> Hi all,
>
> Commit
>
> 768ec4c012ac ("ath10k: update HOST capability qmi message")
>
> is missing a Signed-off-by from its author.
Oh, I had missed that. Thanks for reporting.
Unfortunately it would be difficult to rebase wireless-drivers-next so I
can't
On Sun, Feb 10, 2019 at 02:57:23PM -0600, Adam Ford wrote:
> The EVM consists of a system on module (SOM) and baseboard, and LCD.
> This patch adds a DTSI file for the SOM and baseboard separately,
> then a wrapper to combine them and specify processor type and a
> LCD information.
>
>
From: Ong, Hean Loong
Device tree binding for Intel FPGA Video and Image Processing Suite.
The bindings would set the max width, max height,
bits per pixel and memory port width.
The device tree binding only supports the Intel
Arria10 devkit and its variants. Vendor name retained as altr.
From: Ong, Hean Loong
The FPGA FrameBuffer Soft IP could be seen as the GPU and the DRM driver patch
here is
allocating memory for information to be streamed from the ARM/Linux to the
display port.
Basically the driver just wraps the information such as the pixels to be drawn
by
the Sodt
From: Ong Hean Loong
Intel FPGA Video and Image Processing Suite Frame Buffer II
driver config for Arria 10 devkit and its variants
Signed-off-by: Ong, Hean Loong
---
arch/arm/configs/socfpga_defconfig |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git
From: Ong, Hean Loong
Signed-off-by: Ong, Hean Loong
---
drivers/gpu/drm/Kconfig |2 +
drivers/gpu/drm/Makefile |1 +
drivers/gpu/drm/ivip/Kconfig | 14 +++
drivers/gpu/drm/ivip/Makefile |7 ++
drivers/gpu/drm/ivip/intel_vip_conn.c |
Hi Lorenzo,
On 08/02/19 5:50 PM, Lorenzo Pieralisi wrote:
> On Thu, Dec 06, 2018 at 08:52:25PM +0800, Wen Yang wrote:
>> kmemdup has implemented the function that kmalloc() + memcpy().
>> We prefer to kmemdup rather than code opened implementation.
>>
>> This issue was detected with the help of
On 08-02-19, 11:35, Rafael J. Wysocki wrote:
> At least some of the underlying mechanics seem to be very similar.
> You have priority lists, addition and removal of requests etc.
>
> Arguably, PM QoS may be regarded as a bit overly complicated, but
> maybe they both can use a common library
When requeue, if RQF_DONTPREP, rq has contained some driver
specific data, so insert it to hctx dispatch list to avoid any
merge. Take scsi as example, here is the trace event log (no
io scheduler, because RQF_STARTED would prevent merging),
kworker/0:1H-339 [000] ...1 2037.209289:
Hi Dmitry,
On 08/01/19 10:56 AM, Vignesh R wrote:
> AM654 SoCs has ADC IP which is similar to AM335x, but without the
> touchscreen part. Add new compatible to handle AM654 SoCs. Also, it
> seems that existing compatible strings used in the kernel DTs were never
> documented. So, document them
On Mon, Feb 11, 2019 at 02:53:18AM +, Peng Ma wrote:
>
>
> >-Original Message-
> >From: Shawn Guo
> >Sent: 2019年2月1日 14:30
> >To: Peng Ma
> >Cc: ax...@kernel.dk; robh...@kernel.org; mark.rutl...@arm.com; Leo Li
> >; linux-...@vger.kernel.org; devicet...@vger.kernel.org;
>
On Mon, 2019-02-11 at 10:37 +1100, NeilBrown wrote:
> autofs does not expect the pipe it is given
> to have O_NONBLOCK set - specifically if __kernel_write()
> in autofs_write() returns -EAGAIN, this is treated
> as a fatal error and the pipe is closed.
>
> For safety autofs should, therefore,
Hi all,
After merging the rtc tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
ERROR: "rtc_nvmem_unregister" [drivers/rtc/rtc-meson.ko] undefined!
Caused by commit
21358403bb29 ("rtc: support for the Amlogic Meson RTC")
I have reverted that commit for today.
--
On Feb 10, 2019, at 4:39 PM, Nadav Amit wrote:
>> On Jan 28, 2019, at 4:34 PM, Rick Edgecombe
>> wrote:
>>
>> From: Nadav Amit
>>
>> To prevent improper use of the PTEs that are used for text patching, we
>> want to use a temporary mm struct. We initailize it by copying the init
>> mm.
On Fri, 25 Jan 2019, at 05:59, Vijay Khemka wrote:
>
>
> On 1/24/19, 12:16 AM, "Greg Kroah-Hartman"
> wrote:
>
> On Wed, Jan 23, 2019 at 03:06:34PM -0800, Vijay Khemka wrote:
> > Corrected some of return values with appropriate meanings.
> >
> > Signed-off-by: Vijay Khemka
On Fri, 2019-02-08 at 16:04 +0100, Matthias Brugger wrote:
>
> On 09/01/2019 09:21, Seiya Wang wrote:
> > This patch adds the device nodes of ARM Performance Monitor Uint
> > for mt8173.
> >
> > Signed-off-by: Seiya Wang
> > ---
> > arch/arm64/boot/dts/mediatek/mt8173.dtsi | 14 ++
On 10-02-19, 13:14, Jeffrey Hugo wrote:
> Several clock controller drivers define a list of clk_hw devices, and then
> register those devices in probe() before using common code to process the
> rest of initialization. Extend the common code to accept a list of clk_hw
> devices to process, thus
Hi all,
Today's linux-next merge of the rtc tree got a conflict in:
drivers/clk/at91/sama5d2.c
between commit:
77977b800451 ("clk: at91: enable AUDIOPLL as source for PCKx on SAMA5D2")
from the clk tree and commit:
34d2ff2a6019 ("clk: at91: fix masterck name")
from the rtc tree.
I
The following changes since commit d13937116f1e82bf508a6325111b322c30c85eb9:
Linux 5.0-rc6 (2019-02-10 14:42:20 -0800)
are available in the git repository at:
g...@github.com:c-sky/csky-linux.git tags/csky-for-linus-5.0-rc6
for you to fetch changes up to
On 10/02/19 6:49 PM, Boris Brezillon wrote:
> On Tue, 5 Feb 2019 11:43:46 +0530
> Vignesh R wrote:
>
static int cqspi_setup_flash(struct cqspi_st *cqspi, struct device_node
*np)
{
- const struct spi_nor_hwcaps hwcaps = {
- .mask = SNOR_HWCAPS_READ |
MT8183 sample on rising and falling edge. It can reduce half data io.
Signed-off-by: Jitao Shi
---
drivers/gpu/drm/mediatek/mtk_dpi.c | 29 +
1 file changed, 29 insertions(+)
diff --git a/drivers/gpu/drm/mediatek/mtk_dpi.c
b/drivers/gpu/drm/mediatek/mtk_dpi.c
index
Hi Linus,
Please pull a few changes for alpha, including a build fix, a fix for the Eiger
platform, and a fix for a tricky bug uncovered by the strace test suite that
has existed since at least 1997 (v2.1.32)!
Thanks,
Matt
The following changes since commit
In the file Documentation/security/keys-trusted-encrypted, an example is
shown for to create an encrypted key rooted in trusted key. Basically,
the following should work:
KMK_KEY=$(keyctl add trusted kmk "new 32" @u)
keyctl pipe $KMK_KEY > ~/kmk-trusted.blob
EVM_KEY=$(keyctl add encrypted evm
Hi all,
Today's linux-next merge of the scsi-mkp tree got a conflict in:
drivers/scsi/hisi_sas/hisi_sas_v3_hw.c
between commit:
7bb25a89aad2 ("scsi: hisi_sas: Set protection parameters prior to adding SCSI
host")
from Linus' tree and commit:
b3cce125cb1e ("scsi: hisi_sas: Add support
Hi all,
Today's linux-next merge of the scsi-mkp tree got a conflict in:
include/linux/blkdev.h
between commit:
eca7abf31abb ("block: queue flag cleanup")
from the block tree and commit:
8b3238cabd50 ("scsi: block: remove bidi support")
from the scsi-mkp tree.
I fixed it up (see
On Fri, Feb 08, 2019 at 01:02:51AM -0500, Michael S. Tsirkin wrote:
> Now that we have MAP_SHARED, MAP_PRIVATE and MAP_SHARED_VALIDATE on all
> architectures, it probably makes sense to de-duplicate these
> and put them into a common header.
>
> Please review and consider merging though the
On Mon, Feb 11, 2019 at 03:55:53AM +, Li,Rongqing wrote:
> Could you send this patch?
I put it in
http://git.infradead.org/users/willy/linux-dax.git/shortlog/refs/heads/xarray
which is included in linux-next.
> -邮件原件-
> 发件人: Matthew Wilcox [mailto:wi...@infradead.org]
> 发送时间: 2019年2月3日 7:20
> 收件人: Li,Rongqing
> 抄送: linux-kernel@vger.kernel.org
> 主题: Re: [PATCH] XArray tests: allocation has to be GFP_ATOMIC under
> rcu_read_lock
>
> On Tue, Jan 29, 2019 at 07:08:42PM +0800, Li RongQing
On Sun, Feb 10, 2019 at 07:49:12PM +0100, Thomas Gleixner wrote:
> On Fri, 25 Jan 2019, Ming Lei wrote:
> > +static int nvme_setup_affinity(const struct irq_affinity *affd,
> > + struct irq_affinity_desc *masks,
> > + unsigned int nmasks)
> > +{
>
On Sun, Feb 10, 2019 at 05:39:20PM +0100, Thomas Gleixner wrote:
> On Fri, 25 Jan 2019, Ming Lei wrote:
>
> > Use the callback of .setup_affinity() to re-caculate number
> > of queues, and build irqs affinity with help of irq_build_affinity().
> >
> > Then nvme_setup_irqs() gets simplified a
Created a way to clear the multicast forwarding cache on a socket
without having to either remove the entries manually using the delete
entry socket option or destroy and recreate the multicast socket.
Calling the socket option MRT_FLUSH will allow any combination of the
four flag options to be
Hello Thomas,
On Sun, Feb 10, 2019 at 05:30:41PM +0100, Thomas Gleixner wrote:
> Ming,
>
> On Fri, 25 Jan 2019, Ming Lei wrote:
>
> > This patch introduces callback of .setup_affinity into 'struct
> > irq_affinity', so that:
>
> Please see Documentation/process/submitting-patches.rst. Search
v1 -> v2:
Implemented additional flags for static entries
v2 -> v3:
Cleaned up flag logic so any combination of routes can be cleared.
Fixed style errors
Fixed incorrect flag values
Currently the only way to clear the forwarding cache was to delete the
entries one by one using the MRT_DEL_MFC
On Mon, Feb 11, 2019 at 01:57:20AM +, Xuyandong (Yandong Xu, Euler5) wrote:
> > On Tue, Jan 29, 2019 at 05:02:26PM -0600, Bjorn Helgaas wrote:
> > > On Tue, Jan 29, 2019 at 05:47:32PM -0500, Michael S. Tsirkin wrote:
> > > > On Tue, Jan 29, 2019 at 04:43:33PM -0600, Bjorn Helgaas wrote:
> > >
Hi,
On 2/11/19 11:33 AM, Bjorn Helgaas wrote:
On Sun, Feb 10, 2019 at 8:00 PM Lu Baolu wrote:
Hi,
On 2/9/19 6:06 AM, Bjorn Helgaas wrote:
From: Bjorn Helgaas
A local variable initialization is a hint that the variable will be used in
an unusual way. If the initialization is unnecessary,
Hi all,
Today's linux-next merge of the phy-next tree got conflicts in:
drivers/phy/marvell/Kconfig
drivers/phy/marvell/Makefile
between commit:
14dc100b4411 ("phy: armada38x: add common phy support")
from the net-next tree and commit:
9695375a3f4a ("phy: add A3700 COMPHY support")
If an smbus transfer fails, there's no guarantee that the output
buffer was written. So, avoid trying to show the output buffer when
tracing after an error. This was 'mostly harmless', but would trip
up kasan checking if left-over cruft in byte 0 is a large length,
causing us to read from
On Sun, Feb 10, 2019 at 8:00 PM Lu Baolu wrote:
>
> Hi,
>
> On 2/9/19 6:06 AM, Bjorn Helgaas wrote:
> > From: Bjorn Helgaas
> >
> > A local variable initialization is a hint that the variable will be used in
> > an unusual way. If the initialization is unnecessary, that hint becomes a
> >
On Feb 10, 2019, at 7:43 AM, Ran Rozenstein wrote:
>> Subject: [PATCH net-next v5 09/12] socket: Add SO_TIMESTAMPING_NEW
>>
>> Add SO_TIMESTAMPING_NEW variant of socket timestamp options.
>> This is the y2038 safe versions of the SO_TIMESTAMPING_OLD for all
>> architectures.
>>
>> Signed-off-by:
Hey,
Thanks for the note, but..
On Sun, Feb 10, 2019 at 04:25:16AM +, pr-tracker-...@kernel.org wrote:
> The pull request you sent on Sat, 9 Feb 2019 20:17:23 -0800:
>
> > git://git.kernel.org/pub/scm/linux/kernel/git/evalenti/linux-soc-thermal
> > fixes
>
> has been merged into
On Thu, Feb 07, 2019 at 03:18:30PM +, Anson Huang wrote:
> The isl29023 light sensor driver has supported regulator control,
> assign the power supply for isl29023 to enable the control.
>
> Signed-off-by: Anson Huang
Applied all, thanks.
>-Original Message-
>From: Shawn Guo
>Sent: 2019年2月1日 14:30
>To: Peng Ma
>Cc: ax...@kernel.dk; robh...@kernel.org; mark.rutl...@arm.com; Leo Li
>; linux-...@vger.kernel.org; devicet...@vger.kernel.org;
>linux-kernel@vger.kernel.org; linux-arm-ker...@lists.infradead.org; Andy Tang
>
Hi Peter
> The problem I have with this is that it will make schedstats even more
expensive :/
I think the overhead for accounting hierarchy wait time is just the
same as cpuacct.usage. If the performance overhead is low enough(<
1%), is it acceptable?
Thanks
Yuzhoujian
Peter Zijlstra
From: Sven Van Asbroeck
Remove a spinlock which prevents schedule_delayed_work() and
mod_delayed_work() from executing concurrently.
This was required back when mod_delayed_work() did not exist,
and had to be implemented with a cancel + schedule. See
commit e7c2f967445d ("workqueue: use
On Sun, 2019-02-10 at 10:25 -0800, James Bottomley wrote:
> On Sun, 2019-02-10 at 19:10 +0100, Lukas Bulwahn wrote:
> > Mimi Zohar used spaces instead of a tab when adding Jarkko Sakkinen
> > as
> > further maintainer to the KEYS-TRUSTED section entry. So, we rectify
> > this
> > with this commit.
On Thu, Jan 31, 2019 at 03:01:22PM +, Abel Vesa wrote:
> Add RTC support for i.MX8MQ.
>
> Signed-off-by: Abel Vesa
Applied, thanks.
There is no need to retun 0 in mt76_dma_attach(), so switch it to void.
Signed-off-by: Ryder Lee
---
drivers/net/wireless/mediatek/mt76/dma.c | 3 +--
drivers/net/wireless/mediatek/mt76/dma.h | 2 +-
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git
On Mon, Feb 4, 2019 at 8:27 PM Souptick Joarder wrote:
>
> There is no point to continuing assignment after memory allocation
> failed, rather throw error immediately.
>
> Signed-off-by: Souptick Joarder
Any comment on this patch ?
> ---
> v1 -> v2:
> Corrected typo in change log.
>
>
From: Ong, Hean Loong
The FPGA FrameBuffer Soft IP could be seen as the GPU and the DRM driver
patch here is allocating memory for information to be streamed from the
ARM/Linux to the display port.
Basically the driver just wraps the information such as the pixels
to be drawn by the FPGA
From: Ong Hean Loong
Intel FPGA Video and Image Processing Suite Frame Buffer II
driver config for Arria 10 devkit and its variants
Signed-off-by: Ong, Hean Loong
---
arch/arm/configs/socfpga_defconfig |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git
From: Ong, Hean Loong
Device tree binding for Intel FPGA Video and Image Processing Suite. The
binding involved would be generated from the Altera (Intel) Qsys system. The
bindings would set the max width, max height, buts per pixel and memory port
width. The device tree binding only supports
From: Ong, Hean Loong
Signed-off-by: Ong, Hean Loong
---
drivers/gpu/drm/ivip/Kconfig | 14 +++
drivers/gpu/drm/ivip/Makefile |7 ++
drivers/gpu/drm/ivip/intel_vip_conn.c | 91
drivers/gpu/drm/ivip/intel_vip_core.c | 189
On 02/10/2019 09:00 PM, Waiman Long wrote:
> As the generic rwsem-xadd code is using the appropriate acquire and
> release versions of the atomic operations, the arch specific rwsem.h
> files will not be that much faster than the generic code as long as the
> atomic functions are properly
1 - 100 of 317 matches
Mail list logo
