The patch
spi: spi-fsl-spi: remove always-true conditional in fsl_spi_do_one_msg
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
spi: tegra114: clear packed bit for unpacked mode
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent t
The patch
regulator: rc5t583: Get rid of struct rc5t583_regulator
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
The patch
regulator: tps6507x: Convert to regulator core's simplified DT parsing code
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually som
The patch
spi: tegra114: reset controller on probe
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus d
The patch
regulator: tps6507x: Constify tps6507x_pmic_ops
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours)
The patch
regulator: tps6507x: Remove unused *rdev[] from struct tps6507x_pmic
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime i
The patch
spi: tegra114: terminate dma and reset on transfer timeout
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) a
The patch
spi: tegra114: flush fifos
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next
Cleanup and refine some DCMI error messages.
Hugues Fruchet (2):
media: stm32-dcmi: fix error messages
media: stm32-dcmi: do not emit error trace in case of few overrun
drivers/media/platform/stm32/stm32-dcmi.c | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
--
2.7
The patch
spi: tegra114: fix for unpacked mode transfers
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to L
Report overrun error only when it exceeds a given threshold.
Signed-off-by: Hugues Fruchet
---
drivers/media/platform/stm32/stm32-dcmi.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/media/platform/stm32/stm32-dcmi.c
b/drivers/media/platform/stm32/stm3
On Mon, 1 Apr 2019 09:29:16 +0200
Paolo Valente wrote:
>
>
> > Il giorno 29 mar 2019, alle ore 15:10, Jens Axboe
> > ha scritto:
> >
> > On 3/29/19 7:02 AM, Dmitrii Tcvetkov wrote:
> >> Hi,
> >>
> >> I got kernel panic since v5.1-rc1 when working with files on block
> >> device with BFQ sched
Double-word sign-extending shifts by a variable amount are a
non-trivial amount of code and complexity. Doing signed long shifts
before the cast to (s_max) greatly simplifies the object code.
(Yes, I know "signed" is redundant. It's there for emphasis.)
The complex issue raised by this patch is
Move the definition of the code to be written from
__jump_label_transform() to a specialized function.
Signed-off-by: Daniel Bristot de Oliveira
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Greg Kroah-Hartman
Cc: Masami Hiramatsu
Cc: "Steven Rostedt (VMwa
In the batching mode, entries with the same key should also be sorted by the
code, enabling a bsearch() of a code/addr when updating a key.
Signed-off-by: Daniel Bristot de Oliveira
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Greg Kroah-Hartman
Cc: Masami
While tuning a system with CPUs isolated as much as possible, we've
noticed that isolated CPUs were receiving bursts of 12 IPIs, periodically.
Tracing the functions that emit IPIs, we saw chronyd - an unprivileged
process - generating the IPIs when changing a static key, enabling
network timestapi
Add a helper macro to make jump entry iteration code more readable.
Signed-off-by: Daniel Bristot de Oliveira
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Greg Kroah-Hartman
Cc: Masami Hiramatsu
Cc: "Steven Rostedt (VMware)"
Cc: Jiri Kosina
Cc: Josh Poi
Move the check if a jump_entry is valid to a function.
Signed-off-by: Daniel Bristot de Oliveira
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc: Greg Kroah-Hartman
Cc: Masami Hiramatsu
Cc: "Steven Rostedt (VMware)"
Cc: Jiri Kosina
Cc: Josh Poimboeuf
Cc: "
Currently, the jump label of a static key is transformed via the arch
specific function:
void arch_jump_label_transform(struct jump_entry *entry,
enum jump_label_type type)
The new approach (batch mode) uses two arch functions, the first has the
same argumen
Below is the list of build error/warning regressions/improvements in
v5.1-rc3[1] compared to v5.0[2].
Summarized:
- build errors: +0/-1
- build warnings: +137/-104
JFYI, when comparing v5.1-rc3[1] to v5.1-rc2[3], the summaries are:
- build errors: +0/-0
- build warnings: +56/-67
Happy fi
If the architecture supports the batching of jump label updates, use it!
An easy way to see the benefits of this patch is switching the
schedstats on and off. For instance:
-- %<
#!/bin/sh
while [ true ]; do
sysctl -w kernel.sched_sch
Currently, the patch of an address is done in three steps:
-- Pseudo-code #1 - Current implementation ---
1) add an int3 trap to the address that will be patched
sync cores (send IPI to all other CPUs)
2) update all but the first byte of the patched range
sy
Over the last 20 years, the Linux kernel has accumulated hundreds if not
thousands of security vulnerabilities.
One common pattern in most of these security related reports is processes
called "syzkaller", "trinity" or "syz-executor" opening files and then
abuse kernel interfaces causing kernel cr
> Il giorno 1 apr 2019, alle ore 10:55, Dmitrii Tcvetkov
> ha scritto:
>
> On Mon, 1 Apr 2019 09:29:16 +0200
> Paolo Valente wrote:
>>
>>
>>> Il giorno 29 mar 2019, alle ore 15:10, Jens Axboe
>>> ha scritto:
>>>
>>> On 3/29/19 7:02 AM, Dmitrii Tcvetkov wrote:
Hi,
I got ke
Oliver Neukum 於 2019/4/1 下午 04:34 寫道:
On Mo, 2019-04-01 at 14:00 +0800, Ji-Ze Hong (Peter Hong) wrote:
Hi,
I am afraid there is a race condiion in this code.
@@ -315,6 +318,7 @@ static void f81232_process_read_urb(struct urb *urb)
if (lsr & UART_LSR_OE) {
Hi Adrian,
On 01/04/19 2:21 PM, Adrian Hunter wrote:
> On 29/03/19 4:22 PM, Faiz Abbas wrote:
>> Some controllers on TI devices requires the HISPD bit to be cleared
>> even in some high speed modes. Add a quirk that facilitates this
>> requirement.
>
> Could you use sdhci I/O accessors for this?
On 03/25/2019 03:19 PM, Peter Zijlstra wrote:
On Mon, Mar 25, 2019 at 02:47:32PM +0800, Like Xu wrote:
On 2019/3/24 1:28, Peter Zijlstra wrote:
On Sat, Mar 23, 2019 at 10:18:03PM +0800, Like Xu wrote:
=== Brief description ===
This proposal for Intel vPMU is still committed to optimize the ba
On Fri, Mar 29, 2019 at 11:20:04AM -0400, Alex Kogan wrote:
> diff --git a/kernel/locking/mcs_spinlock.h b/kernel/locking/mcs_spinlock.h
> index bc6d3244e1af..71ee4b64c5d4 100644
> --- a/kernel/locking/mcs_spinlock.h
> +++ b/kernel/locking/mcs_spinlock.h
> @@ -17,8 +17,18 @@
>
> struct mcs_spinl
On Fri, Mar 29, 2019 at 11:20:01AM -0400, Alex Kogan wrote:
> The following locktorture results are from an Oracle X5-4 server
> (four Intel Xeon E7-8895 v3 @ 2.60GHz sockets with 18 hyperthreaded
> cores each).
The other interesting number is on a !NUMA machine. What do these
patches do there? R
During my regression testing I noticed the cadence GPIO driver
fails on the latest gpio for-next tree.
I think the reason is this patch:
commit 96cd559817f2 ("Merge branch 'devel' into for-next")
Here is a part of the test log:
Loopback 8 -> 24
TESTING: gpio: 488: output direction PASSED
TESTING
Hi Sugaya, Arnd, Olof,
On Thu, Mar 28, 2019 at 02:35:54PM -0500, Rob Herring wrote:
> +arm-soc
>
> On Mon, Mar 18, 2019 at 5:05 AM Maxime Ripard
> wrote:
> >
> > Commit fd73403a4862 ("dt-bindings: arm: Add SMP enable-method for
> > Milbeaut") added support for a new cpu enable-method, but did so
On 1/04/19 12:01 PM, Faiz Abbas wrote:
> Hi Adrian,
>
> On 01/04/19 2:21 PM, Adrian Hunter wrote:
>> On 29/03/19 4:22 PM, Faiz Abbas wrote:
>>> Some controllers on TI devices requires the HISPD bit to be cleared
>>> even in some high speed modes. Add a quirk that facilitates this
>>> requirement.
On Thu, Mar 28, 2019 at 1:02 AM Thomas Gleixner wrote:
> On Thu, 7 Mar 2019, Ondrej Mosnacek wrote:
>
> > Emit an audit record every time selected NTP parameters are modified
> > from userspace (via adjtimex(2) or clock_adjtime(2)).
> >
> > Such events will now generate records of type AUDIT_TIME_
On Wed, 2019-03-27 at 17:19 +0800, wangyan wang wrote:
> From: chunhui dai
>
> Recalculate the rate of this clock, by querying hardware.
You just describe _WHAT_ do you do here, I would like you to describe
_WHT_ do you do here. I think this patch is to make implementation of
recalc_rate() to ma
Hi,
This looks good to me.
Reviewed-by: Kunihiko Hayashi
Thanks,
On Sat, 30 Mar 2019 17:11:37 +0800
Chunfeng Yun wrote:
> Use devm_clk_get_optional() to get optional clock
>
> Cc: Kunihiko Hayashi
> Signed-off-by: Chunfeng Yun
> ---
> drivers/phy/socionext/phy-uniphier-usb3hs.c | 10 +++-
On Thu, Mar 28, 2019 at 12:27 AM John Stultz wrote:
> On Thu, Mar 7, 2019 at 4:33 AM Ondrej Mosnacek wrote:
> >
> > Emit an audit record whenever the system clock is changed (i.e. shifted
> > by a non-zero offset) by a syscall from userspace. The syscalls than can
> > (at the time of writing) tri
On Fri, Mar 29, 2019 at 11:20:04AM -0400, Alex Kogan wrote:
> +static inline void pass_mcs_lock(struct mcs_spinlock *node,
> + struct mcs_spinlock *next)
> +{
> + struct mcs_spinlock *succ = NULL;
> +
> + succ = find_successor(node);
> +
> + if (succ) {
> +
On Sun, Mar 31, 2019 at 09:28:03PM +0300, Andrey Abramov wrote:
> This is the logical continuation of the "lib/sort & lib/list_sort:
> faster and smaller" series by George Spelvin (added to linux-next
> recently).
>
> Since Spectre mitigations have made indirect function calls more
> expensive, an
Hi Boris,
On Sat, Mar 30, 2019 at 3:16 PM Boris Brezillon
wrote:
> The AT25 protocol fits pretty well in the spi-mem model. Convert the
> at25 spi driver to a spi-mem driver and use the dirmap API instead of
> forging SPI messages manually.
> This makes the driver compatible with spi-mem-only con
On Thursday, March 28, 2019 11:33:21 AM CEST Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> There is not reason for the minimum iowait boost value in the
> schedutil cpufreq governor to depend on the available range of CPU
> frequencies. In fact, that dependency is generally confusing,
>
On Sat, Mar 30, 2019 at 12:20 PM Borislav Petkov wrote:
>
> From: Borislav Petkov
>
> Using static_cpu_has() is pointless on those paths, convert them to the
> boot_cpu_has() variant.
>
> No functional changes.
>
> Signed-off-by: Borislav Petkov
> Cc: Len Brown
> Cc: linux...@vger.kernel.org
>
On Mon, Apr 1, 2019 at 11:31 AM Rafael J. Wysocki wrote:
>
> On Sat, Mar 30, 2019 at 12:20 PM Borislav Petkov wrote:
> >
> > From: Borislav Petkov
> >
> > Using static_cpu_has() is pointless on those paths, convert them to the
> > boot_cpu_has() variant.
> >
> > No functional changes.
> >
> > Si
On Mon, Apr 01, 2019 at 11:06:53AM +0200, Peter Zijlstra wrote:
> On Fri, Mar 29, 2019 at 11:20:04AM -0400, Alex Kogan wrote:
> > diff --git a/kernel/locking/mcs_spinlock.h b/kernel/locking/mcs_spinlock.h
> > index bc6d3244e1af..71ee4b64c5d4 100644
> > --- a/kernel/locking/mcs_spinlock.h
> > +++ b/
On Mon, Apr 01, 2019 at 08:34:44AM +, 吳昊澄 Ricky wrote:
> Dear Greg k-h,
>
> I saw the patch is already in Linus's tree
> But I found it is not my v3-patch
> Can you help me to check this status kindly?
I had already applied and submitted your patch when you sent the v3
patch. I can not go ba
This patch enables enough time to ROME controller to bootup
after we bring the enable pin out of reset.
Fixes: 05ba533c5c11 ("Bluetooth: hci_qca: Add serdev support").
Signed-off-by: Balakrishna Godavarthi
Reviewed-by: Rocky Liao
Tested-by: Rocky Liao
Tested-by: Claire Chang
---
Changes in v2:
On Sat, Mar 30, 2019 at 05:41:19AM +1100, James Morris wrote:
> On Fri, 29 Mar 2019, Jarkko Sakkinen wrote:
>
> > Hi James,
> >
> > These are critical fixes for v5.1. Contains also couple of new selftests for
> > v5.1 features (partial reads in /dev/tpm0). I hope these could still reach
> > the r
On 3/28/2019 6:45 PM, Thierry Reding wrote:
On Tue, Mar 26, 2019 at 08:43:22PM +0530, Vidya Sagar wrote:
Add support for Tegra194 PCIe controllers. These controllers are based
on Synopsys DesignWare core IP.
Signed-off-by: Vidya Sagar
---
.../bindings/pci/nvidia,tegra194-pcie.txt |
On Thu, 2019-03-28 at 16:22 +, Srinivas Kandagatla wrote:
> Checking for value of type default value just after allocating will
> always be zero and the type register default values will never be
> read,
> so fix this!
>
> Without this patch setting irq type will be silently ignored.
> Patch "
On Mon, Apr 1, 2019 at 1:53 AM Jann Horn wrote:
>
> On Mon, Apr 1, 2019 at 12:33 AM Christian Brauner
> wrote:
> > On Sun, Mar 31, 2019 at 03:16:47PM -0700, Linus Torvalds wrote:
> > > On Sun, Mar 31, 2019 at 3:03 PM Christian Brauner
> > > wrote:
> > > > Thanks for the input. The problem Jann
On Wed, 27 Feb 2019, Gwendal Grignou wrote:
> Chromebook Embedded Controller protocol is defined in the kernel at
> cros_ec_commands.h.
> The source of trust for the EC protocol is at
> https://chromium.googlesource.com/chromiumos/platform/ec/+/master/include/ec_commands.h
>
> Only needed changes
> On 1 Apr 2019, at 11:39, Vitaly Kuznetsov wrote:
>
> Paolo Bonzini writes:
>
>> On 29/03/19 16:32, Liran Alon wrote:
>>> Paolo I am not sure this is the case here. Please read my other
>>> replies in this email thread.
>>>
>>> I think this is just a standard issue of a level-triggered int
From: Laurentiu Tudor
Make sure to free the i2c adapter on the error exit path.
Signed-off-by: Laurentiu Tudor
Reviewed-by: Mukesh Ojha
Reviewed-by: Uwe Kleine-Konig
Fixes: e1ab9a468e3b ("i2c: imx: improve the error handling in
i2c_imx_dma_request()")
---
Changes in v2:
- fixed formatting g
On Fri, 29 Mar 2019, Amelie DELAUNAY wrote:
> Hi,
>
> A gentle ping on this series (mfd + pinctrl patches, DT patches will be
> taken in STM32 soc tree).
I currently have over 100 reviews in my backlog.
Please be patient. You are on the list.
> On 2/27/19 10:34 AM, Amelie Delaunay wrote:
> >
On Fri, 29 Mar 2019, Morris Ku wrote:
> Hi,
> Thanks for review, my replies are inline:
I literally have no idea what this is!
It's a reply to a diff of a reply to a patch AFAICS!
I think the best I can do is point you to:
Documentation/process/submitting-patches.rst
> Signed-off-by: Morris
On 4/1/2019 1:46 PM, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski
It should have been 'management' not 'managemend'.
Fixes: 7945f929f1a7 ("drivers: provide devm_platform_ioremap_resource()")
Signed-off-by: Bartosz Golaszewski
---
drivers/base/platform.c | 2 +-
1 file changed, 1
Every EFI binary is in PE format. And we know that PE format needs to have
MZ MS-DOS header as there is written offset to PE header.
Therefore generated bzImage binary with CONFIG_EFI_STUB option is MS-DOS
executable binary.
We already know the "requirement" that Windows PE executable started in
On Thu, 28 Mar 2019, Stephen Rothwell wrote:
> Hi Randy,
>
> On Wed, 27 Mar 2019 13:32:26 -0700 Randy Dunlap wrote:
> >
> > on i386 or x86_64:
> >
> > WARNING: unmet direct dependencies detected for MFD_SUN6I_PRCM
> > Depends on [n]: HAS_IOMEM [=y] && ARCH_SUNXI
> > Selected by [y]:
> > -
On Mon, Apr 01, 2019 at 11:27:25AM +0200, Rafael J. Wysocki wrote:
> On Thursday, March 28, 2019 11:33:21 AM CEST Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > There is not reason for the minimum iowait boost value in the
> > schedutil cpufreq governor to depend on the available ra
On Tue, Mar 26, 2019 at 08:21:57AM -0400, Steven Rostedt wrote:
> Peter, Ingo,
>
> Are you OK with this patch? If you ack it, I'll pull it in through my
Sure,
Acked-by: Peter Zijlstra (Intel)
Liran Alon writes:
> So to sum-up: This matches what I mentioned in my previous emails right?
> That vector 96 is not related, and the only issue here is that
> level-triggered interrupt handler for vector 80 is doing EOI before lowering
> the irq-line.
> Which cause vector 80 to be injected in
On Mon, Apr 1, 2019 at 3:49 PM Mika Westerberg
wrote:
>
> On Fri, Mar 29, 2019 at 04:38:20PM +0800, Chris Chiu wrote:
> > On Thu, Mar 28, 2019 at 8:34 PM Mika Westerberg
> > wrote:
> > >
> > > On Thu, Mar 28, 2019 at 08:19:59PM +0800, Chris Chiu wrote:
> > > > On Thu, Mar 28, 2019 at 5:38 PM Dani
On Sat, Mar 30, 2019 at 09:13:46PM +0800, Muchun Song wrote:
> When we not use flat memory, the mem_map will be NULL and
> pfn_to_page(max_pfn) is a pointer which is located in kernel space. So
> max_mapnr is assigned a very large number(e.g., 0x_) - fix
> it.
>
> Signed-off-by: Mu
Hi Adrian,
On 01/04/19 2:42 PM, Adrian Hunter wrote:
> On 1/04/19 12:01 PM, Faiz Abbas wrote:
>> Hi Adrian,
>>
>> On 01/04/19 2:21 PM, Adrian Hunter wrote:
>>> On 29/03/19 4:22 PM, Faiz Abbas wrote:
Some controllers on TI devices requires the HISPD bit to be cleared
even in some high spe
Currently on panic, kernel will lower the loglevel and print out
new printk msg only. With this patch, user can configure the
"panic_print" to see all dmesg in buffer, some of which they may
have never seen due to the loglevel setting.
Signed-off-by: Feng Tang
---
Documentation/admin-guide/kerne
On Wed, Mar 27, 2019 at 10:12:56PM +0100, Wolfram Sang wrote:
> Commit cea443a81c9c ("i2c: Support i2c_transfer in atomic contexts")
> added in_atomic() to the I2C core. However, the use of in_atomic()
> outside of core kernel code is discouraged and was already[1] when this
> code was added in ear
Current console_flush_on_panic() will only dump the new messages
in buffer, and users may need an opportunity to check all the
messages on panic which could help debugging, as user may haven't
seen the log before panic due to loglevel settings.
Add a flag for console_flush_on_panic() to chose whet
On Tue, 26 Mar 2019, Jeffrey Hugo wrote:
> This adds the initial DT for the Lenovo Miix 630 laptop. Supported
> functionality includes USB (host), microSD-card, keyboard, and trackpad.
>
> Signed-off-by: Jeffrey Hugo
> ---
> arch/arm64/boot/dts/qcom/Makefile | 1 +
> arch/arm64/b
Hi Maxime,
Thanks for pointing my bug.
On 2019/04/01 18:10, Maxime Ripard wrote:
Hi Sugaya, Arnd, Olof,
On Thu, Mar 28, 2019 at 02:35:54PM -0500, Rob Herring wrote:
+arm-soc
On Mon, Mar 18, 2019 at 5:05 AM Maxime Ripard wrote:
Commit fd73403a4862 ("dt-bindings: arm: Add SMP enable-method
On Fri, Mar 29, 2019 at 03:05:54PM -0700, Paul E. McKenney wrote:
> On Fri, Mar 29, 2019 at 02:51:26PM -0700, H. Peter Anvin wrote:
> > On 3/29/19 2:09 PM, Paul E. McKenney wrote:
> > >>
> > >> Note: the atomic versions of these functions obviously need to have
> > >> "volatile" and the clobber any
Hi Boris,
I love your patch! Yet something to improve:
[auto build test ERROR on char-misc/char-misc-testing]
[also build test ERROR on v5.1-rc3 next-20190401]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hello, Andrew.
>
> It's a lot of new code. I t looks decent and I'll toss it in there for
> further testing. Hopefully someone will be able to find the time for a
> detailed review.
>
I have got some proposals and comments about simplifying the code a bit.
So i am about to upload the v3 for furt
From: Pankaj Suryawanshi
Sent: 01 April 2019 13:26
To: linux-kernel@vger.kernel.org; linux...@kvack.org
Subject: CMA area pages information
Hello,
Is there any way to get CMA area pages information (tool/application) ?
Trying to get CMA-pages info using
Mark Brown writes:
> On Wed, Mar 27, 2019 at 03:29:55PM +1100, Michael Ellerman wrote:
>> Mark Brown writes:
>
>> > Hrm, seems PowerPC is still not using the common clock API - is there
>> > any plan for that? There are some ASoC PowerPC uses so it's going to be
>> > a bit of an issue as we expa
On 3/31/2019 12:12 PM, Rob Herring wrote:
On Tue, Mar 26, 2019 at 08:43:22PM +0530, Vidya Sagar wrote:
Add support for Tegra194 PCIe controllers. These controllers are based
on Synopsys DesignWare core IP.
Signed-off-by: Vidya Sagar
---
.../bindings/pci/nvidia,tegra194-pcie.txt | 20
On Mon, Apr 01, 2019 at 11:01:13AM +0200, Johannes Thumshirn wrote:
> Over the last 20 years, the Linux kernel has accumulated hundreds if not
> thousands of security vulnerabilities.
>
> One common pattern in most of these security related reports is processes
> called "syzkaller", "trinity" or "
There are several issues with the formula used for calculating the
deviation from the intended rate:
1. While min_err and last_stop are signed, srr and baud are unsigned.
Hence the signed values are promoted to unsigned, which will lead
to a bogus value of deviation if min_err is negati
Hi Lee,
On Mon, 1 Apr 2019 11:27:32 +0100 Lee Jones wrote:
>
> On Thu, 28 Mar 2019, Stephen Rothwell wrote:
>
> > I reported that a while ago (x86_64 allmodconfig after the merge of the
> > sunxi tree). Apparently there is a fix out there but it hasn't been
> > applied yet.
>
> Where is the
Hi,
On Mon, Apr 01, 2019 at 07:52:06PM +0900, Sugaya, Taichi wrote:
> On 2019/04/01 18:10, Maxime Ripard wrote:
> > Hi Sugaya, Arnd, Olof,
> >
> > On Thu, Mar 28, 2019 at 02:35:54PM -0500, Rob Herring wrote:
> > > +arm-soc
> > >
> > > On Mon, Mar 18, 2019 at 5:05 AM Maxime Ripard
> > > wrote:
>
On 2019-03-31, Andy Lutomirski wrote:
> > On Mar 31, 2019, at 3:17 PM, Linus Torvalds
> > wrote:
> >> On Sun, Mar 31, 2019 at 2:10 PM Christian Brauner
> >> wrote:
> >>
> >> I don't think that we want or can make them equivalent since that would
> >> mean we depend on procfs.
> >
> > Sure we
On Sat, Mar 30, 2019 at 10:18:38AM -0700, Nathan Chancellor wrote:
> On Tue, Mar 26, 2019 at 03:30:04PM +0900, Greg Kroah-Hartman wrote:
> > 4.9-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Andrey Konovalov
> >
> > commit 32fd8
On 3/28/2019 6:03 PM, Thierry Reding wrote:
On Tue, Mar 26, 2019 at 08:43:20PM +0530, Vidya Sagar wrote:
move PCIe config space capability search API to common designware file
as this can be used by both host and ep mode codes.
It also adds extended capability search APIs.
Signed-off-by: Vidya
On 01/04/2019 13:22, Matthew Wilcox wrote:
[...]
>
> I think you should have credited Cisco for the idea.
>
> https://twitter.com/RedTeamPT/status/1110843396657238016
I actually had the idea longer but they won the race by several days.
Just not sure if their calendar was broken or it was a se
On 25/03/2019 15:59, Neil Armstrong wrote:
> This patchset adds nodes for Video Display support.
>
> Dependencies :
> - patch 1: VPU, HDMI & Power Controller bindings still in reviewe at [1]
> - patch 2: None
> - patch 3, 4, 5: Patch 1
>
> [1] https://lkml.kernel.org/r/20190313141030.5958-1-narms
On 4/1/2019 4:18 PM, Feng Tang wrote:
Current console_flush_on_panic() will only dump the new messages
in buffer, and users may need an opportunity to check all the
messages on panic which could help debugging, as user may haven't
seen the log before panic due to loglevel settings.
Add a flag
On 25/03/2019 11:03, Neil Armstrong wrote:
> Add following peripherals :
> - SAR-ADC
> - USB
> - Mali GPU
>
> Dependencies :
> - ADC
>
> Depends on CLKID_AO_SAR_ADC_SEL, stable clk headers tags will be
> available after v5.1-rc4
>
> Bindings has been merged for 5.2-rc1
>
> - USB
>
> USB depend
On Mon 01-04-19 09:59:36, Oscar Salvador wrote:
> On Fri, Mar 29, 2019 at 02:42:43PM +0100, Michal Hocko wrote:
> > Having a larger contiguous area is definitely nice to have but you also
> > have to consider the other side of the thing. If we have a movable
> > memblock with unmovable memory then
On Sun, 2019-03-31 at 18:16 +0530, Mukesh Ojha wrote:
> On 3/31/2019 6:04 PM, Hanna Hawa wrote:
> > Update driver license to be in-line with Linux conventions.
> >
> > Signed-off-by: Hanna Hawa
> > ---
> > drivers/irqchip/irq-alpine-msi.c | 5 +
> > 1 file changed, 1 insertion(+), 4 deleti
On 4/1/2019 2:31 PM, Johannes Thumshirn wrote:
Over the last 20 years, the Linux kernel has accumulated hundreds if not
thousands of security vulnerabilities.
One common pattern in most of these security related reports is processes
called "syzkaller", "trinity" or "syz-executor" opening files
CONFIG_VALIDATE_FS_PARSER is a debugging tool to check that the parser
tables are vaguely sane. It was set to default to 'Y' for the moment to
catch errors in upcoming fs conversion development.
Make sure it is not enabled by default in the final release of v5.1.
Fixes: 31d921c7fb969172 ("vfs: A
> > "This matches the use cases for atomic I2C transfers I have seen so far:
> > very late communication (mostly to a PMIC) to powerdown or reboot the
> > system."
>
> Ah, sorry, I missed that.
>
> > And yes, I would never recommend a HW design to use I2C for shutting
> > down/rebooting. But suc
On Mon, Mar 25, 2019 at 8:11 PM wrote:
>
> From: Jérôme Glisse
>
> This is a all in one helper that fault pages in a range and map them to
> a device so that every single device driver do not have to re-implement
> this common pattern.
>
> This is taken from ODP RDMA in preparation of ODP RDMA co
Currently, a CUSE server running on a 64-bit kernel can tell when an
ioctl request comes from a process running a 32-bit ABI, but cannot tell
whether the requesting process is using legacy IA32 emulation or x32
ABI, for example. In particular, the server does not know the size of
the client proces
On Sun, Mar 31, 2019 at 08:13:38PM -0600, Andy Lutomirski wrote:
>
>
> > On Mar 31, 2019, at 3:17 PM, Linus Torvalds
> > wrote:
> >
> >> On Sun, Mar 31, 2019 at 2:10 PM Christian Brauner
> >> wrote:
> >>
> >> I don't think that we want or can make them equivalent since that would
> >> mean
On 4/1/2019 4:55 PM, Geert Uytterhoeven wrote:
There are several issues with the formula used for calculating the
deviation from the intended rate:
1. While min_err and last_stop are signed, srr and baud are unsigned.
Hence the signed values are promoted to unsigned, which will lead
Hi Mark,
On 04/03/2019 13:31, Jon Hunter wrote:
> From: Jonathan Hunter
>
> Commit 78a24e10cd94 ("ASoC: soc-core: clear platform pointers on error")
> re-worked the clean-up of any platform pointers that may have been
> initialised by the function snd_soc_init_platform(). This commit missed
> on
On Mon, Apr 01, 2019 at 06:41:57PM +0800, Chris Chiu wrote:
> On Mon, Apr 1, 2019 at 3:49 PM Mika Westerberg
> wrote:
> > On Fri, Mar 29, 2019 at 04:38:20PM +0800, Chris Chiu wrote:
> > Sure I can but it probably does not happen until end of the week because
> > I'm currently busy with something
Hi Dmitry,
-Original Message-
From: Dmitry Torokhov [mailto:d...@chromium.org]
Sent: Saturday, March 30, 2019 2:24 AM
To: Hans de Goede; 廖崇榮
Cc: Vladislav Dalechyn; Benjamin Tissoires; Jiri Kosina;
kai.heng.f...@canonical.com; swb...@chromium.org; bige...@linutronix.de; open
list:HID CO
On Mon, Apr 01, 2019 at 10:36:24PM +1100, Stephen Rothwell wrote:
> Hi Lee,
>
> On Mon, 1 Apr 2019 11:27:32 +0100 Lee Jones wrote:
> >
> > On Thu, 28 Mar 2019, Stephen Rothwell wrote:
> >
> > > I reported that a while ago (x86_64 allmodconfig after the merge of the
> > > sunxi tree). Apparently t
On 3/28/2019 10:29 PM, Thierry Reding wrote:
On Tue, Mar 26, 2019 at 08:43:23PM +0530, Vidya Sagar wrote:
Add P2U (PIPE to UPHY) and PCIe controller nodes to device tree.
The Tegra194 SoC contains six PCIe controllers and twenty P2U instances
grouped into two different PHY bricks namely High-Spe
701 - 800 of 1306 matches
Mail list logo