All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Gherzan <andrei@gherzan.ro>
To: yoctoproject.org@herrie.org
Cc: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi] [patch] linux-raspberrypi_Rename_linux.inc_to_linux-rpi.inc
Date: Mon, 4 Apr 2016 21:28:46 +0200	[thread overview]
Message-ID: <20160404192846.GA6860@resin> (raw)
In-Reply-To: <5702B520.6060608@herrie.org>

[-- Attachment #1: Type: text/plain, Size: 2482 bytes --]

Hello,

On Mon, Apr 04, 2016 at 08:40:32PM +0200, Herrie wrote:
> From 164d6ec1b054fa241e65ac4961d204edd9965061 Mon Sep 17 00:00:00 2001
> From: Alan Stice <alan@alanstice.com>
> Date: Thu, 10 Mar 2016 08:52:07 -0800
> Subject: [PATCH] linux-raspberrypi: Rename linux.inc to linux-rpi.inc Rename
>  linux.inc to prevent it from impacting other machines while building
> multiple targets with same architecture sharing sstate.
>
> Signed-off-by: Alan Stice <alan@alanstice.com>
> Signed-off-by: Herman van Hazendonk <github.com@herrie.org>
> ---
>  recipes-kernel/linux/linux-raspberrypi.inc |   2 +-
>  recipes-kernel/linux/linux-rpi.inc         | 132
> +++++++++++++++++++++++++++++
>  recipes-kernel/linux/linux.inc             | 132
> -----------------------------
>  3 files changed, 133 insertions(+), 133 deletions(-)
>  create mode 100644 recipes-kernel/linux/linux-rpi.inc
>  delete mode 100644 recipes-kernel/linux/linux.inc
>
> diff --git a/recipes-kernel/linux/linux-raspberrypi.inc
> b/recipes-kernel/linux/linux-raspberrypi.inc
> index 24e7fe2..7ab1de2 100644
> --- a/recipes-kernel/linux/linux-raspberrypi.inc
> +++ b/recipes-kernel/linux/linux-raspberrypi.inc
> @@ -1,4 +1,4 @@
> -require linux.inc
> +require linux-rpi.inc
>  inherit linux-raspberrypi-base
>
>  DESCRIPTION = "Linux Kernel for Raspberry Pi"
> diff --git a/recipes-kernel/linux/linux-rpi.inc
> b/recipes-kernel/linux/linux-rpi.inc
> new file mode 100644
> index 0000000..fae78b7
> --- /dev/null
> +++ b/recipes-kernel/linux/linux-rpi.inc
> @@ -0,0 +1,132 @@
> +DESCRIPTION = "Linux Kernel"
> +SECTION = "kernel"
> +LICENSE = "GPLv2"
> +
> +LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
> +
> +inherit kernel siteinfo
> +require recipes-kernel/linux/linux-yocto.inc
> +
> +# Enable OABI compat for people stuck with obsolete userspace
> +ARM_KEEP_OABI ?= "1"
> +
> +# Quirk for udev greater or equal 141
> +UDEV_GE_141 ?= "1"
> +
> +# Set the verbosity of kernel messages during runtime
> +# You can define CMDLINE_DEBUG in your local.conf or distro.conf to
> override this behaviour
> +CMDLINE_DEBUG ?= '${@base_conditional("DISTRO_TYPE", "release", "quiet",
> "debug", d)}'

There seems to be issues in applying this patch as some of the lines get
wrapped to (probably) 80 chars or so. Could you please make sure you
send this patch in plain text and without this wrapping? Thanks man.

--
Andrei Gherzan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2016-04-04 19:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04 18:40 [meta-raspberrypi] [patch] linux-raspberrypi_Rename_linux.inc_to_linux-rpi.inc Herrie
2016-04-04 19:28 ` Andrei Gherzan [this message]
2016-04-04 19:45   ` Herrie
2016-04-04 21:58     ` Andrei Gherzan

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=20160404192846.GA6860@resin \
    --to=andrei@gherzan.ro \
    --cc=yocto@yoctoproject.org \
    --cc=yoctoproject.org@herrie.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.