Remove the clever example about read-write lock because this type of
lock is not reccomended anymore (according to the very same document).
So there is no reason to teach cleaver things that people should not do.
Signed-off-by: Federico Vaga
---
Documentation/locking/spinlocks.rst | 12 -
Ignore this, the commit message is incorrect. I am sending a V3
On Saturday, September 7, 2019 12:48:41 PM CEST Federico Vaga wrote:
> Remove the clever example about read-write lock because these type of
> lock is not reccomended anymore (according to the very same document).
> So there is no rea
On Sat, 7 Sep 2019, Markus Heiser wrote:
> Am 07.09.19 um 20:04 schrieb Mauro Carvalho Chehab:
> > No idea. I would actually prefer to just remove the restriction, and let
> > the SPDX header to be anywhere inside the first comment block inside a
> > file [2].
>
> > That's basically how this threa
kunit wrapper script ('kunit.py') receives a sub-command (only 'run' for
now) as its argument. If no sub-command is given, it prints help
message and just quit. However, an example command in the kunit
documentation for a verification of kunit is missing the sub-command.
This commit fixes the exa
On Sat, Sep 7, 2019 at 9:15 PM Joe Perches wrote:
>
> Standard integer promotion is already done and %hx and %hhx is useless
> so do not encourage the use of %hh[xudi] or %h[xudi].
>
> As Linus said in:
> Link:
> https://lore.kernel.org/lkml/CAHk-=wgoxnmsj8GEVFJSvTwdnWm8wVJthefNk2n6+4TC=20...@mai
Am 07.09.19 um 20:04 schrieb Mauro Carvalho Chehab:
Em Sat, 7 Sep 2019 19:33:06 +0200
Markus Heiser escreveu:
An (uncatched) exception is thrown, when writing UTF-8 to a stream which
do not support UTF-8 .. this is not a crash, it mostly indicates that the
developper makes some wrong assumption
Em Sat, 7 Sep 2019 19:33:06 +0200
Markus Heiser escreveu:
> Am 07.09.19 um 18:22 schrieb Mauro Carvalho Chehab:
> > Em Sat, 7 Sep 2019 16:36:36 +0200
> > Markus Heiser escreveu:
> >
> >> Am 07.09.19 um 15:34 schrieb Jonathan Corbet:
> >>> On Thu, 5 Sep 2019 16:57:47 -0300
> >>> Mauro Carva
Am 07.09.19 um 18:22 schrieb Mauro Carvalho Chehab:
Em Sat, 7 Sep 2019 16:36:36 +0200
Markus Heiser escreveu:
Am 07.09.19 um 15:34 schrieb Jonathan Corbet:
On Thu, 5 Sep 2019 16:57:47 -0300
Mauro Carvalho Chehab wrote:
The description at Documentation/process/license-rules.rst is ve
Em Sat, 7 Sep 2019 16:36:36 +0200
Markus Heiser escreveu:
> Am 07.09.19 um 15:34 schrieb Jonathan Corbet:
> > On Thu, 5 Sep 2019 16:57:47 -0300
> > Mauro Carvalho Chehab wrote:
> >
> >> The description at Documentation/process/license-rules.rst is very strict
> >> with regards to the positi
Am 07.09.19 um 15:34 schrieb Jonathan Corbet:
On Thu, 5 Sep 2019 16:57:47 -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.
In the past several developers and maintainers
On Thu, 5 Sep 2019 16:57:47 -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.
>
> In the past several developers and maintainers interpreted it on a
> more permissive way,
In a normal piece of text the use of 'iff' does not guarantee a correct
interpretation because it is easy to confuse it for a typo (if or iff?).
I believe that IFF should not be used outside a logical/mathematical
expression. For this reason with this patch I am replacing 'iff' with
'if an only if
Remove the clever example about read-write lock because these type of
lock is not reccomended anymore (according to the very same document).
So there is no reason to teach cleaver things that people should not do.
(and by the way there was a little typo)
Signed-off-by: Federico Vaga
---
Documen
13 matches
Mail list logo
