backports.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Doyle <wpdster@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: backports@vger.kernel.org
Subject: Re: How to use backports?
Date: Tue, 15 May 2018 16:26:14 -0400	[thread overview]
Message-ID: <CAF_dkJDB077igL5AiySBXo_aam=8wozCg=-Rc-9=7qMqFd4kKA@mail.gmail.com> (raw)
In-Reply-To: <1526414646.4450.13.camel@sipsolutions.net>

Hello Johannes,
Thank you for your quick reply.
On Tue, May 15, 2018 at 4:04 PM, Johannes Berg
<johannes@sipsolutions.net> wrote:
>> From reading https://backports.wiki.kernel.org/index.php/Documentation/integration
>> it would appear that I should be able to do something vaguely like:
>>
>> $ ./gentree.py --integrate --clean --gitdebug ../linux-ath-erstrom
>> ../buildroot/build/linux-custom
>
> In theory yes. I can't really recommend --integrate, it's untested. I
> may remove it entirely since nobody is maintaining it.
So, that's all that I see documented at
https://backports.wiki.kernel.org/index.php/Documentation.  That page
describes 2 workflows: "kernel integration mode" and  "package
releases mode".  The link to the "kernel integration mode"
documentation describes how to run gentree.py.  The link to the
"package releases mode" documentation just says to run "make
menuconfig" without giving any details of how to connect the newer
source tree to an older revision.

It turns out, for my project, I would prefer to use the "kernel
integration mode", since I would really like to turn off loadable
modules (not needed for my space-constrained embedded target).  But if
the "too hard" LED comes on, I can let that go.

Anyway... am I looking in the wrong place for documentation?  Should I
be looking elsewhere?

How do folks use backports anyway?

>
>> You need to have installed: spatch >= 1.0.6
>> Try installing the package: coccinelle
>
> Indeed. There was actually a very recent commit (latest commit) that
> would make this require only an earlier version. Reverting that may be
> easier for you.
OK, I'll try that.  Thanks.
(that just failed to find a
../buildroot/build/linux-custom/backports/Kconfig... which smells a
little like bitrot to me).


>> So, first questions first...
>> Should I reasonably expect gentree to run on a 16.04 LTS Ubuntu?  If
>> so, what dependencies should I install?
>
> No idea, sorry.
>
> johannes
>
If folks don't tend to use this tool on Ubuntu LTS releases, what
version of Linux do you use it on?  What is known to work?

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

  reply	other threads:[~2018-05-15 20:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 19:41 How to use backports? Patrick Doyle
2018-05-15 20:04 ` Johannes Berg
2018-05-15 20:26   ` Patrick Doyle [this message]
2018-05-15 20:30     ` Johannes Berg
2018-05-15 22:19       ` Steve deRosier
2018-05-16 13:24         ` Patrick Doyle
2018-05-16 13:26           ` Johannes Berg
2018-05-16 13:28             ` Patrick Doyle

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='CAF_dkJDB077igL5AiySBXo_aam=8wozCg=-Rc-9=7qMqFd4kKA@mail.gmail.com' \
    --to=wpdster@gmail.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).