From: Sven Eckelmann <sven@narfation.org>
To: Felix Kaechele <felix@kaechele.ca>
Cc: b.a.t.m.a.n@lists.open-mesh.org, linus.luessing@c0d3.blue
Subject: Re: [PATCH] batman-adv: compat: Fix build on RHEL 8.1 and clones
Date: Tue, 28 Jan 2020 18:32:06 +0100 [thread overview]
Message-ID: <18814629.hYLCy3ASfM@sven-edge> (raw)
In-Reply-To: <2187ec70-4276-5178-b7ad-d029bd8561fb@kaechele.ca>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
On Tuesday, 28 January 2020 18:19:16 CET Felix Kaechele wrote:
[..]
> No worries. Just saw that there are some provisions for Debian (which I
> guess is what some of the maintainers are using) in the code.
Good point, there was the make-kpkg hack. @Linus, can this be dropped? The
correct way to build a private Debian package of the kernel is to use
`make deb-pkg`
[...]
> I'm not interested in maintaining this upstream indefinitely and I agree
> with you that carrying around fixes for all kinds of weird quirks is a
> burden on maintainers.
>
> I'm happy to just carry this patch in my DKMS RPM packages I maintain
> for batman-adv.
As said, if you want to maintain it upstream then feel free to resent the
patch with the requested change. The "reasonable new upstream kernels" part
was about the way we drop support for older kernels. The oldest kernel we want
to support is the the oldest kernel not marked as EOL on
https://www.kernel.org/category/releases.html
If the RHEL quirks don't become too bothersome and you take care of it then it
should be a relative small problem for us. I just don't want to be the person
taking care of kernels which I don't use.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-28 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 18:07 [PATCH] batman-adv: compat: Fix build on RHEL 8.1 and clones Felix Kaechele
2020-01-25 19:17 ` Sven Eckelmann
2020-01-28 17:19 ` Felix Kaechele
2020-01-28 17:32 ` Sven Eckelmann [this message]
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=18814629.hYLCy3ASfM@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=felix@kaechele.ca \
--cc=linus.luessing@c0d3.blue \
/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