On Tue, 2019-01-22 at 15:57:21 UTC, Joe Lawrence wrote:
> From: Nicolai Stange
>
> The ppc64 specific implementation of the reliable stacktracer,
> save_stack_trace_tsk_reliable(), bails out and reports an "unreliable
> trace" whenever it finds an exception frame on the stack. Stack frames
> are
On Fri, Feb 08, 2019 at 07:05:26AM -0500, Stefan Berger wrote:
> See my comment on [PATCH v11 08/16]. It needs to be added in that patch
> since otherwise rc holds a non-zero value on function exit, which is wrong
> at that point.
The snippet in question:
rc = chip->ops->send(chip, buf, count);
i
On Sat, 2019-02-02 at 12:54:27 UTC, Mathieu Malaterre wrote:
> There is not point in having a trailing semicolon after a closing curly
> brace. Remove it.
>
> Signed-off-by: Mathieu Malaterre
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/e5c27ef7a5f204ff2f894f0dd7ed3774
che
On Mon, 2019-01-28 at 16:11:36 UTC, Brajeswar Ghosh wrote:
> Remove linux/rtc.h which is included more than once
>
> Signed-off-by: Brajeswar Ghosh
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/75f8a37580b64f87c223fbd08db6b2f7
cheers
On Fri, 2019-02-01 at 10:46:52 UTC, Christophe Leroy wrote:
> Since commit c40dd2f76644 ("powerpc: Add System RAM to /proc/iomem")
> it is possible to use the generic walk_system_ram_range() and
> the generic page_is_ram().
>
> To enable the use of walk_system_ram_range() by the IBM EHEA
> etherne
On Sat, 2019-02-02 at 13:05:35 UTC, Mathieu Malaterre wrote:
> Move the static keyword around to remove the following warnings (W=1):
>
> arch/powerpc/platforms/ps3/os-area.c:212:1: error: 'static' is not at
> beginning of declaration [-Werror=old-style-declaration]
> arch/powerpc/platforms/p
On Tue, 2019-01-29 at 16:37:55 UTC, Christophe Leroy wrote:
> Today's message is useless:
>
> [ 42.253267] Kernel stack overflow in process (ptrval), r1=c65500b0
>
> This patch fixes it:
>
> [ 66.905235] Kernel stack overflow in process sh[356], r1=c65560b0
>
> Fixes: ad67b74d2469 ("printk:
On Thu, 2019-01-17 at 16:19:05 UTC, Sabyasachi Gupta wrote:
> Remove linux/syscalls.h which is included more than once
>
> Signed-off-by: Sabyasachi Gupta
> Acked-by: Souptick Joarder
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/45a202a3fefc6ee7b19b1222bfb5b067
cheers
On 05/02/19 6:48 AM, David Lechner wrote:
> On 2/4/19 11:17 AM, Bartosz Golaszewski wrote:
>> From: Bartosz Golaszewski
>>
>> The timer interrupts specified in commit 3652e2741f42 ("ARM: dts:
>> da850: Add clocks") are wrong but since the current timer code
>> hard-codes them, the bug was never sp
On 2/8/19 8:02 AM, Jarkko Sakkinen wrote:
On Fri, Feb 08, 2019 at 07:05:26AM -0500, Stefan Berger wrote:
See my comment on [PATCH v11 08/16]. It needs to be added in that patch
since otherwise rc holds a non-zero value on function exit, which is wrong
at that point.
The snippet in question:
rc
The patch
dt-bindings: sound: msm8916-wcd-analog: fix example regulator names
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next
The patch
ASoC: codecs: jz4725b: Remove unnecessary const qualifier
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.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
ASoC: doc: Fix typos in dpcm.rst
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.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 patch
SoC: stm32: i2s: manage clock power
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.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 dur
The patch
regulator: rt5033: Constify rt5033_safe_ldo_ops and rt5033_buck_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 patch
ASoC: stm32: i2s: add power management
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.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
The patch
regulator: fix device unlinking
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) and sent to Linu
On 2019-01-30 13:27:13 [+0100], Borislav Petkov wrote:
> On Wed, Jan 30, 2019 at 01:06:47PM +0100, Sebastian Andrzej Siewior wrote:
> > I don't know if hackbench would show anything besides noise.
>
> Yeah, if a sensible benchmark (dunno if hackbench is among them :))
> shows no difference, is als
On Fri, Feb 08, 2019 at 07:22:48AM -0500, Stefan Berger wrote:
> On 2/8/19 6:50 AM, Jarkko Sakkinen wrote:
> > On Thu, Feb 07, 2019 at 09:14:54PM -0500, Stefan Berger wrote:
> >
> > > chip->ops = NULL;
> > > up_write(&chip->ops_sem);
> > > }
> > > diff --git a/drivers/char/tpm/tpm-in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Linus,
Please pull some more powerpc fixes for 5.0:
The following changes since commit 7bea7ac0ca0121798f3618d16201ca4dc4e67a00:
powerpc/syscalls: Fix syscall tracing (2019-01-15 21:32:25 +1100)
are available in the git repository at:
https
On 2/4/19 10:55 AM, Theodore Y. Ts'o wrote:
> On Sun, Feb 03, 2019 at 08:09:37AM -0500, Prarit Bhargava wrote:
>> Ted, the bug I'm trying to fix is the warning:
>>
>> random: get_random_bytes called from start_kernel+0x8e/0x587 with crng_init=0
>>
>> during early boot. Even with the kernel para
On Fri, Feb 08, 2019 at 08:10:32AM -0500, Stefan Berger wrote:
> On 2/8/19 8:02 AM, Jarkko Sakkinen wrote:
> > On Fri, Feb 08, 2019 at 07:05:26AM -0500, Stefan Berger wrote:
> > > See my comment on [PATCH v11 08/16]. It needs to be added in that patch
> > > since otherwise rc holds a non-zero value
D_CAN supports up to 128 message objects, comparing to 32 on C_CAN.
However, some CPUs with D_CAN controller have their own limits:
TI AM335x Sitara CPU, for example, supports max of 64 message objects.
This patch extends max D_CAN message objects up to 64.
Signed-off-by: Andrejs Cainikovs
---
Make number of D_CAN RX message objects configurable. This will allow
having bigger (or smaller) RX buffer instead of 50/50 split for RX/TX.
Signed-off-by: Andrejs Cainikovs
---
drivers/net/can/c_can/Kconfig | 8 ++
drivers/net/can/c_can/c_can.c | 64 +---
When the oscillator of the rtc gets interrupted,
e.g. due to an empty battery, reading from the rtc will now return an error
and the oscillator bit will be cleared, once the rtc is successfully reset.
Signed-off-by: Oliver Rohe
---
drivers/rtc/rtc-rs5c372.c | 54 +
On Thu, Feb 07, 2019 at 12:36:54PM -0500, Dennis Zhou wrote:
> On Thu, Feb 07, 2019 at 05:59:26PM +0100, David Sterba wrote:
> > On Mon, Feb 04, 2019 at 03:19:56PM -0500, Dennis Zhou wrote:
> > > Dennis Zhou (12):
> > > btrfs: add helpers for compression type and level
> > > btrfs: rename works
Hi Miroslav,
On Fri, Feb 08, 2019 at 10:24:21AM +0100, Miroslav Benes wrote:
> Hi Kamalesh,
>
> On Fri, 8 Feb 2019, Kamalesh Babulal wrote:
>
> > On Wed, Feb 06, 2019 at 11:28:32AM +0100, Petr Mladek wrote:
> > > On Tue 2019-02-05 09:59:33, Josh Poimboeuf wrote:
> > > > On Tue, Feb 05, 2019 at 0
This patch adds support to compute context invoke method on the
remote processor (DSP).
This involves setting up the functions input and output arguments,
input and output handles and mapping the dmabuf fd for the
argument/handle buffers.
The below diagram depicts invocation of a single method whe
This patch adds basic driver model for Qualcomm FastRPC driver which
implements an IPC (Inter-Processor Communication) mechanism that
allows for clients to transparently make remote method invocations
across processor boundaries.
Each DSP rpmsg channel is represented as fastrpc channel context and
The FastRPC driver implements an IPC (Inter-Processor Communication)
mechanism that allows for clients to transparently make remote method
invocations across DSP and APPS boundaries. This enables developers
to offload tasks to the DSP and free up the application processor for
other tasks.
Co-devel
Hi Daniel & Thomas,
Do we have the chance to get this patch merged for K5.1?
Thanks,
Joseph
On 2/2/19 12:16 AM, Joseph Lo wrote:
Add support for the Tegra210 timer that runs at oscillator clock
(TMR10-TMR13). We need these timers to work as clock event device and to
replace the ARMv8 architect
This patch adds support to create or attach remote shell process.
The shell process called fastrpc_shell_0 is usually loaded on the DSP
when a user process is spawned.
Most of the work is derived from various downstream Qualcomm kernels.
Credits to various Qualcomm authors who have contributed to
User process can involve dealing with big buffer sizes, and also passing
buffers from one compute context bank to other compute context bank for
complex dsp algorithms.
This patch adds support to fastrpc to make it a proper dmabuf exporter
to avoid making copies of buffers.
Co-developed-by: Thier
Thanks for reviewing the v5 here is new version addressing the
comments from v6.
This patchset adds support to Qualcomm FastRPC driver which implements
an IPC (Inter-Processor Communication) mechanism that allows for clients
to transparently make remote method invocations across processor boundarie
On 04/02/19 10:47 PM, Bartosz Golaszewski wrote:
> +static unsigned int davinci_timer_read(struct davinci_timer_data *timer,
> +unsigned int reg)
> +{
> + return __raw_readl(timer->base + reg);
> +}
> +
> +static void davinci_timer_write(struct davinci_timer
On 08/02/2019 02:16, Brian Masney wrote:
> Add a new function irq_domain_translate_twocell() that is to be used as
> the translate function in struct irq_domain_ops for the v2 IRQ API.
>
> This patch also changes irq_domain_xlate_twocell() from the v1 IRQ API
> to call irq_domain_translate_twocell
Dear Valued Customer,
Consolidate your debts with Dial Direct Loan SA for your peace of
mind at a fixed interest rate of 4.75%,personal and business loans
are also welcome.For details
open enclosed documents and file in your applications by sending an email
to: infodialdirectlo...@mail2con
Hi Sugaya,
thank you for the patch!
Since Masahiro has previously added the Uniphier pin control driver
I would like him to provide a review of this patch, if possible. I also
want to make sure that the hardware is different enough from the
existing Uniphier pin control so that it really needs a
On 08.02.2019 03:14, Stefan Berger wrote:
On 2/7/19 8:51 PM, Stefan Berger wrote:
On 2/7/19 7:33 PM, Jarkko Sakkinen wrote:
On Thu, Feb 07, 2019 at 06:29:43PM -0500, Stefan Berger wrote:
On 2/7/19 4:29 PM, Jarkko Sakkinen wrote:
diff --git a/drivers/char/tpm/tpm2-cmd.c b/drivers/char/tpm
Re-sending entire patchset due to missed cover letter, sorry.
This patchset introduces support for 64 D_CAN message objects with an option of
unequal split between RX/TX.
The rationale behind this is that there are lots of frame loss on higher bus
speeds. Below are test results from my custom Sit
D_CAN supports up to 128 message objects, comparing to 32 on C_CAN.
However, some CPUs with D_CAN controller have their own limits:
TI AM335x Sitara CPU, for example, supports max of 64 message objects.
This patch extends max D_CAN message objects up to 64.
Signed-off-by: Andrejs Cainikovs
---
Make number of D_CAN RX message objects configurable. This will allow
having bigger (or smaller) RX buffer instead of 50/50 split for RX/TX.
Signed-off-by: Andrejs Cainikovs
---
drivers/net/can/c_can/Kconfig | 8 ++
drivers/net/can/c_can/c_can.c | 64 +---
On 2/7/19 5:20 AM, Bartlomiej Zolnierkiewicz wrote:
> Add Buddha PATA controller driver. It enables libata support for
> the Buddha, Catweasel and X-Surf expansion boards on the Zorro
> expansion bus.
>
> Module removal is currently unsupported (the old IDE's buddha
> driver also doesn't support i
Hi Sugaya,
thanks for your patch!
On Fri, Feb 8, 2019 at 1:32 PM Sugaya Taichi
wrote:
> Add DT bindings document for Milbeaut M10V pinctrl.
>
> Signed-off-by: Sugaya Taichi
(...)
> +- interrupts: three interrupts specifer.
> +- interrupt-names: corresponds "interrupts" factor.
(...)
> +
On 2/8/19 4:38 AM, John Paul Adrian Glaubitz wrote:
> Hi!
>
> On 2/7/19 1:20 PM, Bartlomiej Zolnierkiewicz wrote:
>> Add Buddha PATA controller driver. It enables libata support for
>> the Buddha, Catweasel and X-Surf expansion boards on the Zorro
>> expansion bus.
>>
>> Module removal is currentl
On Tue, Feb 5, 2019 at 11:25 AM Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Add lookup entries for the vbus and overcurrent gpios for omapl138-hawk.
>
> Signed-off-by: Bartosz Golaszewski
Reviewed-by: Linus Walleij
Yours,
Linus Walleij
On Tue, Feb 5, 2019 at 11:25 AM Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Add lookup entries for vbus and overcurrent gpios for da830-evm.
>
> Signed-off-by: Bartosz Golaszewski
Reviewed-by: Linus Walleij
Yours,
Linus Walleij
On 2/8/19 2:33 PM, Jens Axboe wrote:
>> It's a bit confusing, but my primary name is Adrian, despite being
>> the third one. So if this ends in a changelog, please change this
>> to "- added Tested-by from Adrian".
>
> The stuff below the --- line will not make it into the git log.
Aha, I didn't
On Fri, Feb 08, 2019 at 03:17:54PM +0200, Jarkko Sakkinen wrote:
> On Fri, Feb 08, 2019 at 08:10:32AM -0500, Stefan Berger wrote:
> > On 2/8/19 8:02 AM, Jarkko Sakkinen wrote:
> > > On Fri, Feb 08, 2019 at 07:05:26AM -0500, Stefan Berger wrote:
> > > > See my comment on [PATCH v11 08/16]. It needs
On 2/8/2019 5:39 AM, Thomas Gleixner wrote:
On Thu, 31 Jan 2019, Liang, Kan wrote:
+u64 perf_get_page_size(u64 virt)
+{
+ unsigned long flags;
+ unsigned int level;
+ pte_t *pte;
+
+ if (!virt)
+ return 0;
+
+ /*
+* Interrupts are disabled,
Commit-ID: 0521e8be211cd20d547bff9da2534b7ed6f2c1b9
Gitweb: https://git.kernel.org/tip/0521e8be211cd20d547bff9da2534b7ed6f2c1b9
Author: Peter Zijlstra
AuthorDate: Fri, 8 Feb 2019 13:08:59 +0100
Committer: Thomas Gleixner
CommitDate: Fri, 8 Feb 2019 14:31:56 +0100
x86/mm/cpa: Fix set_mc
Commit-ID: c81cd5c08d676483bb09f4809660d2a1abea0062
Gitweb: https://git.kernel.org/tip/c81cd5c08d676483bb09f4809660d2a1abea0062
Author: Bo Yu
AuthorDate: Fri, 8 Feb 2019 07:53:43 -0500
Committer: Thomas Gleixner
CommitDate: Fri, 8 Feb 2019 14:32:33 +0100
x86/mtrr: Remove unused variabl
Commit-ID: ba2ba356b2c849ec62d5fefa9cd4168163b13211
Gitweb: https://git.kernel.org/tip/ba2ba356b2c849ec62d5fefa9cd4168163b13211
Author: Sergey Senozhatsky
AuthorDate: Tue, 8 Jan 2019 22:02:24 +0900
Committer: Thomas Gleixner
CommitDate: Fri, 8 Feb 2019 14:32:33 +0100
x86/cpu_entry_area
Steven, Mike, any comments on that?
On 08/01/2019 13:12, matthias@kernel.org wrote:
> From: Jasper Mattsson
>
> Currently, DRAM-related clocks are not marked with CLK_IS_CRITICAL
> for MT6797. This causes memory corruption when the system is
> booted without clk_ignore_unused.
> This patch m
Commit-ID: 653a561bb2fd34e470594eb1bdba3357630e8df7
Gitweb: https://git.kernel.org/tip/653a561bb2fd34e470594eb1bdba3357630e8df7
Author: Sergey Senozhatsky
AuthorDate: Tue, 8 Jan 2019 22:02:25 +0900
Committer: Thomas Gleixner
CommitDate: Fri, 8 Feb 2019 14:32:34 +0100
x86/fpu: Move init
On Tue, Feb 5, 2019 at 4:17 PM Nikolaus Voss wrote:
> Make platform data optional and add DT id table.
> Switch to dynamically mapped GPIOs and IRQs if not provided
> via platform data.
>
> Signed-off-by: Nikolaus Voss
Patch applied with Michael's ACK.
Yours,
Linus Walleij
On Tue, Feb 5, 2019 at 4:17 PM Nikolaus Voss wrote:
> Interupts were generated using GPIN interrupts of
> ADP5588. These interrupts have two important limitations:
> 1. Interrupts can only be generated for either rising or
>falling edges but not both.
> 2. Interrupts are reasserted as long as
On 10/21/18 1:59 PM, Wolfram Sang wrote:
> We should get 'driver_data' from 'struct device' directly. Going via
> platform_device is an unneeded step back and forth.
Applied, thanks.
--
Jens Axboe
On 12/5/18 12:50 PM, Rob Herring wrote:
> Convert string compares of DT node names to use of_node_name_eq helper
> instead. This removes direct access to the node name pointer.
Applied, thanks.
--
Jens Axboe
On 2/6/19 10:13 PM, Guenter Roeck wrote:
> The following traceback is sometimes seen when booting an image in qemu:
>
> [ 54.608293] cdrom: Uniform CD-ROM driver Revision: 3.20
> [ 54.611085] Fusion MPT base driver 3.04.20
> [ 54.611877] Copyright (c) 1999-2008 LSI Corporation
> [ 54.61623
On 07.02.19 19:06, Andy Shevchenko wrote:
Hi,
> Overall I have a feeling that this driver can be replaced with> existing
> generic one where one register per pin is allocated.>
Unfortunately, I didn't look deep into this and hope Linus will help> to
figure this out.
this also was my first though
Modify setkey callback for cbc des and 3des to check for weak keys.
Signed-off-by: Iuliana Prodan
---
drivers/crypto/caam/caamalg.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/crypto/caam/caamalg.c b/drivers/crypto/caam/caamalg.c
index 90d83ae..9eac509 100644
Add ecb mode support for aes, des, 3des and arc4 ciphers.
ecb(*) reuses existing skcipher implementation, updating it with support
for no IV.
Signed-off-by: Iuliana Prodan
---
drivers/crypto/caam/Kconfig| 1 +
drivers/crypto/caam/caamalg.c | 190 +--
This patch set adds ecb mode support for aes, des, 3des and arc4 ciphers.
skcipher implementation is reused, making sure to handle the no IV case.
While here:
-fix a DMA API issue where initial src/dst_nents are used instead of nents
returned by dma_map_sg()
-export arc4 defines in a common header
The mapped_{src,dst}_nents _returned_ from the dma_map_sg call (which
could be less than src/dst_nents) have to be used to generate the aead,
skcipher job descriptors.
Signed-off-by: Iuliana Prodan
---
drivers/crypto/caam/caamalg.c | 27 ---
1 file changed, 20 insertions(
Some arc4 cipher algorithm defines show up in two places:
crypto/arc4.c and drivers/crypto/bcm/cipher.h.
Let's export them in a common header and update their users.
Signed-off-by: Iuliana Prodan
---
crypto/arc4.c | 5 +
drivers/crypto/bcm/cipher.h | 4 +---
include/crypto/ar
On Mon, Feb 4, 2019 at 3:24 PM Roger Quadros wrote:
> From: Suman Anna
>
> This patch adds the bindings for the Programmable Real-Time Unit
> and Industrial Communication Subsystem (PRU-ICSS) present on various
> SoCs such as AM33xx, AM437x, AM57xx, Keystone 66AK2G SoC, etc. It is
> present on t
On Tue, Feb 5, 2019 at 8:59 PM Krzysztof Kozlowski wrote:
> Remove the legacy, ugly API of exposing the static value of external
> wakeup interrupts mask, because all arch-machine users where converted
> to use generic implementation from pinctrl driver.
>
> Signed-off-by: Krzysztof Kozlowski
>
Waiman reported that on large systems with a large amount of interrupts the
readout of /proc/stat takes a long time to sum up the interrupt
statistics. In principle this is not a problem. but for unknown reasons
some enterprise quality software reads /proc/stat with a high frequency.
The reason fo
Waiman reported that on large systems with a large amount of interrupts the
readout of /proc/stat takes a long time to sum up the interrupt
statistics. In principle this is not a problem. but for unknown reasons
some enterprise quality software reads /proc/stat with a high frequency.
The reason fo
Waiman reported that on large systems with a large amount of interrupts the
readout of /proc/stat takes a long time to sum up the interrupt
statistics. In principle this is not a problem. but for unknown reasons
some enterprise quality software reads /proc/stat with a high frequency.
The reason fo
On Fri, Feb 08, 2019 at 01:23:04PM +, Srinivas Kandagatla wrote:
> +static int fastrpc_invoke(struct fastrpc_user *fl, char __user *argp)
> +{
> + struct fastrpc_invoke_args *args = NULL;
> + struct fastrpc_invoke inv;
> + u32 nscalars;
> + int err;
> +
> + if (copy_from_use
On Thu, Feb 07, 2019 at 08:53:05PM -0800, David Coles wrote:
> GPIO pin mapping taken from NetGear NV+ v2 5.3.13 kernel sources[1]
> (see arch/arm/plat-feroceon/mv_hal/rtc/ext_rtc/usiLCD.c).
Kirkwood! It has been a while since we had a kirkwood patch. Some NAS
boxes seem to never die. Nice to see
On Fri, Feb 08, 2019 at 01:23:05PM +, Srinivas Kandagatla wrote:
> +static int fastrpc_init_create_process(struct fastrpc_user *fl,
> + char __user *argp)
> +{
> + struct fastrpc_init_create init;
> + struct fastrpc_invoke_args args[6];
All on the st
On Mon, Jan 21, 2019 at 4:36 PM Jerome Brunet wrote:
> On Mon, 2019-01-21 at 14:53 +0100, Linus Walleij wrote:
> > On Thu, Jan 17, 2019 at 11:23 AM Jerome Brunet wrote:
> >
> > > This patchset fixes the initial pinctrl support added for th g12a SoC
> > > family, which is mainly around the registe
On Thu, Feb 7, 2019 at 2:55 PM Paul Cercueil wrote:
> Add the pins and groups for the "lcd" pin function in the JZ4725B SoC.
>
> Signed-off-by: Paul Cercueil
Patch applied.
Yours,
Linus Walleij
Thanks for the review,
On 08/02/2019 13:55, Greg KH wrote:
+
+ /* Make sure reserved field is set to 0 */
+ if (args->reserved) {
+ kfree(args);
+ return -EINVAL;
Am I wrong in that you are only checking the first reserved
On 2/8/19 8:33 AM, Jarkko Sakkinen wrote:
if (len != be32_to_cpu(header->length)) {
rc = -EFAULT;
goto out;
}
rc = tpm2_commit_space(chip, space, ordinal, buf, &len);
if (rc)
dev_err(&chip->dev, "tpm2_commit_space: error %d\n", rc);
That unconditional call to commit spa
On Fri, Feb 08, 2019 at 10:43:40AM +0530, Kishon Vijay Abraham I wrote:
> > I don't see the whole series on linux-pci (I only see patches 2, 6, 8, 9),
>
> I do see all the patches here
> https://patchwork.kernel.org/project/linux-pci/list/. Maybe it arrived little
> late?
For some reason Gmail d
On Fri, Feb 8, 2019 at 7:19 AM Greg KH wrote:
>
> I would like to see other people review and put their "name" on the
> patchset either with a "reviewed-by:" or "ack" or something.
That's what I would love to see too !
And I agree with you that a patchset like this needs more review.
Probably a
Fixed regulators do not have associated bus addresses and are typically
placed directly under the root node where their names must still be
unique despite not having a unit address.
Fix the malformed example node which had a unit address but no "reg"
property by dropping the unit address.
Also, t
A portion of send() callbacks have returned length, in many cases just
returning back what was given as an argument, and tpm_crb has returned 0 on
success. This patch set fixes and unifies the behaviour.
Jarkko Sakkinen (2):
tpm: Unify the send callback behaviour
tpm/tpm_i2c_atmel: Return -E2
Bisected guest kernel changes crashing qemu. Landed at
"6c1cd97bda drm/virtio: fix resource id handling". Looked again, and
noticed we where not only leaking *some* ids, but *all* ids. The old
code never ever called virtio_gpu_resource_id_put().
So, commit 6c1cd97bda effectively makes the linux
This variable is useless.
---
drivers/iommu/dma-iommu.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c
index 8e04b0603a4a..eff301d5e496 100644
--- a/drivers/iommu/dma-iommu.c
+++ b/drivers/iommu/dma-iommu.c
@@ -291,7 +29
The send() callback should never return length as it does not in every
driver except tpm_crb in the success case. The reason is that the main
transmit functionality only cares about whether the transmit was
successful or not and ignores the count completely.
Cc: sta...@vger.kernel.org
Signed-off-b
Return -E2BIG when the transfer is incomplete. The upper layer does
not retry, so not doing that is incorrect behaviour.
Cc: sta...@vger.kernel.org
Fixes: a2871c62e186 ("tpm: Add support for Atmel I2C TPMs")
Signed-off-by: Jarkko Sakkinen
---
drivers/char/tpm/tpm_i2c_atmel.c | 4
1 file cha
Feel free to add my...
Suggested-by: Sedat Dilek (see my comment in [1])
[1] https://github.com/ClangBuiltLinux/linux/issues/341#issuecomment-459788558
On Fri, Feb 08, 2019 at 09:02:22AM -0500, Stefan Berger wrote:
> On 2/8/19 8:33 AM, Jarkko Sakkinen wrote:
> >
> > if (len != be32_to_cpu(header->length)) {
> > rc = -EFAULT;
> > goto out;
> > }
> >
> > rc = tpm2_commit_space(chip, space, ordinal, buf, &len);
> > if (rc)
> > dev_err(&
On Fri, Feb 08, 2019 at 02:28:50PM +0100, Alexander Steffen wrote:
> Applying those changes fixes all the issues I saw, thanks. I'll retest
> Jarkko's tree without custom patches, once you've agreed on the rc question.
Just send a two patch patch set how I believe the regression should
be properly
On Fri, Feb 08, 2019 at 02:01:33PM +, Srinivas Kandagatla wrote:
> Thanks for the review,
>
> On 08/02/2019 13:55, Greg KH wrote:
> > > +
> > > + /* Make sure reserved field is set to 0 */
> > > + if (args->reserved) {
> > > + kfree(args);
> > > +
On Fri, Jan 25, 2019 at 03:45:03PM -0800, Bjorn Andersson wrote:
> Enabling PCIe requires several of the PCIe related resets from GCC, so
> add them all.
>
> Signed-off-by: Bjorn Andersson
> ---
>
> Stephen, I suggest that we merge this patch through Andy's devicetree branch,
> together with the
gpiod_get_index_optional can return ERR_PTR, add IS_ERR checking for it.
While at it, also remove a redundant NULL test for gpiod in error path.
Signed-off-by: Axel Lin
---
drivers/regulator/lm363x-regulator.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/regu
On 2019-02-08 13:46, Dmitry Osipenko wrote:
> 08.02.2019 1:25, Dmitry Osipenko пишет:
>>> 08.02.2019 1:16, Sowjanya Komatineni пишет:>
> This is wrong, 65535 = 64 * 1024 - 1.
>
> Let's just use size-constants provided by kernel:
>
> static const struct i2c_adapter_quirks tegra_
[+cc Thomas]
On Fri, Feb 08, 2019 at 06:11:15PM +0530, Subrahmanya Lingappa wrote:
> On Tue, Jan 29, 2019 at 1:40 PM Z.q. Hou wrote:
> >
> > From: Hou Zhiqiang
> >
> > Avoid to issue CFG transactions to link partner when the PCIe
> > link is not up. And allow CFG transactions to all functions of
On Fri, Feb 08, 2019 at 10:34:45AM +0100, Petr Mladek wrote:
> On Fri 2019-02-08 11:50:05, Kamalesh Babulal wrote:
> > On Wed, Feb 06, 2019 at 11:28:32AM +0100, Petr Mladek wrote:
> > > On Tue 2019-02-05 09:59:33, Josh Poimboeuf wrote:
> > > > On Tue, Feb 05, 2019 at 03:33:28AM +0900, Alice Ferrazz
On Fri, Feb 08, 2019 at 09:05:11AM -0500, Sven Van Asbroeck wrote:
> On Fri, Feb 8, 2019 at 7:19 AM Greg KH wrote:
> >
> > I would like to see other people review and put their "name" on the
> > patchset either with a "reviewed-by:" or "ack" or something.
>
> That's what I would love to see too !
On Fri, Jan 25, 2019 at 03:45:05PM -0800, Bjorn Andersson wrote:
> The Qualcomm PCIe2 PHY is based on design from Synopsys and found in
> several different platforms where the QMP PHY isn't used.
>
> Signed-off-by: Bjorn Andersson
> ---
> drivers/phy/qualcomm/Kconfig | 8 +
> drivers/
On Fri, Jan 25, 2019 at 03:45:06PM -0800, Bjorn Andersson wrote:
> Before introducing the QCS404 platform, which uses the same PCIe
> controller as IPQ4019, migrate this to use the bulk clock API, in order
> to make the error paths slighly cleaner.
>
> Signed-off-by: Bjorn Andersson
> ---
> driv
Le 08/02/2019 à 05:11, Callum Sinclair a écrit :
> Currently the only way to clear the mfc cache was to delete the entries
mfc stands for 'multicast forwarding cache', so 'mfc cache' is a bit strange.
> one by one using the MRT_DEL_MFC socket option or to destroy and
> recreate the socket.
Note th
On 01/02/2019 00:53, Sai Prakash Ranjan wrote:
Add support for coresight CPU debug module on Qualcomm
Kryo CPUs. This patch adds the UCI entries for Kryo CPUs
found on MSM8996 which shares the same PIDs as ETMs.
Without this, below error is observed on MSM8996:
[5.429867] OF: graph: no p
301 - 400 of 1100 matches
Mail list logo
