Mathieu Poirier writes:
>> +static ssize_t notrace stm_write(struct stm_data *data, unsigned int master,
>> + unsigned int channel, const char *buf, size_t count)
>> +{
>> +ssize_t sz;
>> +
>> +sz = stm_data_write(data, master, channel, true, buf, count);
>> +if
On 10/02/2018 06:21 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.18.12 release.
There are 228 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
Apparently, this code does not actually fall through to the next case
because the machine restarts before it has a chance. However, for the
sake of maintenance and readability, we better add the missing break
statement.
Addresses-Coverity-ID: 1437892 ("Missing break in switch")
Signed-off-by:
Apparently, this code does not actually fall through to the next case
because the machine restarts before it has a chance. However, for the
sake of maintenance and readability, we better add the missing break
statement.
Addresses-Coverity-ID: 1437892 ("Missing break in switch")
Signed-off-by:
On 10/02/2018 06:23 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.74 release.
There are 137 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 10/02/2018 06:23 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.74 release.
There are 137 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 10/02/2018 06:24 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.131 release.
There are 94 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 10/02/2018 06:24 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.131 release.
There are 94 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
Mathieu Poirier writes:
> On Thu, Sep 20, 2018 at 03:45:37PM +0300, Alexander Shishkin wrote:
>> Hi,
>>
>> These are patches I have queued so far, that I'm planning to send to
>> Greg for the next merge window. This is mainly support for MIPI SyS-T
>> protocol and all the infrastructure changes
Mathieu Poirier writes:
> On Thu, Sep 20, 2018 at 03:45:37PM +0300, Alexander Shishkin wrote:
>> Hi,
>>
>> These are patches I have queued so far, that I'm planning to send to
>> Greg for the next merge window. This is mainly support for MIPI SyS-T
>> protocol and all the infrastructure changes
CPU0:
snd_trident_hw_free
snd_trident_free_voice
line 3870: spin_lock_irqsave()
line 3881: voice->substream = NULL; [WRITE]
CPU1:
snd_trident_interrupt
line 3798: snd_pcm_period_elapsed(voice->substream); [READ]
As for voice->substream, the WRITE operation in
CPU0:
snd_trident_hw_free
snd_trident_free_voice
line 3870: spin_lock_irqsave()
line 3881: voice->substream = NULL; [WRITE]
CPU1:
snd_trident_interrupt
line 3798: snd_pcm_period_elapsed(voice->substream); [READ]
As for voice->substream, the WRITE operation in
On Wed, Oct 03, 2018 at 02:34:02PM +0200, Peter Zijlstra wrote:
>
> Subject: ACPI/NUMA: Fix KASLR build error
>
> There is no point in trying to compile KASLR specific code when there is
> no KASLR.
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
Yeah, Peter and I were just talking on IRC and
On Wed, Oct 03, 2018 at 02:34:02PM +0200, Peter Zijlstra wrote:
>
> Subject: ACPI/NUMA: Fix KASLR build error
>
> There is no point in trying to compile KASLR specific code when there is
> no KASLR.
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
Yeah, Peter and I were just talking on IRC and
Hi All,
This is regarding the protected pins configuration reading and printing
from non-secure operating systems.
GPIO framework is checking whether pin is in use(flag FLAG_REQUESTED) or
not in gpiolib_dbg_show().
If GPIO chip drivers are overriding the dbg_show callback, drivers are
not
Hi All,
This is regarding the protected pins configuration reading and printing
from non-secure operating systems.
GPIO framework is checking whether pin is in use(flag FLAG_REQUESTED) or
not in gpiolib_dbg_show().
If GPIO chip drivers are overriding the dbg_show callback, drivers are
not
Subject: ACPI/NUMA: Fix KASLR build error
There is no point in trying to compile KASLR specific code when there is
no KASLR.
Signed-off-by: Peter Zijlstra (Intel)
---
diff --git a/drivers/acpi/numa.c b/drivers/acpi/numa.c
index 3d69834c692f..5767733976b3 100644
--- a/drivers/acpi/numa.c
+++
Subject: ACPI/NUMA: Fix KASLR build error
There is no point in trying to compile KASLR specific code when there is
no KASLR.
Signed-off-by: Peter Zijlstra (Intel)
---
diff --git a/drivers/acpi/numa.c b/drivers/acpi/numa.c
index 3d69834c692f..5767733976b3 100644
--- a/drivers/acpi/numa.c
+++
Oh, Cc-ing Andrew
message id: lkml.kernel.org/r/20181003105114.ga24...@embeddedor.com
---
On (10/03/18 21:26), Sergey Senozhatsky wrote:
> On (10/03/18 12:51), Gustavo A. R. Silva wrote:
> Replace "fallthru" with a proper "fall through" annotation.
>
> This fix is part of the ongoing efforts
Oh, Cc-ing Andrew
message id: lkml.kernel.org/r/20181003105114.ga24...@embeddedor.com
---
On (10/03/18 21:26), Sergey Senozhatsky wrote:
> On (10/03/18 12:51), Gustavo A. R. Silva wrote:
> Replace "fallthru" with a proper "fall through" annotation.
>
> This fix is part of the ongoing efforts
Hi Janusz,
On Wed, 3 Oct 2018 14:00:28 +0200
Janusz Krzysztofik wrote:
> Replace legacy callbacks with ->select_chip() and ->exec_op().
Thanks for working on that, that's really appreciated.
>
> Implementation of NAND_OP_WAITRDY_INSTR has been based on legacy
> nand_wait_ready(),
I don't
On Wed, 3 Oct 2018 14:14:28 +0200
Miguel Ojeda wrote:
> HI Dominique,
>
> On Wed, Oct 3, 2018 at 12:37 AM Dominique Martinet
> wrote:
> >
> > Miguel Ojeda wrote on Wed, Oct 03, 2018:
> > > As I have read, -next is supposed to be a vision of what the merge
> > > window will look like after
Hi Janusz,
On Wed, 3 Oct 2018 14:00:28 +0200
Janusz Krzysztofik wrote:
> Replace legacy callbacks with ->select_chip() and ->exec_op().
Thanks for working on that, that's really appreciated.
>
> Implementation of NAND_OP_WAITRDY_INSTR has been based on legacy
> nand_wait_ready(),
I don't
On Wed, 3 Oct 2018 14:14:28 +0200
Miguel Ojeda wrote:
> HI Dominique,
>
> On Wed, Oct 3, 2018 at 12:37 AM Dominique Martinet
> wrote:
> >
> > Miguel Ojeda wrote on Wed, Oct 03, 2018:
> > > As I have read, -next is supposed to be a vision of what the merge
> > > window will look like after
On 03/10/2018 09:46, Tao Ren wrote:
> On 10/2/18, 11:57 PM, "Linus Walleij"
> wrote:
>
>> My thought is go for (2) and do all changes in one patch :)
>
> No problem, Linus. One more question: looks like my first patch
> 4451d3f59f2a (fix set_next_event handler) is not merged back to
>
On 03/10/2018 09:46, Tao Ren wrote:
> On 10/2/18, 11:57 PM, "Linus Walleij"
> wrote:
>
>> My thought is go for (2) and do all changes in one patch :)
>
> No problem, Linus. One more question: looks like my first patch
> 4451d3f59f2a (fix set_next_event handler) is not merged back to
>
On (10/03/18 12:51), Gustavo A. R. Silva wrote:
> Replace "fallthru" with a proper "fall through" annotation.
>
> This fix is part of the ongoing efforts to enabling
> -Wimplicit-fallthrough
Hmm, comments as annotations?
> Signed-off-by: Gustavo A. R. Silva
Reviewed-by: Sergey Senozhatsky
On (10/03/18 12:51), Gustavo A. R. Silva wrote:
> Replace "fallthru" with a proper "fall through" annotation.
>
> This fix is part of the ongoing efforts to enabling
> -Wimplicit-fallthrough
Hmm, comments as annotations?
> Signed-off-by: Gustavo A. R. Silva
Reviewed-by: Sergey Senozhatsky
On (10/03/18 11:23), Petr Mladek wrote:
> On Fri 2018-09-28 18:53:04, Sergey Senozhatsky wrote:
> > CON_PRINTBUFFER console registration requires us to do several
> > preparation steps:
> > - Rollback console_seq to replay logbuf messages which were already
> > seen on other consoles;
> > - Set
On (10/03/18 11:23), Petr Mladek wrote:
> On Fri 2018-09-28 18:53:04, Sergey Senozhatsky wrote:
> > CON_PRINTBUFFER console registration requires us to do several
> > preparation steps:
> > - Rollback console_seq to replay logbuf messages which were already
> > seen on other consoles;
> > - Set
Hello
On 10/02/2018 02:28 AM, Pavel Machek wrote:
> On Fri 2018-09-28 13:29:47, Dan Murphy wrote:
>> Remove support for the LM3697 LED device
>> from the ti-lmu. The LM3697 will be supported
>> via a stand alone LED driver.
>>
>> Signed-off-by: Dan Murphy
>
> NAK, for reasons I explained
Hello
On 10/02/2018 02:28 AM, Pavel Machek wrote:
> On Fri 2018-09-28 13:29:47, Dan Murphy wrote:
>> Remove support for the LM3697 LED device
>> from the ti-lmu. The LM3697 will be supported
>> via a stand alone LED driver.
>>
>> Signed-off-by: Dan Murphy
>
> NAK, for reasons I explained
when the kernel inits a SE, its quite possible we have pending interrupts
from bootloaders which did not handle/clear them. So do this in kernel at
the SE init, to avoid some of it causing bad behavior, while at it also
club all the register writes needed to clear the se irqs into a function
to
when the kernel inits a SE, its quite possible we have pending interrupts
from bootloaders which did not handle/clear them. So do this in kernel at
the SE init, to avoid some of it causing bad behavior, while at it also
club all the register writes needed to clear the se irqs into a function
to
Fix a TURBOchannel support regression with commit 205e1b7f51e4
("dma-mapping: warn when there is no coherent_dma_mask") that caused
coherent DMA allocations to produce a warning such as:
defxx: v1.11 2014/07/01 Lawrence V. Stefani and others
tc1: DEFTA at MMIO addr = 0x1e90, IRQ = 20,
Fix a TURBOchannel support regression with commit 205e1b7f51e4
("dma-mapping: warn when there is no coherent_dma_mask") that caused
coherent DMA allocations to produce a warning such as:
defxx: v1.11 2014/07/01 Lawrence V. Stefani and others
tc1: DEFTA at MMIO addr = 0x1e90, IRQ = 20,
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1056539 ("Missing break in switch")
Signed-off-by: Gustavo A. R. Silva
---
drivers/spi/spi-pxa2xx.c | 1 +
1 file changed, 1 insertion(+)
diff --git
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1056539 ("Missing break in switch")
Signed-off-by: Gustavo A. R. Silva
---
drivers/spi/spi-pxa2xx.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Hello
On 10/03/2018 07:00 AM, Dan Murphy wrote:
> Hello
>
> On 10/02/2018 05:07 PM, Pavel Machek wrote:
>> Hi!
>>
We have debated this over and over and now we have 3 different
implementations
available we need to collude on which one we want to support.
Jacek I defer
Hello
On 10/03/2018 07:00 AM, Dan Murphy wrote:
> Hello
>
> On 10/02/2018 05:07 PM, Pavel Machek wrote:
>> Hi!
>>
We have debated this over and over and now we have 3 different
implementations
available we need to collude on which one we want to support.
Jacek I defer
On Tue, Oct 02, 2018 at 01:42:38PM +, Leonard Crestez wrote:
> This turns the phy off and on again instead of leaving it up from uboot
> and it doesn't work for some reason. However looking at
> reg_fixed_voltage_probe introducing an edge seems to be intentional for
> regulators which are not
On Tue, Oct 02, 2018 at 01:42:38PM +, Leonard Crestez wrote:
> This turns the phy off and on again instead of leaving it up from uboot
> and it doesn't work for some reason. However looking at
> reg_fixed_voltage_probe introducing an edge seems to be intentional for
> regulators which are not
On Tue, Oct 02, 2018 at 02:58:00PM +0530, Nayna Jain wrote:
>
>
> On 10/02/2018 06:12 AM, Jarkko Sakkinen wrote:
> > On Sat, Sep 29, 2018 at 01:30:20AM +0300, Tomas Winkler wrote:
> > > Move tpm1_pcr_extend to tpm1-cmd.c and remove
> > > unused pcrextend_header structure and
> > >
On Tue, Oct 02, 2018 at 02:58:00PM +0530, Nayna Jain wrote:
>
>
> On 10/02/2018 06:12 AM, Jarkko Sakkinen wrote:
> > On Sat, Sep 29, 2018 at 01:30:20AM +0300, Tomas Winkler wrote:
> > > Move tpm1_pcr_extend to tpm1-cmd.c and remove
> > > unused pcrextend_header structure and
> > >
On Tue, Oct 02, 2018 at 04:58:25AM +, Winkler, Tomas wrote:
>
>
> >
> > On Sat, Sep 29, 2018 at 01:30:26AM +0300, Tomas Winkler wrote:
> > > Add tpm2_pcr_extend() function to tpm2-cmd.c with signature required
> > > by tpm-interface.c. It wraps the original open code implementation.
> > >
On Tue, Oct 02, 2018 at 04:58:25AM +, Winkler, Tomas wrote:
>
>
> >
> > On Sat, Sep 29, 2018 at 01:30:26AM +0300, Tomas Winkler wrote:
> > > Add tpm2_pcr_extend() function to tpm2-cmd.c with signature required
> > > by tpm-interface.c. It wraps the original open code implementation.
> > >
Hello
On 10/02/2018 05:07 PM, Pavel Machek wrote:
> Hi!
>
>>> We have debated this over and over and now we have 3 different
>>> implementations
>>> available we need to collude on which one we want to support.
>>>
>>> Jacek I defer to you and Pavel since you are both LED maintainers.
>>>
>>> I
Hello
On 10/02/2018 05:07 PM, Pavel Machek wrote:
> Hi!
>
>>> We have debated this over and over and now we have 3 different
>>> implementations
>>> available we need to collude on which one we want to support.
>>>
>>> Jacek I defer to you and Pavel since you are both LED maintainers.
>>>
>>> I
Replace legacy callbacks with ->select_chip() and ->exec_op().
Implementation of NAND_OP_WAITRDY_INSTR has been based on legacy
nand_wait_ready(), otherwise that function would probabaly have to be
reimplemented inside the driver. Hence, legacy callback ->dev_ready()
is still used.
Use of
Replace legacy callbacks with ->select_chip() and ->exec_op().
Implementation of NAND_OP_WAITRDY_INSTR has been based on legacy
nand_wait_ready(), otherwise that function would probabaly have to be
reimplemented inside the driver. Hence, legacy callback ->dev_ready()
is still used.
Use of
On Wed, Oct 03, 2018 at 03:10:58AM -0700, Joe Perches wrote:
> On Wed, 2018-10-03 at 11:00 +0300, Andy Shevchenko wrote:
> > On Sat, Sep 29, 2018 at 12:54 AM Joe Perches wrote:
> > > Please fix this defect appropriately.
> > >
> > > linux-next MAINTAINERS section:
> > >
> > > 7441
On Wed, Oct 03, 2018 at 03:10:58AM -0700, Joe Perches wrote:
> On Wed, 2018-10-03 at 11:00 +0300, Andy Shevchenko wrote:
> > On Sat, Sep 29, 2018 at 12:54 AM Joe Perches wrote:
> > > Please fix this defect appropriately.
> > >
> > > linux-next MAINTAINERS section:
> > >
> > > 7441
This removes the entry for pmc_core.h file in the MAINTAINERS as the
file is already removed by a previous commit.
"platform/x86: intel_pmc_core: Remove unused header file"
Reported-by: Joe Perches
Signed-off-by: Rajneesh Bhardwaj
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff
This removes the entry for pmc_core.h file in the MAINTAINERS as the
file is already removed by a previous commit.
"platform/x86: intel_pmc_core: Remove unused header file"
Reported-by: Joe Perches
Signed-off-by: Rajneesh Bhardwaj
---
MAINTAINERS | 1 -
1 file changed, 1 deletion(-)
diff
On Wed, Oct 03, 2018 at 10:55:19AM +0200, Jiri Kosina wrote:
> Greg,
>
> please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
>
> to receive HID subsystem fixes
Now pulled, thanks.
greg k-h
On Wed, Oct 03, 2018 at 10:55:19AM +0200, Jiri Kosina wrote:
> Greg,
>
> please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
>
> to receive HID subsystem fixes
Now pulled, thanks.
greg k-h
On Tue, 2018-10-02 at 21:56 +0200, Linus Walleij wrote:
> On Tue, Oct 2, 2018 at 8:37 PM Leonard Crestez <
> leonard.cres...@nxp.com> wrote:
>
> > This issue was exposed by commit efdfeb079cc3 ("regulator: fixed:
> > Convert to use GPIO descriptor only") which causes the "gpios"
> > property
> >
On Tue, 2018-10-02 at 21:56 +0200, Linus Walleij wrote:
> On Tue, Oct 2, 2018 at 8:37 PM Leonard Crestez <
> leonard.cres...@nxp.com> wrote:
>
> > This issue was exposed by commit efdfeb079cc3 ("regulator: fixed:
> > Convert to use GPIO descriptor only") which causes the "gpios"
> > property
> >
On Wed 03-10-18 17:07:13, Anshuman Khandual wrote:
>
>
> On 10/03/2018 04:29 PM, Michal Hocko wrote:
[...]
> > It is not the platform that decides. That is the whole point of the
> > distinction. It is us to say what is feasible and what we want to
> > support. Do we want to support giga pages
On Wed 03-10-18 17:07:13, Anshuman Khandual wrote:
>
>
> On 10/03/2018 04:29 PM, Michal Hocko wrote:
[...]
> > It is not the platform that decides. That is the whole point of the
> > distinction. It is us to say what is feasible and what we want to
> > support. Do we want to support giga pages
On Tue, Oct 02, 2018 at 11:21:42AM +0300, Andy Shevchenko wrote:
> I would rather go with two prototypes to get()/set() a clump in the bitmap
> in a way when it's aligned and BITS_PER_LONG % clump_size == 0.
To make things much easier, restrict clump_size to the one
from the following set:
1,
On Tue, Oct 02, 2018 at 11:21:42AM +0300, Andy Shevchenko wrote:
> I would rather go with two prototypes to get()/set() a clump in the bitmap
> in a way when it's aligned and BITS_PER_LONG % clump_size == 0.
To make things much easier, restrict clump_size to the one
from the following set:
1,
Commit b5861e5cf2fcf83031ea3e26b0a69d887adf7d21 introduced a check on
the interrupt-window and NMI-window CPU execution controls in order to
inject an external interrupt vmexit before the first guest instruction
executes. However, when APIC virtualization is enabled the host does not
need a
Commit b5861e5cf2fcf83031ea3e26b0a69d887adf7d21 introduced a check on
the interrupt-window and NMI-window CPU execution controls in order to
inject an external interrupt vmexit before the first guest instruction
executes. However, when APIC virtualization is enabled the host does not
need a
hi Ulf
On 10/03/2018 11:22 AM, Ulf Hansson wrote:
+ Srinivas
for next series, I will add Srinivas
[...]
#ifdef CONFIG_DMA_ENGINE
-static void mmci_dma_setup(struct mmci_host *host)
+static inline void mmci_dma_release(struct mmci_host *host);
+
+int mmci_dmae_setup(struct mmci_host
hi Ulf
On 10/03/2018 11:22 AM, Ulf Hansson wrote:
+ Srinivas
for next series, I will add Srinivas
[...]
#ifdef CONFIG_DMA_ENGINE
-static void mmci_dma_setup(struct mmci_host *host)
+static inline void mmci_dma_release(struct mmci_host *host);
+
+int mmci_dmae_setup(struct mmci_host
Hi all,
Changes since 20181002:
The vfs tree gained conflicts against the f2fs tree.
The net-next tree gained a conflict against the net tree.
The bpf-next tree gained a build failure so I used the version from
next-20181002.
The devicetree tree gained a conflict against the c6x tree.
The
Hi all,
Changes since 20181002:
The vfs tree gained conflicts against the f2fs tree.
The net-next tree gained a conflict against the net tree.
The bpf-next tree gained a build failure so I used the version from
next-20181002.
The devicetree tree gained a conflict against the c6x tree.
The
The current rx peak function fails to read the data if size is
less than 4bytes.
Use memcpy_fromio to support data reads of size less than 4 bytes.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/qcom_glink_smem.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff
The current rx peak function fails to read the data if size is
less than 4bytes.
Use memcpy_fromio to support data reads of size less than 4 bytes.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/qcom_glink_smem.c | 12
1 file changed, 4 insertions(+), 8 deletions(-)
diff
On 10/03/2018 04:29 PM, Michal Hocko wrote:
> On Wed 03-10-18 15:28:23, Anshuman Khandual wrote:
>>
>>
>> On 10/03/2018 12:28 PM, Michal Hocko wrote:
>>> On Wed 03-10-18 07:46:27, Anshuman Khandual wrote:
On 10/02/2018 06:09 PM, Michal Hocko wrote:
> On Tue 02-10-18 17:45:28,
On 10/03/2018 04:29 PM, Michal Hocko wrote:
> On Wed 03-10-18 15:28:23, Anshuman Khandual wrote:
>>
>>
>> On 10/03/2018 12:28 PM, Michal Hocko wrote:
>>> On Wed 03-10-18 07:46:27, Anshuman Khandual wrote:
On 10/02/2018 06:09 PM, Michal Hocko wrote:
> On Tue 02-10-18 17:45:28,
On 10/2/18 8:27 PM, Waiman Long wrote:
On 10/02/2018 12:19 PM, Manfred Spraul wrote:
A bit related to the patch series that increases IPC_MNI:
(User space) id reuse create the risk of data corruption:
Process A: calls ipc function
Process A: sleeps just at the beginning of the syscall
Process
On 10/2/18 8:27 PM, Waiman Long wrote:
On 10/02/2018 12:19 PM, Manfred Spraul wrote:
A bit related to the patch series that increases IPC_MNI:
(User space) id reuse create the risk of data corruption:
Process A: calls ipc function
Process A: sleeps just at the beginning of the syscall
Process
On Tue, Oct 02, 2018 at 01:16:21PM +0200, Jiri Olsa wrote:
> On Tue, Oct 02, 2018 at 11:41:36AM +0100, John Garry wrote:
>
> SNIP
>
> > >
> > >
> > > ---
> > > diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
> > > index 1ec1d9bc2d63..fb2a0dab3978 100644
> > > ---
On Tue, Oct 02, 2018 at 01:16:21PM +0200, Jiri Olsa wrote:
> On Tue, Oct 02, 2018 at 11:41:36AM +0100, John Garry wrote:
>
> SNIP
>
> > >
> > >
> > > ---
> > > diff --git a/tools/perf/util/header.c b/tools/perf/util/header.c
> > > index 1ec1d9bc2d63..fb2a0dab3978 100644
> > > ---
Add support to wait on poll to get signal notifications.
Send POLLPRI mask to indicate the signal change.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/rpmsg_char.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/rpmsg/rpmsg_char.c
Add TICOMGET and TIOCMSET ioctl support for rpmsg char device nodes
to get/set the low level transport signals.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/rpmsg_char.c | 54 +++---
1 file changed, 51 insertions(+), 3 deletions(-)
diff --git
Add support to wait on poll to get signal notifications.
Send POLLPRI mask to indicate the signal change.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/rpmsg_char.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/drivers/rpmsg/rpmsg_char.c
Add TICOMGET and TIOCMSET ioctl support for rpmsg char device nodes
to get/set the low level transport signals.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/rpmsg_char.c | 54 +++---
1 file changed, 51 insertions(+), 3 deletions(-)
diff --git
Native signals over SMEM transport are different from Linux TIOCM signals.
Add a macro to convert signals when sent or received from clients.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/qcom_glink_native.c | 29 +
1 file changed, 29 insertions(+)
diff
Native signals over SMEM transport are different from Linux TIOCM signals.
Add a macro to convert signals when sent or received from clients.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/qcom_glink_native.c | 29 +
1 file changed, 29 insertions(+)
diff
Glink transport support signals to exchange state notification between
local and remote side clients. Adding support to send/receive the signal
command and notify the clients through callback and POLL notification.
Arun Kumar Neelakantam (5):
rpmsg: glink: Add GLINK signal support for RPMSG
Register a callback to get the signal notifications from rpmsg.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/rpmsg_char.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/rpmsg/rpmsg_char.c b/drivers/rpmsg/rpmsg_char.c
index a76b963..86003d5 100644
---
Glink transport support signals to exchange state notification between
local and remote side clients. Adding support to send/receive the signal
command and notify the clients through callback and POLL notification.
Arun Kumar Neelakantam (5):
rpmsg: glink: Add GLINK signal support for RPMSG
Register a callback to get the signal notifications from rpmsg.
Signed-off-by: Arun Kumar Neelakantam
---
drivers/rpmsg/rpmsg_char.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/rpmsg/rpmsg_char.c b/drivers/rpmsg/rpmsg_char.c
index a76b963..86003d5 100644
---
Add support to handle SMD signals to RPMSG over GLINK. SMD signals
mimic serial protocol signals to notify of ports opening and closing.
This change affects the rpmsg core, rpmsg char and glink drivers.
Signed-off-by: Chris Lew
Signed-off-by: Arun Kumar Neelakantam
---
Add support to handle SMD signals to RPMSG over GLINK. SMD signals
mimic serial protocol signals to notify of ports opening and closing.
This change affects the rpmsg core, rpmsg char and glink drivers.
Signed-off-by: Chris Lew
Signed-off-by: Arun Kumar Neelakantam
---
> -Original Message-
> From: Robin Murphy [mailto:robin.mur...@arm.com]
> Sent: 03 October 2018 11:37
> To: Shameerali Kolothum Thodi ;
> lorenzo.pieral...@arm.com
> Cc: will.dea...@arm.com; mark.rutl...@arm.com; Guohanjun (Hanjun Guo)
> ; John Garry ;
> pa...@codeaurora.org;
On Wed, Oct 03, 2018 at 01:20:44PM +0200, Håkon Bugge wrote:
> Hi Greg,
>
>
> I hope you will find this note appropriate.
>
> The stable cherry-pick of upstream commit ebeeb1ad9b8a ("rds: tcp: use
> rds_destroy_pending() to synchronize netns/module teardown and rds
> connection/workq
On Wed, Oct 03, 2018 at 01:20:44PM +0200, Håkon Bugge wrote:
> Hi Greg,
>
>
> I hope you will find this note appropriate.
>
> The stable cherry-pick of upstream commit ebeeb1ad9b8a ("rds: tcp: use
> rds_destroy_pending() to synchronize netns/module teardown and rds
> connection/workq
> -Original Message-
> From: Robin Murphy [mailto:robin.mur...@arm.com]
> Sent: 03 October 2018 11:37
> To: Shameerali Kolothum Thodi ;
> lorenzo.pieral...@arm.com
> Cc: will.dea...@arm.com; mark.rutl...@arm.com; Guohanjun (Hanjun Guo)
> ; John Garry ;
> pa...@codeaurora.org;
On Wed 03-10-18 12:17:52, Suzuki K Poulose wrote:
[...]
> I have been under the idea that all the checks at the same level could
> have the same indentation. (i.e, 2 tabs in this case for each). Looks
> like there is no rule about it. How about replacing it with a
> switch..case ?
I would simply
On Wed 03-10-18 12:17:52, Suzuki K Poulose wrote:
[...]
> I have been under the idea that all the checks at the same level could
> have the same indentation. (i.e, 2 tabs in this case for each). Looks
> like there is no rule about it. How about replacing it with a
> switch..case ?
I would simply
Hi Greg,
I hope you will find this note appropriate.
The stable cherry-pick of upstream commit ebeeb1ad9b8a ("rds: tcp: use
rds_destroy_pending() to synchronize netns/module teardown and rds
connection/workq management") provokes the following stack trace when running
with debug:
kernel:
Hi Greg,
I hope you will find this note appropriate.
The stable cherry-pick of upstream commit ebeeb1ad9b8a ("rds: tcp: use
rds_destroy_pending() to synchronize netns/module teardown and rds
connection/workq management") provokes the following stack trace when running
with debug:
kernel:
On Wed, Oct 3, 2018 at 12:17 AM Arnd Bergmann wrote:
>
> memremap() is declared in linux/io.h, not in asm/io.h, so we should
> include that header to avoid build errors:
>
> drivers/platform/x86/dcdbas.c: In function 'dcdbas_check_wsmt':
> drivers/platform/x86/dcdbas.c:572:15: error: implicit
On Wed, Oct 3, 2018 at 12:17 AM Arnd Bergmann wrote:
>
> memremap() is declared in linux/io.h, not in asm/io.h, so we should
> include that header to avoid build errors:
>
> drivers/platform/x86/dcdbas.c: In function 'dcdbas_check_wsmt':
> drivers/platform/x86/dcdbas.c:572:15: error: implicit
On 03/10/18 12:10, Anshuman Khandual wrote:
On 10/03/2018 03:52 PM, Suzuki K Poulose wrote:
On 02/10/18 13:56, Anshuman Khandual wrote:
On 10/02/2018 06:08 PM, Suzuki K Poulose wrote:
Hi Anshuman
On 02/10/18 13:15, Anshuman Khandual wrote:
Architectures like arm64 have PUD level
On 03/10/18 12:10, Anshuman Khandual wrote:
On 10/03/2018 03:52 PM, Suzuki K Poulose wrote:
On 02/10/18 13:56, Anshuman Khandual wrote:
On 10/02/2018 06:08 PM, Suzuki K Poulose wrote:
Hi Anshuman
On 02/10/18 13:15, Anshuman Khandual wrote:
Architectures like arm64 have PUD level
801 - 900 of 1152 matches
Mail list logo
