linux/meta-openembedded.git/meta-oe/recipes-connectivity/rfkill, branch mickledore-next

recipes: Update LICENSE variable to use SPDX license identifiers

2022-03-05T01:41:45+00:00

Signed-off-by: Khem Raj

Convert to new override syntax

2021-08-03T17:21:25+00:00

This is the result of automated script (0.9.1) conversion: oe-core/scripts/contrib/convert-overrides.py . converting the metadata to use ":" as the override character instead of "_". Signed-off-by: Martin Jansa

rfkill: update to 1.0

2021-02-14T08:30:07+00:00

Signed-off-by: Oleksandr Kravchuk Signed-off-by: Khem Raj

rfkill: Clarify BSD license variant

2019-10-25T17:29:51+00:00

The License of rfkill is BSD-0-Clause. Signed-off-by: Christophe Priouzeau Signed-off-by: Khem Raj

rfkill: update to 0.5

2015-01-08T10:58:43+00:00

Also make SUMMARY a bit more useful. Signed-off-by: Paul Eggleton Signed-off-by: Martin Jansa

rfkill: fix the SRC_URI

2014-12-10T12:33:29+00:00

It has been changed to: http://www.kernel.org/pub/software/network/rfkill/ Signed-off-by: Jackie Huang Signed-off-by: Martin Jansa

meta-oe: use BPN in SRC_URI

2014-07-15T12:56:55+00:00

Fixed SRC_URI: * ${PN} -> ${BPN}, use ${BP} if it was ${PN}-${PV} * ${P} -> ${BP} Otherwise we would meet do_fetch errors when we do the multilib, native or nativesdk build. Signed-off-by: Robert Yang Signed-off-by: Martin Jansa

recipes: convert remaining SUMMARY/DESCRIPTION cosmetic issues

2014-02-23T22:20:02+00:00

Changes: - rename SUMMARY with length > 80 to DESCRIPTION - rename DESCRIPTION with length < 80 to (non present tag) SUMMARY - drop final point character at the end of SUMMARY string - remove trailing whitespace of SUMMARY line Note: don't bump PR Signed-off-by: Matthieu Crapet Signed-off-by: Martin Jansa

rfkill: Fix build when WORKDIR is included in some git checkout

2013-11-18T22:14:27+00:00

Signed-off-by: Martin Jansa

recipes: Unify indentation

2013-04-15T14:23:17+00:00

* This change is only aesthetic (unlike indentation in Python tasks). * Some recipes were using tabs. * Some were using 8 spaces. * Some were using mix or different number of spaces. * Make them consistently use 4 spaces everywhere. * Yocto styleguide advises to use tabs (but the only reason to keep tabs is the need to update a lot of recipes). Lately this advice was also merged into the styleguide on the OE wiki. * Using 4 spaces in both types of tasks is better because it's less error prone when someone is not sure if e.g. do_generate_toolchain_file() is Python or shell task and also allows to highlight every tab used in .bb, .inc, .bbappend, .bbclass as potentially bad (shouldn't be used for indenting of multiline variable assignments and cannot be used for Python tasks). * Don't indent closing quote on multiline variables we're quite inconsistent wheater it's first character on line under opening quote or under first non-whitespace character in previous line. Signed-off-by: Martin Jansa Acked-by: Koen Kooi