mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Platform-specific kernel patchset not applied to kernel headers package?
Date: Mon, 29 Jan 2018 12:55:22 +0100	[thread overview]
Message-ID: <CABDcavZ89PMGMO8517=LjoTHTKmgq=LcO4yT2Q+0Psij-_jJgw@mail.gmail.com> (raw)
In-Reply-To: <20180129103720.njvzqdjralhiwptl@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 3082 bytes --]

Hi,

2018-01-29 11:37 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.de>:

> Hi,
>
> On Mon, Jan 29, 2018 at 10:51:07AM +0100, Guillermo Rodriguez Garcia wrote:
> > 2018-01-26 13:58 GMT+01:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> > > On Fri, Jan 26, 2018 at 01:40:31PM +0100, Alexander Dahl wrote:
> > > > 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.
> > >
> > >
> > > Right, check that thread.
> > >
> > > Also, why do you need a 'series.<platform>' instead of a normal series
> > > file?
> > >
> >
> > I used series.<platform> because the BSP currently supports two platforms
> > (two boards), and some of the patches are platform-specific.
> >
> >
> > > And why do you need the patches for the kernel headers?
> > >
> >
> > This is because I am building imx6 specific packages which require a set
> of
> > kernel headers, and these must include imx6-specific bits.
> >
> > In the thread that Alexander mentioned in his reply you mention the
> > following:
> >
> > 1. Move the patches to configs/platform-XXX/patches/linux-4.9.47/ and
> just
> > use 'series'.
>
> In most cases, that's the correct way to handle this. All platform specific
> files should be in configs/platform-XXX/ anyways.
>
> Keeping the patches Toplevel has one use-case:
> Some patches are used by both platforms. I'd still move the patches to the
> platforms and use symlinks to share: Patches can be in subdirs, so just on
> Symlink to the common set of patches is enough.
>
> > I guess this solves my problem, however, just out of curiosity: If the
> > kernel headers package will pick up the correct patchset from
> > configs/platform-XXX/patches/linux-4.9.47, shouldn't it also pick it up
> if
> > it lives in patches/linux-4.9.47/series.XXX ?
>
> Checking in configs/platform-XXX/patches/ is a generic PTXdist mechanism.
> Using 'series.XXX' is a hack in the Kernel patches to work with bad
> patches. It's a mechanism that I'd like to get rid of. But there are still
> people using it.
> It's not something I want to spread to other packages.
>

Thank you for the explanation, I know understand the background and
motivations.

Still I would suggest to either get rid of the "series.XXX" hack (perhaps
with a check and a warning) or make it applicable to kernel headers as
well. The current behaviour is a bit surprising.

Anyway my problem is solved now so thank you again.
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

[-- Attachment #1.2: Type: text/html, Size: 4428 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-01-29 11:55 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
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 [this message]
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='CABDcavZ89PMGMO8517=LjoTHTKmgq=LcO4yT2Q+0Psij-_jJgw@mail.gmail.com' \
    --to=guille.rodriguez@gmail.com \
    --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