public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [PATCH 0/3] Bitbake fix, kernel-specific package naming
Date: Thu, 22 Nov 2018 13:58:37 +0100	[thread overview]
Message-ID: <cover.1542891520.git.jan.kiszka@siemens.com> (raw)

See patches for details.

Jan Kiszka (3):
  bitbake: Update to fixed master revision
  RECIPE-API-CHANGELOG: Reorder and capitalize sentences
  Append KERNEL_NAME to dependent custom modules and u-boot-script

 RECIPE-API-CHANGELOG.md                            |  73 +++++++++++----------
 bitbake/bin/toaster                                |   4 +-
 .../bitbake-user-manual-intro.xml                  |  13 +++-
 .../bitbake-user-manual-metadata.xml               |  31 ++++++++-
 .../bitbake-user-manual-ref-variables.xml          |  59 ++++++++++++++---
 .../figures/bb_multiconfig_files.png               | Bin 0 -> 19991 bytes
 bitbake/lib/bb/cooker.py                           |   9 +--
 bitbake/lib/bb/data_smart.py                       |   9 ++-
 bitbake/lib/bb/fetch2/__init__.py                  |   1 +
 bitbake/lib/bb/fetch2/git.py                       |  13 ++--
 bitbake/lib/bb/fetch2/gitsm.py                     |  71 ++++++++++----------
 bitbake/lib/bb/fetch2/npm.py                       |   2 +-
 bitbake/lib/bb/parse/ast.py                        |   2 +-
 bitbake/lib/bb/parse/parse_py/BBHandler.py         |   2 +-
 bitbake/lib/bb/server/process.py                   |  15 +++--
 bitbake/lib/bb/siggen.py                           |  10 +--
 bitbake/lib/bb/tests/fetch.py                      |   5 +-
 bitbake/lib/bb/utils.py                            |  31 ++++-----
 meta-isar/conf/local.conf.sample                   |   2 +-
 meta-isar/conf/machine/de0-nano-soc.conf           |   2 +-
 meta-isar/conf/multiconfig/bananapi-stretch.conf   |   2 +-
 .../recipes-bsp/u-boot-script/u-boot-script_1.0.bb |   2 +
 meta/recipes-kernel/linux-module/module.inc        |   2 +
 23 files changed, 227 insertions(+), 133 deletions(-)

-- 
2.16.4


             reply	other threads:[~2018-11-22 12:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22 12:58 Jan Kiszka [this message]
2018-11-22 12:58 ` [PATCH 1/3] bitbake: Update to fixed master revision Jan Kiszka
2018-11-22 13:12   ` Henning Schild
2018-11-22 13:14     ` Jan Kiszka
2018-11-22 13:18       ` Henning Schild
2018-11-22 13:25         ` Jan Kiszka
2018-11-22 13:58           ` Henning Schild
2018-11-22 14:28             ` Jan Kiszka
2018-11-22 15:36               ` Henning Schild
2018-11-22 15:42                 ` Jan Kiszka
2018-11-22 13:19       ` Jan Kiszka
2018-11-23 11:27   ` Maxim Yu. Osipov
2018-11-22 12:58 ` [PATCH 2/3] RECIPE-API-CHANGELOG: Reorder and capitalize sentences Jan Kiszka
2018-11-22 13:10   ` [PATCH v2 " Jan Kiszka
2018-11-23 11:28     ` Maxim Yu. Osipov
2018-11-22 12:58 ` [PATCH 3/3] Append KERNEL_NAME to dependent custom modules and u-boot-script Jan Kiszka
2018-11-23 11:28   ` Maxim Yu. Osipov
2018-11-23 11:34     ` Jan Kiszka
2018-11-23 11:38       ` [PATCH v2 " Jan Kiszka
2018-11-23 12:35         ` Maxim Yu. Osipov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1542891520.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox