From: Andrew Morton <akpm@linux-foundation.org>
To: Yury Norov <yury.norov@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: wrong patch order
Date: Mon, 26 Apr 2021 17:19:38 -0700 [thread overview]
Message-ID: <20210426171938.60060f21f03963e2bf374e03@linux-foundation.org> (raw)
In-Reply-To: <20210426171451.GA133505@yury-ThinkPad>
On Mon, 26 Apr 2021 10:14:51 -0700 Yury Norov <yury.norov@gmail.com> wrote:
> Hi Andrew,
>
> In the next-20210426 I see the commit 7c3c0a5796a8 "h8300:
> rearrange headers inclusion order in asm/bitops" is applied after
> a54cbe7fa597 "lib: add fast path for find_next_*_bit()".
>
> This may cause cause build failure for h8300 while bisecting.
>
> Can you please change order of the patches so that 7c3c0a5796a8 would
> follow 68b80f24c2f6 "arch: rearrange headers inclusion order in
> asm/bitops for m68k and sh"? It's also possible to merge 7c3c0a5796a8
> and 68b80f24c2f6 because they address the same issue.
I renamed
lib-add-fast-path-for-find_first__bit-and-find_last_bit-fix.patch to
arch-rearrange-headers-inclusion-order-in-asm-bitops-for-m68k-and-sh-fix.patch
and queued it immediately after
arch-rearrange-headers-inclusion-order-in-asm-bitops-for-m68k-and-sh.patch,
as a fix against
arch-rearrange-headers-inclusion-order-in-asm-bitops-for-m68k-and-sh.patch,
to be folded into
arch-rearrange-headers-inclusion-order-in-asm-bitops-for-m68k-and-sh.patch
tools-disable-wno-type-limits.patch
tools-bitmap-sync-function-declarations-with-the-kernel.patch
tools-sync-bitmap_last_word_mask-macro-with-the-kernel.patch
arch-rearrange-headers-inclusion-order-in-asm-bitops-for-m68k-and-sh.patch
arch-rearrange-headers-inclusion-order-in-asm-bitops-for-m68k-and-sh-fix.patch
lib-extend-the-scope-of-small_const_nbits-macro.patch
tools-sync-small_const_nbits-macro-with-the-kernel.patch
lib-inline-_find_next_bit-wrappers.patch
tools-sync-find_next_bit-implementation.patch
lib-add-fast-path-for-find_next__bit.patch
lib-add-fast-path-for-find_first__bit-and-find_last_bit.patch
tools-sync-lib-find_bit-implementation.patch
maintainers-add-entry-for-the-bitmap-api.patch
prev parent reply other threads:[~2021-04-27 0:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 17:14 Yury Norov
2021-04-27 0:19 ` Andrew Morton [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=20210426171938.60060f21f03963e2bf374e03@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yury.norov@gmail.com \
/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
all inboxes | Powered by JetHome®