From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Platform-specific kernel patchset not applied to kernel headers package?
Date: Fri, 26 Jan 2018 13:40:31 +0100 [thread overview]
Message-ID: <20180126124030.37ehgkax5csjhfuz@falbala.home.lespocky.de> (raw)
In-Reply-To: <CABDcavYA_FRmROQnd1-V8LcTc0W_D-XYi68=f_CeVSOQQsNDJw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 907 bytes --]
Hei hei,
On Fri, Jan 26, 2018 at 08:58:52AM +0100, Guillermo Rodriguez Garcia wrote:
> I am creating a ptxdist BSP and have a series.<platform> patchset for a
> given kernel version. I have noticed that this patchset is ignored when the
> KERNEL_HEADER package is built -- instead, a "series" file is automatically
> created and used.
>
> Is this normal/expected? Shouldn't the series.<platform> file be used
> instead?
It is at least known. I stumbled over this last year:
https://www.mail-archive.com/ptxdist@pengutronix.de/msg12233.html
Michael gave some hints for possible workarounds.
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF 08FA 34AD CD00 7221 5CC6 ***
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-01-26 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 7:58 Guillermo Rodriguez Garcia
2018-01-26 12:40 ` Alexander Dahl [this message]
2018-01-26 12:58 ` Michael Olbrich
2018-01-29 9:51 ` Guillermo Rodriguez Garcia
2018-01-29 10:37 ` Michael Olbrich
2018-01-29 11:55 ` Guillermo Rodriguez Garcia
2018-01-29 9:51 ` Guillermo Rodriguez Garcia
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=20180126124030.37ehgkax5csjhfuz@falbala.home.lespocky.de \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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