It should related to the way you send the patch.
Currently, on the patchwork, for this series, Revision 5 is like this:
[1/4] util-linux: add setpriv utility
<https://patchwork.openembedded.org/series/18163/#> 162216
<https://patchwork.openembedded.org/patch/162216/> Randy MacLeod
<https://patchwork.openembedded.org/project/oe-core/patches/?submitter=3343>
Master Next
[4/4] bash: use setpriv, sed.sed to run ptests
<https://patchwork.openembedded.org/series/18163/#> 162223
<https://patchwork.openembedded.org/patch/162223/> Randy MacLeod
<https://patchwork.openembedded.org/project/oe-core/patches/?submitter=3343>
New
[3/4] ptest-runner: enable child procs as session leader
<https://patchwork.openembedded.org/series/18163/#> 162219
<https://patchwork.openembedded.org/patch/162219/> Randy MacLeod
<https://patchwork.openembedded.org/project/oe-core/patches/?submitter=3343>
Master Next
[4/4] bash: use setpriv, sed.sed to run ptests
<https://patchwork.openembedded.org/series/18163/#> 162218
<https://patchwork.openembedded.org/patch/162218/> Randy MacLeod
<https://patchwork.openembedded.org/project/oe-core/patches/?submitter=3343>
Master Next
So patch cannot be merge.
There is patch of patchwork doc related to this:
Patchwork supports:
* Re-sending a single patch as a reply to the reviewer email. This
is usually only used when a few patches have to be resent.
* Re-sending a full series as a new thread.
+ [PATCH 0/3] Cover Letter Subject
+--> [PATCH 1/3] Patch 1
+--> [PATCH 2/3] Patch 2
| +--> Re: [PATCH 2/3] Patch 2 (reviewer comments)
| +--> [PATCH v2 2/3] Patch 2 (v2 of patch 2/3)
+--> [PATCH 3/3] Patch 3
+ [PATCH v2 0/3] Cover Letter Subject
+--> [PATCH v2 1/3] Patch 1 (v2 of patch 1/3)
+--> [PATCH v2 2/3] Patch 2 (v2 of patch 2/3)
+--> [PATCH v2 3/3] Patch 3 (v2 of patch 3/3)
On 6/15/19 1:13 AM, Randy MacLeod wrote:
On 6/14/19 1:01 PM, Patchwork wrote:
* 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 ca737408bb)
This appears to be wrong.
From my local repo:
$ git log --oneline -6
3461af0c76 (HEAD -> bash-ptest) bash: use setpriv, sed.sed to run ptests
7ab387fcac ptest-runner: enable child procs as session leader
ef6ef10236 libcap-ng: split into libcap-ng/libcap-ng-python
11d5c1bbfd util-linux: add setpriv utility
ca737408bb (origin/master, origin/HEAD, master) <------ same id as above
bluez: fix test case failures with GCC 9
c6b49cb752 kernel-fitimage: uboot-sign: Check UBOOT_DTB_BINARY before
adding deps
I was setting the 'In-reply-to' field to the original thread so
perhaps patchtest is confused by that or I did something wrong since
I've rarely used that feature of git send-email.
--
BRs
Sandy(Li Changqing)
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
