Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 161
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 18 7月, 2018 1 次提交
  3. 30 3月, 2018 1 次提交
  5. 26 3月, 2018 1 次提交
    • N
      kbuild: rename built-in.o to built-in.a · f49821ee
      由 Nicholas Piggin 提交于 
      Incremental linking is gone, so rename built-in.o to built-in.a, which
is the usual extension for archive files.

This patch does two things, first is a simple search/replace:

git grep -l 'built-in\.o' | xargs sed -i 's/built-in\.o/built-in\.a/g'

The second is to invert nesting of nested text manipulations to avoid
filtering built-in.a out from libs-y2:

-libs-y2 := $(filter-out %.a, $(patsubst %/, %/built-in.a, $(libs-y)))
+libs-y2 := $(patsubst %/, %/built-in.a, $(filter-out %.a, $(libs-y)))
Signed-off-by: NNicholas Piggin <npiggin@gmail.com>
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      f49821ee
  7. 16 12月, 2017 1 次提交
    • M
      kbuild: prepare to remove C files pre-generated by flex and bison · 033dba2e
      由 Masahiro Yamada 提交于 
      In Linux build system convention, pre-generated files are version-
controlled with a "_shipped" suffix.  During the kernel building,
they are simply shipped (copied) removing the suffix.

This approach can reduce external tool dependency for the kernel build,
but it is tedious to manually regenerate such artifacts from developers'
point of view.  (We need to do "make REGENERATE_PARSERS=1" every time
we touch real source files such as *.l, *.y)

Some months ago, I sent out RFC patches to run flex, bison, and gperf
during the build.

In the review and test, Linus noticed gperf-3.1 had changed the lookup
function prototype.  Then, the use of gperf in kernel was entirely
removed by commit bb3290d9 ("Remove gperf usage from toolchain").

This time, I tested several versions of flex and bison, and I was not
hit by any compatibility issue except a flaw in flex-2.6.3; if you
generate lexer for dtc and genksyms with flex-2.6.3, you will see
"yywrap redefined" warning.  This was not intentional, but a bug,
fixed by flex-2.6.4.  Otherwise, both flex and bison look fairly
stable for a long time.

This commit prepares some build rules to remove the _shipped files.
Also, document minimal requirement for flex and bison.

Rationale for the minimal version:
The -Wmissing-prototypes option of GCC warns "no previous prototype"
for lexers generated by flex-2.5.34 or older, so I chose 2.5.35 as the
required version for flex.  Flex-2.5.35 was released in 2008.  Bison
looks more stable.  I did not see any problem with bison-2.0, released
in 2004.  I did not test bison-1.x, but bison-2.0 should be old enough.

Tested flex versions:
  2.5.35
  2.5.36
  2.5.37
  2.5.39
  2.6.0
  2.6.1
  2.6.2
  2.6.3   (*)
  2.6.4

 (*) flex-2.6.3 causes "yywrap redefined" warning

Tested bison versions:
  2.0
  2.1
  2.2
  2.3
  2.4
  2.4.1
  2.5.1
  2.6
  2.6.1
  2.6.2
  2.6.3
  2.6.4
  2.6.5
  2.7
  2.7.1
  3.0
  3.0.1
  3.0.2
  3.0.3
  3.0.4
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      033dba2e
  9. 18 7月, 2017 2 次提交
  11. 30 6月, 2017 1 次提交
  13. 16 5月, 2017 1 次提交
  15. 07 5月, 2017 2 次提交
    • M
      docs: complete bumping minimal GNU Make version to 3.81 · 13e09881
      由 Max Filippov 提交于 
      Commit 37d69ee3 ("docs: bump minimal GNU Make version to 3.81")
changes one entry of GNU make version in the changes.rst, there's still
one more entry saying that one need version 3.80.  Fix that.
Signed-off-by: NMax Filippov <jcmvbkbc@gmail.com>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      13e09881
    • M
      docs: bump minimal GNU Make version to 3.81 · 37d69ee3
      由 Masahiro Yamada 提交于 
      Since 2014, you can't successfully build kernels with GNU Make version
3.80. Example errors:

  $ git describe
  v4.11
  $ make --version | head -1
  GNU Make 3.80
  $ make defconfig
    HOSTCC  scripts/basic/fixdep
  scripts/Makefile.host:135: *** missing separator.  Stop.
  make: *** [defconfig] Error 2
  $ make ARCH=arm64 help
  arch/arm64/Makefile:43: *** unterminated call to function `warning': missing `)'.  Stop.
  $ make help >/dev/null
  ./Documentation/Makefile.sphinx:25: Extraneous text after `else' directive
  ./Documentation/Makefile.sphinx:31: *** only one `else' per conditional.  Stop.
  make: *** [help] Error 2

