DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>, distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH 7/8] mips, mipsel: don't actually compile the kernel
Date: Wed, 24 Nov 2021 15:53:38 +0100	[thread overview]
Message-ID: <20211124145338.GY28736@pengutronix.de> (raw)
In-Reply-To: <20211025073735.GD29451@pengutronix.de>

On Mon, Oct 25, 2021 at 09:37:35AM +0200, Michael Olbrich wrote:
> On Sun, Oct 24, 2021 at 09:45:33PM +0200, Roland Hieber wrote:
> > The kernel package only exists to serve a REF_CONFIG for the extra
> > kernel packages, and to compile the userspace kernel tools for debugging
> > purposes. Make the actual kernel compilation and install steps a no-op
> > to save time during the build process, but leave the respective lines in
> > to make porting upstream patches to the kernel recipe easier in the
> > future.
> 
> Why is it easier? The kernel package is completely different now. It serves
> a different purpose and the lines that are commented mean that patches
> won't apply either. And I don't think it's actually useful to backport
> anything.

Any feedback?

> > Signed-off-by: Roland Hieber <rhi@pengutronix.de>

rsc
-- 
Pengutronix e.K.                           | Dipl.-Ing. Robert Schwebel  |
Steuerwalder Str. 21                       | https://www.pengutronix.de/ |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-9    |

_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de


  reply	other threads:[~2021-11-24 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-24 19:45 [DistroKit] [PATCH 1/8] mips, mipsel: kernel-*: bring back KERNEL_*_PATH Roland Hieber
2021-10-24 19:45 ` [DistroKit] [PATCH 2/8] mips, mipsel: kernel-*: bring up-to-date with PTXdist 2021.07.0 template Roland Hieber
2021-10-24 19:45 ` [DistroKit] [PATCH 3/8] mips, mipsel: kernel-*: rework device-tree handling Roland Hieber
2021-10-24 19:45 ` [DistroKit] [PATCH 4/8] mips, mipsel: kernel-*: use ptx/config-version and ptx/config-md5 Roland Hieber
2021-10-24 19:45 ` [DistroKit] [PATCH 5/8] ptxdist: migrate 2021.06.0 -> 2021.10.0 Roland Hieber
2021-10-24 19:45 ` [DistroKit] [PATCH 6/8] mips, mipsel: kernel: re-fork from PTXdist 2021.10.0 Roland Hieber
2021-10-24 19:54   ` [DistroKit] [PATCH v2 " Roland Hieber
2021-10-24 19:45 ` [DistroKit] [PATCH 7/8] mips, mipsel: don't actually compile the kernel Roland Hieber
2021-10-25  7:37   ` Michael Olbrich
2021-11-24 14:53     ` Robert Schwebel [this message]
2021-11-25 11:42       ` Roland Hieber
2021-10-24 19:45 ` [DistroKit] [PATCH 8/8] mips, mipsel: update kernel configs Roland Hieber

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=20211124145338.GY28736@pengutronix.de \
    --to=r.schwebel@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    --cc=rhi@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