On Sat, May 18, 2019 at 06:16:28PM +0800, Weitao Hou wrote:
> fix lenght to length
Can you please fix all the instances of this in the tree?
$ git grep lenght | grep -v spelling.txt
Documentation/devicetree/bindings/usb/s3c2410-usb.txt: - reg: address and
lenght of the controller memory mapped
Hi all,
In commit
532b0f7ece4c ("tipc: fix modprobe tipc failed after switch order of device
registration")
Fixes tag
Fixes: 7e27e8d6130c
has these problem(s):
- missing subject
Please do not split Fixes tags over more than one line.
--
Cheers,
Stephen Rothwell
pgp5Wrg2nD4j5.pgp
On Sat, May 18, 2019 at 2:16 PM Ingo Molnar wrote:
>
>
> * tip-bot for Stephane Eranian wrote:
>
> > Commit-ID: 6b89d4c1ae8596a8c9240f169ef108704de373f2
> > Gitweb:
> > https://git.kernel.org/tip/6b89d4c1ae8596a8c9240f169ef108704de373f2
> > Author: Stephane Eranian
> > AuthorDate:
Author: Felipe Gasper
Date: Sat May 18 20:04:40 2019 -0500
net: Add UNIX_DIAG_UID to Netlink UNIX socket diagnostics.
This adds the ability for Netlink to report a socket's UID along with the
other UNIX diagnostic information that is already available. This will
allow diagnostic
Hi Linus,
Please pull some late Kbuild updates.
(The reasons for lateness are;
[1] rebasing to avoid merge conflicts
[2] pick up patches that were not taken care of
by arch maintainers
[3] some (e.g. checker of module name uniqueness)
are good to merge even in the last minutes of MW
)
According to the AD7150 configuration register description, bit 7 assumes
value 1 when the threshold mode is fixed and 0 when it is adaptive,
however, the operation that identifies this mode was considering the
opposite values.
This patch renames the boolean variable to describe it correctly and
Hi Linus,
The following changes since commit ab02888e39212af2d1dddc565cd67192548b9fd8:
Merge tag 'armsoc-defconfig' of
git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc (2019-05-16 09:35:26
-0700)
are available in the git repository at:
Add a of_device_id struct array of_match_table variable and subsequent
call to MODULE_DEVICE_TABLE macro to device tree support.
Co-developed-by: Thiago L. A. Miller
Signed-off-by: Thiago L. A. Miller
Co-developed-by: Osvaldo M. Yasuda
Signed-off-by: Osvaldo M. Yasuda
Signed-off-by: João
Create list of compatible device ids to be matched with those stated in
the device tree.
Signed-off-by: Bárbara Fernandes
Signed-off-by: Wilson Sales
Co-developed by: Wilson Sales
---
drivers/staging/iio/adc/ad7192.c | 12
1 file changed, 12 insertions(+)
diff --git
Create structure of type of_device_id in order to register all devices
the driver is able to manage.
Signed-off-by: Bárbara Fernandes
Signed-off-by: Wilson Sales
Co-developed-by: Wilson Sales
---
drivers/staging/iio/addac/adt7316-spi.c | 13 +
1 file changed, 13 insertions(+)
Accomplish device tree compatibility to driver ADIS16203
by adding of_device_id table and making a subsequent call to
MODULE_DEVICE_TABLE.
Signed-off-by: Thiago Estrela
Signed-off-by: Tiago Napoli
Co-developed-by: Tiago Napoli
Signed-off-by: Pedro Sousa
Co-developed-by: Pedro Sousa
Create macro for capacitance channels in order to remove the repeated
code and improve its readability.
Signed-off-by: Bárbara Fernandes
Signed-off-by: Wilson Sales
Co-developed-by: Wilson Sales
---
drivers/staging/iio/cdc/ad7150.c | 29 -
1 file changed, 12
Create structure of type of_device_id in order to register all devices
the driver is able to manage.
Signed-off-by: Bárbara Fernandes
Signed-off-by: Melissa Wen
Co-developed-by: Melissa Wen
Signed-off-by: Wilson Sales
Co-developed-by: Wilson Sales
---
drivers/staging/iio/cdc/ad7150.c | 10
Changes switches from old text bindings, to YAML bindings, and also
include adi,reference-select property to specify the source for the
reference voltage signal.
Signed-off-by: João Victor Marques de Oliveira
Signed-off-by: Thiago L. A. Miller
Co-developed-by: Thiago L. A. Miller
This series of patches set a struct of_device_id with all the devices this
driver is able to manage and also add a macro to facilitate channel creation for
its two capacitance channels.
Bárbara Fernandes (2):
staging: iio: cdc: ad7150: create of_device_id array
staging: iio: cdc: ad7150:
This patch adds a YAML binding for the Analog Devices AD7780/1 and
AD7170/1 analog-to-digital converters.
Signed-off-by: Renato Lui Geh
---
.../bindings/iio/adc/adi,ad7780.txt | 48 ---
.../bindings/iio/adc/adi,ad7780.yaml | 85 +++
2 files changed, 85
Add a of_device_id struct variable and subsequent call to
MODULE_DEVICE_TABLE macro to support device tree.
Signed-off-by: João Seckler
Signed-off-by: Lucas Oshiro
Co-developed-by: Lucas Oshiro
---
drivers/staging/iio/cdc/ad7746.c | 10 ++
1 file changed, 10 insertions(+)
diff --git
Convert the old device tree documentation to yaml format.
Signed-off-by: Lucas Oshiro
Signed-off-by: Rodrigo Ribeiro
Co-developed-by: Rodrigo Ribeiro
---
Hello,
We've added Stefan Popa as maintainer of the yaml documentation of this driver
because we found through git that he was the author
Add a of_device_id struct and MODULE_DEVICE_TABLE call, in order to add
device-tree support for this driver.
Signed-off-by: Lucas Oshiro
Signed-off-by: Rodrigo Ribeiro
Co-developed-by: Rodrigo Ribeiro
---
drivers/staging/iio/accel/adis16240.c | 6 ++
1 file changed, 6 insertions(+)
diff
On Sat, May 18, 2019 at 04:18:43PM -0400, Theodore Ts'o wrote:
> > What would you prefer to happen in such situations? Commit summaries
> > modified enough to confuse CI tools into *NOT* noticing that those
> > are versions of the same patch? Some kind of metadata telling the
> > same tools
* tip-bot for Stephane Eranian wrote:
> Commit-ID: 6b89d4c1ae8596a8c9240f169ef108704de373f2
> Gitweb:
> https://git.kernel.org/tip/6b89d4c1ae8596a8c9240f169ef108704de373f2
> Author: Stephane Eranian
> AuthorDate: Thu, 9 May 2019 14:45:56 -0700
> Committer: Ingo Molnar
>
Hi Lucas,
On Sat, May 18, 2019 at 6:01 PM Lucas Oshiro wrote:
>
> Add a of_device_id struct and MODULE_DEVICE_TABLE call.
Please provide an explanation as to why you are doing this.
Thanks
On Sat, May 18, 2019 at 2:38 PM Hariprasad Kelam
wrote:
>
> fix below warning reported by coccichec
>
> drivers/staging/media/imx/imx-media-capture.c:617:5-8: Unneeded
> variable: "ret". Return "0" on line 630
>
> Signed-off-by: Hariprasad Kelam
Reviewed-by: Fabio Estevam
Thanks
The RISC-V architecture has a register named the "Supervisor Exception
Program Counter", or "sepc". This abbreviation triggers
checkpatch.pl's misspelling detector, resulting in noise in the
checkpatch output. The risk that this noise could cause more useful
warnings to be missed seems to
Add a of_device_id struct and MODULE_DEVICE_TABLE call.
Signed-off-by: Lucas Oshiro
Signed-off-by: Rodrigo Ribeiro
Co-developed-by: Rodrigo Ribeiro
---
drivers/staging/iio/accel/adis16240.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/staging/iio/accel/adis16240.c
Linus,
Please pull the latest perf-core-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-core-for-linus
# HEAD: 62e1c09418fc16d27720b128275cac61367e2c1b Merge tag
'perf-core-for-mingo-5.2-20190517' of
Hi Marco,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.1 next-20190517]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Add a of_device_id struct variable and subsequent call to
MODULE_DEVICE_TABLE macro to support device tree.
Signed-off-by: João Seckler
Signed-off-by: Anderson Reis
Co-developed-by: Anderson Reis
Signed-off-by: Andre Tadeu de Carvalho
Co-developed-by: Andre Tadeu de Carvalho
---
From: Jason Wang
Date: Fri, 17 May 2019 00:29:48 -0400
> Hi:
>
> This series try to prevent a guest triggerable CPU hogging through
> vhost kthread. This is done by introducing and checking the weight
> after each requrest. The patch has been tested with reproducer of
> vsock and virtio-net.
On Sat, May 18, 2019 at 05:21:42PM +0100, Al Viro wrote:
> IOW, Dan's fix folded into the offending commit. And that kind of
> pattern is not rare; I would argue that appending Dan's patch at
> the end of queue and leaving the crap in between would be a fucking
> bad idea - it would've left a
From: Willem de Bruijn
Date: Sat, 18 May 2019 14:19:07 -0400
> On Sat, May 18, 2019 at 2:09 PM Willem de Bruijn
> wrote:
>>
>> On Sat, May 18, 2019 at 3:34 AM syzbot
>> wrote:
>> >
>> > Hello,
>> >
>> > syzbot found the following crash on:
>> >
>> > HEAD commit:510e2ced ipv6: fix src addr
Hello,
On Saturday, May 18, 2019 7:49:49 PM CEST you wrote:
> On Sat, 18 May 2019, syzbot wrote:
> >
> > syzbot has tested the proposed patch but the reproducer still triggered
> > crash:
> > KASAN: use-after-free Read in usb_driver_release_interface
> >
> > usb 1-1: Loading firmware file
On Sat, May 18, 2019 at 07:38:34AM +0100, Lee Jones wrote:
> "- Acked-by: indicates an agreement by another developer (often a
> maintainer of the relevant code) that the patch is appropriate for
> inclusion into the kernel."
>
> And I, as a developer (and not a Maintainer in this
Fix "warning: regexp escape sequence is not a known regexp operator" on
gawk 5.0.0.
Results found by:
- grepping '\\[^\[\\^$.|?*+()a-z]' on *.awk
- grepping 'awk.*\\[^\[\\^$.|?*+()a-z]'
- running awk --lint -f /dev/null on *.awk
Signed-off-by: Alex Xu (Hello71)
---
Add register bit definitions from documentation to header file and use
them instead of magic constants. No changes to generated binary.
Signed-off-by: Ondrej Zary
---
drivers/scsi/fdomain.c | 144 -
drivers/scsi/fdomain.h | 117
Excerpts from Mikhail Gavrilov's message of May 18, 2019 7:07 am:
> On Sat, 18 May 2019 at 11:44, Mikhail Gavrilov
> wrote:
>> [28616.429757] EXT4-fs error (device nvme0n1p2): ext4_find_extent:908:
>> inode #8: comm jbd2/nvme0n1p2-: pblk 23101439 bad header/extent:
>> invalid extent entries -
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+200d4bb11b23d9293...@syzkaller.appspotmail.com
Tested on:
commit: 43151d6c usb-fuzzer: main usb gadget fuzzer driver
git tree:
On Sat, 18 May 2019, Konstantin Khlebnikov wrote:
> On 18.05.2019 18:17, Thomas Gleixner wrote:
> > On Wed, 15 May 2019, Konstantin Khlebnikov wrote:
> >
> > > Timekeeping watchdog verifies doubtful clocksources using more reliable
> > > candidates. For x86 it likely verifies 'tsc' using 'hpet'.
Harry,
On Sun, 19 May 2019, Harry Pan wrote:
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
> I just want to point out: it is wrong if a problematic watchdog clocksource
On Sat, May 18, 2019 at 2:09 PM Willem de Bruijn
wrote:
>
> On Sat, May 18, 2019 at 3:34 AM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:510e2ced ipv6: fix src addr routing with the exception table
> > git tree: net
> > console output:
These two changes really look like net-next material, and net-next is
closed at the moment.
Please resubmit these when net-next opens back up.
Thank you.
On Sat, May 18, 2019 at 3:34 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:510e2ced ipv6: fix src addr routing with the exception table
> git tree: net
> console output: https://syzkaller.appspot.com/x/log.txt?x=15b7e608a0
> kernel config:
Perform sanity check on the watchdog to validate its interval, avoid
to generate a false alarm that incorrectly marks the main clocksource
as unstable when there comes discrepancy.
Say if there is a discrepancy between the current clocksource and watchdog,
validate the watchdog deviation first,
On 18.05.2019 18:17, Thomas Gleixner wrote:
On Wed, 15 May 2019, Konstantin Khlebnikov wrote:
Timekeeping watchdog verifies doubtful clocksources using more reliable
candidates. For x86 it likely verifies 'tsc' using 'hpet'. But 'hpet'
is far from perfect too. It's better to have second
From: "Jorge E. Moreira"
Date: Thu, 16 May 2019 13:51:07 -0700
> Avoid a race in which static variables in net/vmw_vsock/af_vsock.c are
> accessed (while handling interrupts) before they are initialized.
...
> Fixes: 22b5c0b63f32 ("vsock/virtio: fix kernel panic after device hot-unplug")
> Cc:
On Sat, 18 May 2019, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer still triggered
> crash:
> KASAN: use-after-free Read in usb_driver_release_interface
>
> usb 1-1: Loading firmware file isl3887usb
> usb 1-1: Direct firmware load for isl3887usb failed
Some VPU variants may run at higher clock speeds. They actually need
extra speed to be capable of decoding more complex codecs like HEVC or
bigger image sizes (4K).
Expand variant structure with mod_rate information.
Signed-off-by: Jernej Skrabec
---
drivers/staging/media/sunxi/cedrus/cedrus.c
fix below warning reported by coccichec
drivers/staging/media/imx/imx-media-capture.c:617:5-8: Unneeded
variable: "ret". Return "0" on line 630
Signed-off-by: Hariprasad Kelam
---
drivers/staging/media/imx/imx-media-capture.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
Hello,
syzbot has tested the proposed patch but the reproducer still triggered
crash:
KASAN: use-after-free Read in usb_driver_release_interface
usb 1-1: Loading firmware file isl3887usb
usb 1-1: Direct firmware load for isl3887usb failed with error -2
usb 1-1: Firmware not found.
p54usb
> On May 17, 2019, at 8:48 PM, Felipe Gasper wrote:
>
> Author: Felipe Gasper
> Date: Fri May 17 16:54:40 2019 -0500
>
> net: Add UNIX_DIAG_UID to Netlink UNIX socket diagnostics.
>
> This adds the ability for Netlink to report a socket’s UID along with the
> other UNIX diagnostic
* Arnaldo Carvalho de Melo wrote:
> Em Sat, May 18, 2019 at 10:42:23AM +0200, Ingo Molnar escreveu:
> > Pick up the latest v5.2-to-be kernel ABI headers and synchronize them with
> > tooling:
> >
> > - arch/x86/entry/syscalls/syscall_64.tbl =>
> >
Add a node describing the KEYADC on the A64.
Signed-off-by: Luca Weiss
---
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
b/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
index
On Sat, 18 May 2019, syzbot wrote:
> Hello,
>
> syzbot tried to test the proposed patch but build/boot failed:
One of these times I'll get it right...
Alan Stern
#syz test: https://github.com/google/kasan.git usb-fuzzer
drivers/net/wireless/intersil/p54/p54usb.c | 37
Hi Dmitry,
On Fri, 2019-05-17 at 14:30 -0700, Dmitry Torokhov wrote:
> Hi Sefano,
>
> On Fri, May 17, 2019 at 11:17:40PM +0200, Stefano Manni wrote:
> > Add wakeup support to the maxtouch driver.
> > The device can wake up the system from suspend,
> > mark the IRQ as wakeup capable, so that
On 5/17/19 2:03 AM, xiaolinkui wrote:
> Use struct_size() to keep code sample.
What do you mean by that?
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements
Hi Paolo,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 72cf0b07418a9c8349aa9137194b1ccba6e54a9d
commit: c011d23ba046826ccf8c4a4a6c1d01c9ccaa1403 kvm: fix compilation on aarch64
date: 28 hours
On Sat, May 18, 2019 at 05:21:42PM +0100, Al Viro wrote:
> On Sat, May 18, 2019 at 05:00:39PM +0200, Dmitry Vyukov wrote:
> > On Fri, May 17, 2019 at 4:08 PM Dmitry Vyukov wrote:
> > >
> > > On Fri, May 17, 2019 at 3:48 PM Al Viro wrote:
> > > >
> > > > On Fri, May 17, 2019 at 03:17:02AM -0700,
On Sat, May 18, 2019 at 05:00:39PM +0200, Dmitry Vyukov wrote:
> On Fri, May 17, 2019 at 4:08 PM Dmitry Vyukov wrote:
> >
> > On Fri, May 17, 2019 at 3:48 PM Al Viro wrote:
> > >
> > > On Fri, May 17, 2019 at 03:17:02AM -0700, syzbot wrote:
> > > > This bug is marked as fixed by commit:
> > > >
On 5/17/19 2:26 AM, xiaolinkui wrote:
> Use the new struct_size() helper to keep code simple.
>
This is not the reason why this helper was created.
And if you are going to copy/paste changelog texts, at
least try to understand and compile[1][2] the code
before submitting it.
--
Gustavo
[1]
mmc1 node where wifi module is connected doesn't have properly defined
power supplies so wifi module is never powered up. Fix that by
specifying additional power supplies.
Additionally, this STB may have either Realtek or Broadcom based wifi
module. One based on Broadcom module also needs
On Wed, Apr 24, 2019 at 12:18 AM Vineeth Remanan Pillai
wrote:
>
> From: Peter Zijlstra (Intel)
>
> Instead of only selecting a local task, select a task for all SMT
> siblings for every reschedule on the core (irrespective which logical
> CPU does the reschedule).
>
> NOTE: there is still
On Sat, 18 May 2019, Harry Pan wrote:
> This patch performs a sanity check on the deviation of the clocksource
> watchdog,
Please read Documentation/process/submitting-patches.rst and search for
'This patch'.
> target to reduce false alarm that incorrectly marks current clocksource
> unstable
The SUNXI_WATCHDOG option is required to make the
watchdog available on Allwinner H6.
Enable this option as a module.
Signed-off-by: Clément Péron
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
Allwinner H6 has a similar watchdog as the A64 which is already
a compatible of the A31.
This commit sort the lines and add the H6 compatible.
Signed-off-by: Clément Péron
---
.../devicetree/bindings/watchdog/sunxi-wdt.txt | 10 ++
1 file changed, 6 insertions(+), 4
Allwinner H6 has a watchog node which seems broken
on some boards.
Test has been performed on several boards.
Chen-Yu Tsai boards:
Pine H64 - H6448BA 7782 => OK
OrangePi Lite 2 - H8068BA 61C2 => KO
Martin Ayotte boards:
Pine H64 - H8069BA 6892 => OK
OrangePi 3 - HA047BA 69W2 => KO
OrangePi One
Hi,
Allwinner H6 SoC has two watchdogs.
As we are not sure that both A64 and H6 are stricly identical, I have
introduced the H6 bindings.
After investigation it seems that on some boards the first watchdog doesn't
make it properly reboot. Please see details in the commit log.
I think it's
Allwinner H6 has a r_watchdog similar to A64.
Declare it in the device-tree.
Signed-off-by: Clément Péron
---
arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi
On Wed, 15 May 2019, Konstantin Khlebnikov wrote:
> Timekeeping watchdog verifies doubtful clocksources using more reliable
> candidates. For x86 it likely verifies 'tsc' using 'hpet'. But 'hpet'
> is far from perfect too. It's better to have second opinion if possible.
>
> We're seeing sudden
Dne petek, 17. maj 2019 ob 09:30:48 CEST je Maxime Ripard napisal(a):
> Hi,
>
> On Thu, May 16, 2019 at 06:10:39PM +0200, Jernej Skrabec wrote:
> > mmc1 node where wifi module is connected doesn't have properly defined
> > power supplies so wifi module is never powered up. Fix that by
> >
On Fri, May 17, 2019 at 4:08 PM Dmitry Vyukov wrote:
>
> On Fri, May 17, 2019 at 3:48 PM Al Viro wrote:
> >
> > On Fri, May 17, 2019 at 03:17:02AM -0700, syzbot wrote:
> > > This bug is marked as fixed by commit:
> > > vfs: namespace: error pointer dereference in do_remount()
> > > But I can't
On Fri, May 17, 2019 at 11:36:59PM +0200, Gregory CLEMENT wrote:
> While there was a git repository used for the mvebu subsystem since many
> years, it was not documented. let's add it.
>
> Signed-off-by: Gregory CLEMENT
Reviewed-by: Andrew Lunn
Andrew
This patch performs a sanity check on the deviation of the clocksource watchdog,
target to reduce false alarm that incorrectly marks current clocksource unstable
when there comes discrepancy.
Say if there is a discrepancy between the current clocksource and watchdog,
validate the watchdog
On Thu, May 16, 2019 at 07:44:20PM +0530, srikanth wrote:
> Hello,
>
> On power9 host, performing memory hotunplug from ppc64le guest results in
> kernel oops.
>
> Kernel used : https://github.com/torvalds/linux/tree/v5.1 built using
> ppc64le_defconfig for host and ppc64le_guest_defconfig for
On Fri, May 17, 2019 at 02:51:17PM -0400, Joe Lawrence wrote:
> Miroslav reported that the livepatch self-tests were failing,
> specifically a case in which the consistency model ensures that we do
> not patch a current executing function, "TEST: busy target module".
>
> Recent renovations to
Hi,
On Sat, May 18, 2019 at 12:51 AM Heiko Stuebner wrote:
>
> Hi,
>
> Am Samstag, 18. Mai 2019, 01:57:47 CEST schrieb Doug Anderson:
> > Elaine and Caesar,
> >
> > On Tue, May 7, 2019 at 4:50 PM Douglas Anderson
> > wrote:
> > >
> > > While testing a newer kernel on rk3288-based Chromebooks I
Em Sat, May 18, 2019 at 10:42:23AM +0200, Ingo Molnar escreveu:
> Pick up the latest v5.2-to-be kernel ABI headers and synchronize them with
> tooling:
>
> - arch/x86/entry/syscalls/syscall_64.tbl =>
> tools/perf/arch/x86/entry/syscalls/syscall_64.tbl # new syscalls
> -
fix lengh to length
Signed-off-by: Weitao Hou
---
drivers/sfi/sfi_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/sfi/sfi_core.c b/drivers/sfi/sfi_core.c
index a5136901dd8a..b184c541cfd0 100644
--- a/drivers/sfi/sfi_core.c
+++ b/drivers/sfi/sfi_core.c
@@
fix lenght to length
Signed-off-by: Weitao Hou
---
sound/soc/qcom/qdsp6/q6asm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/qcom/qdsp6/q6asm.c b/sound/soc/qcom/qdsp6/q6asm.c
index 4f85cb19a309..e8141a33a55e 100644
--- a/sound/soc/qcom/qdsp6/q6asm.c
+++
On Tue, Apr 30, 2019 at 08:32:20PM +, Ghannam, Yazen wrote:
> From: Yazen Ghannam
>
> The number of MCA banks is provided per logical CPU. Historically, this
> number has been the same across all CPUs, but this is not an
> architectural guarantee. Future AMD systems may have MCA bank counts
On Thu, 2019-05-09 at 12:59:38 UTC, Christophe Leroy wrote:
> flush_hash_pages() runs with data translation off, so current
> task_struct has to be accesssed using physical address.
>
> Reported-by: Erhard F.
> Fixes: f7354ccac844 ("powerpc/32: Remove CURRENT_THREAD_INFO and rename
> TI_CPU")
>
On Wed, 2019-05-15 at 09:07:50 UTC, "Tobin C. Harding" wrote:
> kfree() after kobject_put(). Who ever wrote this was on crack.
>
> Fixes: 7e8039795a80 ("powerpc/cacheinfo: Fix kobject memleak")
> Signed-off-by: Tobin C. Harding
Applied to powerpc fixes, thanks.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Linus,
Please pull some powerpc fixes for 5.2:
The following changes since commit b970afcfcabd63cd3832e95db096439c177c3592:
Merge tag 'powerpc-5.2-1' of
ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/powerpc/linux (2019-05-10
05:29:27
Linus,
here are some I2C core API additions which are kind of simple but
enhance error checking for users a lot, especially by returning errno
now. There are wrappers to still support the old API but it will be
removed once all users are converted.
This comes a bit later in a seperate pull
On Wed, 15 May 2019 13:41:17 -0500
Eddie James wrote:
> The DPS310 supports measurement of pressure, so support that in the
> driver. Use background measurement like the temperature sensing and
> default to lowest precision and lowest measurement rate.
>
> Signed-off-by: Eddie James
One really
On Wed, 15 May 2019 13:41:16 -0500
Eddie James wrote:
> From: Christopher Bostic
>
> Add a manufacturer's suggested workaround to deal with early revisions
> of chip that don't indicate correct temperature. Readings can be in the
> ~60C range when they should be in the ~20's.
>
>
On Wed, 15 May 2019 13:41:15 -0500
Eddie James wrote:
> From: Joel Stanley
>
> The DPS310 is a temperature and pressure sensor. It can be accessed over
> i2c and SPI.
>
> Signed-off-by: Eddie James
Hi Eddie,
One spacing issue in the Kconfig file otherwise I think this looks good.
However,
On Thu, 16 May 2019 16:10:47 +0800
Chun-Hung Wu wrote:
> Move auxadc platform_driver_register() from module_init
> to subsys_initcall because auxadc user drivers
> are all moudle drivers, need to gurantee
> auxadc driver ready before module_init.
>
Is it not possible to make them use deferred
On Thu, 16 May 2019 16:10:46 +0800
Chun-Hung Wu wrote:
> Move suspend/resume to late_suspend and
> early_resume to gurantee users can use auxadc
guarantee
> driver at suspend/resume stage.
No problem with the patch content, but we need a reason why they may
want to do so?
Thanks,
Jonathan
>
On Thu, 16 May 2019 16:10:44 +0800
Chun-Hung Wu wrote:
> Add compatible node for mt6765 auxadc
>
> Signed-off-by: Chun-Hung Wu
Applied, but in numeric order. There was also another clashing patch
that caused some fuzz.
thanks,
Jonathan
> ---
>
On Thu, 16 May 2019 16:10:45 +0800
Chun-Hung Wu wrote:
Hi,
I changed the title to just say we were adding support to
the existing driver.
Applied to the togreg branch of iio.git and pushed out as
testing for the autobuilders to play with it.
Thanks,
Jonathan
> 1. Add calibrated sample
On Thu, 16 May 2019 17:32:08 +0300
Beniamin Bia wrote:
> Support for register access was added for spi devices.
>
> Signed-off-by: Beniamin Bia
Looks fine. For my reference please add
Acked-by: Jonathan Cameron
> ---
> drivers/iio/adc/ad7606.c | 25 +
> 1 file
On Sat, 18 May 2019 11:07:49 +0100
Jonathan Cameron wrote:
> On Thu, 16 May 2019 17:32:05 +0300
> Beniamin Bia wrote:
>
> > Because this driver will support multiple configurations for software,
> > the software configuration was made generic.
> >
> > Signed-off-by: Beniamin Bia
> Applied
On Sat, 18 May 2019 11:04:49 +0100
Jonathan Cameron wrote:
> On Thu, 16 May 2019 17:32:04 +0300
> Beniamin Bia wrote:
>
> > The device dependent options which are going to be different for devices
> > which will be supported in the future by this driver,
> > were moved in chip info for a more
On Thu, 16 May 2019 17:32:07 +0300
Beniamin Bia wrote:
> Support for ad7616 running in software was added. In order
> to activate the software mode, HW_RNGSEL pins must be pulled low.
> Oversampling and input ranges are now configured in corresponding
> registers. Ad7616 has multiple scale
On Thu, 16 May 2019 17:32:06 +0300
Beniamin Bia wrote:
> In order to support AD7616 software mode, the spi register access must be
> added and the calculation of registers address must be generic.
> The length of address and bit which specifies the read/write operation is
> different for every
fix lenght to length
Signed-off-by: Weitao Hou
---
kernel/sysctl.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/kernel/sysctl.c b/kernel/sysctl.c
index 943c89178e3d..0736a1d580df 100644
--- a/kernel/sysctl.c
+++ b/kernel/sysctl.c
@@ -187,17 +187,17 @@
On Thu, 16 May 2019 17:32:05 +0300
Beniamin Bia wrote:
> Because this driver will support multiple configurations for software,
> the software configuration was made generic.
>
> Signed-off-by: Beniamin Bia
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders
On Thu, 16 May 2019 17:32:04 +0300
Beniamin Bia wrote:
> The device dependent options which are going to be different for devices
> which will be supported in the future by this driver,
> were moved in chip info for a more generic driver. This patch allows
> supporting more devices by the
On Sat, 18 May 2019 at 06:25, Jayachandran Chandrasekharan Nair
wrote:
>
> On Mon, May 06, 2019 at 07:10:40PM +0100, Will Deacon wrote:
> > On Mon, May 06, 2019 at 06:13:12AM +, Jayachandran Chandrasekharan Nair
> > wrote:
> > > Perhaps someone from ARM can chime in here how the cas/yield
On Fri, 17 May 2019 16:38:56 -0700
Gwendal Grignou wrote:
> Add a IIO driver that reports the angle between the lid and the base for
> ChromeOS convertible device.
>
> Tested on eve with ToT EC firmware.
> Check driver is loaded and lid angle is correct.
>
> Signed-off-by: Gwendal Grignou
Hi
1 - 100 of 212 matches
Mail list logo
