Em Thu, 5 Sep 2019 13:40:08 -0600
Jonathan Corbet escreveu:
> On Thu, 5 Sep 2019 16:28:10 -0300
> Mauro Carvalho Chehab wrote:
>
> > I don't think we can count that python 3 uses utf-8 per default.
> >
> > I strongly suspect that, if one uses a Python3 version < 3.7, it will
> > still default
On Thu, 2019-09-05 at 16:57 -0300, Mauro Carvalho Chehab wrote:
> The description at Documentation/process/license-rules.rst is very strict
> with regards to the position where the SPDX tags should be.
[]
> PS.: I sent already a RFC version for those patches along with this
> thread:
>
>
> h
The author of the license-rules.rst file wanted to be very restrict
with regards to the location of the SPDX header. It says that
the SPDX header "shall be added at the first possible line in
a file which can contain a comment". Not happy with this already
restrictive requiement, it goes further:
Those extensions are released under GPLv2, as stated at the
:license: markup tag.
Add the corresponding SPDX tags for such license.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/sphinx/kernel_include.py | 1 +
Documentation/sphinx/rstFlatTable.py | 1 +
2 files changed, 2 insertions(
The description at Documentation/process/license-rules.rst is very strict
with regards to the position where the SPDX tags should be.
In the past several developers and maintainers interpreted it on a
more permissive way, placing the SPDX header between lines 1 to 15,
with are the ones which the
On Thu, 5 Sep 2019 16:28:10 -0300
Mauro Carvalho Chehab wrote:
> I don't think we can count that python 3 uses utf-8 per default.
>
> I strongly suspect that, if one uses a Python3 version < 3.7, it will
> still default to ASCII.
>
> On a quick look, the new UTF-8 mode was added on PEP-540:
>
Em Thu, 5 Sep 2019 06:57:01 -0600
Jonathan Corbet escreveu:
> On Thu, 5 Sep 2019 06:23:13 -0300
> Mauro Carvalho Chehab wrote:
>
> > Python's PEP-263 [1] dictates that an script that needs to default to
> > UTF-8 encoding has to follow this rule:
> >
> > 'Python will default to ASCII as s
On Thu, 2019-09-05 at 09:07 -0300, Mauro Carvalho Chehab wrote:
> There are currently 227 files that don't complain with the "up to line 3"
> rule, including COPYING (with should probably be excluded from the check).
>
> Patches are at:
>
> https://git.linuxtv.org/mchehab/experimental.git/l
Em Thu, 5 Sep 2019 16:17:23 +0200
Greg Kroah-Hartman escreveu:
> On Thu, Sep 05, 2019 at 06:57:01AM -0600, Jonathan Corbet wrote:
> > On Thu, 5 Sep 2019 06:23:13 -0300
> > Mauro Carvalho Chehab wrote:
> >
> > > Python's PEP-263 [1] dictates that an script that needs to default to
> > > UTF-8
On Thu, Sep 05, 2019 at 12:32:49PM +0800, Yafang Shao wrote:
> On Thu, Sep 5, 2019 at 4:42 AM Daniel Jordan
> wrote:
> > I wonder if we shouldn't just get rid of the whole script, it's hard to
> > remember to keep in sync with vmscan changes and I can't think of a way to
> > remedy that short of
On Thu, Sep 05, 2019 at 06:57:01AM -0600, Jonathan Corbet wrote:
> On Thu, 5 Sep 2019 06:23:13 -0300
> Mauro Carvalho Chehab wrote:
>
> > Python's PEP-263 [1] dictates that an script that needs to default to
> > UTF-8 encoding has to follow this rule:
> >
> > 'Python will default to ASCII a
On Thu, 5 Sep 2019 06:23:13 -0300
Mauro Carvalho Chehab wrote:
> Python's PEP-263 [1] dictates that an script that needs to default to
> UTF-8 encoding has to follow this rule:
>
> 'Python will default to ASCII as standard encoding if no other
>encoding hints are given.
>
>
Em Thu, 5 Sep 2019 11:27:03 +0200
Greg Kroah-Hartman escreveu:
> On Thu, Sep 05, 2019 at 06:23:13AM -0300, Mauro Carvalho Chehab wrote:
> > The author of the license-rules.rst file wanted to be very restrict
> > with regards to the location of the SPDX header. It says that
> > the SPDX header "sh
From: Stoica Cosmin-Stefan
Add initial version of device tree for S32V234-EVB, including nodes for the
4 Cortex-A53 cores, AIPS bus with UART modules, ARM architected timer and
Generic Interrupt Controller (GIC).
Keep SoC level separate from board level to let future boards with this SoC
share c
Hello,
NXP's S32V234[1] ("Treerunner") vision microprocessors are targeted for
high-performance, computationally intensive vision and sensor fusion
applications that require automotive safety levels. They include leading
edge Camera Vision modules like APEX-2, ISP and GPU. The S32V234-EVB and
S32V
For consistency reasons, spell the controller name as "LINFlexD" in
comments and documentation.
Signed-off-by: Stefan-Gabriel Mirea
---
Documentation/admin-guide/kernel-parameters.txt | 2 +-
drivers/tty/serial/Kconfig | 8
drivers/tty/serial/fsl_linflexuart.c
From: Stoica Cosmin-Stefan
Add documentation for the serial communication interface module (LINFlexD),
found in two instances on S32V234.
Signed-off-by: Stoica Cosmin-Stefan
Signed-off-by: Larisa Grigore
Signed-off-by: Stefan-Gabriel Mirea
Reviewed-by: Rob Herring
---
.../bindings/serial/fs
From: Mihaela Martinas
Add configuration option for the NXP S32 platform family in
Kconfig.platforms. For starters, the only SoC supported will be Treerunner
(S32V234), with a single execution target: the S32V234-EVB (rev 29288)
board.
Signed-off-by: Mihaela Martinas
Signed-off-by: Stoica Cosmi
From: Mihaela Martinas
Enable support for the S32V234 SoC, including the previously added UART
driver.
Signed-off-by: Mihaela Martinas
Signed-off-by: Adrian.Nitu
Signed-off-by: Stoica Cosmin-Stefan
Signed-off-by: Stefan-Gabriel Mirea
---
arch/arm64/configs/defconfig | 3 +++
1 file changed,
From: Eddy Petrișor
Add entry for the NXP S32V234 Customer Evaluation Board to the board/SoC
bindings.
Signed-off-by: Eddy Petrișor
Signed-off-by: Stefan-Gabriel Mirea
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/arm/fsl.yaml | 6 ++
1 file changed, 6 insertions(+)
dif
Hello Greg,
On 9/4/2019 10:53 AM, gre...@linuxfoundation.org wrote:
> On Fri, Aug 23, 2019 at 07:11:37PM +, Stefan-gabriel Mirea wrote:
>> For consistency reasons, spell the controller name as "LINFlexD" in
>> comments and documentation.
>>
>> Signed-off-by: Stefan-Gabriel Mirea
>> ---
>> Do
Those extensions are released under GPLv2, as stated at the
:license: markup tag.
Add the corresponding SPDX tags for such license.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/sphinx/kernel_include.py | 1 +
Documentation/sphinx/rstFlatTable.py | 1 +
2 files changed, 2 insertions(
Em Thu, 5 Sep 2019 11:27:03 +0200
Greg Kroah-Hartman escreveu:
> On Thu, Sep 05, 2019 at 06:23:13AM -0300, Mauro Carvalho Chehab wrote:
> > The author of the license-rules.rst file wanted to be very restrict
> > with regards to the location of the SPDX header. It says that
> > the SPDX header "sh
On Thu, Sep 05, 2019 at 06:23:13AM -0300, Mauro Carvalho Chehab wrote:
> The author of the license-rules.rst file wanted to be very restrict
> with regards to the location of the SPDX header. It says that
> the SPDX header "shall be added at the first possible line in
> a file which can contain a
The author of the license-rules.rst file wanted to be very restrict
with regards to the location of the SPDX header. It says that
the SPDX header "shall be added at the first possible line in
a file which can contain a comment". Not happy with this already
restrictive requiement, it goes further:
On Saturday, August 31, 2019 4:43:44 PM CEST Jonathan Corbet wrote:
> On Sat, 31 Aug 2019 15:41:16 +0200
>
> Federico Vaga wrote:
> > several CPU's and you want to use spinlocks you can potentially use
> >
> > -cheaper versions of the spinlocks. IFF you know that the spinlocks are
> > +cheaper
26 matches
Mail list logo
