backports.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>, backports@vger.kernel.org
Subject: Re: What distro can run recent backports?
Date: Mon, 16 Jul 2018 13:16:52 -0700	[thread overview]
Message-ID: <2823e04b-0434-42eb-12be-4e7a8e2d35b8@candelatech.com> (raw)
In-Reply-To: <1531770284.3265.0.camel@sipsolutions.net>

On 07/16/2018 12:44 PM, Johannes Berg wrote:
> On Mon, 2018-07-16 at 10:49 -0700, Ben Greear wrote:
>> Hello,
>>
>> I'm trying to make backports work with my 4.16-ct kernel.  I tried Fedora-27, but it has
>> some bug relate to spatch so it cannot run there.
>
> I think it's an upstream spatch bug. You could use an older version and
> revert the recent genl_const patch.
>
> I'm on F27 but haven't gotten it to work recently (and am out for the
> next ~4 weeks)
>
> johannes

Thanks, I did try reverting the patch, and that got me farther, and after
more hacking on some incompatible patches and some Kconfig issues,
I got it to start building, and then it blew up all over the place.

This patch is part of what I used, by the way:

https://www.spinics.net/lists/backports/msg04115.html

It seems like a fragile house of cards, and I think maybe I should just
go back to manually copying files around and then fixing the incompatibilities.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

--
To unsubscribe from this list: send the line "unsubscribe backports" in

  reply	other threads:[~2018-07-16 20:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16 17:49 What distro can run recent backports? Ben Greear
2018-07-16 19:44 ` Johannes Berg
2018-07-16 20:16   ` Ben Greear [this message]
2018-07-16 22:15     ` Ben Greear

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=2823e04b-0434-42eb-12be-4e7a8e2d35b8@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=backports@vger.kernel.org \
    --cc=johannes@sipsolutions.net \
    /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;
as well as URLs for NNTP newsgroup(s).