On 09/07/2018 03:48 PM, Andy Lutomirski wrote:
>>
>> For part of the page fault handler, "error_code" does exactly
>> match PFEC. But, during later parts, it diverges and starts to
>> mean something a bit different.
>>
>> Give it two names for its two jobs.
> How hard would it be to just remove
On 09/07/2018 03:48 PM, Andy Lutomirski wrote:
>>
>> For part of the page fault handler, "error_code" does exactly
>> match PFEC. But, during later parts, it diverges and starts to
>> mean something a bit different.
>>
>> Give it two names for its two jobs.
> How hard would it be to just remove
On Tue, Sep 04, 2018 at 11:24:57AM +0100, Srinivas Kandagatla wrote:
> This patch add new bindings required to support MBHC
> (Multi Button Headset Control) block in the codec.
> This block is used for jack insert/removal detection,
> headset type detection and 8 button press/release events.
>
>
On Tue, Sep 04, 2018 at 11:24:57AM +0100, Srinivas Kandagatla wrote:
> This patch add new bindings required to support MBHC
> (Multi Button Headset Control) block in the codec.
> This block is used for jack insert/removal detection,
> headset type detection and 8 button press/release events.
>
>
On Tue, 4 Sep 2018 11:24:48 +0100, Srinivas Kandagatla wrote:
> This patch updates wcd9335 bindings with recommended properties.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> .../devicetree/bindings/sound/qcom,wcd9335.txt | 10 +-
> 1 file changed, 5 insertions(+), 5
On Tue, 4 Sep 2018 11:24:48 +0100, Srinivas Kandagatla wrote:
> This patch updates wcd9335 bindings with recommended properties.
>
> Signed-off-by: Srinivas Kandagatla
> ---
> .../devicetree/bindings/sound/qcom,wcd9335.txt | 10 +-
> 1 file changed, 5 insertions(+), 5
On Mon, Sep 03, 2018 at 05:22:39PM +0530, Rohit kumar wrote:
> Add devicetree bindings documentation file for Qualcomm
> Technolgies Inc ADSP Peripheral Image Loader.
>
> Signed-off-by: Rohit kumar
> ---
> .../bindings/remoteproc/qcom,adsp-pil.txt | 123
> +
> 1
On Mon, Sep 03, 2018 at 05:22:39PM +0530, Rohit kumar wrote:
> Add devicetree bindings documentation file for Qualcomm
> Technolgies Inc ADSP Peripheral Image Loader.
>
> Signed-off-by: Rohit kumar
> ---
> .../bindings/remoteproc/qcom,adsp-pil.txt | 123
> +
> 1
Hi Philipp,
I need to make the reset controller on the SoCFPGA platform initialize
early. I have one solution which is similar to what reset-sunxi is
doing, making the "altr,rst-mgr" initialize early in a separate
reset-socfpga.c but using the reset-simple operations.
I'm guessing SoCFPGA may
Hi Philipp,
I need to make the reset controller on the SoCFPGA platform initialize
early. I have one solution which is similar to what reset-sunxi is
doing, making the "altr,rst-mgr" initialize early in a separate
reset-socfpga.c but using the reset-simple operations.
I'm guessing SoCFPGA may
cpuidle_get_last_residency() is just a wrapper for retrieves
device's last_residency, it's also weirdly the only
wrapper function for accessing cpuidle_* struct member,
and my best guess is it could be a leftover from v2.x
Anyhow, since the only two users(ladder and menu governor)
can access
cpuidle_get_last_residency() is just a wrapper for retrieves
device's last_residency, it's also weirdly the only
wrapper function for accessing cpuidle_* struct member,
and my best guess is it could be a leftover from v2.x
Anyhow, since the only two users(ladder and menu governor)
can access
On Fri, 31 Aug 2018 12:20:38 -0700, Florian Fainelli wrote:
> Document the Broadcom roboswitch Switch Register Access Block interrupt
> lines and additional register base addresses for port mux configuration
> and SGMII status/configuration registers.
>
> Signed-off-by: Florian Fainelli
> ---
>
On Fri, 31 Aug 2018 12:20:38 -0700, Florian Fainelli wrote:
> Document the Broadcom roboswitch Switch Register Access Block interrupt
> lines and additional register base addresses for port mux configuration
> and SGMII status/configuration registers.
>
> Signed-off-by: Florian Fainelli
> ---
>
On Thu, Aug 30, 2018 at 08:02:05PM +0200, Krzysztof Kozlowski wrote:
> Samsung Exynos SoCs and boards related bindings evolved since the initial
> introduction, but initially the bindings were minimal and a bit incomplete
> (they never described all the hardware modules available in the SoCs).
>
On Thu, Aug 30, 2018 at 08:02:05PM +0200, Krzysztof Kozlowski wrote:
> Samsung Exynos SoCs and boards related bindings evolved since the initial
> introduction, but initially the bindings were minimal and a bit incomplete
> (they never described all the hardware modules available in the SoCs).
>
Hi zhong,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.19-rc3 next-20180910]
[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/linux
Hi zhong,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.19-rc3 next-20180910]
[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/linux
Jacek
On 09/10/2018 02:07 PM, Jacek Anaszewski wrote:
> Dan, Pavel,
>
> On 09/10/2018 04:37 PM, Dan Murphy wrote:
>> Jacek
>>
>> On 09/08/2018 02:53 PM, Jacek Anaszewski wrote:
>>> Dan,
>>>
>>> On 09/07/2018 03:52 PM, Dan Murphy wrote:
>>> [...]
>
>> And I think Jacek pointed out that
Jacek
On 09/10/2018 02:07 PM, Jacek Anaszewski wrote:
> Dan, Pavel,
>
> On 09/10/2018 04:37 PM, Dan Murphy wrote:
>> Jacek
>>
>> On 09/08/2018 02:53 PM, Jacek Anaszewski wrote:
>>> Dan,
>>>
>>> On 09/07/2018 03:52 PM, Dan Murphy wrote:
>>> [...]
>
>> And I think Jacek pointed out that
GPIOs with no kernel drivers can still be used from user space, don't
request them from the board file.
Signed-off-by: Janusz Krzysztofik
---
arch/arm/mach-omap1/board-ams-delta.c | 40 +--
1 file changed, 1 insertion(+), 39 deletions(-)
diff --git
GPIOs with no kernel drivers can still be used from user space, don't
request them from the board file.
Signed-off-by: Janusz Krzysztofik
---
arch/arm/mach-omap1/board-ams-delta.c | 40 +--
1 file changed, 1 insertion(+), 39 deletions(-)
diff --git
Hi Aaron,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.19-rc3 next-20180910]
[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
Hi Aaron,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.19-rc3 next-20180910]
[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
On Thu, 30 Aug 2018 16:13:48 +0800, Hanjie Lin wrote:
> From: Yue Wang
>
> The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
> PCI core. This patch adds documentation for the DT bindings in Meson PCIe
> controller.
>
> Signed-off-by: Yue Wang
> Signed-off-by: Hanjie
On Thu, 30 Aug 2018 16:13:48 +0800, Hanjie Lin wrote:
> From: Yue Wang
>
> The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
> PCI core. This patch adds documentation for the DT bindings in Meson PCIe
> controller.
>
> Signed-off-by: Yue Wang
> Signed-off-by: Hanjie
On Mon, 10 Sep 2018, Anup Patel wrote:
> On Mon, Sep 10, 2018 at 10:09 PM, Christoph Hellwig
> wrote:
> > On Mon, Sep 10, 2018 at 10:05:42PM +0530, Anup Patel wrote:
> >> I am quite sure RISC-V spec does not restrict the use of other
> >> local interrupts. Different CPU implementations can have
On Mon, 10 Sep 2018, Anup Patel wrote:
> On Mon, Sep 10, 2018 at 10:09 PM, Christoph Hellwig
> wrote:
> > On Mon, Sep 10, 2018 at 10:05:42PM +0530, Anup Patel wrote:
> >> I am quite sure RISC-V spec does not restrict the use of other
> >> local interrupts. Different CPU implementations can have
On Mon, 10 Sep 2018, Schaufler, Casey wrote:
> Yes, It would require that this patch be tested against all the existing
> security modules that provide a ptrace_access_check hook. It's not like
> the security module writers don't have a bunch of locking issues to deal
> with.
Yeah, that was
On Mon, 10 Sep 2018, Schaufler, Casey wrote:
> Yes, It would require that this patch be tested against all the existing
> security modules that provide a ptrace_access_check hook. It's not like
> the security module writers don't have a bunch of locking issues to deal
> with.
Yeah, that was
Hi Simon,
Thank you for the updated set.
On 09/09/2018 12:38 PM, Simon Shields wrote:
> Hi,
>
> This patch series adds DT bindings (patch #1) and the corresponding driver
> (patch #2) for the Panasonic AN30259A 3-channel LED driver. AN30259A
> uses an internal clock for controlling
Hi Simon,
Thank you for the updated set.
On 09/09/2018 12:38 PM, Simon Shields wrote:
> Hi,
>
> This patch series adds DT bindings (patch #1) and the corresponding driver
> (patch #2) for the Panasonic AN30259A 3-channel LED driver. AN30259A
> uses an internal clock for controlling
From: Sai Praneeth
There may exist some buggy UEFI firmware implementations that access efi
memory regions other than EFI_RUNTIME_SERVICES_ even after
the kernel has assumed control of the platform. This violates UEFI
specification. Hence, provide a efi specific page fault handler which
recovers
From: Sai Praneeth
There may exist some buggy UEFI firmware implementations that access efi
memory regions other than EFI_RUNTIME_SERVICES_ even after
the kernel has assumed control of the platform. This violates UEFI
specification. Hence, provide a efi specific page fault handler which
recovers
On Mon, Sep 10, 2018 at 12:26:58PM -0700, Tony Lindgren wrote:
> * Guenter Roeck [180910 18:35]:
> > On Mon, Sep 10, 2018 at 09:08:36AM -0700, Tony Lindgren wrote:
> > > OK thanks for tracking that down, next-20180910 boots again
> > > for me.
> > >
> >
On Mon, Sep 10, 2018 at 12:26:58PM -0700, Tony Lindgren wrote:
> * Guenter Roeck [180910 18:35]:
> > On Mon, Sep 10, 2018 at 09:08:36AM -0700, Tony Lindgren wrote:
> > > OK thanks for tracking that down, next-20180910 boots again
> > > for me.
> > >
> >
On Tue, Jul 24, 2018 at 04:12:50PM +0530, Taniya Das wrote:
> The CPUfreq HW present in some QCOM chipsets offloads the steps necessary
> for changing the frequency of CPUs. The driver implements the cpufreq
> driver interface for this hardware engine.
>
> Signed-off-by: Saravana Kannan
>
On Tue, Jul 24, 2018 at 04:12:50PM +0530, Taniya Das wrote:
> The CPUfreq HW present in some QCOM chipsets offloads the steps necessary
> for changing the frequency of CPUs. The driver implements the cpufreq
> driver interface for this hardware engine.
>
> Signed-off-by: Saravana Kannan
>
> -Original Message-
> From: Jiri Kosina [mailto:ji...@kernel.org]
> Sent: Monday, September 10, 2018 12:14 PM
> To: Schaufler, Casey
> Cc: Thomas Gleixner ; Ingo Molnar ;
> Peter Zijlstra ; Josh Poimboeuf
> ; Andrea Arcangeli ;
> Woodhouse, David ; Andi Kleen ;
> Tim Chen ;
> -Original Message-
> From: Jiri Kosina [mailto:ji...@kernel.org]
> Sent: Monday, September 10, 2018 12:14 PM
> To: Schaufler, Casey
> Cc: Thomas Gleixner ; Ingo Molnar ;
> Peter Zijlstra ; Josh Poimboeuf
> ; Andrea Arcangeli ;
> Woodhouse, David ; Andi Kleen ;
> Tim Chen ;
* Guenter Roeck [180910 18:35]:
> On Mon, Sep 10, 2018 at 09:08:36AM -0700, Tony Lindgren wrote:
> > OK thanks for tracking that down, next-20180910 boots again
> > for me.
> >
>
> Did you try to shutdown and/or reboot ?
>
> You might see something like the att
* Guenter Roeck [180910 18:35]:
> On Mon, Sep 10, 2018 at 09:08:36AM -0700, Tony Lindgren wrote:
> > OK thanks for tracking that down, next-20180910 boots again
> > for me.
> >
>
> Did you try to shutdown and/or reboot ?
>
> You might see something like the att
Hi Olof,
> -Original Message-
> From: Olof Johansson [mailto:o...@lixom.net]
> Sent: Saturday, September 08, 2018 6:15 PM
> To: Jolly Shah
> Cc: ard.biesheu...@linaro.org; Ingo Molnar ; Greg Kroah-
> Hartman ; m...@codeblueprint.co.uk; Sudeep
> Holla ; hkallwe...@gmail.com; Kees Cook
> ;
Hi Olof,
> -Original Message-
> From: Olof Johansson [mailto:o...@lixom.net]
> Sent: Saturday, September 08, 2018 6:15 PM
> To: Jolly Shah
> Cc: ard.biesheu...@linaro.org; Ingo Molnar ; Greg Kroah-
> Hartman ; m...@codeblueprint.co.uk; Sudeep
> Holla ; hkallwe...@gmail.com; Kees Cook
> ;
Hi All,
Adding more clarification on top of what Michal said:
Here ioctl is not a system ioctl and just a eemi API like other interface APIs.
It cannot be called from userspace. Only Linux drivers can use this API for
defined ioctl operations. This API is meant for any platform specific
Hi All,
Adding more clarification on top of what Michal said:
Here ioctl is not a system ioctl and just a eemi API like other interface APIs.
It cannot be called from userspace. Only Linux drivers can use this API for
defined ioctl operations. This API is meant for any platform specific
On Mon, 10 Sep 2018, Schaufler, Casey wrote:
> Why are you dropping the LSM check here, when in v4 you fixed the
> SELinux audit locking issue? We can avoid introducing an LSM hook
> and all the baggage around it if you can do the security_ptrace_access_check()
> here.
So what guarantees that
On Mon, 10 Sep 2018, Schaufler, Casey wrote:
> Why are you dropping the LSM check here, when in v4 you fixed the
> SELinux audit locking issue? We can avoid introducing an LSM hook
> and all the baggage around it if you can do the security_ptrace_access_check()
> here.
So what guarantees that
From: Tom Zanussi
Currently, the onmatch action data binds the onmatch action to data
related to synthetic event generation. Since we want to allow the
onmatch handler to potentially invoke a different action, and because
we expect other handlers to generate synthetic events, we need to
From: Tom Zanussi
Currently, the onmatch action data binds the onmatch action to data
related to synthetic event generation. Since we want to allow the
onmatch handler to potentially invoke a different action, and because
we expect other handlers to generate synthetic events, we need to
From: Tom Zanussi
Currently, tracing snapshots are context-free - they capture the ring
buffer contents at the time the tracing_snapshot() function was
invoked, and nothing else. Additionally, they're always taken
unconditionally - the calling code can decide whether or not to take a
snapshot,
From: Tom Zanussi
Currently, tracing snapshots are context-free - they capture the ring
buffer contents at the time the tracing_snapshot() function was
invoked, and nothing else. Additionally, they're always taken
unconditionally - the calling code can decide whether or not to take a
snapshot,
From: Tom Zanussi
The hist trigger action code currently implements two essentially
hard-coded pairs of 'actions' - onmax(), which tracks a variable and
saves some event fields when a max is hit, and onmatch(), which is
hard-coded to generate a synthetic event.
These hardcoded pairs (track
From: Tom Zanussi
The hist trigger action code currently implements two essentially
hard-coded pairs of 'actions' - onmax(), which tracks a variable and
saves some event fields when a max is hit, and onmatch(), which is
hard-coded to generate a synthetic event.
These hardcoded pairs (track
From: Tom Zanussi
Add support for hist:handlerXXX($var).snapshot(), which will take a
snapshot of the current trace buffer whenever handlerXXX is hit.
As a first user, this also adds snapshot() action support for the
onmax() handler i.e. hist:onmax($var).snapshot().
Signed-off-by: Tom Zanussi
From: Tom Zanussi
Add support for a hist:onchange($var) handler, similar to the onmax()
handler but triggering whenever there's any change in $var, not just a
max.
Signed-off-by: Tom Zanussi
---
Documentation/trace/histogram.txt | 97 +++
From: Tom Zanussi
Add support for hist:handlerXXX($var).snapshot(), which will take a
snapshot of the current trace buffer whenever handlerXXX is hit.
As a first user, this also adds snapshot() action support for the
onmax() handler i.e. hist:onmax($var).snapshot().
Signed-off-by: Tom Zanussi
From: Tom Zanussi
Add support for a hist:onchange($var) handler, similar to the onmax()
handler but triggering whenever there's any change in $var, not just a
max.
Signed-off-by: Tom Zanussi
---
Documentation/trace/histogram.txt | 97 +++
From: Tom Zanussi
Add a 'trace(synthetic_event_name, params)' alternative to
synthetic_event_name(params).
Currently, the syntax used for generating synthetic events is to
invoke synthetic_event_name(params) i.e. use the synthetic event name
as a function call.
Users requested a new form that
From: Tom Zanussi
Add a 'trace(synthetic_event_name, params)' alternative to
synthetic_event_name(params).
Currently, the syntax used for generating synthetic events is to
invoke synthetic_event_name(params) i.e. use the synthetic event name
as a function call.
Users requested a new form that
From: Tom Zanussi
Future patches will want to print a histogram key outside a histogram
- add and use hist_trigger_print_key() for that purpose.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)
diff
From: Tom Zanussi
The action refactor code allowed actions and handlers to be separated,
but the existing onmax handler and save action code is still not
flexible enough to handle arbitrary coupling. This change generalizes
them and in the process makes additional handlers and actions easier
to
From: Tom Zanussi
Future patches will want to print a histogram key outside a histogram
- add and use hist_trigger_print_key() for that purpose.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace_events_hist.c | 19 +++
1 file changed, 15 insertions(+), 4 deletions(-)
diff
From: Tom Zanussi
The action refactor code allowed actions and handlers to be separated,
but the existing onmax handler and save action code is still not
flexible enough to handle arbitrary coupling. This change generalizes
them and in the process makes additional handlers and actions easier
to
From: Tom Zanussi
Hi,
This is v4 of the hist trigger snapshot and onchange additions
patchset. It adds fixes to a couple problems noticed by Namhyung Kim,
as well as one minor syntax addition ('trace' keyword for generating
synthetic events) also suggested by him.
v3->v4 changes:
- added
From: Tom Zanussi
Hi,
This is v4 of the hist trigger snapshot and onchange additions
patchset. It adds fixes to a couple problems noticed by Namhyung Kim,
as well as one minor syntax addition ('trace' keyword for generating
synthetic events) also suggested by him.
v3->v4 changes:
- added
Dan, Pavel,
On 09/10/2018 04:37 PM, Dan Murphy wrote:
> Jacek
>
> On 09/08/2018 02:53 PM, Jacek Anaszewski wrote:
>> Dan,
>>
>> On 09/07/2018 03:52 PM, Dan Murphy wrote:
>> [...]
> And I think Jacek pointed out that the bindings references in this
> bindings
> don't even exist.
Dan, Pavel,
On 09/10/2018 04:37 PM, Dan Murphy wrote:
> Jacek
>
> On 09/08/2018 02:53 PM, Jacek Anaszewski wrote:
>> Dan,
>>
>> On 09/07/2018 03:52 PM, Dan Murphy wrote:
>> [...]
> And I think Jacek pointed out that the bindings references in this
> bindings
> don't even exist.
Hi Georgi,
This driver uses of_icc_get which is very likely to fail if it probes
before the interconnect provider. Would it be possible for icc_get to
return/differentiate both -EPROBE_DEFER and other errors to prevent the
driver to continually probe defer if the path doesn't actually exist
or
Hi Georgi,
This driver uses of_icc_get which is very likely to fail if it probes
before the interconnect provider. Would it be possible for icc_get to
return/differentiate both -EPROBE_DEFER and other errors to prevent the
driver to continually probe defer if the path doesn't actually exist
or
Hi Sergey, Jiri,
On Mon, 2018-09-10 at 14:14 +0900, Sergey Senozhatsky wrote:
> On (09/07/18 08:39), Jiri Slaby wrote:
> > > [ 244.944070]
> > > [ 244.944070] Showing all locks held in the system:
> > > [ 244.945558] 1 lock held by khungtaskd/18:
> > > [ 244.946495] #0: (ptrval)
Hi Sergey, Jiri,
On Mon, 2018-09-10 at 14:14 +0900, Sergey Senozhatsky wrote:
> On (09/07/18 08:39), Jiri Slaby wrote:
> > > [ 244.944070]
> > > [ 244.944070] Showing all locks held in the system:
> > > [ 244.945558] 1 lock held by khungtaskd/18:
> > > [ 244.946495] #0: (ptrval)
On Mon, Sep 10, 2018 at 8:33 PM Neil Armstrong wrote:
>
> Add missing chosen and memory nodes.
>
> Signed-off-by: Neil Armstrong
out of curiosity:
- does the bootloader add the memory node (meaning that this is just a
cosmetic bit)?
- setting stdout-path is always a good idea, without it you
On Mon, Sep 10, 2018 at 8:33 PM Neil Armstrong wrote:
>
> Add missing chosen and memory nodes.
>
> Signed-off-by: Neil Armstrong
out of curiosity:
- does the bootloader add the memory node (meaning that this is just a
cosmetic bit)?
- setting stdout-path is always a good idea, without it you
On Mon, Sep 10, 2018 at 10:18:33AM -0700, Tadeusz Struk wrote:
> Currently the TPM driver only supports blocking calls, which doesn't allow
> asynchronous IO operations to the TPM hardware.
> This patch changes it and adds support for nonblocking write and a new poll
> function to enable
On Mon, Sep 10, 2018 at 10:18:33AM -0700, Tadeusz Struk wrote:
> Currently the TPM driver only supports blocking calls, which doesn't allow
> asynchronous IO operations to the TPM hardware.
> This patch changes it and adds support for nonblocking write and a new poll
> function to enable
Hi Saravana,
On 2018-08-07 11:19, skan...@codeaurora.org wrote:
On 2018-08-02 14:00, skan...@codeaurora.org wrote:
On 2018-08-02 02:56, MyungJoo Ham wrote:
Many CPU architectures have caches that can scale independent of the
CPUs.
Frequency scaling of the caches is necessary to make sure the
Hi Saravana,
On 2018-08-07 11:19, skan...@codeaurora.org wrote:
On 2018-08-02 14:00, skan...@codeaurora.org wrote:
On 2018-08-02 02:56, MyungJoo Ham wrote:
Many CPU architectures have caches that can scale independent of the
CPUs.
Frequency scaling of the caches is necessary to make sure the
On Mon, Sep 10, 2018 at 11:51 PM Tony Lindgren wrote:
>
> Hi,
>
> I'm seeing a regression with Linux next with commit 7b6ec2ae877a
> ("fs: convert return type int to vm_fault_t") where apps can just
> hang.
>
> The reproducable test case I have is to remove a distro package
> and then add it back
On Mon, Sep 10, 2018 at 11:51 PM Tony Lindgren wrote:
>
> Hi,
>
> I'm seeing a regression with Linux next with commit 7b6ec2ae877a
> ("fs: convert return type int to vm_fault_t") where apps can just
> hang.
>
> The reproducable test case I have is to remove a distro package
> and then add it back
On Mon, Sep 10, 2018 at 8:39 PM Neil Armstrong wrote:
>
> Use the correct compatible for the AXG ethernet mac node.
>
> Signed-off-by: Neil Armstrong
I wonder if you should add a "Fixes" tag. apart from that:
Acked-by: Martin Blumenstingl
On Mon, Sep 10, 2018 at 8:39 PM Neil Armstrong wrote:
>
> Use the correct compatible for the AXG ethernet mac node.
>
> Signed-off-by: Neil Armstrong
I wonder if you should add a "Fixes" tag. apart from that:
Acked-by: Martin Blumenstingl
On Mon, Sep 10, 2018 at 10:18:28AM -0700, Tadeusz Struk wrote:
> Add a ptr to struct tpm_space to the file_priv and consolidate
> of the write operations for the two interfaces.
>
> Tested-by: Philip Tricca
> Signed-off-by: Tadeusz Struk
Reviewed-by: Jarkko Sakkinen
/Jarkko
On Mon, Sep 10, 2018 at 10:18:28AM -0700, Tadeusz Struk wrote:
> Add a ptr to struct tpm_space to the file_priv and consolidate
> of the write operations for the two interfaces.
>
> Tested-by: Philip Tricca
> Signed-off-by: Tadeusz Struk
Reviewed-by: Jarkko Sakkinen
/Jarkko
Use the correct compatible for the AXG ethernet mac node.
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
Use the correct compatible for the AXG ethernet mac node.
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
b/arch/arm64/boot/dts/amlogic/meson-axg.dtsi
On Thu, Sep 06, 2018 at 05:50:01PM -0700, Joe Perches wrote:
> On Thu, 2018-09-06 at 19:35 +0200, Miguel Ojeda wrote:
> > > Which one is right and why the kernel tree is polluted with C99-headers
> > > when they do not pass checkpatch.pl?
>
> checkpatch ignores c99 headers since 2016.
For
On Thu, Sep 06, 2018 at 05:50:01PM -0700, Joe Perches wrote:
> On Thu, 2018-09-06 at 19:35 +0200, Miguel Ojeda wrote:
> > > Which one is right and why the kernel tree is polluted with C99-headers
> > > when they do not pass checkpatch.pl?
>
> checkpatch ignores c99 headers since 2016.
For
Add missing chosen and memory nodes.
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-axg-s400.dts | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
b/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
index
Add missing chosen and memory nodes.
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-axg-s400.dts | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
b/arch/arm64/boot/dts/amlogic/meson-axg-s400.dts
index
On Thu, Sep 06, 2018 at 07:35:46PM +0200, Miguel Ojeda wrote:
> Hi Jarkko,
>
> On Thu, Sep 6, 2018 at 11:21 AM, Jarkko Sakkinen
> wrote:
> > There is another open. If I grep through the kernel tree I see SPDX
> > headers that are decorated both with C99- and C89-style comments. I
> > guess I
On Thu, Sep 06, 2018 at 07:35:46PM +0200, Miguel Ojeda wrote:
> Hi Jarkko,
>
> On Thu, Sep 6, 2018 at 11:21 AM, Jarkko Sakkinen
> wrote:
> > There is another open. If I grep through the kernel tree I see SPDX
> > headers that are decorated both with C99- and C89-style comments. I
> > guess I
using any.
> >
> > The default return value for security_fs_context_parse_param() should be
> > -ENOPARAM, both in security.h and security.c.
> >
> > I've fixed my tree and Al has pulled it, but we're now waiting on Stephen
> > Rothwell to refresh linux/next.
>
> OK
using any.
> >
> > The default return value for security_fs_context_parse_param() should be
> > -ENOPARAM, both in security.h and security.c.
> >
> > I've fixed my tree and Al has pulled it, but we're now waiting on Stephen
> > Rothwell to refresh linux/next.
>
> OK
On Mon 03 Sep 04:52 PDT 2018, Rohit kumar wrote:
> This adds Non PAS ADSP PIL driver for Qualcomm
> Technologies Inc SoCs.
> Added initial support for SDM845 with ADSP bootup and
> shutdown operation handled from Application Processor
> SubSystem(APSS).
>
> Signed-off-by: Rohit kumar
Thanks
On Mon 03 Sep 04:52 PDT 2018, Rohit kumar wrote:
> This adds Non PAS ADSP PIL driver for Qualcomm
> Technologies Inc SoCs.
> Added initial support for SDM845 with ADSP bootup and
> shutdown operation handled from Application Processor
> SubSystem(APSS).
>
> Signed-off-by: Rohit kumar
Thanks
Hi Rob,
On Fri, Sep 7, 2018 at 2:16 PM Christian Hewitt
wrote:
>
> This change adds the uart_A used by the brmcfmac sdio module in the
> WeTek Hub and WeTek Play 2 devices. meson_uart_probe seems to mandate
> an alias (without it, BT is not working) so this is also included.
>
> Signed-off-by:
Hi Rob,
On Fri, Sep 7, 2018 at 2:16 PM Christian Hewitt
wrote:
>
> This change adds the uart_A used by the brmcfmac sdio module in the
> WeTek Hub and WeTek Play 2 devices. meson_uart_probe seems to mandate
> an alias (without it, BT is not working) so this is also included.
>
> Signed-off-by:
On Thu, 30 Aug 2018 00:42:12 +0530, Sibi Sankar wrote:
> Remove the additional definition tag declared for WCSS sub-system
> under reset-names.
>
> Reviewed-by: Matthias Kaehlcke
> Signed-off-by: Sibi Sankar
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 4 ++--
> 1 file
On Thu, 30 Aug 2018 00:42:12 +0530, Sibi Sankar wrote:
> Remove the additional definition tag declared for WCSS sub-system
> under reset-names.
>
> Reviewed-by: Matthias Kaehlcke
> Signed-off-by: Sibi Sankar
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 4 ++--
> 1 file
301 - 400 of 1628 matches
Mail list logo
