Hi, I have tested the patch on 5.12.0-rc4+, it seems to fix the problem.
Regards,
butt3rflyh4ck.
On Mon, Mar 22, 2021 at 7:47 PM Chao Yu wrote:
>
> butt3rflyh4ck reported a bug found by
> syzkaller fuzzer with custom modifications in 5.12.0-rc3+ [1]:
>
> dump_stack+0xfa/0x151
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
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
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
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
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
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
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
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
+++
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
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
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
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
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
Add power-domains found on rk3568 socs.
Signed-off-by: Elaine Zhang
---
drivers/soc/rockchip/pm_domains.c | 31 +++
1 file changed, 31 insertions(+)
diff --git a/drivers/soc/rockchip/pm_domains.c
b/drivers/soc/rockchip/pm_domains.c
index 54eb6cfc5d5b..a2c19c845cf2
According to a description from TRM, add all the power domains
Signed-off-by: Elaine Zhang
---
include/dt-bindings/power/rk3568-power.h | 32
1 file changed, 32 insertions(+)
create mode 100644 include/dt-bindings/power/rk3568-power.h
diff --git
Support power domain function for RK3568 Soc.
Change in V2:
[PATCH v2 1/3]: No change.
[PATCH v2 2/3]: Fix up yaml code styles.
[PATCH v2 3/3]: No change.
Elaine Zhang (3):
dt-bindings: add power-domain header for RK3568 SoCs
dt-bindings: Convert the rockchip power_domain to YAML and extend
This converts the rockchip power domain family bindings to YAML schema,
and add binding documentation for the power domains found on Rockchip
RK3568 SoCs.
Signed-off-by: Elaine Zhang
---
.../bindings/soc/rockchip/power_domain.txt| 136 -
.../rockchip/rockchip,power-controller.yaml
On 23-03-21, 16:33, Jie Deng wrote:
> On 2021/3/23 15:27, Viresh Kumar wrote:
>
> > 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
Hey Konrad,
Thanks for the review!
On Mon, 22 Mar 2021 at 18:27, Konrad Dybcio
wrote:
>
> Hi!
>
>
> > + tsens0: thermal-sensor@c222000 {
> > + compatible = "qcom,sm8350-tsens", "qcom,tsens-v2";
> > + reg = <0 0x0C263000 0 0x1ff>, /* TM */
> >
Hi Nick,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 84196390620ac0e5070ae36af84c137c6216a7dc
commit: 1e1b6d63d6340764e00356873e5794225a2a03ea lib/string.c: implement stpcpy
date: 6 months ago
config:
Hi Marcel,
Thanks for your suggestion. I implemented it in v2, please take another look.
On Mon, 22 Mar 2021 at 23:53, Marcel Holtmann wrote:
>
> Hi Archie,
>
> > There is a possibility of receiving a zapped sock on
> > l2cap_sock_connect(). This could lead to interesting crashes, one
> > such
On 23.03.2021 09:32:10, Oliver Hartkopp wrote:
> I wonder if the compiler configurations (gcc -v) or the options used at
> kernel build time are identical.
I tested several compilers and with my .config never triggered a
problem, but with Rong Chen it does. I'm trying to figure out which
option
On Tue, 23 Mar 2021, Bhaskar Chowdhury wrote:
> s/nothign/nothing/
>
> Signed-off-by: Bhaskar Chowdhury
You've sent the same patch before? I've already pushed it.
BR,
Jani.
> ---
> drivers/gpu/drm/i915/display/intel_dpll_mgr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
Enjoy!
The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:
Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git ib-mfd-power-v5.13
for you to fetch changes up to
On 2021-03-22 15:48, Geert Uytterhoeven wrote:
This driver has many users of "client->dev". Add shorthands to
simplify
the code.
Signed-off-by: Geert Uytterhoeven
---
drivers/auxdisplay/ht16k33.c | 43 ++--
1 file changed, 22 insertions(+), 21 deletions(-)
On 22.03.21 22:56, Theodore Ts'o wrote:
> On Mon, Mar 22, 2021 at 08:25:15PM +0100, Thorsten Leemhuis wrote:
>> I agree to the last point and yeah, maybe regressions are the more
>> important problem we should work on – at least from the perspective of
>> kernel development. But from the users
On 2021-03-23 08:34:47 [+0100], Uwe Kleine-König wrote:
> Hello Sebastian,
Hi Uwe,
> 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
On Mon, Mar 22, 2021 at 01:33:38PM -0700, Dipen Patel wrote:
> Hi Richard,
>
> Thanks for your input and time. Please see below follow up.
>
> On 3/20/21 8:38 AM, Richard Cochran wrote:
> > On Sat, Mar 20, 2021 at 01:44:20PM +0100, Arnd Bergmann wrote:
> >> Adding Richard Cochran as well, for
tree/branch:
https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
branch HEAD: f4d010298f01aac657191629d6e9e11d978cc64d doc: Fix statement of
RCU's memory-ordering requirements
elapsed time: 726m
configs tested: 122
configs skipped: 3
The following configs have been
Hi Chunfeng,
I love your patch! Perhaps something to improve:
[auto build test WARNING on usb/usb-testing]
[also build test WARNING on robh/for-next linus/master v5.12-rc4 next-20210323]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest
On Tue, Mar 23, 2021 at 10:59:01AM +0800, Xu Yihang wrote:
> Fixes the following W=1 kernel build warning(s):
> ../arch/x86/kernel/cpu/intel.c: In function ‘init_intel’:
> ../arch/x86/kernel/cpu/intel.c:644:20: warning: variable ‘l2’ set but not
> used [-Wunused-but-set-variable]
>unsigned
From: Colin Ian King
There is a spelling mistake in a dev_err message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/media/platform/imx-jpeg/mxc-jpeg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/imx-jpeg/mxc-jpeg.c
On Tue, 02 Mar 2021, Andy Shevchenko wrote:
> In ->remove() unregister resources in reversed order, i.e. MFD devices first
> followed by I²C clock.
>
> Signed-off-by: Andy Shevchenko
> ---
> drivers/mfd/intel_quark_i2c_gpio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied,
On Thu, 18 Feb 2021 22:23:23 +, Nicola Mazzucato wrote:
> In this V8 I have addressed your comments:
> - correct the goto in patch 1/3
> - improve comment in patch 2/3 for dev_pm_opp_get_opp_count()
>
> Many thanks,
> Nicola
>
> [...]
(New commit info after rebase to v5.12-rc2 for obvious
On Fri, 5 Mar 2021 17:33:17 +, Robin Murphy wrote:
> The PLDA root complex on Juno relies on an address-based lookup table to
> generate AXI attributes for inbound PCI transactions, and as such will
> not pass any transaction not matching any programmed address range. The
> standard firmware
On Mon, Mar 22, 2021 at 04:34:28PM +0530, Roja Rani Yarubandi wrote:
> This reverts commit 048eb908a1f2 ("soc: qcom-geni-se: Add interconnect
> support to fix earlycon crash")
>
> ICC core and platforms drivers supports sync_state feature with
> commit 7d3b0b0d8184 ("interconnect: qcom: Use
Hi Jonathan,
On Thu, Mar 18, 2021 at 12:12:02PM +, Sudeep Holla wrote:
> On Tue, Mar 16, 2021 at 10:38:43PM -0700, Jyoti Bhayana wrote:
> > Hi Christian,
> >
> > Thanks for the detailed explanation. Sounds good to me.
> >
>
> Can I get official Reviewed-by or Acked-by please if you are
On Tue, Mar 23, 2021 at 09:53:03AM +0100, Vitaly Kuznetsov wrote:
> hardware_disable_test produces 512 snippets like
> ...
> main: [511] waiting semaphore
> run_test: [511] start vcpus
> run_test: [511] all threads launched
> main: [511] waiting 368us
> main: [511] killing child
>
> and this
Hi!
> > > (a) the traditional include guard optimization HAS NO HIDDEN SEMANTIC
> > > MEANING. It's a pure optimization that doesn't actually change
> > > anything else. If you don't do the optimization, absolutely nothing
> > > changes.
> >
> > And if the parser is well written the optimisation
On 20.03.21 10:36, Miaohe Lin wrote:
If the zone device page does not belong to un-addressable device memory,
the variable entry will be uninitialized and lead to indeterminate pte
entry ultimately. Fix this unexpectant case and warn about it.
s/unexpectant/unexpected/
Fixes: df6ad69838fc
From: zhichao Cai
vaules -> values
Signed-off-by: zhichao Cai
---
drivers/tty/serial/8250/8250_mtk.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/8250/8250_mtk.c
b/drivers/tty/serial/8250/8250_mtk.c
index f7d3023..c6633dc 100644
---
On Tue, 23 Mar 2021 at 11:32, Peter Zijlstra wrote:
>
> On Tue, Mar 23, 2021 at 10:52:41AM +0100, Marco Elver wrote:
>
> > with efs->func==__perf_event_enable. I believe it's sufficient to add
> >
> > mutex_lock(_event->child_mutex);
> > list_del_init(>child_list);
> >
On Fri 19-03-21 10:26:32, Oscar Salvador wrote:
> Let the caller check whether it can pass MHP_MEMMAP_ON_MEMORY by
> checking mhp_supports_memmap_on_memory().
> MHP_MEMMAP_ON_MEMORY can only be set in case
> ARCH_MHP_MEMMAP_ON_MEMORY_ENABLE is enabled, the architecture supports
> altmap, and the
On 22.03.21 15:05, Claudio Imbrenda wrote:
Prefixing needs to be applied to the guest real address to translate it
into a guest absolute address.
The value of MSO needs to be added to a guest-absolute address in order to
obtain the host-virtual.
Fixes: 223ea46de9e79 ("s390/kvm: VSIE: correctly
We encounter a resume issue in our device sometimes. The mmc device's
parent list is
mmc0:0001->mmc_host mmc0->fa63.mmc->soc in our soc. We found in the blow
case with mmc0->power.disable_depth=0 the mmc_runtime_resume will be skipped,
which cause subsequent mmc command fail.
On Mon, Mar 22, 2021 at 05:01:59PM +0100, David Hildenbrand wrote:
> It used to be true that we can have system RAM only on the first level
> in the resourc tree. However, this is no longer holds for driver-managed
> system RAM (i.e., dax/kmem and virtio-mem).
>
> The function walk_mem_res() only
Alexander, Ahmad,
On 23/03/2021 at 11:55, Ahmad Fatoum wrote:
Hello Alexander,
On 23.03.21 11:45, Alexander Dahl wrote:
Hei hei,
I could not get ethernet to work on SAMA5D27-SOM1-EK1 with kernels v5.10 and
v5.11 built by a recent ptxdist based DistroKit BSP, while it used to work with
an
Ping.
> -Original Message-
> From: Bharat Kumar Gogada
> Sent: Monday, March 15, 2021 11:43 AM
> To: Bharat Kumar Gogada ; linux-
> p...@vger.kernel.org; linux-kernel@vger.kernel.org
> Cc: bhelg...@google.com
> Subject: RE: [PATCH v3 1/2] PCI: xilinx-nwl: Enable coherent PCIe DMA traffic
* Paul E. McKenney wrote:
> > > * there are no read-side primitives analogous to rcu_read_lock() and
> > > * rcu_read_unlock() because this primitive is intended to determine
> > > * that all tasks have passed through a safe state, not so much for
> > > - * data-strcuture synchronization.
>
The following commit has been merged into the locking/urgent branch of tip:
Commit-ID: 291da9d4a9eb3a1cb0610b7f4480f5b52b1825e7
Gitweb:
https://git.kernel.org/tip/291da9d4a9eb3a1cb0610b7f4480f5b52b1825e7
Author:Thomas Gleixner
AuthorDate:Mon, 22 Mar 2021 09:46:13 +01:00
On 23.03.21 12:06, Andy Shevchenko wrote:
On Mon, Mar 22, 2021 at 05:01:58PM +0100, David Hildenbrand wrote:
It used to be true that we can have busy system RAM only on the first level
in the resourc tree. However, this is no longer holds for driver-managed
system RAM (i.e., added via dax/kmem
Thanks for your patch.
I would like to change the prefix to "video: hyperv_fb:" to be more
specific.
On Tue, Mar 23, 2021 at 12:33:50AM -0700, Lv Yunlong wrote:
> In function hvfb_probe in hyperv_fb.c, it calls hvfb_getmem(hdev, info)
> and return err when info->apertures is freed.
>
> In the
On Thu, Feb 18, 2021 at 06:40:51PM +0300, Serge Semin wrote:
> On Thu, Feb 18, 2021 at 04:32:29PM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Feb 18, 2021 at 06:29:04PM +0300, Serge Semin wrote:
> > > Bjorn, Greg, Felippe, Andy,
> > > Any comments on this series? Bjorn, Greg you asked me to
On Tue, Mar 16, 2021 at 04:36:57AM +0800, Hongren Zheng (Zenithal) wrote:
> The commit e0546fd8b748b19d8edd1550530da8ebad6e4b31 implemented device
> mode for user space tools, however the corresponding options are not
> documented in man page.
When referring to commits in the kernel, they should
Hi Miquel,
On Tue, 23 Mar 2021 at 19:32, Miquel Raynal wrote:
> You can run nandbiterrs -i /dev/mtdX
>
> You'll see if there is ECC correction or not (and its level).
These are results I get for both of the nandbiterrs tests.
# nandbiterrs -i /dev/mtd1
incremental biterrors test
Successfully
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
---
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
On 2021-03-22 15:48, Geert Uytterhoeven wrote:
ht16k33_probe() does not use the passed i2c_device_id, so the driver
can
be converted trivially to the new-style of i2c probing.
Signed-off-by: Geert Uytterhoeven
---
drivers/auxdisplay/ht16k33.c | 5 ++---
1 file changed, 2 insertions(+), 3
On Mon, Mar 22, 2021 at 06:08:44PM -0400, Peter Xu wrote:
> v4:
> - Fixed a few "subordinate clauses" (SC) cases [Alex]
> - Reword in ioctl_userfaultfd.2 to use bold font for the two modes referenced,
> so as to be clear on what is "both" referring to [Alex]
>
> v3:
> - Don't use "Currently",
From: Tan Tee Min
Add support for PHY loopback for the Marvell 88E2110 PHY.
This allow user to perform selftest using ethtool.
Signed-off-by: Tan Tee Min
Signed-off-by: Wong Vee Khee
---
drivers/net/phy/marvell10g.c | 12
1 file changed, 12 insertions(+)
diff --git
On Tue, 2021-03-09 at 13:43 +0300, Alexander Mikhalitsyn wrote:
> On Sat, 06 Mar 2021 17:13:32 +0800
> Ian Kent wrote:
>
> > On Fri, 2021-03-05 at 14:55 +0300, Alexander Mikhalitsyn wrote:
> > > On Fri, 05 Mar 2021 18:10:02 +0800
> > > Ian Kent wrote:
> > >
> > > > On Thu, 2021-03-04 at 13:11
On Mon, 22 Mar 2021, Min Li wrote:
> >
> > I'm pretty confused. This has been sent ~6 times already. What is the v1
> > of?
> > Is this a different driver? If so, why does it have the same $SUBJECT line?
> >
> > If this is not actually v1. Please provide a change-log.
> >
>
>
> Hi Lee
>
On Fri, 12 Mar 2021, matthias@kernel.org wrote:
> From: Matthias Brugger
>
> For regulators a compatible string is superfluous. Drop the string.
>
> Signed-off-by: Matthias Brugger
> ---
> drivers/mfd/mt6397-core.c | 3 ---
> 1 file changed, 3 deletions(-)
Acked-by: Lee Jones
--
Lee
On 2021/3/11 4:49, Jaegeuk Kim wrote:
On 03/10, Huang Jianan wrote:
Hi Richard,
On 2021/3/9 12:01, Matthew Wilcox wrote:
On Tue, Mar 09, 2021 at 10:23:35AM +0800, Weichao Guo wrote:
Hi Richard,
On 2021/3/8 19:53, Richard Palethorpe wrote:
Hello,
kern :err : [ 187.461914] F2FS-fs
On Mon, Mar 22, 2021 at 9:17 PM Dipen Patel wrote:
> My follow-up concerns on both Linus's and Kent's feedback:
>
> 1. Please correct me if I am wrong, lineevent in the gpiolib* is only
> serves the userspace clients.
> 1.a What about kernel drivers wanting to use this feature for
Hi Chunfeng,
I love your patch! Perhaps something to improve:
[auto build test WARNING on usb/usb-testing]
[also build test WARNING on robh/for-next linus/master v5.12-rc4 next-20210323]
[cannot apply to mediatek/for-next]
[If your patch is applied to the wrong git tree, kindly drop us a note
On Mon, Mar 22, 2021 at 05:44:01PM +0100, Fabrice Gasnier wrote:
> On 3/19/21 12:00 PM, William Breathitt Gray wrote:
> > static const struct atmel_tcb_config tcb_rm9200_config = {
> > diff --git a/drivers/counter/stm32-lptimer-cnt.c
> > b/drivers/counter/stm32-lptimer-cnt.c
> > index
Hello Jon, could I ask you a review for this patch?
Thanks,
SeongJae Park
On Mon, Mar 22, 2021 at 10:46 PM Johannes Weiner wrote:
>
> On Sat, Mar 20, 2021 at 12:38:14AM +0800, Muchun Song wrote:
> > The rcu_read_lock/unlock only can guarantee that the memcg will not be
> > freed, but it cannot guarantee the success of css_get (which is in the
> > refill_stock when
On Thu, 18 Mar 2021, Kiran Gunda wrote:
> As per the current implementation, after FSC (Full Scale Current)
> and brightness update the sync bits are set-then-cleared.
> But, the FSC and brightness sync takes place when the sync bits are
> set (e.g. on a rising edge). So the hardware team
On 22.03.21 17:01, David Hildenbrand wrote:
It used to be true that we can have busy system RAM only on the first level
in the resourc tree. However, this is no longer holds for driver-managed
system RAM (i.e., added via dax/kmem and virtio-mem), which gets added on
lower levels.
We have two
: 406e47652161d4f0d9bc4cd6237b36c51497ec75 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
14696baaf4c43fe53f738bc292bbe169eed93d5d)
reproduce
On Wed, 03 Mar 2021, Fabrice Gasnier wrote:
> The ARR register is cleared unconditionally upon probing, after the maximum
> value has been read. This initial condition is rather not intuitive, when
> considering the counter child driver. It rather expects the maximum value
> by default:
> - The
s/preceeds/precedes/ .two different places
s/rsponse/response/
s/cetain/certain/
s/precison/precision/
Fix a sentence construction as per suggestion.
Signed-off-by: Bhaskar Chowdhury
---
Changes from V1:
Bad sentence construction missed my eyes , correced by following
Randy's
On Tue, Mar 23, 2021 at 02:28:54AM -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
On Sun, Mar 21, 2021 at 7:37 PM Jonathan Cameron
wrote:
>
> On Sat, 20 Mar 2021 17:41:00 +
> Jonathan Cameron wrote:
>
> > On Mon, 15 Mar 2021 09:58:08 +
> > "Sa, Nuno" wrote:
> >
> > > > -Original Message-
> > > > From: Alexandru Ardelean
> > > > Sent: Saturday, March 6, 2021
On Tue, 2021-01-19 at 12:07 +0100, Bartosz Golaszewski wrote:
> On Tue, Jan 19, 2021 at 8:23 AM Matti Vaittinen
> wrote:
> > Support GPO(s) found from ROHM BD71815 power management IC. The IC
> > has two
> > GPO pins but only one is properly documented in data-sheet. The
> > driver
> > exposes
On Tue, Mar 23, 2021 at 10:08:00AM +0100, Linus Walleij wrote:
> On Mon, Mar 22, 2021 at 9:17 PM Dipen Patel wrote:
>
> > My follow-up concerns on both Linus's and Kent's feedback:
> >
> > 1. Please correct me if I am wrong, lineevent in the gpiolib* is only
> > serves the userspace
On Mon, 22 Mar 2021 at 18:20, 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.
>
>
On Tue, Mar 23, 2021 at 10:52:41AM +0100, Marco Elver wrote:
> with efs->func==__perf_event_enable. I believe it's sufficient to add
>
> mutex_lock(_event->child_mutex);
> list_del_init(>child_list);
> mutex_unlock(_event->child_mutex);
>
> right before removing from context.
On Tue, Mar 23, 2021 at 09:14:53AM +, Lee Jones wrote:
> On Tue, 02 Mar 2021, Andy Shevchenko wrote:
>
> > The structures are used as place holders, so they are modified at run-time.
> > Obviously they may not be constants.
> >
> > BUG: unable to handle page fault for address: d0643220
> >
On Tue, Mar 23, 2021 at 09:20:57AM +, Lee Jones wrote:
> On Tue, 02 Mar 2021, Andy Shevchenko wrote:
>
> > It's convenient and less error prone to use definitions to address
> > different cells in an array. For this purpose we may reuse existing
> > BAR definitions.
...
> > + {
> > +
On 23/03/2021 01:51, Vladimir Oltean wrote:
> From: Vladimir Oltean
>
> The SWITCHDEV_ATTR_ID_BRIDGE_AGEING_TIME attribute is only emitted from:
>
> sysfs/ioctl/netlink
> -> br_set_ageing_time
>-> __set_ageing_time
>
> therefore not at bridge port creation time, so:
> (a) switchdev drivers
On Thu, Mar 18, 2021 at 03:29:19PM -0500, Madhavan T. Venkataraman wrote:
>
>
> On 3/18/21 1:26 PM, Mark Brown wrote:
> > On Mon, Mar 15, 2021 at 11:57:55AM -0500, madve...@linux.microsoft.com
> > wrote:
> >
> >> + /* Terminal record, nothing to unwind */
> >> + if (fp == (unsigned long)
On Tue, 23 Mar 2021 at 11:01, Adrien Grassein wrote:
>
> Hey Robert,
>
> Thanks for the update.
>
> Le mar. 23 mars 2021 à 10:10, Robert Foss a écrit :
> >
> > Hey Adrien,
> >
> > Sorry about the slow reply, but I just received the documentation from
> > the vendor. So let's dig in to the HPD
Andrew Jones writes:
> On Tue, Mar 23, 2021 at 09:53:03AM +0100, Vitaly Kuznetsov wrote:
>> hardware_disable_test produces 512 snippets like
>> ...
>> main: [511] waiting semaphore
>> run_test: [511] start vcpus
>> run_test: [511] all threads launched
>> main: [511] waiting 368us
>> main:
On Fri 19-03-21 10:26:33, Oscar Salvador wrote:
> Self stored memmap leads to a sparse memory situation which is unsuitable
> for workloads that requires large contiguous memory chunks, so make this
> an opt-in which needs to be explicitly enabled.
>
> To control this, let memory_hotplug have its
From: Tan Tee Min
Cross timestamping is supported on Integrated Ethernet Controller in
Intel SoC such as EHL and TGL with Always Running Timer.
The hardware cross-timestamp result is made available to
applications through the PTP_SYS_OFFSET_PRECISE ioctl which calls
stmmac_getcrosststamp().
On Mon, 22 Mar 2021 20:58:27 +
Mel Gorman wrote:
> On Mon, Mar 22, 2021 at 08:32:54PM +, Chuck Lever III wrote:
> > >> It is returning some confusing (to me) results. I'd like
> > >> to get these resolved before posting any benchmark
> > >> results.
> > >>
> > >> 1. When it has visited
Le mar. 23 mars 2021 à 11:42, Robert Foss a écrit :
>
> On Tue, 23 Mar 2021 at 11:01, Adrien Grassein
> wrote:
> >
> > Hey Robert,
> >
> > Thanks for the update.
> >
> > Le mar. 23 mars 2021 à 10:10, Robert Foss a écrit :
> > >
> > > Hey Adrien,
> > >
> > > Sorry about the slow reply, but I
On 23.03.21 12:11, Andy Shevchenko wrote:
On Mon, Mar 22, 2021 at 05:02:00PM +0100, David Hildenbrand wrote:
All IORESOURCE_SYSTEM_RAM and IORESOURCE_MEM now properly consider the
whole resource tree, not just the first level. Let's drop the unused
first_lvl / siblings_only logic.
All
On 23.03.21 12:08, Andy Shevchenko wrote:
On Mon, Mar 22, 2021 at 05:01:59PM +0100, David Hildenbrand wrote:
It used to be true that we can have system RAM only on the first level
in the resourc tree. However, this is no longer holds for driver-managed
system RAM (i.e., dax/kmem and
On Sun, Mar 07, 2021 at 12:52:19AM -0800, Jia-Ju Bai wrote:
> When usb_otg_descriptor_alloc() returns NULL to usb_desc, no error
> return code of msg_bind() is assigned.
> To fix this bug, status is assigned with -ENOMEM in this case.
>
> Reported-by: TOTE Robot >
You have 2 '>' on the end of
The "u16 CcxRmState[2];" array field in struct "rtllib_network" has 4
bytes in total while the operations performed on this array through-out
the code base are only 2 bytes.
The "CcxRmState" field is fed only 2 bytes of data using memcpy():
(In rtllib_rx.c:1972)
On Tue, 23 Mar 2021 11:51:04 +0200
Alexandru Ardelean wrote:
> On Sun, Mar 21, 2021 at 7:37 PM Jonathan Cameron
> wrote:
> >
> > On Sat, 20 Mar 2021 17:41:00 +
> > Jonathan Cameron wrote:
> >
> > > On Mon, 15 Mar 2021 09:58:08 +
> > > "Sa, Nuno" wrote:
> > >
> > > > >
On Wed, Jan 06, 2021 at 02:55:40PM +0100, Martin Blumenstingl wrote:
> The legacy PCI interrupt lines need to be enabled using PCIE_APP_IRNEN
> bits 13 (INTA), 14 (INTB), 15 (INTC) and 16 (INTD). The old code however
> was taking (for example) "13" as raw value instead of taking BIT(13).
> Define
On 2021-03-22 18:46, Marc Zyngier wrote:
The new 'no_msi' attribute solves the problem of advertising the lack
of MSI capability for host bridges that know for sure that there will
be no MSI for their end-points.
However, there is a whole class of host bridges that cannot know
whether MSIs will
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:
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
301 - 400 of 1668 matches
Mail list logo
