From: Michael Olbrich <m.olbrich@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: [DistroKit] [PATCH 0/3] platform-rpi: various cleanups
Date: Fri, 26 Oct 2018 14:15:52 +0200 [thread overview]
Message-ID: <20181026121555.3722-1-m.olbrich@pengutronix.de> (raw)
Hi,
I built the rpi platform to check that my layer change works correctly and
I noticed some other issues. These are just some minor fixes and cleanups.
I also noticed that the kernel config is quite different from the v7a
config. Some of that seems to be pretty arbitrary and suboptimal. E.g. no
optimized ARM crypto implementations, no idle handler and things like that.
Is there a reason for this?
Michael
Michael Olbrich (3):
platform-rpi: image-boot-vfat: add missing dependency
platform-rpi: platformconfig: building the kernel requires openssl
platform-rpi: platformconfig: some cleanup
configs/platform-rpi/platformconfig | 14 +++++++-------
configs/platform-rpi/platforms/image-boot-vfat.in | 1 +
2 files changed, 8 insertions(+), 7 deletions(-)
--
2.19.0
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next reply other threads:[~2018-10-26 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 12:15 Michael Olbrich [this message]
2018-10-26 12:15 ` [DistroKit] [PATCH 1/3] platform-rpi: image-boot-vfat: add missing dependency Michael Olbrich
2018-10-26 12:15 ` [DistroKit] [PATCH 2/3] platform-rpi: platformconfig: building the kernel requires openssl Michael Olbrich
2018-10-26 12:15 ` [DistroKit] [PATCH 3/3] platform-rpi: platformconfig: some cleanup Michael Olbrich
2018-10-26 13:29 ` [DistroKit] [PATCH 0/3] platform-rpi: various cleanups Robert Schwebel
2018-10-31 22:37 ` Roland Hieber
2018-11-01 9:42 ` Michael Olbrich
2018-11-01 9:55 ` Robert Schwebel
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=20181026121555.3722-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=distrokit@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