The keyboard and trackpad on recent MacBook's (since 8,1) and
MacBookPro's (13,* and 14,*) are attached to an SPI controller instead
of USB, as previously. The higher level protocol is not publicly
documented and hence has been reverse engineered. As a consequence there
are still a number of
This changeset adds a driver for the SPI keyboard and trackpad on recent
MacBook's and MacBook Pro's. The driver has seen a fair amount of use
over the last 2 years (basically anybody running linux on these
machines), with only relatively small changes in the last year or so.
For those interested,
commit d6abe6df706c (drm/bridge: sil_sii8620: do not have a dependency
of RC_CORE) changed the driver to select both RC_CORE and INPUT.
However, this causes problems with other drivers, in particular an input
driver that depends on MFD_INTEL_LPSS_PCI (to be added in a separate
commit):
On Fri, Apr 5, 2019 at 8:11 AM Thomas Gleixner wrote:
>
> From: Andy Lutomirski
>
> The IRQ stack lives in percpu space, so an IRQ handler that overflows it
> will overwrite other data structures.
>
> Use vmap() to remap the IRQ stack so that it will have the usual guard
> pages that
On 4/5/2019 6:44 PM, David Laight wrote:
From: Sai Prakash Ranjan
diff --git a/drivers/hwtracing/stm/core.c b/drivers/hwtracing/stm/core.c
index 93ce3aa740a9..21a5838f6e67 100644
--- a/drivers/hwtracing/stm/core.c
+++ b/drivers/hwtracing/stm/core.c
@@ -168,7 +168,7 @@ static int
Providing a range for usleep_range() allows the hrtimer subsystem to
coalesce timers - the delay is runtime configurable so a factor 2
is taken to provide the range.
Signed-off-by: Nicholas Mc Guire
---
Problem located with an experimental coccinelle script
Providing a range for usleep_range() allows the hrtimer subsystem to
coalesce timers - as this delay has no upper limit anyway (interrupts
or context switch is possible) it should not hurt to extend this
from 2 to 2-4 milliseconds.
Signed-off-by: Nicholas Mc Guire
---
Problem located with an
Provide a stub for within_module() when CONFIG_MODULES is not set. This
is needed to build CONFIG_GCOV_KERNEL.
Fixes: 8c3d220cb6b5 ("gcov: clang support")
Suggested-by: Matthew Wilcox
Reported-by: Randy Dunlap
Reported-by: kbuild test robot
Link: https://marc.info/?l=linux-mm=155384681109231=2
Hi Kees, Nick,
On Sat, Apr 6, 2019 at 1:52 AM Nick Desaulniers wrote:
>
> On Fri, Apr 5, 2019 at 9:11 AM Kees Cook wrote:
> >
> > On Fri, Apr 5, 2019 at 3:17 AM Masahiro Yamada
> > wrote:
> > > I want to propose alternative solution.
> > > Please check the attached patches.
>
> ```
> My plan
On Thu, Mar 28, 2019 at 10:56:35PM +0800, Liu Song wrote:
> From: Liu Song
>
> At the beginning, nblocks has been assigned. There is no need
> to repeat the assignment in the while loop, and remove it.
>
> Signed-off-by: Liu Song
> Reviewed-by: Jan Kara
Thanks, applied.
Thanks Andy! I just posted v14, which addresses all the comments you mentioned
below for v13.
Regards,
Liming
> -Original Message-
> From: Andy Shevchenko
> Sent: Friday, April 5, 2019 11:44 AM
> To: Liming Sun
> Cc: David Woods ; Andy Shevchenko ;
> Darren Hart ; Vadim
> Pasternak
This commit adds the TmFifo platform driver for Mellanox BlueField
Soc. TmFifo is a shared FIFO which enables external host machine
to exchange data with the SoC via USB or PCIe. The driver is based
on virtio framework and has console and network access enabled.
Reviewed-by: Vadim Pasternak
> On Mon, Apr 01, 2019 at 07:47:14PM -0700, Life is hard, and then you die
> wrote:
> >
> > On Thu, Mar 28, 2019 at 12:29:52PM +0100, Greg Kroah-Hartman wrote:
> > > On Thu, Mar 28, 2019 at 03:27:55AM -0700, Life is hard, and then you die
> > > wrote:
> > > >
> > > > On Thu, Mar 28, 2019 at
The commit 665ac7e92757 ("acpi/hmat: Register processor domain to its
memory") introduced an uninitialized "struct memory_target" that could
cause an incorrect branching.
drivers/acpi/hmat/hmat.c:385:6: warning: variable 'target' is used
uninitialized whenever 'if' condition is false
This reverts
commit 420b82f84294 ("spi: rockchip: set min/max speed")
commit 74b7efa82b11 ("spi: rockchip: precompute rx sample delay")
The former breaks bursts of writes of 48 bytes or more.
Both patches touch the same part of the file and it is not trivial to
only revert the first. Reverting
On Wed, Apr 3, 2019 at 7:03 PM Zhaoyang Huang wrote:
>
> From: Zhaoyang Huang
>
> In previous implementation, the number of refault pages is used
> for judging the refault period of each page, which is not precised.
> We introduce the timestamp into the workingset's entry to measure
> the file
Hi,
please, forget my previous mail about
eff0275e5253604429aedc42b008c5fcaa6cc597
spi: rockchip: simplify use_dma logic
i messed up with commit IDs, sorry.
The first offending commit is one later than that:
commit 420b82f842941a32adf309ca1b193adfc77616b0
Date: Wed Oct 31 11:57:07 2018 +0100
On Tue, Apr 2, 2019 at 3:42 AM Patrick Bellasi wrote:
>
> Utilization clamping allows to clamp the CPU's utilization within a
> [util_min, util_max] range, depending on the set of RUNNABLE tasks on
> that CPU. Each task references two "clamp buckets" defining its minimum
> and maximum
On Thu, 20 Dec 2018, Rob Herring wrote:
> On Fri, Dec 14, 2018 at 09:21:54PM -0800, Paul Walmsley wrote:
> > Add initial board data for the SiFive HiFive Unleashed A00.
> >
> > Currently the data populated in this DT file describes the board
> > DRAM configuration and the external clock sources
On Fri, Apr 05, 2019 at 05:50:10PM -0500, Alex Elder wrote:
> On 4/5/19 3:53 PM, Dan Carpenter wrote:
> > On Fri, Apr 05, 2019 at 03:00:46PM -0500, Madhumitha Prabakaran
> > wrote:
> >> Fix spinlock_t definition without comment.
> >>
> >> Signed-off-by: Madhumitha Prabakaran
>
> Madhumitha, the
The commit 510ded33e075 ("slab: implement slab_root_caches list")
changes the name of the list node within "struct kmem_cache" from
"list" to "root_caches_node", but leaks_show() still use the "list"
which causes a crash when reading /proc/slab_allocators.
BUG: unable to handle kernel NULL
On Fri, Apr 05, 2019 at 11:53:04PM +0300, Dan Carpenter wrote:
> On Fri, Apr 05, 2019 at 03:00:46PM -0500, Madhumitha Prabakaran wrote:
> > Fix spinlock_t definition without comment.
> >
> > Signed-off-by: Madhumitha Prabakaran
> > ---
> > drivers/staging/greybus/connection.h | 2 +-
> > 1 file
Added a blank line after declarations.
Signed-off-by: Gabriela Bittencourt
---
I'm adding STAGING SUBSYSTEM open list
drivers/staging/rtl8723bs/hal/hal_com_phycfg.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/rtl8723bs/hal/hal_com_phycfg.c
Hi again,
just found the first offending commit:
commit eff0275e5253604429aedc42b008c5fcaa6cc597
Date: Wed Oct 31 11:57:06 2018 +0100
spi: rockchip: simplify use_dma logic
We only need to know if we're using dma when setting
up the transfer, so just use a local variable for
Hi!
> >I am not sure about existing driver. Important thing for me is that
> >new drivers use consistent naming.
> >
> >>In cases like above:
> >>
> >> keyboardist::kbd_backlight
> >> tclnumpad::kbd_backlight
> >>
> >>we could do with the following:
> >>
> >> :kbd-backlight
> >>
Added a blank line after declarations.
Signed-off-by: Gabriela Bittencourt
---
drivers/staging/rtl8723bs/hal/hal_com_phycfg.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/rtl8723bs/hal/hal_com_phycfg.c
b/drivers/staging/rtl8723bs/hal/hal_com_phycfg.c
index
Fix checkpatch space coding style errors, warnings and checks on
rtl819x_TSProc.c
Signed-off-by: Caio Salvador Rohwedder
---
Changes in v2:
- change commit message
- fix remaining space errors
---
.../rtl8192u/ieee80211/rtl819x_TSProc.c | 112 +-
1 file
The pull request you sent on Sat, 6 Apr 2019 23:30:43 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git
> i2c/for-current-fixed
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/faac51ddac4575880f20e5c70fa1d50401dd940a
Thank you!
--
Deet-doot-dot,
On Fri, Apr 05, 2019 at 09:32:35PM +0200, Thomas Gleixner wrote:
> > +/* Add support for architecture specific output in /proc/pid/status */
> > +extern void arch_proc_pid_status(struct seq_file *m, struct task_struct
> > *task);
^^
Unnecessary extern.
Linus,
I2C has a simple but wanted driver bugfix.
Please pull.
Thanks,
Wolfram
The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6:
Linux 5.1-rc3 (2019-03-31 14:39:29 -0700)
are available in the Git repository at:
The pull request you sent on Sat, 6 Apr 2019 22:29:32 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
> parisc-5.1-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/373c392508577b24e293ff4994e919087fed2495
Thank you!
--
Deet-doot-dot,
Hi Linus,
please pull four small parisc architecture fixes for kernel 5.1 from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-5.1-2
A 32-bit boot regression fix introduced in the merge window, a QEMU detection
fix and two fixes by Sven regarding ptrace &
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
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 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/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 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 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 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 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 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
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
My Greeting, May Almighty God Bless You, Did you receive the letter i
sent to you. Please answer me.
Best Regard,
Miss Maureen Magoko.
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.
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
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
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
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
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
Hello, Kindly Please confirm is you.
Regard,
Rufus
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
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
>
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, 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
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 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
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 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
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 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.
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.
>
>
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
unsubscribe linux-kernel
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
> >
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
>
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
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(+),
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
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
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
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
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
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
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
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:
>
>
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
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
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
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
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
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 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!
> >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
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,
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,
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
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 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
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.
---
1 - 100 of 132 matches
Mail list logo
