From: Joo Yong-Seok <joo.yongseok@gmail.com>
To: backports@vger.kernel.org
Subject: Question about backport output generation with linux-4.9
Date: Mon, 7 Mar 2022 08:55:30 -0800 [thread overview]
Message-ID: <CAE3xvfbJudPQa9w5oe-LEjnZSj9CqrMts2jN-a2cmd4Wb+m1TQ@mail.gmail.com> (raw)
Hi,
I am a newbie on linux-backport and I have a problem generating a
backport output with linux-kernel 4.9.y checkout. These are what I ran
to generate backport output against linux-4.9 kernel.
1) "git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git;
git checkout linux-4.9.y" # linux-stable git repo clone for
source
2) "git clone git://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git";
git checkout linux-4.19.y" # linux-backports
3) In backports directory, ran "./gentree --copy-list copy-list
--clean /abs-path/linux-stable /abs-path/output"
I hit many gentree errors like
> File doesn't exists
> Patch error (refcount.c lock, rhashtable related things...)
> Another patch errors
I resolved by removing the patch files and directly modified the
source in linux-4.9 stable repo as well as modified Kconfig file under
backports/compat.
Also, remove files that don't exist.
I am really wondering whether these procedures are the right way to
generate the backport output.
I need to generate mac80211.ko / cfg80211.ko / and wifi-driver.ko
against our linux-4.9 kernel source code to support a lower version of
kernel.
If I checked out linux-5.4.y kernel from linux-stable repo and checked
out linux-5.4.y from backport repo, I don't see these types of errors.
Please advise me.
Thank you.
--
To unsubscribe from this list: send the line "unsubscribe backports" in
reply other threads:[~2022-03-07 16:55 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=CAE3xvfbJudPQa9w5oe-LEjnZSj9CqrMts2jN-a2cmd4Wb+m1TQ@mail.gmail.com \
--to=joo.yongseok@gmail.com \
--cc=backports@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).