On Fri, 29 Mar 2019 17:06:46 +0100, Jerome Brunet wrote:
> Add a new compatible string and additional clock ids for audio clock
> controller of the g12a SoC family.
>
> Signed-off-by: Jerome Brunet
> ---
> .../bindings/clock/amlogic,axg-audio-clkc.txt | 3 ++-
>
On Sat, 30 Mar 2019 06:50:37 +0100, Sergio Paracuellos wrote:
> Add bindings to describe Mediatek MT7621 PCIe PHY.
>
> Signed-off-by: Sergio Paracuellos
> ---
> .../bindings/phy/mediatek,mt7621-pci-phy.txt | 28 +++
> 1 file changed, 28 insertions(+)
> create mode 100644
>
On Wed, Mar 27, 2019 at 01:14:47PM +0800, Peter Shih wrote:
> From: Pi-Hsun Shih
>
> Add a DT binding documentation for ChromeOS EC driver over rpmsg.
>
> Signed-off-by: Pi-Hsun Shih
> ---
> Changes from v6:
> - No change.
>
> Changes from v5:
> - New patch.
> ---
>
On Fri, 29 Mar 2019 15:13:22 +1300, Chris Packham wrote:
> Add an example showing how to use the addr-gpios property to deal with a
> system with limited IO space.
>
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Chris Packham
> ---
> Changes in v2:
> - None
>
>
On Mon, 1 Apr 2019 14:43:04 +0800, Elaine Zhang wrote:
> Add a new compatible for thermal founding on PX30 SoCs.
>
> Signed-off-by: Elaine Zhang
> ---
> Documentation/devicetree/bindings/thermal/rockchip-thermal.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring
On Tue, 2 Apr 2019 16:18:41 +0300, Beniamin Bia wrote:
> Document support for AD7616 Analog to Digital Converter.
>
> Signed-off-by: Beniamin Bia
> ---
> Documentation/devicetree/bindings/iio/adc/adi,ad7606.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring
On Mon, 1 Apr 2019 12:13:35 +0200, =?UTF-8?q?Guido=20G=C3=BCnther?= wrote:
> Add support for the MIXEL DPHY IP as found on NXP's i.MX8MQ SoCs.
>
> Signed-off-by: Guido Günther
> Reviewed-by: Sam Ravnborg
> ---
> .../bindings/phy/mixel,mipi-dsi-phy.txt | 29 +++
> 1 file
On Mon, 1 Apr 2019 10:17:18 -0700, Douglas Anderson wrote:
> From: Sean Paul
>
> This patch adds a new subnode to simple-panel allowing us to override
> the typical timing expressed in the panel's display_timing.
>
> Changes in v2:
> - Split out the binding into a new patch (Rob)
> -
On Wed, 3 Apr 2019 10:16:25 +0200, =?UTF-8?q?Yannick=20Fertr=C3=A9?= wrote:
> This patch adds documentation of a new property phy-dsi-supply to the
> STM32 DSI controller.
>
> Signed-off-by: Yannick Fertré
> ---
> Documentation/devicetree/bindings/display/st,stm32-ltdc.txt | 3 +++
> 1 file
On Thu, Apr 04, 2019 at 01:50:20AM +, Chris Packham wrote:
> Hi,
>
> I'm implementing support for some modular Linux based systems using
> device tree overlays. The code is working but it seems a little more
> fiddly that than it should be so I'm wondering if I'm doing it right.
>
> An
On Thu, Apr 04, 2019 at 07:09:23AM +0200, Niklas Cassel wrote:
> From: Sricharan R
>
> The kryo cpufreq driver reads the nvmem cell and uses that data to
> populate the opps. There are other qcom cpufreq socs like krait which
> does similar thing. Except for the interpretation of the read data,
On Thu, Apr 04, 2019 at 07:09:28AM +0200, Niklas Cassel wrote:
> Add DT bindings to describe the CPR HW found on certain Qualcomm SoCs.
>
> Co-developed-by: Jorge Ramirez-Ortiz
> Signed-off-by: Jorge Ramirez-Ortiz
> Signed-off-by: Niklas Cassel
> ---
> .../bindings/power/avs/qcom,cpr.txt
On Wed, 3 Apr 2019 17:38:20 -0700, Paul Walmsley wrote:
> Add preprocessor macros for the important PRCI output clocks
> that are needed by both the FU540 PRCI driver and DT data.
> Details are available in the FU540 manual in Chapter 7 of
>
>
On Wed, 3 Apr 2019 10:20:25 +, Jacky Bai wrote:
> From: Bai Ping
>
> Add the binding doc for nxp system counter timer module.
>
> Signed-off-by: Bai Ping
> ---
> change v1->v2
> - remove the blank line at EOF
> change v2->v3
> - update the binding example based on the driver change
> ---
On Wed, Apr 03, 2019 at 04:52:44PM +0200, Flavio Suligoi wrote:
> Some RTC devices have a battery-low automatic detection circuit.
> The battery-low event is usually reported with:
>
> - a bit change in a RTC status register
> - a hw signaling (generally using an interrupt generation), changing
>
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This automated bisection report was sent to you on the basis *
* that you may be involved with the breaking commit it has *
* found. No manual investigation has been done to verify it, *
* and the root cause of the
Running 'make dt_binding_check' fails for
Documentation/devicetree/bindings/arm/cpus.yaml. This is due to tabs
used for indentation:
$ dt-doc-validate Documentation/devicetree/bindings/arm/cpus.yaml
Documentation/devicetree/bindings/arm/cpus.yaml: while scanning a plain scalar
in "", line
On Sat, Apr 6, 2019 at 1:26 AM Paul Walmsley wrote:
>
> Running 'make dt_binding_check' fails for
> Documentation/devicetree/bindings/arm/cpus.yaml. This is due to tabs
> used for indentation:
You're the 3rd fix. :( We're waiting on arm-soc folks to apply it.
Rob
On Wed, Apr 03, 2019 at 11:00:59AM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Add the DT binding document for the battery charger module of max77650.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> .../power/supply/max77650-charger.txt | 27 +++
>
When the buffer write failed, 'end_buffer_write_sync' and
'end_buffer_async_write' will clear the uptodate flag. But the
data in the buffer maybe newer than disk. In some case, this
will lead data corruption.
For example: ext4 flush metadata to disk failed, it will clear
the uptodate flag. when a
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev.2019.04.04a
head: 6f1d86fa5cd6dc95118310607a6bc6f3c6e3092a
commit: 07366215c9b454bb6ee5648e18ee91a5c4fd0ea6 [35/54] drivers/gpu/drm/amd:
Dynamically allocate kfd_processes_srcu
config: mips-allyesconfig (attached
hns3_client_stop() should be called after unregister_netdev(),
otherwise the ongoing reset task may start the client just after it.
Fixes: a6d818e31d08 ("net: hns3: Add vport alive state checking support")
Signed-off-by: Huazhong Tan
Signed-off-by: Peng Li
---
It is unnecessary to deal with the new coming reset if
it is lower than the ongoing one.
Signed-off-by: Huazhong Tan
Signed-off-by: Peng Li
---
drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c | 4
1 file changed, 4 insertions(+)
diff --git
If the reset has been done successfully, the ongoing reset timer
is unnecessary.
Signed-off-by: Huazhong Tan
Signed-off-by: Peng Li
---
drivers/net/ethernet/hisilicon/hns3/hns3pf/hclge_main.c | 1 +
1 file changed, 1 insertion(+)
diff --git
If a vport is not alive, it is unnecessary to notify it to reset
before PF asserting a reset. So before inform vport to reset,
we need to check its alive state firstly.
Fixes: aa5c4f175be6 ("net: hns3: add reset handling for VF when doing PF reset")
Signed-off-by: Huazhong Tan
Signed-off-by:
On Sat, Apr 6, 2019 at 12:08 AM Arnaud Pouliquen
wrote:
>
>
>
> On 4/5/19 4:03 PM, xiang xiao wrote:
> > On Fri, Apr 5, 2019 at 8:33 PM Arnaud Pouliquen
> > wrote:
> >>
> >>
> >>
> >> On 4/5/19 12:12 PM, xiang xiao wrote:
> >>> On Fri, Apr 5, 2019 at 12:14 AM Arnaud Pouliquen
> >>> wrote:
>
On 4/6/2019 8:41 AM, YueHaibing wrote:
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/staging/rtlwifi/rtl8822be/hw.c: In function
'rtl8822be_update_hal_rate_mask':
drivers/staging/rtlwifi/rtl8822be/hw.c:2144:5: warning:
variable 'curtxbw_40mhz' set but not used
* Alexander Potapenko wrote:
> On Fri, Apr 5, 2019 at 11:39 AM Ingo Molnar wrote:
> >
> >
> > * Alexander Potapenko wrote:
> >
> > > 1. Use memory clobber in bitops that touch arbitrary memory
> > >
> > > Certain bit operations that read/write bits take a base pointer and an
> > >
On 4/6/2019 8:37 AM, YueHaibing wrote:
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/staging/comedi/drivers/dyna_pci10xx.c: In function
'dyna_pci10xx_insn_write_ao':
drivers/staging/comedi/drivers/dyna_pci10xx.c:109:21: warning:
variable 'range' set but not used
changes interupts --> interrupts to fix warning reported by checkpatch
tool
Signed-off-by: Hariprasad Kelam
---
Changes in v2:
- Make the Subject more clear by including changed file path.
---
drivers/staging/comedi/drivers/dt2811.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On 4/6/2019 8:41 AM, YueHaibing wrote:
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/staging/rtl8192e/rtl8192e/rtl_pci.c: In function 'rtl92e_check_adapter':
drivers/staging/rtl8192e/rtl8192e/rtl_pci.c:36:6: warning:
variable 'VenderID' set but not used [-Wunused-but-set-variable]
On 4/6/2019 8:42 AM, YueHaibing wrote:
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/staging/rtlwifi/base.c: In function 'rtl_tx_agg_stop':
drivers/staging/rtlwifi/base.c:1733:23: warning:
variable 'tid_data' set but not used [-Wunused-but-set-variable]
On 4/6/2019 1:53 PM, Hariprasad Kelam wrote:
changes interupts --> interrupts to fix warning reported by checkpatch
tool
Signed-off-by: Hariprasad Kelam
Reviewed-by: Mukesh Ojha
Cheers,
-Mukesh
---
Changes in v2:
- Make the Subject more clear by including changed file path.
---
On Fri 2019-04-05 13:15:34, Guenter Roeck wrote:
> On Thu, Apr 04, 2019 at 11:10:08AM -0600, Nick Crews wrote:
> > The EC is in charge of controlling the keyboard backlight on
> > the Wilco platform. We expose a standard LED class device at
> > /sys/class/leds/platform::kbd_backlight. This driver
Commit-ID: 5b77e95dd7790ff6c8fbf1cd8d0104ebed818a03
Gitweb: https://git.kernel.org/tip/5b77e95dd7790ff6c8fbf1cd8d0104ebed818a03
Author: Alexander Potapenko
AuthorDate: Tue, 2 Apr 2019 13:28:13 +0200
Committer: Ingo Molnar
CommitDate: Sat, 6 Apr 2019 09:52:02 +0200
x86/asm: Use
On Fri, Apr 05, 2019 at 09:25:27AM -0700, Matthew Wilcox wrote:
> I don't think that's a good idea; we should only document functions we
> want other people to use.
Yap.
> I could also go for renaming this to __size_ab_plus_c.
Let's just leave it short as it is now - the comment should be good
Hi,
On 05-04-19 16:15, Sasha Levin wrote:
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.0.6, v4.19.33, v4.14.110, v4.9.167,
Hi,
On 06-04-19 01:01, Luís Ferreira wrote:
Hi,
Basically we need to come up with a convention to (optionally) indicate
the sensors location with a udev attribute set by:
/lib/udev/hwdb.d/60-sensor.hwdb
So should we start adding `ACCEL_LOCATION=display` and
`ACCEL_LOCATION=keyboard`
Changed passing argument as "0 to NULL" which resolves below sparse warning
arch/x86/kvm/x86.c:3096:61: warning: Using plain integer as NULL pointer
Signed-off-by: Hariprasad Kelam
---
arch/x86/kvm/x86.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/x86.c
Hi!
> >I have not yet gone through the series in great detail.
> >
> >This will change the userland ABI, right? Now, I understand that old ABI is
> >bad, but
> >will it break someone's code?
>
> It will not break anyone since the generic support for composing
> LED names is used only if struct
On 06/04/2019 09:23, Hariprasad Kelam wrote:
changes interupts --> interrupts to fix warning reported by checkpatch
tool
Signed-off-by: Hariprasad Kelam
---
Changes in v2:
- Make the Subject more clear by including changed file path.
---
drivers/staging/comedi/drivers/dt2811.c | 2 +-
1
Hi!
> The patch set introduces also a set of predefined LED_FUNCTION
> names to be used in DT bindings. This along with the removal
> of devicename section from LED naming pattern will help to keep
> LED sysfs interface more uniform and not varying depending on
> underlaying hardware driving the
On 05/04/19 6:58 PM, Roger Quadros wrote:
> AM5 and DRA7 SoC families have different set of modules
> in them so the SoC sepecific dtsi files need to be separated.
>
> e.g. Some of the major differences between AM576 and DRA76
>
> DRA76x AM576x
>
> USB3 x
> USB4
On 06/04/2019 04:07, YueHaibing wrote:
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/staging/comedi/drivers/dyna_pci10xx.c: In function
'dyna_pci10xx_insn_write_ao':
drivers/staging/comedi/drivers/dyna_pci10xx.c:109:21: warning:
variable 'range' set but not used
changed passing function argument "0 to NULL" to fix below sparse
warning
kernel/pid_namespace.c:55:76: warning: Using plain integer as NULL
pointer
did changes to avoid checkpatch error "prefer a maximum 75 chars per
line"
Signed-off-by: Hariprasad Kelam
---
kernel/pid_namespace.c | 3 ++-
1
This patch adds a device id for the new static replicator compatible
string; it changes the driver name from "coresight-replicator" to
"coresight-static-replicator" as well.
Signed-off-by: Leo Yan
---
drivers/hwtracing/coresight/coresight-replicator.c | 3 ++-
1 file changed, 2 insertions(+), 1
CoreSight uses below bindings for replicator:
Static replicator, aka. non-configurable replicator:
"arm,coresight-replicator";
Dynamic replicator, aka. configurable replicator:
"arm,coresight-dynamic-replicator", "arm,primecell";
The compatible string "arm,coresight-replicator" is
Since CoreSight hardware topology can use a 'hidden' funnel in the
trace data path, this kind funnel doesn't have register for accessing
and is used by default from hardware design perspective. Below is an
example for related hardware topology:
+--+ +--+
| cpu0 |->| ETM |-\
Following the same fashion with replicator DT binding, this patch is to
unify the DT binding for funnel to support static and dynamic modes;
finally we get the funnel DT binding as below:
Before patch:
Static funnel, aka. non-configurable funnel:
Not supported;
Dynamic funnel, aka.
Since before there have no platforms use static funnel in mainline
kernel (though maybe some in-house SoC has used it but didn't upstream
for mainline kernel yet so we don't be aware for it), when enable
CoreSight DT binding for hikey960, we found the SoC uses the static
funnel in the link path
Hi Rob, Suzuki,
On Sat, Apr 06, 2019 at 07:21:44PM +0800, Leo Yan wrote:
> Following the same fashion with replicator DT binding, this patch is to
> unify the DT binding for funnel to support static and dynamic modes;
> finally we get the funnel DT binding as below:
>
> Before patch:
>
>
On 06/04/2019 11.32, Borislav Petkov wrote:
> On Fri, Apr 05, 2019 at 09:25:27AM -0700, Matthew Wilcox wrote:
>> I don't think that's a good idea; we should only document functions we
>> want other people to use.
>
> Yap.
Exactly, not kernel-doc'ing was a deliberate choice.
>> I could also go
Hello Linus,
Here are a few fixes for 5.1, please pull.
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git
Problem:
When a kernel module is compiled as a separate module, some important
information about the kernel module is available via .modinfo section of
the module. In contrast, when the kernel module is compiled into the
kernel, that information is not available.
Information about built-in
This patch makes some improvement in how IOCTLs behave when the device is
disabled or under reset.
The new code checks, at the start of every IOCTL, if the device is
disabled or in reset. If so, it prints an appropriate kernel message and
returns -EBUSY to user-space.
In addition, the code
This patch fixes a bug in the implementation of the function that removes
the device.
The bug can happen when the device is removed but not the driver itself
(e.g. remove by the OS due to PCI freeze in Power architecture).
In that case, there maybe open users that are calling IOCTLs while the
Greetings My Dear,
I sent this mail praying it will found you in a good condition of
health, since I myself are in a very critical health condition in
which I sleep every night without knowing if I may be alive to see
the next day. I am Mrs. Monika John Carlsen from Denmark wife of late
Mr
During hard-reset, contexts are closed as part of the tear-down process.
After a context is closed, the driver cleans up the page tables of that
context in the device's DRAM. This action is both dangerous and
unnecessary.
It is unnecessary, because the device is going through a hard-reset, which
On 06/04/2019 01:07:13-0500, Rob Herring wrote:
> On Wed, Apr 03, 2019 at 04:52:44PM +0200, Flavio Suligoi wrote:
> > Some RTC devices have a battery-low automatic detection circuit.
> > The battery-low event is usually reported with:
> >
> > - a bit change in a RTC status register
> > - a hw
On 15/02/2019 11:13:59+0800, Xuefeng Wang wrote:
> When setting rtc alarm (RTC_WKALM_SET), the tm_year is not checked if it
> is in suiteable range. Use INT_MAX - 1900 to check it.
>
> UBSAN: Undefined behaviour in drivers/rtc/rtc-lib.c:119:30
> signed integer overflow:
> 2147483647 + 1900 cannot
Remove duplicate header which is included twice.
Signed-off-by: Souptick Joarder
Acked-by: Mike Rapoport
---
v2: Added Acked-by tag.
arch/arm/mm/mmu.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mm/mmu.c b/arch/arm/mm/mmu.c
index f3ce341..a64a3c5 100644
--- a/arch/arm/mm/mmu.c
Changes passing function argument 0 to NULL to avoid below sparse
warning
CHECK drivers/watchdog//machzwd.c
drivers/watchdog//machzwd.c:321:25: warning: Using plain integer as NULL
pointer
Signed-off-by: Hariprasad Kelam
---
drivers/watchdog/machzwd.c | 2 +-
1 file changed, 1 insertion(+),
Removed duplicate headers which are included twice.
Signed-off-by: Souptick Joarder
---
tools/perf/util/data.c | 1 -
tools/perf/util/get_current_dir_name.c | 1 -
tools/perf/util/stat-display.c | 1 -
3 files changed, 3 deletions(-)
diff --git a/tools/perf/util/data.c
On Fri, Apr 5, 2019 at 11:38 PM kernel test robot wrote:
>
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> WIP.x86/stackguards
>
> commit 8b275b3754465d502d393f8ae8dd355b7067e73f
>
On Sat, Apr 6, 2019 at 6:54 AM Andy Lutomirski wrote:
>
> On Fri, Apr 5, 2019 at 11:38 PM kernel test robot wrote:
> >
> > Greetings,
> >
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> >
unsubscribe linux-kernel
Hi Pavel,
On 4/6/19 11:53 AM, Pavel Machek wrote:
Hi!
The patch set introduces also a set of predefined LED_FUNCTION
names to be used in DT bindings. This along with the removal
of devicename section from LED naming pattern will help to keep
LED sysfs interface more uniform and not varying
On Thu, Apr 04, 2019 at 07:32:00PM +0200, gre...@linuxfoundation.org wrote:
On Thu, Apr 04, 2019 at 04:16:57PM +, Slavomir Kaslev wrote:
On Thu, 2019-04-04 at 10:45 +0200, Greg Kroah-Hartman wrote:
> 5.0-stable review patch. If anyone has any objections, please let me
> know.
>
>
On Fri, Apr 5, 2019 at 9:19 AM Tycho Andersen wrote:
>
> If the kernel oopses in an interrupt, nothing re-enables interrupts:
You probably should also set irq_count back to -1, too, if you really
want this thing to fully survive being called from an IRQ.
From: YueHaibing
When building CONFIG_DEBUG_FS is not set
gcc warn this:
drivers/spi/spi-bcm2835aux.c: In function bcm2835aux_spi_probe:
drivers/spi/spi-bcm2835aux.c:591:2: error: too many arguments to function
bcm2835aux_debugfs_create
bcm2835aux_debugfs_create(bs, dev_name(>dev));
On Wed, Apr 03, 2019 at 09:27:28PM +0300, Jarkko Sakkinen wrote:
On Wed, Apr 03, 2019 at 09:18:27PM +0300, Jarkko Sakkinen wrote:
On Tue, Apr 02, 2019 at 03:33:16PM -0400, Sasha Levin wrote:
> This patch adds support for a software-only implementation of a TPM
> running in TEE.
>
> There is
This patch fixes pin assign of cts and rts signal of UART3.
Currently GPIO3_C2 and C3 pins are assigned but TRM says that
GPIO3_C0 and C1 are correct.
Refer:
RK3399 TRM v1.4 - Table 19-1 UART Interface Description
Signed-off-by: Katsuhiro Suzuki
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi
On 2019/4/6 4:27, Jann Horn wrote:
> On Fri, Apr 5, 2019 at 10:02 PM Aubrey Li wrote:
>> AVX-512 components use could cause core turbo frequency drop. So
>> it's useful to expose AVX-512 usage elapsed time as a heuristic hint
>> for the user space job scheduler to cluster the AVX-512 using tasks
Hey Wolfram,
On Wed, Apr 03, 2019 at 10:47:56PM +0200, Wolfram Sang wrote:
> On Mon, Apr 01, 2019 at 01:14:37PM +0300, laurentiu.tu...@nxp.com wrote:
> > From: Laurentiu Tudor
> >
> > Make sure to free the i2c adapter on the error exit path.
> >
> > Signed-off-by: Laurentiu Tudor
> >
On Sat, Apr 06, 2019 at 05:48:47PM +0200, Uwe Kleine-König wrote:
> Hey Wolfram,
>
> On Wed, Apr 03, 2019 at 10:47:56PM +0200, Wolfram Sang wrote:
> > On Mon, Apr 01, 2019 at 01:14:37PM +0300, laurentiu.tu...@nxp.com wrote:
> > > From: Laurentiu Tudor
> > >
> > > Make sure to free the i2c
Add Pincfgs to enable the i.MX6's OTG feature for UDOO
Signed-off-by: Markus Kueffner
---
arch/arm/boot/dts/imx6qdl-udoo.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/imx6qdl-udoo.dtsi
b/arch/arm/boot/dts/imx6qdl-udoo.dtsi
index 776bfc7..42954ee
On Sat, 6 Apr 2019, Andrea Parri wrote:
> > > I'd have:
> > >
> > > *x = 1; /* A */
> > > smp_mb__before_atomic();
> > > r0 = xchg_relaxed(x, 2); /* B (read or write part) */
> > >
> > > => (A ->barrier B)
> >
> > Perhaps so. It wasn't clear initially how these should be treated, so
>
While implementing kprobes on PA-RISC (without kretprobes) compilation
fails when CONFIG_KPROBE_EVENTS is enabled:
kernel/trace/trace_kprobe.o: in function `trace_kprobe_create':
kernel/trace/trace_kprobe.c:666: undefined reference to `kprobe_on_func_entry'
kernel/trace/trace_kprobe.o: in
Hello, Kindly Please confirm is you.
Regard,
Rufus
On Tue, Mar 26, 2019 at 12:20 PM Kirill Smelkov wrote:
>
> Commit 9c225f2655 (vfs: atomic f_pos accesses as per POSIX) added locking for
> file.f_pos access and in particular made concurrent read and write not
> possible
> [...]
Ok, I have applied this patch - but this patch only - as a
Sven Schnelle wrote:
While implementing kprobes on PA-RISC (without kretprobes) compilation
fails when CONFIG_KPROBE_EVENTS is enabled:
Thanks for working on that! Is there a specific reason kretprobes is not
being enabled on parisc?
kernel/trace/trace_kprobe.o: in function
Hi,
i have been experiencing issues writing to NOR-Flash SPI Memories
from two RK3399-based platforms: gru-kevin and sapphire board.
For kevin, this resulted in a bricked device because that memory
is the only boot device.
Fortunately an external programmer is available.
In order to isolate
Hi Naveen,
On Sat, Apr 06, 2019 at 10:52:47PM +0530, Naveen N. Rao wrote:
> Sven Schnelle wrote:
> > While implementing kprobes on PA-RISC (without kretprobes) compilation
> > fails when CONFIG_KPROBE_EVENTS is enabled:
>
> Thanks for working on that! Is there a specific reason kretprobes is not
The pull request you sent on Sat, 6 Apr 2019 14:06:53 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/abelloni/linux.git
> tags/rtc-5.1-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/be76865df56f22f29ab20e671143761d78ed09c8
Thank you!
--
Deet-doot-dot, I
The commit 665ac7e92757 ("acpi/hmat: Register processor domain to its
memory") introduced some memory leaks below due to it fails to release
the heap memory in an error path, and then the stack __initdata memory
which reference them get freed during boot renders those heap memory as
leaks.
My Greeting, May Almighty God Bless You, Did you receive the letter i
sent to you. Please answer me.
Best Regard,
Miss Maureen Magoko.
This macro adds some debug code to check that the augment tree
is maintained correctly, meaning that every node contains valid
subtree_max_size value.
By default this option is set to 0 and not active. It requires
recompilation of the kernel to activate it. Set to 1, compile
the kernel.
This macro adds some debug code to check that vmap allocations
are happened in ascending order.
By default this option is set to 0 and not active. It requires
recompilation of the kernel to activate it. Set to 1, compile
the kernel.
Signed-off-by: Uladzislau Rezki (Sony)
Reviewed-by: Roman
Currently an allocation of the new vmap area is done over busy
list iteration(complexity O(n)) until a suitable hole is found
between two busy areas. Therefore each new allocation causes
the list being grown. Due to over fragmented list and different
permissive parameters an allocation can take a
Hello.
This is the v4.
Objective
-
Please have a look for the description at: https://lkml.org/lkml/2018/10/19/786
But let me also summarize it a bit here as well. The current implementation has
O(N)
complexity. Requests with different permissive parameters can lead to long
allocation
On 4/6/2019 6:43 PM, Souptick Joarder wrote:
Remove duplicate header which is included twice.
Signed-off-by: Souptick Joarder
Acked-by: Mike Rapoport
---
v2: Added Acked-by tag.
arch/arm/mm/mmu.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/arm/mm/mmu.c b/arch/arm/mm/mmu.c
On 4/6/2019 6:44 PM, Hariprasad Kelam wrote:
Changes passing function argument 0 to NULL to avoid below sparse
warning
CHECK drivers/watchdog//machzwd.c
drivers/watchdog//machzwd.c:321:25: warning: Using plain integer as NULL
pointer
Signed-off-by: Hariprasad Kelam
Reviewed-by: Mukesh
On 4/6/2019 7:06 PM, Souptick Joarder wrote:
Removed duplicate headers which are included twice.
Signed-off-by: Souptick Joarder
Reviewed-by: Mukesh Ojha
Cheers,
-Mukesh
---
tools/perf/util/data.c | 1 -
tools/perf/util/get_current_dir_name.c | 1 -
On 4/6/2019 8:44 PM, Yue Haibing wrote:
From: YueHaibing
When building CONFIG_DEBUG_FS is not set
gcc warn this:
drivers/spi/spi-bcm2835aux.c: In function bcm2835aux_spi_probe:
drivers/spi/spi-bcm2835aux.c:591:2: error: too many arguments to function
bcm2835aux_debugfs_create
On Fri, Apr 5, 2019 at 8:52 PM Evan Green wrote:
> On Fri, Apr 5, 2019 at 12:28 AM Rajneesh Bhardwaj
> wrote:
> > On Mon, Apr 01, 2019 at 11:05:04AM -0700, Evan Green wrote:
> > This register is a 32 bit register untill ICL generation and a recent patch
> > from Rajat fixed the overflow
On 4/6/2019 4:18 PM, Hariprasad Kelam wrote:
changed passing function argument "0 to NULL" to fix below sparse
warning
kernel/pid_namespace.c:55:76: warning: Using plain integer as NULL
pointer
did changes to avoid checkpatch error "prefer a maximum 75 chars per
line"
Signed-off-by:
On 4/6/2019 3:06 PM, Hariprasad Kelam wrote:
Changed passing argument as "0 to NULL" which resolves below sparse warning
arch/x86/kvm/x86.c:3096:61: warning: Using plain integer as NULL pointer
Signed-off-by: Hariprasad Kelam
Reviewed-by: Mukesh Ojha
Cheers,
-Mukesh
---
On 4/6/19 6:14 AM, Hariprasad Kelam wrote:
Changes passing function argument 0 to NULL to avoid below sparse
warning
CHECK drivers/watchdog//machzwd.c
drivers/watchdog//machzwd.c:321:25: warning: Using plain integer as NULL
pointer
Signed-off-by: Hariprasad Kelam
[reluctantly]
On Fri, Apr 05, 2019 at 12:16:39PM +0200, Florian Weimer wrote:
> * Peter Zijlstra:
>
> > On Wed, Apr 03, 2019 at 11:08:09PM +0300, Alexey Dobriyan wrote:
> >> Currently there is no easy way to get the number of CPUs on the system.
>
> The size of the affinity mask is only related to the number
1 - 100 of 132 matches
Mail list logo
