[PATCH] busybox: Fix typo in patch

[PATCH] busybox: Fix typo in patch

[Khem Raj]

Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
 ...1-Remove-syscall-wrappers-around-clock_gettime-closes-.patch | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/busybox/busybox/0001-Remove-syscall-wrappers-around-clock_gettime-closes-.patch b/meta/recipes-core/busybox/busybox/0001-Remove-syscall-wrappers-around-clock_gettime-closes-.patch
index 1217daa108..0c7f9b8132 100644
--- a/meta/recipes-core/busybox/busybox/0001-Remove-syscall-wrappers-around-clock_gettime-closes-.patch
+++ b/meta/recipes-core/busybox/busybox/0001-Remove-syscall-wrappers-around-clock_gettime-closes-.patch
@@ -63,7 +63,7 @@ Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
 -		 * typically requiring -lrt. We just skip all this mess */
 -		syscall(__NR_clock_gettime, CLOCK_REALTIME, &ts);
 -#elif ENABLE_FEATURE_DATE_NANO && __TIMESIZE == 64
--		/* Let's only suppor the 64 suffix syscalls for 64-bit time_t.
+-		/* Let's only support the 64 suffix syscalls for 64-bit time_t.
 -		 * This simplifies the code for us as we don't need to convert
 -		 * between 64-bit and 32-bit. We also don't have a way to
 -		 * report overflow errors here.
-- 
2.25.0

✗ patchtest: failure for busybox: Fix typo in patch

[Patchwork]

== Series Details ==

Series: busybox: Fix typo in patch
Revision: 1
URL   : https://patchwork.openembedded.org/series/22636/
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 7331062f82)



If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Guidelines:     https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite:     http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe