From: Fengguang Wu <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@01.org, Linus Torvalds <torvalds@linux-foundation.org>,
Will Deacon <will.deacon@arm.com>,
Oleg Nesterov <oleg@redhat.com>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-kernel@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: Question on smp_mb__before_spinlock
Date: Mon, 5 Sep 2016 19:26:36 +0800 [thread overview]
Message-ID: <20160905112636.s4sol2r4vyo5lxo5@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20160905101937.GY10153@twins.programming.kicks-ass.net>
Hi Peter,
On Mon, Sep 05, 2016 at 12:19:37PM +0200, Peter Zijlstra wrote:
>On Mon, Sep 05, 2016 at 05:56:46PM +0800, kbuild test robot wrote:
>> Hi Peter,
>>
>> [auto build test ERROR on linus/master]
>> [also build test ERROR on v4.8-rc5 next-20160825]
>> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>> [Suggest to use git(>=2.9.0) format-patch --base=<commit> (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on]
>> [Check https://git-scm.com/docs/git-format-patch for more information]
>
>What happend to not applying patches that lack a SoB and the subject
>doesn't even include [PATCH] either.
Sorry the current logic assumes "Re: " in subject. Just fixed it to
ignore all patches w/o SOB.
Regards,
Fengguang
next prev parent reply other threads:[~2016-09-05 11:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 9:37 Question on smp_mb__before_spinlock Peter Zijlstra
2016-09-05 9:56 ` kbuild test robot
2016-09-05 10:19 ` Peter Zijlstra
2016-09-05 11:26 ` Fengguang Wu [this message]
2016-09-05 10:10 ` Will Deacon
2016-09-06 11:17 ` Peter Zijlstra
2016-09-06 17:42 ` Will Deacon
2016-09-05 10:37 ` Paul E. McKenney
2016-09-05 11:34 ` Peter Zijlstra
2016-09-05 13:57 ` Paul E. McKenney
2016-09-05 10:51 ` kbuild test robot
2016-09-07 12:17 ` Nicholas Piggin
2016-09-07 13:23 ` Peter Zijlstra
2016-09-07 13:51 ` Will Deacon
2016-09-12 2:35 ` Nicholas Piggin
2016-09-12 2:27 ` Nicholas Piggin
2016-09-12 12:54 ` Peter Zijlstra
2016-09-13 2:05 ` Nicholas Piggin
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=20160905112636.s4sol2r4vyo5lxo5@wfg-t540p.sh.intel.com \
--to=lkp@intel.com \
--cc=benh@kernel.crashing.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).