From: Philipp Rudo <prudo@linux.ibm.com>
To: linux-s390@vger.kernel.org
Subject: [PATCH v2 0/5] s390-tools: Add install script for zfcpdump
Date: Tue, 07 Aug 2018 13:33:01 +0000 [thread overview]
Message-ID: <20180807133306.46056-1-prudo@linux.ibm.com> (raw)
Hi everybody
here is v2 of the series.
changes v1 -> v2:
- In description of patch 5 mention that zipl expects to find the
zfcpdump kernel at ZFCPDUMP_IMAGE.
- Add Reviewed-Bys
When there are no more comments I will push the commits at the end of the
week.
Thanks
Philipp
----
Hi everybody
currently every distro handles the zfcpdump kernel differently. However,
with systemd (>= 203) there is a general script (kernel-install) available
for kernel installs. This script allows the execution of drop-in scripts to
deal with specific aspects of the kernel installation. Add such a drop-in
script to s390-tools to allow unifying zfcpdump kernel handling among the
distros and simplifying the interaction between zipl and zfcpdump.
At the moment the script is only generated but not installed to allow
distros to decide if/where they want to install it.
Before the script is added some minor cleanups are made regarding zfcpdump
related macros. The goal here is to reduce unnecessary macro definitions and
to unify the naming in zfcpdump and zipl.
Thanks
Philipp
Philipp Rudo (5):
zfcpdump: Remove unused macros
zipl: Rename FSDUMP_PART_* macros
Makefile: Rename ZFCPDUMP_PART_* macros
zipl: Move macro definition to Makefile
zfcpdump: Add install script for zfcpdump
.gitignore | 3 +-
common.mak | 7 +--
zfcpdump/10-zfcpdump.install.in | 114 ++++++++++++++++++++++++++++++++++++++++
zfcpdump/Makefile | 22 +++++---
zipl/include/zipl.h | 7 ---
zipl/src/Makefile | 7 +--
zipl/src/job.c | 10 ++--
7 files changed, 143 insertions(+), 27 deletions(-)
create mode 100755 zfcpdump/10-zfcpdump.install.in
--
2.16.4
reply other threads:[~2018-08-07 13:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180807133306.46056-1-prudo@linux.ibm.com \
--to=prudo@linux.ibm.com \
--cc=linux-s390@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox