All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4 4/4] Update syscalls files
Date: Wed, 23 Oct 2024 14:57:07 +0200	[thread overview]
Message-ID: <20241023125707.GA594199@pevik> (raw)
In-Reply-To: <69c655f5-3635-48c7-a925-544ad2af05ca@suse.com>

Hi Andrea,

> Hi Petr,

...
> > Also, this 4th patch also does not apply. Unlike first commit there are more
> > conflicts (applying of course on the top of the 3 previous patches):

> > Description: [v4,4/4] Update syscalls files
> > Applying: Update syscalls files
> > error: patch failed: include/lapi/syscalls/arm.in:1
> > error: include/lapi/syscalls/arm.in: patch does not apply
> > error: patch failed: include/lapi/syscalls/arm64.in:294
> > error: include/lapi/syscalls/arm64.in: patch does not apply
> > error: patch failed: include/lapi/syscalls/ia64.in:341
> > error: include/lapi/syscalls/ia64.in: patch does not apply
> > error: patch failed: include/lapi/syscalls/x86_64.in:349
> > error: include/lapi/syscalls/x86_64.in: patch does not apply
> > Patch failed at 0001 Update syscalls files
> This is really strange. It's not happening for me even with the latest HEAD.
> Did you rebase first?

I was applying to the master (as I wrote first I need to adjust first patch
which also didn't apply, but that's just a single line). Don't bother if the
problem is really on my side.  But pushing the patchset to your fork would help
me to actually test the code.

Kind regards,
Petr

> > Kind regards,
> > Petr
> Andrea

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-10-23 12:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  9:45 [LTP] [PATCH v4 0/4] Automatically generate syscalls.h Andrea Cervesato
2024-10-09  9:45 ` [LTP] [PATCH v4 1/4] Refactor regen.sh script to generate syscalls Andrea Cervesato
2024-10-14 12:45   ` Li Wang
2024-10-25 10:03   ` Petr Vorel
2024-10-09  9:45 ` [LTP] [PATCH v4 2/4] Add script to generate arch(s) dependant syscalls Andrea Cervesato
2024-10-15  8:12   ` Li Wang
2024-10-25 10:20   ` Petr Vorel
2024-10-30  8:40     ` Andrea Cervesato via ltp
2024-10-09  9:45 ` [LTP] [PATCH v4 3/4] Delete obsolete strip_syscall.awk file Andrea Cervesato
2024-10-15  8:10   ` Li Wang
2024-10-25 10:23   ` Petr Vorel
2024-10-09  9:45 ` [LTP] [PATCH v4 4/4] Update syscalls files Andrea Cervesato
2024-10-15  6:49   ` Li Wang
2024-10-15  7:04     ` Li Wang
2024-10-15 17:17       ` Petr Vorel
2024-10-23 12:34         ` Andrea Cervesato via ltp
2024-10-23 12:57           ` Petr Vorel [this message]
2024-10-23 14:30             ` Andrea Cervesato via ltp
2024-10-25  9:37               ` Petr Vorel
2024-10-23 12:11     ` Andrea Cervesato via ltp

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=20241023125707.GA594199@pevik \
    --to=pvorel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.