Specify regulators and enable the node. The firmware uses the 8
bit version of the host capability message, so specify this quirk.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dts | 11 +++
1 file changed, 11 insertions(+)
diff --git
Setup the TLMM UFS_RESET to make the UFS core reset the UFS memory
device during initialization.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dts
Hi Balakrishna,
Sorry for the late reply. I was on vacation for the past few days.
The chipset we use is QCA6174A-3 and rjliao has already confirmed that
IBS won't work without RAM fw downloaded.
Please ignore this change.
Thanks,
Claire
On Fri, Oct 11, 2019 at 3:21 PM Balakrishna Godavarthi
On 17-10-19, 13:35, Sudeep Holla wrote:
> This driver have been used and tested for year now and the extensive
> debug/log messages in the driver are not really required anymore.
> Get rid of those unnecessary log messages.
>
> Signed-off-by: Sudeep Holla
> ---
>
Specify the firmware-name for the adsp, cdsp and mpss and enable the
nodes.
Signed-off-by: Bjorn Andersson
---
.../boot/dts/qcom/sdm850-lenovo-yoga-c630.dts | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dts
On Thu, Oct 17, 2019 at 11:26:54PM +0200, Rafael J. Wysocki wrote:
> On Thu, Oct 17, 2019 at 9:36 PM Rafael J. Wysocki wrote:
> >
> > On Thu, Oct 17, 2019 at 6:35 PM Sudeep Holla wrote:
> > >
> > > dev_pm_qos_remove_request ends calling {max,min}_freq_req QoS notifiers
> > > which schedule
On Wed, Oct 16, 2019 at 12:27 AM Hans de Goede wrote:
> On 10/15/19 7:39 AM, John Stultz wrote:
> > On Thu, Oct 3, 2019 at 1:51 PM Hans de Goede wrote:
> >> On 03-10-2019 22:37, John Stultz wrote:
> >>> Fair point. I'm sort of taking a larger patchset and trying to break
> >>> it up into more
nbrand
>> Acked-by: Michal Hocko
>> Signed-off-by: Anshuman Khandual
>> ---
>> This is based on https://patchwork.kernel.org/patch/11190213/
>
> Hi Anshuman,
>
> I'm having trouble finding a tree that this applies cleanly too,
> which one did you use? (late
Hi all,
Today's linux-next merge of the char-misc tree got a conflict in:
drivers/android/binder.c
between commit:
45d02f79b539 ("binder: Don't modify VMA bounds in ->mmap handler")
from the char-misc.current tree and commit:
990be7476485 ("binder: Use common definition of SZ_1K")
If 'idle=nomwait' is specified or process matching what's in
processor_idle_dmi_table, we should't use MWAIT at bootup stage before
cpuidle driver loaded, even if it's preferred by default on Intel.
Add a check so that HALT instruction is used in those cases.
Signed-off-by: Zhenzhong Duan
Cc:
On 17-10-19, 13:35, Sudeep Holla wrote:
> Fix the following checkpatch checks/warnings:
>
> CHECK: Unnecessary parentheses around the code
> CHECK: Alignment should match open parenthesis
> CHECK: Prefer kernel type 'u32' over 'uint32_t'
> WARNING: Missing a blank line after declarations
>
>
On Thu, Oct 17, 2019 at 11:08 PM Christoph Hellwig wrote:
>
> The RISC-V ISA only supports flushing the instruction cache for the
> local CPU core. Currently we always offload the remote TLB flushing to
> the SBI, which then issues an IPI under the hoods. But with M-mode
> we do not have an SBI
On Fri, Oct 18, 2019 at 11:17:40AM +0530, Viresh Kumar wrote:
> On 17-10-19, 13:35, Sudeep Holla wrote:
> > diff --git a/drivers/cpufreq/arm_big_little.c
> > b/drivers/cpufreq/vexpress-spc-cpufreq.c
> > similarity index 90%
> > rename from drivers/cpufreq/arm_big_little.c
> > rename to
On Thu, Oct 17, 2019 at 11:08 PM Christoph Hellwig wrote:
>
> When running in M-mode we can't use the SBI to set the timer, and
> don't have access to the time CSR as that usually is emulated by
> M-mode. Instead provide code that directly accesses the MMIO for
> the timer.
>
> Signed-off-by:
On Thu, Oct 17, 2019 at 09:36:30PM +0200, Rafael J. Wysocki wrote:
> On Thu, Oct 17, 2019 at 6:35 PM Sudeep Holla wrote:
> >
> > dev_pm_qos_remove_request ends calling {max,min}_freq_req QoS notifiers
> > which schedule policy update work. It may end up racing with the freeing
> > the policy and
On Thu, Oct 17, 2019 at 09:38:18PM -0700, Paul Walmsley wrote:
> On Fri, 18 Oct 2019, Luc Van Oostenryck wrote:
>
> > On Thu, Oct 17, 2019 at 05:49:24PM -0700, Paul Walmsley wrote:
> > > sparse complains loudly when string literals associated with
> > > preprocessor directives are split into
On 17-10-19, 13:35, Sudeep Holla wrote:
> diff --git a/drivers/cpufreq/arm_big_little.c
> b/drivers/cpufreq/vexpress-spc-cpufreq.c
> similarity index 90%
> rename from drivers/cpufreq/arm_big_little.c
> rename to drivers/cpufreq/vexpress-spc-cpufreq.c
> index 7fe52fcddcf1..b7e1aa000c80 100644
>
On Thu, Oct 17, 2019 at 7:57 PM Huacai Chen wrote:
>
> In do_hres(), we currently use whether the return value of __arch_get_
> hw_counter() is negtive to indicate fallback, but this is not a good
> idea. Because:
>
> 1, ARM64 returns ULL_MAX but MIPS returns 0 when clock_mode is invalid;
> 2,
Hello,
syzbot found the following crash on:
HEAD commit:283ea345 coccinelle: api/devm_platform_ioremap_resource: r..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=122f199b60
kernel config: https://syzkaller.appspot.com/x/.config?x=f0a8b0a0736a2ac1
On Thu, Oct 17, 2019 at 11:08 PM Christoph Hellwig wrote:
>
> When we get booted we want a clear slate without any leaks from previous
> supervisors or the firmware. Flush the instruction cache and then clear
> all registers to known good values. This is really important for the
> upcoming
On Thu, Oct 17, 2019 at 11:08 PM Christoph Hellwig wrote:
>
> The kernel runs in M-mode without using page tables, and thus can't run
> bare metal without help from additional firmware.
>
> Most of the patch is just stubbing out code not needed without page
> tables, but there is an interesting
On 17-10-19, 18:34, Rafael J. Wysocki wrote:
> [BTW, Viresh, it looks like cpufreq_set_policy() should still ensure
> that the new min is less than the new max, because the QoS doesn't do
> that.]
The ->verify() callback does that for us I believe.
--
viresh
On 17-10-19, 16:16, Rafael J. Wysocki wrote:
> [Also note that the current code in device PM QoS uses MIN and MAX
> here in the same way. :-)]
Stupid me, enough embarrassment for the day :(
--
viresh
On 17-10-19, 17:35, Sudeep Holla wrote:
> dev_pm_qos_remove_request ends calling {max,min}_freq_req QoS notifiers
> which schedule policy update work.
I don't think that's correct. We remove the notifiers first and then
only remove the requests. Though it is possible due to the other bug
we are
On Thu, Oct 17, 2019 at 11:07 PM Christoph Hellwig wrote:
>
> If we always compile the get_break_insn_length inline function we can
> remove the ifdefs and let dead code elimination take care of the warn
> branch that is now unreadable because the report_bug stub always
> returns
On 10/16/19 5:26 PM, Vincent Guittot wrote:
> On Wed, 16 Oct 2019 at 09:21, Parth Shah wrote:
>>
>>
>>
>> On 9/19/19 1:03 PM, Vincent Guittot wrote:
>>
>> [...]
>>
>>> Signed-off-by: Vincent Guittot
>>> ---
>>> kernel/sched/fair.c | 585
>>>
On Thu, Oct 17, 2019 at 11:08 PM Christoph Hellwig wrote:
>
> RISC-V has the concept of a cpu level interrupt controller. The
> interface for it is split between a standardized part that is exposed
> as bits in the mstatus/sstatus register and the mie/mip/sie/sip
> CRS. But the bit to actually
From: Yonglong Liu
Currently, the num_msi_left means the vector numbers of NIC,
but if the PF supported RoCE, it contains the vector numbers
of NIC and RoCE(Not expected).
This may cause interrupts lost in some case, because of the
NIC module used the vector resources which belongs to RoCE.
On Thu, Oct 17, 2019 at 11:08 PM Christoph Hellwig wrote:
>
> The numerical levels for External/Timer/Software interrupts differ
> between S-mode and M-mode.
>
> Signed-off-by: Christoph Hellwig
> ---
> arch/riscv/kernel/irq.c | 12 +---
> 1 file changed, 9 insertions(+), 3 deletions(-)
Hi Jeffrey,
On 10/2/2019 6:46 AM, Jeffrey Hugo wrote:
The GPUCC manages the clocks for the Adreno GPU found on MSM8998.
Signed-off-by: Jeffrey Hugo
---
drivers/clk/qcom/Kconfig | 9 +
drivers/clk/qcom/Makefile| 1 +
drivers/clk/qcom/gpucc-msm8998.c | 346
On 17-10-19, 17:04, John Hubbard wrote:
> The following build warning occurred on powerpc 64-bit builds:
>
> drivers/cpufreq/powernv-cpufreq.c: In function 'init_chip_info':
> drivers/cpufreq/powernv-cpufreq.c:1070:1: warning: the frame size of 1040
> bytes is larger than 1024 bytes
Add devicetree binding for the Bosch BMA400 3-axes ultra-low power
accelerometer sensor.
Signed-off-by: Dan Robertson
---
.../devicetree/bindings/iio/accel/bma400.yaml | 39 +++
1 file changed, 39 insertions(+)
create mode 100644
Add a IIO driver for the Bosch BMA400 3-axes ultra-low power accelerometer.
The driver supports reading from the acceleration and temperature
registers. The driver also supports reading and configuring the output data
rate, oversampling ratio, and scale.
Signed-off-by: Dan Robertson
---
On Thu, Oct 17, 2019 at 11:08 PM Christoph Hellwig wrote:
>
> From: Damien Le Moal
>
> When in M-Mode, we can use the mhartid CSR to get the ID of the running
> HART. Doing so, direct M-Mode boot without firmware is possible.
>
> Signed-off-by: Damien Le Moal
> Signed-off-by: Christoph Hellwig
This patchset adds a IIO driver for the Bosch BMA400 3-axes ultra low-power
accelerometer. The initial implementation of the driver adds read support for
the acceleration and temperature data registers. The driver also has support
for reading and writing to the output data rate, oversampling
On Thu, Oct 17, 2019 at 09:38:18PM -0700, Paul Walmsley wrote:
> On Fri, 18 Oct 2019, Luc Van Oostenryck wrote:
>
> > On Thu, Oct 17, 2019 at 05:49:24PM -0700, Paul Walmsley wrote:
> > > sparse complains loudly when string literals associated with
> > > preprocessor directives are split into
On Thu, Oct 17, 2019 at 11:07 PM Christoph Hellwig wrote:
>
> From: Damien Le Moal
>
> When running in M-mode we can't use SBI based drivers. Add a new
> CONFIG_RISCV_SBI that drivers that do SBI calls can depend on
> instead.
>
> Signed-off-by: Damien Le Moal
> Signed-off-by: Christoph
On Thu, Oct 17, 2019 at 11:08 PM Christoph Hellwig wrote:
>
> Move the sbi poweroff to a separate function and file that is only
> compiled if CONFIG_SBI is set. Provide a new default fallback
> power off that just sits in a wfi loop to save some power.
>
> Signed-off-by: Christoph Hellwig
>
On Thu, Oct 17, 2019 at 09:39:29PM -0700, Paul Walmsley wrote:
> On Fri, 18 Oct 2019, Luc Van Oostenryck wrote:
> > On Thu, Oct 17, 2019 at 05:49:25PM -0700, Paul Walmsley wrote:
> > > ifeq ($(CONFIG_CMODEL_MEDANY),y)
> > > KBUILD_CFLAGS += -mcmodel=medany
> > > + CHECKFLAGS +=
Andrew brought up a reasonable concern with the CMA heap
enumeration in the previous patch set, and I had a few other
minor cleanups to add, so here is yet another pass at the
dma-buf heaps patchset Andrew and I have been working on which
tries to destage a fair chunk of ION functionality.
The
Add generic helper dmabuf ops for dma heaps, so we can reduce
the amount of duplicative code for the exported dmabufs.
This code is an evolution of the Android ION implementation, so
thanks to its original authors and maintainters:
Rebecca Schultz Zavin, Colin Cross, Laura Abbott, and others!
Since the introduction of '5451781dadf8 ("regulator: core: Only count
load for enabled consumers")' in v5.0, the requested load of a regulator
consumer is only accounted for when said consumer is voted enabled.
So there's no need to vote for load ever time the regulator is
enabled or disabled.
Split and rename qca_power_setup() in order to simplify each code path
and to clarify that it is unrelated to qca_power_off() and
qca_power_setup().
Signed-off-by: Bjorn Andersson
---
drivers/bluetooth/hci_qca.c | 61 ++---
1 file changed, 36 insertions(+), 25
This adds a CMA heap, which allows userspace to allocate
a dma-buf of contiguous memory out of a CMA region.
This code is an evolution of the Android ION implementation, so
thanks to its original author and maintainters:
Benjamin Gaignard, Laura Abbott, and others!
NOTE: This patch only adds
Clean up the regulator usage in hci_qca and in particular don't
regulator_set_voltage() for fixed voltages. It cleans up the driver, but more
important it makes bluetooth work on my Lenovo Yoga C630, where the regulator
for vddch0 is defined with a voltage range that doesn't overlap the values in
With the regulator_set_load() and regulator_set_voltage() out of the
enable/disable code paths the code can now use the standard
regulator bulk enable/disable API.
By cloning num_vregs into struct qca_power there's no need to lug around
a reference to the struct qca_vreg_data, which further
This patch adds system heap to the dma-buf heaps framework.
This allows applications to get a page-allocator backed dma-buf
for non-contiguous memory.
This code is an evolution of the Android ION implementation, so
thanks to its original authors and maintainters:
Rebecca Schultz Zavin, Colin
Add very trivial allocation and import test for dma-heaps,
utilizing the vgem driver as a test importer.
A good chunk of this code taken from:
tools/testing/selftests/android/ion/ionmap_test.c
Originally by Laura Abbott
Cc: Benjamin Gaignard
Cc: Sumit Semwal
Cc: Liam Mark
Cc: Pratik
Devices with specific voltage requirements should not request voltage
from the driver, but instead rely on the system configuration to define
appropriate voltages for each rail.
This ensures that PMIC and board variations are accounted for, something
that the 0.1V range in the hci_qca driver
On Thu, Oct 17, 2019 at 11:07 PM Christoph Hellwig wrote:
>
> Remove various not required ifdefs and externs.
>
> Signed-off-by: Christoph Hellwig
> ---
> arch/riscv/include/asm/bug.h | 16 +++-
> 1 file changed, 3 insertions(+), 13 deletions(-)
>
> diff --git
On Thu, Oct 17, 2019 at 11:08 PM Christoph Hellwig wrote:
>
> There is no SBI when we run in M-mode, so fail the compile for any code
> trying to use SBI calls.
>
> Signed-off-by: Christoph Hellwig
> ---
> arch/riscv/include/asm/sbi.h | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
On Fri, 18 Oct 2019, Anup Patel wrote:
> It will be really cool to have this series for Linux-5.4-rcX.
It's way too big to go in via the -rc series. I'm hoping to have it ready
to go for v5.5-rc1.
- Paul
On Thu, Oct 17, 2019 at 05:49:26PM -0700, Paul Walmsley wrote:
> sparse identifies these missing prototypes when building arch/riscv:
>
> arch/riscv/kernel/cpu.c:149:29: warning: symbol 'cpuinfo_op' was not
> declared. Should it be static?
> arch/riscv/kernel/irq.c:27:29: warning: symbol
Everyone:
This series contains patches to fix a couple of regressions in G920
wheel support by hid-logitech-hidpp driver. Without the patches the
wheel remains stuck in autocentering mode ("resisting" any attempt to
trun) as well as missing support for any FF action.
Thanks,
Andrey Smirnov
On Fri, Oct 18, 2019 at 11:18:48AM +0800, Kefeng Wang wrote:
> For kernel logging macro, pr_warning is completely removed and
> replaced by pr_warn, using pr_warn in tools lib bpf for symmetry
> to kernel logging macro, then we could drop pr_warning in the
> whole linux code.
>
> Cc: Alexei
Hi Jens,
On Thu, 17 Oct 2019 18:56:39 -0600 Jens Axboe wrote:
>
> I'll fix these warnings up, guessing it's 32-bit?
Thanks. Yeah 32 bit.
--
Cheers,
Stephen Rothwell
pgpAAZTHyaXeP.pgp
Description: OpenPGP digital signature
G920 device only advertises REPORT_ID_HIDPP_LONG and
REPORT_ID_HIDPP_VERY_LONG in its HID report descriptor, so querying
for REPORT_ID_HIDPP_SHORT with optional=false will always fail and
prevent G920 to be recognized as a valid HID++ device.
To fix this and improve some other aspects, modify
Original version of g920_get_config() contained two kind of actions:
1. Device specific communication to query/set some parameters
which requires active communication channel with the device,
or, put in other way, for the call to be sandwiched between
In collapse_file(), after locking the page, it is necessary to recheck
that the page is up-to-date, clean, and pointing to the proper mapping.
If any check fails, abort the collapse.
Fixes: 99cb0dbd47a1 ("mm,thp: add read-only THP support for (non-shmem) FS")
Cc: Kirill A. Shutemov
Cc: Johannes
On Thu, Oct 17, 2019 at 11:35:48AM -0700, Florian Fainelli wrote:
>
>
> On 10/13/2019 11:15 PM, Oleksij Rempel wrote:
> > Provide basic support for Atheros AR9331 build-in switch. So far it
> > works as port multiplexer without any hardware offloading support.
>
> I glanced through the
On Fri, 18 Oct 2019, Luc Van Oostenryck wrote:
> On Thu, Oct 17, 2019 at 05:49:25PM -0700, Paul Walmsley wrote:
> > Static analysis tools such as sparse don't set the RISC-V C model
> > preprocessor directives such as "__riscv_cmodel_medany", set by the C
> > compilers. This causes the static
A gentle ping on adding DT binding for Hammer (2/2).
On Sat, Oct 5, 2019 at 6:14 PM Ikjoon Jang wrote:
>
> Add a device tree match table.
>
> Change-Id: Iaee68311073cefa4b99cde182bd37d1a67c94ea6
> Signed-off-by: Ikjoon Jang
> ---
> drivers/hid/hid-google-hammer.c | 10 ++
> 1 file
On 17-10-19, 21:55, John Hubbard wrote:
> The following build warning occurred on powerpc 64-bit builds:
>
> drivers/cpufreq/powernv-cpufreq.c: In function 'init_chip_info':
> drivers/cpufreq/powernv-cpufreq.c:1070:1: warning: the frame size of 1040
> bytes is larger than 1024 bytes
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Yoshinori Sato
Cc: Rich Felker
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
drivers/sh/intc/core.c | 4
On Sun, Sep 01, 2019 at 11:06:05AM +0300, Kalle Valo wrote:
> Guenter Roeck writes:
>
> > Hi,
> >
> > On Sat, Aug 03, 2019 at 08:31:01PM -0400, Hui Peng wrote:
> >> The `ar_usb` field of `ath10k_usb_pipe_usb_pipe` objects
> >> are initialized to point to the containing `ath10k_usb` object
> >>
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Daniel Lezcano
Acked-by: Daniel Lezcano
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Robert Richter
Acked-by: Robert Richter
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: "James E.J. Bottomley"
Cc: "Martin K. Petersen"
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
On 17-10-19, 21:34, John Hubbard wrote:
> On 10/17/19 9:27 PM, Viresh Kumar wrote:
> > On 17-10-19, 17:04, John Hubbard wrote:
> >> The following build warning occurred on powerpc 64-bit builds:
> >>
> >> drivers/cpufreq/powernv-cpufreq.c: In function 'init_chip_info':
> >>
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Paul Walmsley
Cc: Palmer Dabbelt
Cc: Albert Ou
Acked-by: Palmer Dabbelt
Reviewed-by: Sergey Senozhatsky
Signed-off-by:
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: "David S. Miller"
Cc: Andrew Morton
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
The "wep" buffer is not initialized. To avoid memory disclosures,
the fix initializes it, as peer functions like rtllib_ccmp_set_key
do.
Signed-off-by: Kangjie Lu
---
drivers/staging/rtl8192e/rtllib_crypt_wep.c | 1 +
1 file changed, 1 insertion(+)
diff --git
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Stephen Rothwell
Cc: Yoshinori Sato
Cc: Rich Felker
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
For kernel logging macro, pr_warning is completely removed and
replaced by pr_warn, using pr_warn in tools lib bpf for symmetry
to kernel logging macro, then we could drop pr_warning in the
whole linux code.
Cc: Alexei Starovoitov
Cc: Daniel Borkmann
Cc: Martin KaFai Lau
Cc: Song Liu
Cc:
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: "Rafael J. Wysocki"
Cc: Len Brown
Cc: James Morse
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Tony Luck
Cc: Fenghua Yu
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
arch/ia64/kernel/setup.c | 2 +-
1
On Thu, Oct 17, 2019 at 11:07 PM Christoph Hellwig wrote:
>
> Many of the privileged CSRs exist in a supervisor and machine version
> that are used very similarly. Provide a new X-naming layer so that
> we don't have to ifdef everywhere for M-mode Linux support.
>
> Contains contributions from
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Philipp Reisner
Cc: Lars Ellenberg
Cc: Jens Axboe
Cc: drbd-...@lists.linbit.com
Reviewed-by: Sergey Senozhatsky
On Fri, Oct 18, 2019 at 6:19 AM Paul Walmsley wrote:
>
> Resolve most warnings from the 'sparse' static analysis tool for the
> arch/riscv codebase. This makes life easier for us as maintainers,
> and makes it easier for developers to use static analysis tools on
> their own changes.
>
> This
For kernel logging macro, pr_warning is completely removed and
replaced by pr_warn, using pr_warn in tools lib api for symmetry
to kernel logging macro, then we could drop pr_warning in the
whole linux code.
Changing __pr_warning to __pr_warn to be consistent.
Cc: Arnaldo Carvalho de Melo
On Thu, Oct 17, 2019 at 05:49:25PM -0700, Paul Walmsley wrote:
> Static analysis tools such as sparse don't set the RISC-V C model
> preprocessor directives such as "__riscv_cmodel_medany", set by the C
> compilers. This causes the static analyzers to evaluate different
> preprocessor paths than
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Steven Rostedt
Cc: Ingo Molnar
Acked-by: Steven Rostedt (VMware)
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Rob Herring
Cc: Frank Rowand
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
drivers/of/fdt.c | 20
For now, all pr_warning are removed, delete pr_warning check in
checkpatch.
Cc: Andy Whitcroft
Cc: Joe Perches
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
scripts/checkpatch.pl | 9 -
1 file changed, 9 deletions(-)
diff --git a/scripts/checkpatch.pl
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Benjamin Herrenschmidt
Cc: linuxppc-...@lists.ozlabs.org
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Andrew Morton
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
lib/cpu_rmap.c | 2 +-
1 file changed, 1
"f->fmt.sdr.reserved" is uninitialized. As other peer drivers
like msi2500 and airspy do, the fix initializes it to avoid
memory disclosures.
Signed-off-by: Kangjie Lu
---
drivers/media/platform/rcar_drif.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/platform/rcar_drif.c
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Herbert Xu
Cc: "David S. Miller"
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
drivers/crypto/n2_core.c |
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Corentin Chary
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: Andy Shevchenko
Reviewed-by: Sergey Senozhatsky
Signed-off-by:
With all pr_warning are removed, saftely drop pr_warning definition.
Cc: Petr Mladek
Cc: Sergey Senozhatsky
Cc: Steven Rostedt
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
include/linux/printk.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Will Deacon
Cc: Mark Rutland
Cc: Catalin Marinas
Acked-by: Will Deacon
Reviewed-by: Sergey Senozhatsky
Signed-off-by:
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Corentin Chary
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: Andy Shevchenko
Reviewed-by: Sergey Senozhatsky
Signed-off-by:
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Christoph Hellwig
Cc: Marek Szyprowski
Cc: Robin Murphy
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Bartlomiej Zolnierkiewicz
Cc: linux-fb...@vger.kernel.org
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
For kernel logging macro, pr_warning is completely removed and
replaced by pr_warn, using pr_warn in tools perf for symmetry
to kernel logging macro, then we could drop pr_warning in the
whole linux code.
Cc: Arnaldo Carvalho de Melo
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Mark Rutland
Cc:
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: David Howells
Cc: linux-...@lists.infradead.org
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Krzysztof Kozlowski
Cc: Sangbeom Kim
Cc: Sylwester Nawrocki
Cc: Jaroslav Kysela
Cc: Takashi Iwai
Reviewed-by: Sergey
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Karsten Keil
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
drivers/isdn/hardware/mISDN/avmfritz.c | 16
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: "David S. Miller"
Reviewed-by: Sergey Senozhatsky
Signed-off-by: Kefeng Wang
---
drivers/ide/tx4938ide.c | 2 +-
As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of
pr_warning"), removing pr_warning so all logging messages use a
consistent _warn style. Let's do it.
Cc: Corentin Chary
Cc: Darren Hart
Cc: Andy Shevchenko
Cc: Andy Shevchenko
Reviewed-by: Sergey Senozhatsky
Signed-off-by:
1 - 100 of 1059 matches
Mail list logo
