Enable logs in venus through debugfs to print
debug information.
Signed-off-by: Malathi Gottam
---
drivers/media/platform/qcom/venus/core.c | 62 -
drivers/media/platform/qcom/venus/core.h | 32 +
drivers/media/platform/qcom/venus/firmware.c | 6 +-
> -Original Message-
> From: Gustavo A. R. Silva [mailto:gust...@embeddedor.com]
> Sent: Thursday, December 27, 2018 4:41 AM
> To: Kang, Luwei ; Paolo Bonzini ;
> Radim Krčmář ; Thomas Gleixner
> ; Ingo Molnar ; Borislav Petkov
> ; H. Peter Anvin ;
> x...@kernel.org
> Cc:
On 28.12.2018 03:26, Wei Wang wrote:
> Some vqs don't need to be allocated when the related feature bits are
> disabled. Callers notice the vq allocation layer by setting the related
> names[i] to be NULL.
>
> This patch series fixes the find_vqs implementations to handle this case.
So the
This is used to hide the metadata address from virtqueue helpers. This
will allow to implement a vmap based fast accessing to metadata.
Signed-off-by: Jason Wang
---
drivers/vhost/vhost.c | 94 +++
1 file changed, 77 insertions(+), 17 deletions(-)
diff
It was noticed that the copy_user() friends that was used to access
virtqueue metdata tends to be very expensive for dataplane
implementation like vhost since it involves lots of software checks,
speculation barrier, hardware feature toggling (e.g SMAP). The
extra cost will be more obvious when
Use one generic vhost_copy_to_user() instead of two dedicated
accessor. This will simplify the conversion to fine grain
accessors. About 2% improvement of PPS were seen during vitio-user
txonly test.
Signed-off-by: Jason Wang
---
drivers/vhost/vhost.c | 11 +--
1 file changed, 1
Hi:
This series tries to access virtqueue metadata through kernel virtual
address instead of copy_user() friends since they had too much
overheads like checks, spec barriers or even hardware feature
toggling.
Test shows about 24% improvement on TX PPS. It should benefit other
cases as well.
Hi Matthias,
On 2018-12-28 01:55, Matthias Kaehlcke wrote:
On Thu, Dec 27, 2018 at 01:01:33PM +0530, Balakrishna Godavarthi wrote:
During initalization of wcn3990, we observed UART is reading some
stray bytes on the Rx line. This is logging Frame reassembly errors
on the serial console. This
* Dmitry V. Levin:
> On Thu, Dec 27, 2018 at 06:18:19PM +0100, Florian Weimer wrote:
>> We have a bit of an interesting problem with respect to the d_off
>> field in struct dirent.
>>
>> When running a 64-bit kernel on certain file systems, notably ext4,
>> this field uses the full 63 bits even
On Thu, Dec 27, 2018 at 09:49:29PM -0800, Andrew Morton wrote:
> On Mon, 24 Dec 2018 15:06:22 +0800 Huang Shijie wrote:
>
> > We may use the addr_in_gen_pool() in the driver module.
> > So export the addr_in_gen_pool for the compiling.
> >
> > ...
> >
> > --- a/lib/genalloc.c
> > +++
do_csum() in lib/checksum.c is too slow in ARM64,
and we can use assembly and algorithm to accelerate it.
Signed-off-by: huhai
---
arch/arm64/include/asm/checksum.h | 3 +
arch/arm64/lib/Makefile | 2 +-
arch/arm64/lib/checksum.c | 144 ++
3
Use DEFINE_DEBUGFS_ATTRIBUTE rather than DEFINE_SIMPLE_ATTRIBUTE
for debugfs files.
Semantic patch information:
Rationale: DEFINE_SIMPLE_ATTRIBUTE + debugfs_create_file()
imposes some significant overhead as compared to
DEFINE_DEBUGFS_ATTRIBUTE + debugfs_create_file_unsafe().
Generated by:
Use DEFINE_DEBUGFS_ATTRIBUTE rather than DEFINE_SIMPLE_ATTRIBUTE
for debugfs files.
Semantic patch information:
Rationale: DEFINE_SIMPLE_ATTRIBUTE + debugfs_create_file()
imposes some significant overhead as compared to
DEFINE_DEBUGFS_ATTRIBUTE + debugfs_create_file_unsafe().
Generated by:
On Tue, 25 Dec 2018, Brajeswar Ghosh wrote:
> Remove video/mipi_display.h which is included more than once
>
> Signed-off-by: Brajeswar Ghosh
Pushed to drm-intel-next-queued, thanks for the patch.
BR,
Jani.
> ---
> drivers/gpu/drm/i915/intel_dsi_vbt.c | 1 -
> 1 file changed, 1 deletion(-)
>
HI Matthias,
On 2018-12-28 01:48, Matthias Kaehlcke wrote:
On Thu, Dec 27, 2018 at 01:01:31PM +0530, Balakrishna Godavarthi wrote:
wcn3990 requires a power pulse to turn ON/OFF along with
regulators. Sometimes we are observing the power pulses are sent
out with some time delay, due to queuing
On Thu, Dec 27, 2018 at 10:31:52PM +0800, Liviu Dudau wrote:
> On Thu, Dec 27, 2018 at 07:09:07AM +, james qian wang (Arm Technology
> China) wrote:
> > On Mon, Dec 24, 2018 at 08:32:14PM +0800, Liviu Dudau wrote:
> > > On Fri, Dec 21, 2018 at 10:00:33AM +, james qian wang (Arm Technology
set_msg_len may fails with -EOVERFLOW, It should be propagate
to upstream.
Fixes: 2debd3325e55 ("crypto: chcr - Add AEAD algos.")
Signed-off-by: YueHaibing
---
drivers/crypto/chelsio/chcr_algo.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
On 28.12.2018 07:34, Heiner Kallweit wrote:
> On 28.12.2018 02:31, Frederic Weisbecker wrote:
>> On Fri, Dec 28, 2018 at 12:11:12AM +0100, Heiner Kallweit wrote:
>>>
> [...]
>>
>> Interesting, the softirq is raised from hardirq but it's not handled in the
>> end of
>> the IRQ. Are you running
From: Youlin Wang
Signed-off-by: John Stultz
Signed-off-by: Youlin Wang
Signed-off-by: Tanglei Han
Cc: Wei Xu
Cc: Rob Herring
Cc: Mark Rutland
---
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git
From: Youlin Wang
There is an new "hisi-pcm-asp-dma-1.0" device added in
"arch/arm64/boot/dts/hisilicon/hi3660.dtsi".
So we have to add a matching id in the driver file:
"{ .compatible = "hisilicon,hisi-pcm-asp-dma-1.0", }"
And also hisi-pcm-asp dma device needs no setting to the clock.
So we
From: Youlin Wang
Extend the k3dma driver binding to support hisi-asp hardware variants.
Signed-off-by: Youlin Wang
Signed-off-by: Tanglei Han
Cc: Vinod Koul
Cc: Rob Herring
Cc: Mark Rutland
---
Documentation/devicetree/bindings/dma/k3dma.txt | 33 -
1 file
Hi
On 2018/12/28 9:39, Stephen Boyd wrote:
Quoting Sugaya, Taichi (2018-12-25 17:35:27)
Hi
On 2018/11/30 17:31, Stephen Boyd wrote:
+ init.num_parents = parents;
+ init.parent_names = parent_names;
+
+ mcm->cname = clk_name;
+ mcm->parent = 0;
+ mcm->hw.init =
On 12/27/2018 08:17 PM, Christian Borntraeger wrote:
On 27.12.2018 12:59, Christian Borntraeger wrote:
On 27.12.2018 12:31, Christian Borntraeger wrote:
This patch triggers random crashes in the guest kernel on s390 early during
boot.
No migration and no setting of the balloon is involved.
On 28.12.2018 02:31, Frederic Weisbecker wrote:
> On Fri, Dec 28, 2018 at 12:11:12AM +0100, Heiner Kallweit wrote:
>>
[...]
>
> Interesting, the softirq is raised from hardirq but it's not handled in the
> end of
> the IRQ. Are you running threaded IRQS by any chance? If so I would expect
>
Using standard CCF interface to set vdec/venc parent clk
and clk rate.
Signed-off-by: Yunfei Dong
Signed-off-by: Qianqian Yan
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
Fix MTK binding document for MT8173 dtsi changed in order
to use standard CCF interface.
MT8173 SoC from Mediatek.
Signed-off-by: Yunfei Dong
Signed-off-by: Qianqian Yan
---
.../devicetree/bindings/media/mediatek-vcodec.txt | 13 +
1 file changed, 13 insertions(+)
diff --git
From: Youlin Wang
Add i2s driver for hisi3660.
Origenal patch from 13dcb3aeefe431010689de314d7543db86ebf93c by Guangke Ji.
Reviewed-by: Feng Chen
Signed-off-by: Kaihua Zhong
Signed-off-by: Jun Chen
Signed-off-by: Guangke Ji
Signed-off-by: John Stultz
Signed-off-by: Youlin Wang
VDec: Using standard CCF interface to set parent clock and
clock rate in dtsi and using common interface to open/close
video decoder clock.
VEnc: Using standard CCF interface to set parent clock/larb
in dtsi and using common interface to open/close
video encoder clock/larb.
Signed-off-by: Yunfei
From: Youlin Wang
Signed-off-by: John Stultz
Signed-off-by: Youlin Wang
Signed-off-by: Tanglei Han
Cc: Wei Xu
Cc: Rob Herring
Cc: Mark Rutland
---
arch/arm64/boot/dts/hisilicon/hi3660.dtsi | 28
1 file changed, 28 insertions(+)
diff --git
Hi,
On the Connex L1430 laptop based on Intel Apollo Lake N3350, Linux
doesn't boot. It hangs early on a blank screen. Reproduced with Linus
git, 4.18 and 4.19 (there is no previous known working kernel
version). EFI earlyprintk shows:
APIC: switch to symmetric I/O mode setup
x2apic: IRQ
On Mon, 24 Dec 2018 15:06:22 +0800 Huang Shijie wrote:
> We may use the addr_in_gen_pool() in the driver module.
> So export the addr_in_gen_pool for the compiling.
>
> ...
>
> --- a/lib/genalloc.c
> +++ b/lib/genalloc.c
> @@ -450,6 +450,7 @@ bool addr_in_gen_pool(struct gen_pool *pool,
On Thu, Dec 27, 2018 at 9:02 PM Tejun Heo wrote:
>
> On Thu, Dec 27, 2018 at 05:53:52PM -0800, Tejun Heo wrote:
> > Vincent knows that part way better than me but I think the safest way
> > would be doing the optimization removal iff tmp_alone_branch is
> > already pointing to leaf_cfs_rq_list.
On 12/27/18 6:45 PM, Andrew Morton wrote:
> On Thu, 27 Dec 2018 11:24:31 -0800 Mike Kravetz
> wrote:
>> It would be better to make an explicit check for mapping != null before
>> calling i_mmap_lock_write/try_to_unmap. In this way, unrelated changes to
>> code above will not potentially lead to
Hi Sergey,
On Thu, Dec 27, 2018 at 11:26:24AM +0900, Sergey Senozhatsky wrote:
> On (12/24/18 12:35), Minchan Kim wrote:
> [..]
> > @@ -645,10 +680,13 @@ static ssize_t writeback_store(struct device *dev,
> > bvec.bv_len = PAGE_SIZE;
> > bvec.bv_offset = 0;
> >
> > -
On Thu, Dec 27, 2018 at 09:31:58PM +0100, Michal Hocko wrote:
On Wed 26-12-18 21:14:46, Wu Fengguang wrote:
This is an attempt to use NVDIMM/PMEM as volatile NUMA memory that's
transparent to normal applications and virtual machines.
The code is still in active development. It's provided for
It makes the code more self-explanatory and tells throughout the code
what magic number refers to:
* state (Hardirq/Softirq)
* direction (used in or enabled above state)
* read or write
We can even remove some comments that were compensating for the lack of
those constant names.
Signed-off-by:
Just a few simplification and code cleanup.
Frederic Weisbecker (2):
locking/lockdep: Simplify mark_held_locks()
locking/lockdep: Provide enum lock_usage_bit mask names
kernel/locking/lockdep.c | 54 +-
kernel/locking/lockdep_internals.h | 4
The enum mark_type appears a bit artificial here. We can directly pass
the base enum lock_usage_bit value to mark_held_locks(). All we need
then is to add the read index for each lock if necessary. It makes the
code clearer.
Signed-off-by: Frederic Weisbecker
Cc: Peter Zijlstra
Cc: Ingo Molnar
Dear Rider,
>From the new RED Racing Parts you find spare parts and accessories for road /
>offroad motorbike and
scooter.
Stickers, ergal / titanium bolts, brake / clutch levers, brake pads, carbon
fiber parts, racing
coolers, clutches and more...
Excellent quality!
Visit our website on
Hi Alexander and Xue Liu,
Am 24.12.18 um 16:32 schrieb Alexander Aring:
> On Tue, Dec 18, 2018 at 02:50:58PM +0100, Xue Liu wrote:
>> On Mon, 17 Dec 2018 at 15:19, Andreas Färber wrote:
>>> Am 17.12.18 um 09:50 schrieb Xue Liu:
I have a question about the architecture of your module. AFAIK
Add support for parsing "firmware-name" dt bindings which specifies
the relative paths of mba/modem/pas image as strings. Fallback to
the default paths for mba/modem/pas image on -EINVAL.
Signed-off-by: Sibi Sankar
---
drivers/remoteproc/qcom_q6v5_mss.c | 46 +++---
Add optional "firmware-name" bindings for Q6V5 MSS and PAS based
remoteprocs. For Q6V5 MSS/PAS the two/one relative firmware
paths/path are to be listed respectively. Fallback to the default
images for mba/modem for Q6V5 MSS or the default Hexagon image
for Q6V5 PAS if the "firmware-name" binding
Q6V5 MSS on certain SoCs like SDM845 are capable of operating under
completely different configuration (like Non-Modem WLAN configuration)
depending on the firmware loaded without any change in boot sequence
of the Hexagon core. The patch series is ultimately aimed to avoid
multiple compatibles
Hi Rob,
Thanks for the review :)
On 2018-12-21 01:40, Rob Herring wrote:
On Wed, Dec 12, 2018 at 06:14:55PM +0530, Sibi Sankar wrote:
Add optional firmware bindings for Q6V5 MSS. It lists the two relative
firmware paths which are used for booting and authenticating the
Hexagon
core.
Hi Rob,
Thanks for the review!
On 2018-12-28 02:51, Rob Herring wrote:
On Wed, Dec 26, 2018 at 06:22:23PM +0530, Sibi Sankar wrote:
Add missing clock bindings for Q6V5 MSS on SDM845 SoCs.
Fixes: fb22022ff63d ("dt-bindings: remoteproc: Add Q6v5 Modem PIL
binding for SDM845")
Signed-off-by:
On Thu, Dec 27, 2018 at 7:46 PM Guenter Roeck wrote:
>
> h8300 builds fail with:
>
> In file included from drivers/of/address.c:11:
> include/linux/pci.h:1966:20: error: redefinition of 'pcibios_penalize_isa_irq'
>
> This is because CONFIG_PCI is not enabled, and pcibios_penalize_isa_irq()
> is
This patch provids netlink method to configure the TSN protocols hardwares.
TSN guaranteed packet transport with bounded low latency, low packet delay
variation, and low packet loss by hardware and software methods.
The three basic components of TSN are:
1. Time synchronization: This was
On 12/28/2018 04:51 AM, Andi Kleen wrote:
Thanks. This looks a lot better than the earlier versions.
Some more comments.
On Wed, Dec 26, 2018 at 05:25:38PM +0800, Wei Wang wrote:
When the vCPU is scheduled in:
- if the lbr feature was used in the last vCPU time slice, set the lbr
stack to
On 12/28/18 at 11:00am, Pingfan Liu wrote:
> The bottom-up allocation style is introduced to cope with movable_node,
> where the limit inferior of allocation starts from kernel's end, due to
> lack of knowledge of memory hotplug info at this early time.
> Beside this original aim, 'kexec -c'
On 28/12/2018 7:06 AM, Rob Herring wrote:
> On Tue, Dec 18, 2018 at 03:34:33PM +0800, Wei Ni wrote:
>> Add optional property "nvidia,thermtrips".
>> If present, these trips will be used as HW shutdown trips,
>> and critical trips will be used as SW shutdown trips.
>>
>> Signed-off-by: Wei Ni
On Thu, Dec 27, 2018 at 11:32:06AM -0800, Yang Shi wrote:
On Wed, Dec 26, 2018 at 9:13 PM Dan Williams wrote:
On Wed, Dec 26, 2018 at 8:11 PM Fengguang Wu wrote:
>
> On Wed, Dec 26, 2018 at 07:41:41PM -0800, Matthew Wilcox wrote:
> >On Wed, Dec 26, 2018 at 09:14:47PM +0800, Fengguang Wu
On Mon, 24 Dec 2018 16:03:12 -0500 Qian Cai wrote:
> Some code in 9b31cf493ff was lost during merging into the -mmotm tree
> for some reasons,
>
> In file included from ./arch/arm64/include/asm/processor.h:46,
> from ./include/linux/rcupdate.h:43,
> from
From: Stefano Cappa
> Hi everyone,
> I already posted this in NXP forum as a comment
> (https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fco
> mmunity.nxp.com%2Fthread%2F359397data=02%7C01%7Cfugang.dua
> n%40nxp.com%7C189d5cad534e470a162508d66c068de2%7C686ea1d3bc2b
>
On 12/27/2018 08:03 PM, Christian Borntraeger wrote:
On 27.08.2018 03:32, Wei Wang wrote:
static int init_vqs(struct virtio_balloon *vb)
{
- struct virtqueue *vqs[3];
- vq_callback_t *callbacks[] = { balloon_ack, balloon_ack, stats_request
};
- static const char * const
On Wed, 26 Dec 2018 16:31:59 +0100 Ard Biesheuvel
wrote:
> Please stop sending EFI patches if you can't be bothered to
> test/reproduce against the EFI tree.
um, sorry, but that's a bit strong. Finding (let alone fixing) a bug
in EFI is a great contribution (thanks!) and the EFI maintainers
Some vqs may not need to be allocated when their related feature bits
are disabled. So callers may pass in such vqs with "names = NULL".
Then we skip such vq allocations.
Signed-off-by: Wei Wang
---
drivers/misc/mic/vop/vop_main.c| 9 +++--
drivers/remoteproc/remoteproc_virtio.c |
Some vqs don't need to be allocated when the related feature bits are
disabled. Callers notice the vq allocation layer by setting the related
names[i] to be NULL.
This patch series fixes the find_vqs implementations to handle this case.
Wei Wang (2):
virtio_pci: use queue idx instead of array
Customer reported a bug on a high end server with many pcie devices, where
kernel bootup with crashkernel=384M, and kaslr is enabled. Even
though we still see much memory under 896 MB, the finding still failed
intermittently. Because currently we can only find region under 896 MB,
if w/0 ',high'
When find_vqs, there will be no vq[i] allocation if its corresponding
names[i] is NULL. For example, the caller may pass in names[i] (i=4)
with names[2] being NULL because the related feature bit is turned off,
so technically there are 3 queues on the device, and name[4] should
correspond to the
The bottom-up allocation style is introduced to cope with movable_node,
where the limit inferior of allocation starts from kernel's end, due to
lack of knowledge of memory hotplug info at this early time.
Beside this original aim, 'kexec -c' prefers to reuse this style to alloc mem
at lower
The bottom-up allocation style is introduced to cope with movable_node,
where the limit inferior of allocation starts from kernel's end, due to
lack of knowledge of memory hotplug info at this early time. But if later,
hotplug info has been got, the limit inferior can be extend to 0.
'kexec -c'
On 2018/12/28 上午10:55, Waiman Long wrote:
> On 12/27/2018 08:31 PM, Wang, Kemi wrote:
>> Hi, Waiman
>>Did you post that patch? Let's see if it helps.
>
> I did post the patch a while ago. I will need to rebase it to a new
> baseline. Will do that in a week or 2.
>
OK．I will take a look
On 12/27/2018 08:31 PM, Wang, Kemi wrote:
> Hi, Waiman
>Did you post that patch? Let's see if it helps.
I did post the patch a while ago. I will need to rebase it to a new
baseline. Will do that in a week or 2.
-Longman
>
> -Original Message-
> From: LKP
On Wed, 26 Dec 2018 13:15:22 +0800 Huang Ying wrote:
> KSM pages may be mapped to the multiple VMAs that cannot be reached
> from one anon_vma. So during swapin, a new copy of the page need to
> be generated if a different anon_vma is needed, please refer to
> comments of
Al Viro mentioned (Message-ID
<20170626041334.gz10...@zeniv.linux.org.uk>)
that there is probably a race condition
lurking in accesses of sk_stamp on 32-bit machines.
sock->sk_stamp is of type ktime_t which is always an s64.
On a 32 bit architecture, we might run into situations of
unsafe access
On Thu, 27 Dec 2018 11:24:31 -0800 Mike Kravetz wrote:
> On 12/27/18 3:44 AM, Colin Ian King wrote:
> > Hi,
> >
> > Static analysis with CoverityScan on linux-next detected a potential
> > null pointer dereference with the following commit:
> >
> > From d8a1051ed4ba55679ef24e838a1942c9c40f0a14
Fixes gcc '-Wunused-but-set-variable' warning when
CONFIG_VMAP_STACK is not set:
kernel/fork.c: In function 'dup_task_struct':
kernel/fork.c:843:20: warning:
variable 'stack_vm_area' set but not used [-Wunused-but-set-variable]
Signed-off-by: YueHaibing
---
kernel/fork.c | 2 +-
1 file
On Thu, Dec 27, 2018 at 08:07:26PM +, Christopher Lameter wrote:
On Wed, 26 Dec 2018, Fengguang Wu wrote:
Each CPU socket can have 1 DRAM and 1 PMEM node, we call them "peer nodes".
Migration between DRAM and PMEM will by default happen between peer nodes.
Which one does numa_node_id()
Hi Tejun,
On 2018/12/28 10:02, Tejun Heo wrote:
> On Thu, Dec 27, 2018 at 05:53:52PM -0800, Tejun Heo wrote:
>> Vincent knows that part way better than me but I think the safest way
>> would be doing the optimization removal iff tmp_alone_branch is
>> already pointing to leaf_cfs_rq_list. IIUC,
On Thu, Dec 27, 2018 at 06:18:19PM +0100, Florian Weimer wrote:
> We have a bit of an interesting problem with respect to the d_off
> field in struct dirent.
>
> When running a 64-bit kernel on certain file systems, notably ext4,
> this field uses the full 63 bits even for small directories
Hello, Linus.
cgroup changes for v4.21.
* Waiman's cgroup2 cpuset support has been finally merged closing one
of the last remaining feature gaps.
* cgroup.procs could show non-leader threads when cgroup2 threaded
mode was used in certain ways. I forgot to push the fix during the
last
If the kernel is configured with KASAN_EXTRA, the stack size is
increasted significantly due to enable this option will set
"-fstack-reuse" to "none" in GCC [1]. As the results, it could trigger
stack overrun quite often with 32k stack size compiled using GCC 8. For
example, this reproducer
On Thu, Dec 27, 2018 at 05:53:52PM -0800, Tejun Heo wrote:
> Vincent knows that part way better than me but I think the safest way
> would be doing the optimization removal iff tmp_alone_branch is
> already pointing to leaf_cfs_rq_list. IIUC, it's pointing to
> something else only while a branch
Hello,
On Thu, Dec 27, 2018 at 05:36:47PM -0800, Linus Torvalds wrote:
> > Unless I'm totally confused, which is definitely possible, I don't
> > think there's a race condition and the only bug is the
> > tmp_alone_branch pointer getting dangled, which maybe doesn't happen
> > all that much?
>
>
From: Florian Fainelli
Date: Thu, 27 Dec 2018 17:06:58 -0800
> Le 12/27/18 à 4:22 PM, David Miller a écrit :
>> From: Kangjie Lu
>> Date: Tue, 25 Dec 2018 22:08:18 -0600
>>
>>> Both bcm_sf2_sw_indir_rw and mdiobus_write_nested could fail, so let's
>>> return their error codes upstream.
>>>
>>>
The pull request you sent on Sun, 23 Dec 2018 16:26:49 -0800:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/xfs-4.21-merge-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/47a43f2f0ce24bb75e3e4500118000585a3b496a
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Wed, 19 Dec 2018 16:11:04 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-4.21-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/32ee34eddad13cd44ad0cb3e659fe6fd49143b62
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Mon, 24 Dec 2018 06:06:16 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git
> tags/locks-v4.21-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/00c569b567c7f1f0da6162868fd02a9f29411805
Thank you!
--
The pull request you sent on Sun, 23 Dec 2018 16:42:04 -0800:
> git://git.kernel.org/pub/scm/fs/xfs/xfs-linux.git tags/iomap-4.21-merge-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/bc77789a491cdc6f47e5bbd1d04ddd283d64658b
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 23 Dec 2018 23:53:34 -0500:
> git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
> tags/ext4_for_linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/f6b1495fba0b66cfa05efa0ca2370513b79b45b6
Thank you!
--
Deet-doot-dot,
The pull request you sent on Wed, 19 Dec 2018 11:17:22 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/teigland/linux-dlm.git dlm-4.21
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/4de3aea385f5a054885bc96ffdb9c7d0ea0c9486
Thank you!
--
Deet-doot-dot, I am a
On Thu, Dec 27, 2018 at 5:15 PM Tejun Heo wrote:
>
> I'm pretty sure enqueue_entity() *has* to be called with rq lock.
> unthrottle_cfs_rq() is called from tg_set_cfs_bandwidth(),
> distribute_cfs_runtime() and unthrottle_offline_cfs_rqs. The first
> two grabs the rq_lock just around the calls
Le 12/27/18 à 2:55 AM, Namhyung Kim a écrit :
> Hello,
>
> On Thu, Dec 20, 2018 at 07:43:35PM -0800, Florian Fainelli wrote:
>> Hi all,
>>
>> I just painfully learned that perf would segfault when
>> CONFIG_KUSER_HELPERS is disabled because it unconditionally makes use of
>
> Could you please
On Fri, Dec 28, 2018 at 12:11:12AM +0100, Heiner Kallweit wrote:
>
> OK, did as you advised and here comes the trace. That's the related dmesg
> part:
>
> [ 1479.025092] x86: Booting SMP configuration:
> [ 1479.025129] smpboot: Booting Node 0 Processor 1 APIC 0x2
> [ 1479.094715] NOHZ:
> >
> >@@ -299,6 +306,7 @@ int cdns3_drd_init(struct cdns3 *cdns)
> >cdns->version = CDNS3_CONTROLLER_V0;
> >cdns->otg_v1_regs = NULL;
> >cdns->otg_regs = regs;
> >+ writel(0x1, >otg_v0_regs->simulate);
> >
Hi, Waiman
Did you post that patch? Let's see if it helps.
-Original Message-
From: LKP [mailto:lkp-boun...@lists.01.org] On Behalf Of Waiman Long
Sent: Tuesday, November 6, 2018 6:40 AM
To: Linus Torvalds ; vba...@suse.cz; Davidlohr
Bueso
Cc: yang@linux.alibaba.com; Linux Kernel
Happy holidays, everyone.
(cc'ing Rik, who has been looking at the scheduler code a lot lately)
On Thu, Dec 27, 2018 at 10:15:17AM -0800, Linus Torvalds wrote:
> [ goes off and looks ]
>
> Oh. unthrottle_cfs_rq -> enqueue_entity -> list_add_leaf_cfs_rq()
> doesn't actually seem to hold the rq
Le 12/27/18 à 6:21 AM, Stefano Cappa a écrit :
> Hi everyone,
> I already posted this in NXP forum as a comment
> (https://community.nxp.com/thread/359397), in yocto mailing list
> (https://lists.yoctoproject.org/pipermail/yocto/2018-December/043664.html)
> and in meta-freescale mailing list
>
The code cleanup mentioned in Fixes tag changed the behavior of
kexec_locate_mem_hole. The kexec_locate_mem_hole will try to
allocate free memory only when kbuf.mem is initialized as zero.
But in x86 kexec_file_load implementation there are a few places
the kbuf.mem is reused like below:
/*
On 12/27/18 at 01:06pm, Dave Young wrote:
> The code cleanup mentioned in Fixes tag changed the behavior of
> kexec_locate_mem_hole. The kexec_locate_mem_hole will try to
> allocate free memory only when kbuf.mem is initialized as zero.
>
> But in x86 kexec_file_load implementation there are a
Le 12/27/18 à 4:22 PM, David Miller a écrit :
> From: Kangjie Lu
> Date: Tue, 25 Dec 2018 22:08:18 -0600
>
>> Both bcm_sf2_sw_indir_rw and mdiobus_write_nested could fail, so let's
>> return their error codes upstream.
>>
>> Signed-off-by: Kangjie Lu
>
> Applied with Subject line adjusted as
On 27/12/2018 17:28:33-0600, Kangjie Lu wrote:
> On Thu, Dec 27, 2018 at 4:31 PM Heiner Kallweit
> wrote:
>
> > On 27.12.2018 21:28, Aditya Pakki wrote:
> > > In rv8803_handle_irq, rv8803_write_reg can return a failed return
> > > value when attempting to write to the bus. The fix checks the
On 27/12/2018 14:28:55-0600, Aditya Pakki wrote:
> In rv8803_handle_irq, rv8803_write_reg can return a failed return
> value when attempting to write to the bus. The fix checks the output
> and throws a dev_warn notifying of the failure.
>
Is there any point in doing that as the error will self
Quoting Sugaya, Taichi (2018-12-25 17:35:27)
> Hi
>
> On 2018/11/30 17:31, Stephen Boyd wrote:
> >> + init.num_parents = parents;
> >> + init.parent_names = parent_names;
> >> +
> >> + mcm->cname = clk_name;
> >> + mcm->parent = 0;
> >> + mcm->hw.init =
> >> +
> >>
kmemdup has implemented the function that kmalloc() + memcpy().
Prefer to kmemdup rather than code opened implementation.
Signed-off-by: Peng Hao
---
arch/arm/mach-lpc32xx/pm.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-lpc32xx/pm.c
From: Peng Hao
Date: Wed, 26 Dec 2018 16:28:30 +0800
> From: Wen Yang
>
> This patch fixes potential double frees if register_hdlc_device() fails.
>
> Signed-off-by: Wen Yang
> Reviewed-by: Peng Hao
Applied.
From: Kangjie Lu
Date: Wed, 26 Dec 2018 00:31:08 -0600
> When acpi_match_device fails, its return value is NULL. Directly using
> the return value without a check may result in a NULL-pointer
> dereference. The fix checks if acpi_match_device fails, and if so,
> returns -EINVAL.
>
>
From: Kangjie Lu
Date: Wed, 26 Dec 2018 00:40:32 -0600
> api_parse can fail, and if it fails, we should not use the ss_parms
> which can be incorrect.
> The fix checks its return value and stops using ss_parms if api_parse
> fails.
>
> Signed-off-by: Kangjie Lu
This patch does not apply.
From: Kangjie Lu
Date: Wed, 26 Dec 2018 00:09:04 -0600
> genlmsg_put could fail. The fix inserts a check of its return value, and
> if it fails, returns -EMSGSIZE.
>
> Signed-off-by: Kangjie Lu
Applied.
From: Kangjie Lu
Date: Tue, 25 Dec 2018 23:05:17 -0600
> efx_mcdi_rpc() could fail. The fix checks its status and issues an error
> message if it fails.
>
> Signed-off-by: Kangjie Lu
> ---
> drivers/net/ethernet/sfc/mcdi.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git
1 - 100 of 348 matches
Mail list logo
