From: DJ Delorie <dj@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: rmorell@nvidia.com, libc-alpha@sourceware.org, carlos@redhat.com,
siddhesh@sourceware.org
Subject: Re: [PATCH] malloc: Fix transposed arguments in sysmalloc_mmap_fallback call
Date: Tue, 07 Mar 2023 13:43:02 -0500 [thread overview]
Message-ID: <xno7p45rnt.fsf@greed.delorie.com> (raw)
In-Reply-To: <0fd25eae-5dbd-1622-4e8b-53874d723bb7@linaro.org>
Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> writes:
> LGTM, I am not sure why patchwork has failed to apply this patch
> (I works manually).
The Message-ID has slashes in it, and while patchwork knows this is
possible, it seems its coverage of quoting them is incomplete. Thus,
the CI machines are unable to download the patch from patchwork to test
it. The "32bit" tests download the whole series, which doesn't have
this problem. So if that test passes, ignore any "apply-patch"
failures.
next prev parent reply other threads:[~2023-03-07 18:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 21:20 Robert Morell
2023-03-07 13:13 ` Adhemerval Zanella Netto
2023-03-07 18:43 ` DJ Delorie [this message]
2023-03-07 18:53 ` Robert Morell
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=xno7p45rnt.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=rmorell@nvidia.com \
--cc=siddhesh@sourceware.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).