From: Hauke Mehrtens <hauke@hauke-m.de>
To: Shetu Ayalew <shetu@mellanox.com>,
"backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: generate backport
Date: Sun, 24 May 2020 17:53:51 +0200 [thread overview]
Message-ID: <23beda14-d3c3-4542-d733-b6c86a244cbe@hauke-m.de> (raw)
In-Reply-To: <AM0PR05MB4738C333E2495962C3CEBAADDAB20@AM0PR05MB4738.eurprd05.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 1937 bytes --]
On 5/24/20 5:39 PM, Shetu Ayalew wrote:
> 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
Hi Shetu,
Currently backports does not work with linux-next, we do not have the
resources to maintain backports on linux-next any more, so we only
target Linus RC releases, 5.7-rc3 is the latest one, so you should use
that one instead of linux-next.
I am using coccinelle 1.0.7 and for me it currently works, I also do not
like the error messages.
I had a look at the patch and you can probably remove it anyway, it is
for kernel < 3.6 and this is not supported anyway.
Hauke
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-05-24 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 15:39 generate backport Shetu Ayalew
2020-05-24 15:53 ` Hauke Mehrtens [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=23beda14-d3c3-4542-d733-b6c86a244cbe@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=shetu@mellanox.com \
/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).