From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: ✗ patchtest: failure for python3: fix run-time deps for core python3 libraries (rev2)
Date: Thu, 06 Apr 2017 12:34:52 +0100 [thread overview]
Message-ID: <1491478492.17200.32.camel@linuxfoundation.org> (raw)
In-Reply-To: <1491457693.3938.15.camel@linux.intel.com>
On Thu, 2017-04-06 at 08:48 +0300, Dmitry Rozhkov wrote:
> On Thu, 2017-04-06 at 05:32 +0000, Patchwork wrote:
> >
> > == Series Details ==
> >
> > Series: python3: fix run-time deps for core python3 libraries
> > (rev2)
> > Revision: 2
> > URL : https://patchwork.openembedded.org/series/6164/
> > State : failure
> >
> > == Summary ==
> >
> >
> > Thank you for submitting this patch series to OpenEmbedded Core.
> > This
> > is
> > an automated response. Several tests have been executed on the
> > proposed
> > series by patchtest resulting in the following failures:
> >
> >
> >
> > * Issue Series does not apply on top of target branch
> > [test_series_merge_on_head]
> > Suggested fix Rebase your series on top of targeted branch
> > Targeted branch master (currently at 3a1cce6591)
> So was my master at 3a1cce6591 when I submitted the patch (and still
> is). And I believe the first version had no problems with applying it
> too.
If you take your patch from the mailing list, it doesn't apply as there
was line wrapping that occurred. I was able to fix it and make it apply
though (so no need to resend).
Cheers,
Richard
prev parent reply other threads:[~2017-04-06 11:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 5:07 [PATCH v2] python3: fix run-time deps for core python3 libraries Dmitry Rozhkov
2017-04-06 5:32 ` ✗ patchtest: failure for python3: fix run-time deps for core python3 libraries (rev2) Patchwork
2017-04-06 5:48 ` Dmitry Rozhkov
2017-04-06 11:34 ` Richard Purdie [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=1491478492.17200.32.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=dmitry.rozhkov@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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 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.