From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2 1/2] Add mseal() syscall declaration
Date: Thu, 25 Jul 2024 17:12:22 +0200 [thread overview]
Message-ID: <ZqJrVmGNDSpOaFxA@yuki> (raw)
In-Reply-To: <7F3E1D80-0F31-4017-9512-A83CA87B4AE1@suse.com>
Hi!
> Sorry but I don’t get it. Resolving conflicts is really something up
> to people who push the code on the mainline (: Also it should be
> pretty easy since it requires to accept both head and coming changes.
I'm pretty sure you would get some pretty hars word if you send patches
to linux kernel that does not apply on the top of each other...
Anyways I'm just trying to get to a solution that would save time for
everyone, because manually fixing a patch that fails to add a line into
18 different files is not something I want to do for each new syscall
patchset you send...
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-07-25 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 8:41 [LTP] [PATCH v2 0/2] Add mseal() testing suite Andrea Cervesato
2024-07-23 8:41 ` [LTP] [PATCH v2 1/2] Add mseal() syscall declaration Andrea Cervesato
2024-07-24 11:25 ` Cyril Hrubis
2024-07-24 13:58 ` Andrea Cervesato via ltp
2024-07-24 14:58 ` Cyril Hrubis
2024-07-24 15:34 ` Andrea Cervesato via ltp
2024-07-25 15:12 ` Cyril Hrubis [this message]
2024-07-23 8:41 ` [LTP] [PATCH v2 2/2] Add mseal01 test Andrea Cervesato
2024-07-25 15:55 ` Cyril Hrubis
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=ZqJrVmGNDSpOaFxA@yuki \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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