From: Shetu Ayalew <shetu@mellanox.com>
To: "backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: generate backport
Date: Sun, 24 May 2020 15:39:30 +0000 [thread overview]
Message-ID: <AM0PR05MB4738C333E2495962C3CEBAADDAB20@AM0PR05MB4738.eurprd05.prod.outlook.com> (raw)
Hi,
I'm trying to create backport based on the backport project. I followed the instructions here - https://backports.wiki.kernel.org/index.php/Documentation/backports/hacking.
I'm using the latest versions of linux-next tree and backports tree and I also installed the latest version of the coccinelle. I did checkout on both trees (of linux-next tree and backports) to many different tags (the last I tryed on was v5.3.6-1). Then I run:
./gentree.py --clean --git-revision v5.3.6-1 /path/to/your/linux-next /path/to/your/newly/created/release
But in all the cases there was always patches that created parsing error. For example on the last tag I got error in patch 0049-no-pfmemalloc/no-pfmemalloc.cocci with the following message:
init_defs_builtins: /usr/local/bin/../lib/coccinelle/standard.h
minus: parse error:
File "/.autodirect/swgwork/shetu/upstream/backports/patches/0049-no-pfmemalloc/no-pfmemalloc.cocci", line 7, column 4, charpos = 90
around = 'page_is_pfmemalloc',
whole content = || page_is_pfmemalloc(page)
which is not much informative, I'm not sure where is the problem. I also checked this file on master branch and other branches
Is it possible you give me two tags (one for the linux-next tree and one for the backport) where the backport should work so I will be able to try it.
Thanks,
Shetu
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next reply other threads:[~2020-05-24 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 15:39 Shetu Ayalew [this message]
2020-05-24 15:53 ` generate backport Hauke Mehrtens
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=AM0PR05MB4738C333E2495962C3CEBAADDAB20@AM0PR05MB4738.eurprd05.prod.outlook.com \
--to=shetu@mellanox.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 NNTP newsgroup(s).