The first breakage was introduced by commit c8589d1e ("kbuild:
handle multi-objs dependency appropriately").  Since then (i.e. v3.18),
GNU Make 3.80 has not been able to compile the kernel, but nobody has
ever complained aboutt (or noticed) it.

Even GNU Make 3.81 is more than 10 years old.  It would not hurt to
match the documentation with reality instead of fixing makefiles.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      37d69ee3
  17. 30 3月, 2017 1 次提交
  19. 09 3月, 2017 1 次提交
    • M
      docs-rst: automatically convert Graphviz and SVG images · db6ccf23
      由 Markus Heiser 提交于 
      This patch brings scalable figure, image handling and a concept to
embed *render* markups:

* DOT (http://www.graphviz.org)
* SVG

For image handling use the 'image' replacement::

    .. kernel-image::  svg_image.svg
       :alt:    simple SVG image

For figure handling use the 'figure' replacement::

    .. kernel-figure::  svg_image.svg
       :alt:    simple SVG image

       SVG image example

Embed *render* markups (or languages) like Graphviz's **DOT** is
provided by the *render* directive.::

  .. kernel-render:: DOT
     :alt: foobar digraph
     :caption: Embedded **DOT** (Graphviz) code.

     digraph foo {
      "bar" -> "baz";
     }

The *render* directive is a concept to integrate *render* markups and
languages, yet supported markups:

* DOT: render embedded Graphviz's **DOT**
* SVG: render embedded Scalable Vector Graphics (**SVG**)

Cc: Jani Nikula <jani.nikula@linux.intel.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Tested-by: NMauro Carvalho Chehab <mchehab@s-opensource.com>
Tested-by: NDaniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com> (v2 - v5)
Signed-off-by: Markus Heiser <markus.heiser@darmarit.de> (v1, v6)
Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      db6ccf23
  21. 28 10月, 2016 1 次提交
  23. 24 10月, 2016 1 次提交
  25. 21 9月, 2016 4 次提交
  27. 12 10月, 2015 1 次提交
  29. 25 9月, 2015 1 次提交
    • D
      MODSIGN: Change from CMS to PKCS#7 signing if the openssl is too old · 283e8ba2
      由 David Howells 提交于 
      The sign-file.c program actually uses CMS rather than PKCS#7 to sign a file
since that allows the target X.509 certificate to be specified by
subjectKeyId rather than by issuer + serialNumber.

However, older versions of the OpenSSL crypto library (such as may be found
in CentOS 5.11) don't support CMS.  Assume everything prior to
OpenSSL-1.0.0 doesn't support CMS and switch to using PKCS#7 in that case.

Further, the pre-1.0.0 OpenSSL only supports PKCS#7 signing with SHA1, so
give an error from the sign-file script if the caller requests anything
other than SHA1.

The compiler gives the following error with an OpenSSL crypto library
that's too old:

  HOSTCC  scripts/sign-file
scripts/sign-file.c:23:25: fatal error: openssl/cms.h: No such file or directory
 #include <openssl/cms.h>
Reported-by: NVinson Lee <vlee@twopensource.com>
Signed-off-by: NDavid Howells <dhowells@redhat.com>
Acked-by: NDavid Woodhouse <David.Woodhouse@intel.com>
      283e8ba2
  31. 28 8月, 2015 1 次提交
  33. 30 12月, 2014 1 次提交
  35. 10 12月, 2014 1 次提交
  37. 09 9月, 2014 2 次提交
  39. 13 7月, 2014 1 次提交
  41. 19 5月, 2014 1 次提交
  43. 28 11月, 2013 1 次提交
  45. 12 7月, 2011 1 次提交
  47. 23 3月, 2011 1 次提交
  49. 12 7月, 2010 1 次提交
  51. 26 3月, 2010 1 次提交
  53. 14 12月, 2009 1 次提交
  55. 19 6月, 2009 1 次提交
  57. 15 6月, 2009 1 次提交
  59. 29 5月, 2009 1 次提交
  61. 30 1月, 2009 1 次提交
  63. 03 8月, 2007 1 次提交
  65. 30 11月, 2006 1 次提交
  67. 25 9月, 2006 1 次提交