Quoting Shaik Sajida Bhanu (2021-03-20 11:17:00)
> diff --git a/arch/arm64/boot/dts/qcom/sc7280-idp.dts
> b/arch/arm64/boot/dts/qcom/sc7280-idp.dts
> index 54d2cb3..4105263 100644
> --- a/arch/arm64/boot/dts/qcom/sc7280-idp.dts
> +++ b/arch/arm64/boot/dts/qcom/sc7280-idp.dts
> @@ -8,6 +8,7 @@
> /
Fix the following sparse warning:
drivers/gpu/drm/nouveau/nvkm/core/client.c:64:1: warning: symbol
'nvkm_uclient_sclass' was not declared. Should it be static?
Signed-off-by: Zou Wei
---
drivers/gpu/drm/nouveau/nvkm/core/client.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
From: mateng
delete unneeded variable 'delay'
Signed-off-by: mateng
---
drivers/input/serio/i8042.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/input/serio/i8042.c b/drivers/input/serio/i8042.c
index abae23a..145bda1 100644
--- a/drivers/input/serio/i8042.c
++
These two HW of wakeup don't follow MediaTek internal IPM rule,
both use a specific way, like as early revision of mt8173.
Due to the index 2 already used by many DTS, it's better to keep
it unchanged for backward compatibility, treat specific ones without
following IPM rule as revision 1.x, meanw
Add support common property usb2-lpm-disable
Signed-off-by: Chunfeng Yun
---
v2: no changes
---
Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.yaml | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/usb/mediatek,mtk-xhci.yaml
b/Documentation/devic
These two HW of wakeup don't follow MediaTek internal IPM rule,
and both use a specific way, like as early revision of mt8173.
Due to the index 2 already used by many DTS, it's better to keep
it unchanged for backward compatibility, treat specific ones without
following IPM rule as revision 1.x, m
The MediaTek 0.96 xHCI controller on some platforms does not
support bulk stream even HCCPARAMS says supporting, due to MaxPSASize
is set a default value 1 by mistake, here use XHCI_BROKEN_STREAMS
quirk to fix it.
Fixes: 94a631d91ad3 ("usb: xhci-mtk: check hcc_params after adding primary hcd")
Sig
The xHCI driver support usb2 HW LPM by default, here add support
XHCI_HW_LPM_DISABLE quirk, then we can disable usb2 lpm when
need it.
Signed-off-by: Chunfeng Yun
---
v2: no changes
---
drivers/usb/host/xhci-mtk.c | 3 +++
drivers/usb/host/xhci-mtk.h | 1 +
2 files changed, 4 insertions(+)
diff
Since the driver only supports the devices created by the OF
core, seems no need MODULE_ALIAS() anymore.
Signed-off-by: Chunfeng Yun
---
v2: no changes
---
drivers/usb/host/xhci-mtk.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/usb/host/xhci-mtk.c b/drivers/usb/host/xhci-mtk.c
ind
Add add support ip-sleep wakeup for MT8192, it's a specific
revision, not following IPM rule.
Signed-off-by: Chunfeng Yun
---
v2:
1. fix typo suggested by Sergei
2. modify revision format
---
drivers/usb/mtu3/mtu3_host.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drive
Add support ip-sleep wakeup for MT8183, it's similar to MT8173,
and it's also a specific one, but not following IPM rule.
Due to the index 2 already used by many DTS, it's better to keep
it unchanged for backward compatibility, treat specific ones without
following IPM rule as revision 1.x, meanwhi
The driver can match only the devices created by the OF core
via the DT table, so the table should be always used.
Signed-off-by: Chunfeng Yun
---
v2: no changes
---
drivers/usb/host/xhci-mtk.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/usb/host/xhci-mtk.c b/d
Add support ip-sleep wakeup for MT8183, it's similar to MT8173,
and it's also a specific one, but not following IPM rule.
Due to the index 2 already used by many DTS, it's better to keep
it unchanged for backward compatibility, treat specific ones without
following IPM rule as revision 1.x, meanwhi
Use wakeup control register offset exactly, and update revision
number
Signed-off-by: Chunfeng Yun
---
v2: modify revision format
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
b/arch/arm6
The driver can match only the devices created by the OF core
via the DT table, so the table should be always used.
Signed-off-by: Chunfeng Yun
---
v2: no changes
---
drivers/usb/mtu3/mtu3_plat.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/usb/mtu3/mtu3_plat.
Add support ip-sleep wakeup for mT8192, it's a specific revision,
and not following IPM rule.
Signed-off-by: Chunfeng Yun
---
v2:
1. fix typo suggested by Sergei
2. modify revision format
---
drivers/usb/host/xhci-mtk.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/driver
Hi all,
Changes since 20210322:
The v4l-dvb tree gained a conflict against the hwmon-staging tree.
The opp tree gained a conflict against the v4l-dvb tree.
The akpm-current tree still had its its build failure.
Non-merge commits (relative to Linus' tree): 5787
5640 files changed, 375045 inser
Quoting Maulik Shah (2021-03-07 21:21:04)
> Hi,
>
> On 3/5/2021 11:12 AM, Rajendra Nayak wrote:
> >
> > On 3/4/2021 5:34 AM, Stephen Boyd wrote:
> >> Quoting Rajendra Nayak (2021-03-03 04:17:49)
> >>> diff --git a/arch/arm64/boot/dts/qcom/sc7280.dtsi
> >>> b/arch/arm64/boot/dts/qcom/sc7280.dtsi
>
Fix the following sparse warning:
drivers/hwtracing/coresight/coresight-etm-perf.c:61:25: warning: symbol
'format_attr_contextid' was not declared. Should it be static?
Signed-off-by: Zou Wei
---
drivers/hwtracing/coresight/coresight-etm-perf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion
Hi,
On 3/23/21 3:11 PM, Aisheng Dong wrote:
>> From: Chanwoo Choi
>> Sent: Tuesday, March 23, 2021 12:11 PM
>>
>> Hi,
>>
>> On 3/23/21 12:25 PM, Dong Aisheng wrote:
>>> Hi Chanwoo,
>>>
>>> On Tue, Mar 23, 2021 at 11:13 AM Dong Aisheng
>> wrote:
A few small fixes and improvements
>
On Mon, Mar 22, 2021 at 09:14:43PM -0700, Randy Dunlap wrote:
> On 3/22/21 6:06 PM, Bhaskar Chowdhury wrote:
> >
> > s/procesing/processing/
> > s/comunication/communication/
> >
> > Signed-off-by: Bhaskar Chowdhury
>
> drivers/staging/wimax/ is in the process of being deleted.
It's already go
On Mon, Mar 22, 2021 at 07:28:42PM +0100, Fabio Aiuto wrote:
> On Mon, Mar 22, 2021 at 05:09:00PM +0100, Greg KH wrote:
> > On Mon, Mar 22, 2021 at 03:31:41PM +0100, Fabio Aiuto wrote:
> > > fix the following checkpatch issues:
> > >
> > > WARNING: externs should be avoided in .c files
> > > 40: F
On Mon, Mar 22, 2021 at 11:42:09PM -0300, Luiz Sampaio wrote:
> Fixed coding style issues.
>
> Signed-off-by: Luiz Sampaio
> ---
> drivers/w1/slaves/w1_ds2438.c | 26 --
> 1 file changed, 12 insertions(+), 14 deletions(-)
Hi,
This is the friendly patch-bot of Greg Kroah
On Mon, Mar 22, 2021 at 08:47:17PM -0700, Lv Yunlong wrote:
> In usbtmc_disconnect, data is got from intf with the
> initial reference. There is no refcount inc operation
> before usbmc_free_int(data). In usbmc_free_int(data),
> the data may be freed.
>
> But later in usbtmc_disconnect, there is a
On 2021/3/22 20:28, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.183 release.
There are 43 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 know.
Responses should be m
On Tue, Mar 23, 2021 at 02:21:52PM +0800, Li Wang wrote:
> Hi linux-s390 experts,
>
> We observed that LTP/clock_gettime04 always FAIL on s390x with
> kernel-v5.12-rc3.
> To simply show the problem, I rewrite the LTP reproducer as a simple C
> below.
> Maybe it's a new bug introduced from the kern
On Tue, Mar 23, 2021 at 07:54:52AM +, Zou Wei wrote:
> Fix the following sparse warning:
>
> drivers/hwtracing/coresight/coresight-etm-perf.c:61:25: warning: symbol
> 'format_attr_contextid' was not declared. Should it be static?
>
> Signed-off-by: Zou Wei
Reviewed-by: Leo Yan
> ---
> dr
On Mon, Mar 22, 2021 at 02:52:31PM -0700, Guenter Roeck wrote:
> On Mon, Mar 22, 2021 at 04:19:10PM +0100, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.26 release.
> > There are 156 patches in this series, all will be posted as a response
> > to this one.
On Mon, Mar 22, 2021 at 04:02:11PM -0500, Tom Lendacky wrote:
> On 3/18/21 3:26 PM, Isaku Yamahata wrote:
> > __set_clr_pte_enc() miscalculates physical address to operate.
> > pfn is in unit of PG_LEVEL_4K, not PGL_LEVEL_{2M, 1G}.
> > Shift size to get physical address should be PAGE_SHIFT,
> > no
On Tue, Mar 23, 2021 at 08:17:47AM +0900, Namjae Jeon wrote:
> > > +
> > > +static int
> > > +compare_oid(unsigned long *oid1, unsigned int oid1len,
> > > + unsigned long *oid2, unsigned int oid2len) {
> > > + unsigned int i;
> > > +
> > > + if (oid1len != oid2len)
> > > + return 0;
> >
On Sun, Mar 21, 2021 at 7:44 PM Alexander Lochmann
wrote:
>
> It simply stores the executed PCs.
> The execution order is discarded.
> Each bit in the shared buffer represents every fourth
> byte of the text segment.
> Since a call instruction on every supported
> architecture is at least four byt
date: 7 weeks ago
config: powerpc64-randconfig-r023-20210323 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project
14696baaf4c43fe53f738bc292bbe169eed93d5d)
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master
Fix the follow link error by select config CRYPTO_ECC and CRYPTO_ECDH.
ERROR: modpost: "ecc_get_curve25519"
[drivers/crypto/hisilicon/hpre/hisi_hpre.ko] undefined!
ERROR: modpost: "ecc_get_curve" [drivers/crypto/hisilicon/hpre/hisi_hpre.ko]
undefined!
ERROR: modpost: "crypto_ecdh_decode_key"
[d
The :c:function: tag evaluation depends on Sphinx version 2 or 3.
Use a syntax that should work with both versions.
Fixes: c0e3bcb25390 ("media: camera-sensor.rst: fix a doc build warning")
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/driver-api/media/camera-sensor.rst | 4 +---
1 file
Hi experts:
When I read scsi kernel code, I found a spell error in
__scsi_remove_device function comments. Patch was made in attach file.
Thanks
//dengke
From 420e051b624c81d298564c416b5a96188dd0bb6a Mon Sep 17 00:00:00 2001
From: dudengke
Date: Tue, 23 Mar 2021 10:57:07 +0800
Subject: [PATCH]
Quoting Laurent Pinchart (2021-03-22 17:00:23)
> Hi Stephen,
>
> On Mon, Nov 02, 2020 at 05:15:24PM -0800, Stephen Boyd wrote:
> > Quoting Sam Ravnborg (2020-11-01 09:37:41)
> > > Hi Stephen.
> > >
> > > On Thu, Oct 29, 2020 at 06:17:34PM -0700, Stephen Boyd wrote:
> > > > This patch series clean
4cd6237b36c51497ec75 opp: Create
> _of_add_table_indexed() to reduce code duplication
> date: 7 weeks ago
> config: powerpc64-randconfig-r023-20210323 (attached as .config)
> compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project
> 14696baaf4c43fe53f738bc292bbe169eed
On 23-03-21, 22:19, Jie Deng wrote:
> +static int __maybe_unused virtio_i2c_freeze(struct virtio_device *vdev)
> +{
> + virtio_i2c_del_vqs(vdev);
> + return 0;
> +}
> +
> +static int __maybe_unused virtio_i2c_restore(struct virtio_device *vdev)
> +{
> + return virtio_i2c_setup_vqs(vdev-
Am 23.03.21 um 07:06 schrieb Rong Chen:
Ugh! Why did the compiler extend the space for the union to 4 bytes?!?
>> Just a random idea but maybe the added padding is due to some
>> kind of odd intrication with the __attribute__((__aligned__(8)))
>> just below? Does this reproduce if we remove
On Mon, Mar 22, 2021 at 07:03:45PM +0100, Arnd Bergmann wrote:
> On Mon, Mar 22, 2021 at 6:03 PM Daniel Thompson
> wrote:
> >
> >
> > Acked-by: Daniel Thompson
> >
> > Which tree do you want to merge this one though? I've got nothing else
> > pending for this file so I am very relaxed about the r
Quoting Taniya Das (2021-03-19 00:47:34)
> Update the RCGs to use shared ops to park the RCGs at XO.
s/Update/fix/?
Can you also elaborate more on why we need to park the RCGs here for all
these different clks? Is the camera driver supposed to not touch these
and let the firmware take over? Is th
This patchset reduce instructions in copy_template.S
to improve the performance of copy memory, when size
is ge 64 bytes.
Yang Yingliang (3):
arm64: lib: introduce ldp2/stp2 macro
arm64: lib: improve copy performance when size is ge 128 bytes
arm64: lib: improve copy performance when size is
On 23.03.2021 10:10:25, Wan Jiabing wrote:
> linux/regmap.h has been included at line 13, so remove the
> duplicate one at line 14.
applied to linux-can-next/testing.
Thanks,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www
Introduce ldp2/stp2 to load/store without add src/dst.
Signed-off-by: Yang Yingliang
---
arch/arm64/include/asm/asm-uaccess.h | 16
arch/arm64/lib/copy_from_user.S | 8
arch/arm64/lib/copy_in_user.S| 8
arch/arm64/lib/copy_to_user.S| 8 +
When copy over 128 bytes, src/dst is added after
each ldp/stp instruction, it will cost more time.
To improve this, we only add src/dst after load
or store 64 bytes.
Copy 4096 bytes cost on Kunpeng920 (ms):
Without this patch:
memcpy: 143.85 copy_from_user: 172.69 copy_to_user: 199.23
With this p
When copy less than 128 and ge than 64 bytes, add src/dst after
load and store 64 bytes to improve performance.
Copy 127 bytes cost on Kunpeng920 (ms):
Without this patch:
memcpy: 14.62 copy_from_user: 14.23 copy_to_user: 14.42
With this patch:
memcpy: 13.85 copy_from_user: 13.26 copy_to_user: 13
A few small fixes and improvements
ChangeLog:
v2 Resend:
* rebase to devfreq-next
* drop original patch 1 & 5.
Patch 5 will be re-sent later when dependent patches merged.
v1->v2:
* squash a few patches
* rebase to devfreq-testing
Dong Aisheng (4):
PM / devfreq: Use more accurate return
On Mon, Mar 22, 2021 at 10:42:24PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> The __static_call_return0() function is declared to return a 'long',
> while it aliases a couple of functions that all return 'int'. When
> building with 'make W=1', gcc warns about this:
>
> kernel/sched/co
First of all, no_central_polling was removed since
commit 7e6fdd4bad03 ("PM / devfreq: Core updates to support devices
which can idle")
Secondly, get_target_freq() is not only called only with update_devfreq()
notified by OPP now, but also min/max freq qos notifier.
So remove this invalid descript
Use the more accurate returned new_freq as resume_freq.
It's the same as how devfreq->previous_freq was updated.
Fixes: 83f8ca45afbf0 ("PM / devfreq: add support for suspend/resume of a
devfreq device")
Signed-off-by: Dong Aisheng
---
drivers/devfreq/devfreq.c | 2 +-
1 file changed, 1 insertion
It's unnecessary to set the same freq again and run notifier calls.
Signed-off-by: Dong Aisheng
---
drivers/devfreq/devfreq.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c
index 85927bd7ee76..a6ee91dd17bd 100644
Current driver actually does not support simple ondemand governor
as it's unable to provide device load information. So removing
the unnecessary callback to avoid confusing.
Right now the driver is using userspace governor by default.
polling_ms was also dropped as it's not needed for non-ondemand
In function hvfb_probe in hyperv_fb.c, it calls hvfb_getmem(hdev, info)
and return err when info->apertures is freed.
In the error1 label of hvfb_probe, info->apertures will be freed twice
by framebuffer_release(info).
My patch sets info->apertures to NULL after it was freed to avoid
double free.
On 23.03.2021 10:54:40, Rong Chen wrote:
> I tried arm-linux-gnueabi (gcc version 10.2.0) and the problem still
> exists, btw we prefer to not use the latest gcc compiler to avoid
> false positives.
FWIW:
I'm using latest debian arm compiler and the BUILD_BUG never triggered.
gcc version 10.2.1 2
Hello Sebastian,
On Mon, Mar 22, 2021 at 09:48:36PM +0100, Sebastian Andrzej Siewior wrote:
> On 2021-03-22 14:40:32 [+0100], Uwe Kleine-König wrote:
> > From a strictly logically point of view you indeed cannot. But if you go
> > to the street and say to people there that they can park their car
On Mon, Mar 22, 2021 at 10:18:17PM +0100, Arnd Bergmann wrote:
> > Steve is correct. Also, why is that warning correct? On x86 we return in
> > RAX, and using int will simply not inspect the upper 32 bits there.
>
> I think the code works correctly on all architectures we support because
> both '
On Tue, Mar 23, 2021 at 08:43:25AM +0800, Bard Liao wrote:
> From: Pierre-Louis Bossart
>
> Now that the auxiliary_bus exists, there's no reason to use platform
> devices as children of a PCI device any longer.
>
> This patch refactors the code by extending a basic auxiliary device
> with Intel
On Mon, Mar 22, 2021 at 11:30:07PM -, tip-bot2 for Arnd Bergmann wrote:
> The following commit has been merged into the locking/core branch of tip:
>
> Commit-ID: 335c73e7c8f7deb23537afbbbe4f8ab48bd5de52
> Gitweb:
> https://git.kernel.org/tip/335c73e7c8f7deb23537afbbbe4f8ab48bd5de5
On Tue, Mar 23, 2021 at 12:18:46PM +0530, Vinod Koul wrote:
> On 23-03-21, 08:43, Bard Liao wrote:
> > From: Pierre-Louis Bossart
> >
> > Now that the auxiliary_bus exists, there's no reason to use platform
> > devices as children of a PCI device any longer.
> >
> > This patch refactors the code
On a typical end product, a vendor may choose to secure some regions in
the NAND memory which are supposed to stay intact between FW upgrades.
The access to those regions will be blocked by a secure element like
Trustzone. So the normal world software like Linux kernel should not
touch these region
On a typical end product, a vendor may choose to secure some regions in
the NAND memory which are supposed to stay intact between FW upgrades.
The access to those regions will be blocked by a secure element like
Trustzone. So the normal world software like Linux kernel should not
touch these region
On Mon, Mar 22, 2021 at 10:49:58PM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> With 'make W=1', gcc warns about casts between incompatible function
> types:
>
> kernel/trace/ftrace.c:128:31: error: cast between incompatible function types
> from 'void (*)(long unsigned int, long unsi
On a typical end product, a vendor may choose to secure some regions in
the NAND memory which are supposed to stay intact between FW upgrades.
The access to those regions will be blocked by a secure element like
Trustzone. So the normal world software like Linux kernel should not
touch these region
Convert Qcom NANDc devicetree binding to YAML.
Signed-off-by: Manivannan Sadhasivam
Reviewed-by: Rob Herring
---
.../devicetree/bindings/mtd/qcom,nandc.yaml | 196 ++
.../devicetree/bindings/mtd/qcom_nandc.txt| 142 -
2 files changed, 196 insertions(+), 142 del
There is a patch similar to yours that was send in advance, as follows:
https://www.spinics.net/lists/linux-crypto/msg54238.html
On 2021/3/23 15:27, Yang Yingliang wrote:
Fix the follow link error by select config CRYPTO_ECC and CRYPTO_ECDH.
ERROR: modpost: "ecc_get_curve25519"
[drivers/crypto
On 23/03/2021 06:09, Leonardo Bras wrote:
According to LoPAR, ibm,query-pe-dma-window output named "IO Page Sizes"
will let the OS know all possible pagesizes that can be used for creating a
new DDW.
Currently Linux will only try using 3 of the 8 available options:
4K, 64K and 16M. According
change 'backwords' to 'backwards'
change 'and argument' to 'an argument'
change 'visibile' to 'visible'
change 'wont't' to 'won't'
reorganize sentence
Signed-off-by: Xiaofeng Cao
---
v2: resume the right boundary
fs/exec.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
dif
There is a timer wrap issue on dra7 for the ARM architected timer.
In a typical clock configuration the timer fails to wrap after 388 days.
To work around the issue, we need to use timer-ti-dm timers instead.
Let's prepare for adding support for percpu timers by adding a common
dmtimer_clkevt_ini
There is a timer wrap issue on dra7 for the ARM architected timer.
In a typical clock configuration the timer fails to wrap after 388 days.
To work around the issue, we need to use timer-ti-dm percpu timers instead.
Let's configure dmtimer3 and 4 as percpu timers by default, and warn about
the is
Hi all,
Here is v2 set of fixes for dra7 ARM architected timer wrap errata i940
where the timer fails to wrap after 388 days. The workaround is to use two
dmtimers as the local timers instead.
Note that these patches depend on timer posted mode fixes series
"[PATCH 0/3] Fixes for timer-ti-dm syst
On 2021-03-23 04:01, Ben Greear wrote:
> On 3/22/21 6:20 PM, Brian Norris wrote:
>> On Mon, Mar 22, 2021 at 4:58 PM Ben Greear wrote:
>>> On 7/22/20 6:00 AM, Felix Fietkau wrote:
On 2020-07-22 14:55, Johannes Berg wrote:
> On Wed, 2020-07-22 at 14:27 +0200, Felix Fietkau wrote:
>
>>
On 23.03.21 08:34, Marc Kleine-Budde wrote:
On 23.03.2021 10:54:40, Rong Chen wrote:
I tried arm-linux-gnueabi (gcc version 10.2.0) and the problem still
exists, btw we prefer to not use the latest gcc compiler to avoid
false positives.
FWIW:
I'm using latest debian arm compiler and the BUILD
On 2021/3/22 22:22, Mike Snitzer wrote:
> On Mon, Mar 22 2021 at 4:11am -0400,
> Christoph Hellwig wrote:
>
>> On Sat, Mar 20, 2021 at 03:19:23PM +0800, Zhiqiang Liu wrote:
>>> From: Zhiqiang Liu
>>>
>>> When we make IO stress test on multipath device, there will
>>> be a metadata err becaus
On Mon 22-03-21 09:57:14, Mike Kravetz wrote:
> On 3/22/21 6:59 AM, Michal Hocko wrote:
> > On Fri 19-03-21 15:42:02, Mike Kravetz wrote:
> >> The number of hugetlb pages can be adjusted by writing to the
> >> sysps/proc files nr_hugepages, nr_hugepages_mempolicy or
> >> nr_overcommit_hugepages. T
On Mon, Mar 22, 2021 at 05:29:21PM -0400, Steven Rostedt wrote:
> On Mon, 22 Mar 2021 22:18:17 +0100
> Arnd Bergmann wrote:
>
> > I think the code works correctly on all architectures we support because
> > both 'int' and 'long' are returned in a register with any unused bits
> > cleared.
> > It
Hi Thomas,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 84196390620ac0e5070ae36af84c137c6216a7dc
commit: b83ba0b9df56f8404ccc6ebcc7050fb8294f0f20 MIPS: of: Introduce helper
function to get DTB
date: 7 weeks ago
On Mon 22-03-21 16:07:29, Mike Kravetz wrote:
> On 3/22/21 7:07 AM, Michal Hocko wrote:
> > On Fri 19-03-21 15:42:03, Mike Kravetz wrote:
> >> The routine set_max_huge_pages reduces the number of hugetlb_pages,
> >> by calling free_pool_huge_page in a loop. It does this as long as
> >> persistent_
On 03/23/21 at 11:13am, Wan Jiabing wrote:
> linux/pgtable.h has been included at line 11 with annotation.
> So we remove the duplicate one at line 8.
>
> Signed-off-by: Wan Jiabing
Thanks for your posting. But this resend is still not good. I have
pasted the suggested log, wondering why you jus
On Mon 22-03-21 16:28:07, Mike Kravetz wrote:
> On 3/22/21 7:31 AM, Michal Hocko wrote:
> > On Fri 19-03-21 15:42:06, Mike Kravetz wrote:
> > [...]
> >> @@ -2090,9 +2084,15 @@ static void return_unused_surplus_pages(struct
> >> hstate *h,
> >>while (nr_pages--) {
> >>h->resv_huge_p
Fix the following sparse warning:
drivers/gpu/drm/nouveau/nvkm/subdev/mc/tu102.c:74:1: warning: symbol
'tu102_mc_intr_mask' was not declared. Should it be static?
drivers/gpu/drm/nouveau/nvkm/subdev/mc/tu102.c:62:1: warning: symbol
'tu102_mc_intr_rearm' was not declared. Should it be static?
Rep
On Tue, Mar 23, 2021 at 08:50:53AM +0100, Michal Hocko wrote:
> > >> +static inline unsigned long min_hp_count(struct hstate *h, unsigned
> > >> long count)
> > >> +{
> > >> +unsigned long min_count;
> > >> +
> > >> +min_count = h->resv_huge_pages + h->nr_huge_pages -
> > >> h->f
Maybe it's easier for us to understand the function of
check_kill_permission.
Signed-off-by: zhouchuangao
---
kernel/signal.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/kernel/signal.c b/kernel/signal.c
index f2a1b89..2fbf68a 100644
--- a/kernel/signal.c
+++ b/kern
On Mon, 2021-03-22 at 22:51 +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann
>
> The correct order is 'static const', not 'const static', as seen from
> make W=1:
>
> drivers/net/wireless/intel/iwlwifi/mvm/rfi.c:14:1: error: 'static' is not at
> beginning of declaration [-Werror=old-style-decl
Hi Andy Shevchenko,
> -Original Message-
> From: Andy Shevchenko
> Sent: Monday, March 22, 2021 10:47 PM
> To: Sai Krishna Potthuri
> Cc: Linus Walleij ; Rob Herring
> ; Michal Simek ; Greg Kroah-
> Hartman ; linux-arm Mailing List ker...@lists.infradead.org>; Linux Kernel Mailing List
On 2021-03-22 15:48, Geert Uytterhoeven wrote:
Use the existing HT16K33_FB_SIZE definition instead of open-coding the
same calculation using an hardcoded value.
While at it, restore reverse Christmas tree variable declaration order.
Signed-off-by: Geert Uytterhoeven
---
drivers/auxdisplay/ht16
On 2021-03-22 15:48, Geert Uytterhoeven wrote:
There is no need to check the return code of input_register_device(),
just propagate it to the caller.
Signed-off-by: Geert Uytterhoeven
---
drivers/auxdisplay/ht16k33.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/driv
Fix the following sparse warning:
drivers/gpu/drm/nouveau/nvkm/subdev/mc/tu102.c:74:1: warning: symbol
'tu102_mc_intr_mask' was not declared. Should it be static?
drivers/gpu/drm/nouveau/nvkm/subdev/mc/tu102.c:62:1: warning: symbol
'tu102_mc_intr_rearm' was not declared. Should it be static?
Rep
Hi Stephen,
On Tue, Mar 9, 2021 at 6:22 AM Sergio Paracuellos
wrote:
>
> This patchset ports CPU clock detection for MT7621 from OpenWrt
> and adds a complete clock plan for the mt7621 SOC.
>
> The documentation for this SOC only talks about two registers
> regarding to the clocks:
> * SYSC_REG_C
Fix the following checkpatch warning:
WARNING: 'compoment' may be misspelled - perhaps 'component'?
Fixes: 8e264c52e1da ("coresight: core: Allow the coresight core driver to be
built as a module")
Signed-off-by: Qi Liu
---
drivers/hwtracing/coresight/coresight-core.c | 2 +-
1 file changed, 1
On Tue, Mar 16, 2021 at 11:56:28AM +0100, Ahmed S. Darwish wrote:
> Hi,
>
> This is a small series to trasform xfrm_state_hash_generation sequence
> counter to seqcount_spinlock_t, instead of plain seqcount_t.
>
> In general, seqcount_LOCKNAME_t sequence counters allows to associate
> the lock us
friendly ping..
On 2021/3/22 10:43, Wu Bo wrote:
> On 2021/3/21 23:29, Zhiqiang Liu wrote:
>> From: Feilong Lin
>>
>> Repeated hot-plugging of pci devices for a virtual
>> machine driven by virtio, we found that there is a
>> leak in kmalloc-4k, which was confirmed as the memory
>> of the pci_dev
On Tue 23-03-21 09:01:02, Peter Zijlstra wrote:
> On Tue, Mar 23, 2021 at 08:50:53AM +0100, Michal Hocko wrote:
>
> > > >> +static inline unsigned long min_hp_count(struct hstate *h, unsigned
> > > >> long count)
> > > >> +{
> > > >> + unsigned long min_count;
> > > >> +
> > > >> + min_
On some ARCHs, such as aarch64, page size may be 64K, meantime there may
be lots of CPU cores. relay_open() needs to allocate pages on each CPU
blktrace, so easily too many pages are taken by blktrace. For example,
on one ARM64 server: 224 CPU cores, 16G RAM, blktrace finally got
allocated 7GB in c
blktrace may pass big trace buffer size via '-b', meantime the system
may have lots of CPU cores, so too much memory can be allocated for
blktrace.
The 1st patch shutdown bltrace in blkdev_close() in case of task
exiting, for avoiding trace buffer leak.
The 2nd patch limits max trace buffer size
blktrace may allocate lots of memory, if the process is terminated
by user or OOM, we need to provide one chance to remove the trace
buffer, otherwise memory leak may be caused.
Fix the issue by shutdown blktrace in case of task exiting in
blkdev_close().
Signed-off-by: Ming Lei
---
fs/block_de
Hi Kishon,
On 23/03/21 11:59 am, Kishon Vijay Abraham I wrote:
> Hi Aswath,
>
> On 23/03/21 10:54 am, Aswath Govindraju wrote:
>> Hi Nishanth,
>>
>> On 22/03/21 9:05 pm, Nishanth Menon wrote:
>>> On 18:42-20210322, Aswath Govindraju wrote:
The following speed modes are now supported in J7200
The following commit has been merged into the locking/core branch of tip:
Commit-ID: ebdbd41bf2536ac57bf315ce9690245e08c5e506
Gitweb:
https://git.kernel.org/tip/ebdbd41bf2536ac57bf315ce9690245e08c5e506
Author:Thomas Gleixner
AuthorDate:Mon, 22 Mar 2021 09:46:13 +01:00
Comm
These were added in commit 780cc0f370 ("usb: gadget: add '__ref' for
rndis_config_register() and cdc_config_register()") to silence
modpost, but they didn't fix the real problem - that was fixed later
by removing wrong __init annotations in commit c94e289f195e ("usb:
gadget: remove incorrect __init
On 2021-03-22 15:48, Geert Uytterhoeven wrote:
Extract the character line display core support from the simple ASCII
LCD driver for the MIPS Boston, Malta & SEAD3 development boards into
its own subdriver, so it can be reused for other displays.
Note that this moves the "message" device attribut
On Thu, 18 Mar 2021 10:08:55 + sj38.p...@gmail.com wrote:
> From: SeongJae Park
>
> This commit adds a simple user space tests for DAMON. The tests are
> using kselftest framework.
>
> Signed-off-by: SeongJae Park
> ---
> tools/testing/selftests/damon/Makefile| 7 +
> .../selft
1 - 100 of 1674 matches
Mail list logo
