From: Alex Shi <alex.shi@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: mingo@redhat.com, corbet@lwn.net,
"open list:LOCKING PRIMITIVES" <linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Sebastian Siewior <bigeasy@linutronix.de>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Juri Lelli <juri.lelli@arm.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 3/3] rtmutex: remove unnecessary adjust prio
Date: Thu, 13 Jul 2017 14:13:45 +0800 [thread overview]
Message-ID: <ce4ed6d3-49bc-dc6f-b0c3-a3a1296b68c7@linaro.org> (raw)
In-Reply-To: <20170712163537.7ipr27jmvxmwjfqt@hirez.programming.kicks-ass.net>
On 07/13/2017 12:35 AM, Peter Zijlstra wrote:
> On Wed, Jul 12, 2017 at 10:14:49AM -0400, Steven Rostedt wrote:
>> On Tue, 11 Jul 2017 22:39:24 +0800
>> Alex Shi <alex.shi@linaro.org> wrote:
>>
>>> Any comments for this little change? It's passed on 0day testing.
>>
>> I think the problem was that this was a third patch after two
>> documentation patches. Where, people put documentation review at the
>> bottom of their priority list.
>>
>> This should have been sent as separate patch on its own.
>
> My problem was the sparse changelog, which forces me to think hard and
> thus is landed on the 'later' queue, which moves at glacial speeds.
>
Yes, I should mentioned I didn't find out any reasons from the history
changelogs.
Thanks for reminder this! :)
Regards
Alex
next prev parent reply other threads:[~2017-07-13 6:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 2:52 [PATCH v4 1/3] rtmutex: update rt-mutex-design Alex Shi
2017-07-07 2:52 ` [PATCH v2 2/3] rtmutex: update rt-mutex Alex Shi
2017-07-11 14:37 ` Alex Shi
2017-07-07 2:52 ` [PATCH 3/3] rtmutex: remove unnecessary adjust prio Alex Shi
2017-07-11 14:39 ` Alex Shi
2017-07-12 14:14 ` Steven Rostedt
2017-07-12 16:35 ` Peter Zijlstra
2017-07-13 6:13 ` Alex Shi [this message]
2017-07-13 6:12 ` Alex Shi
2017-07-11 14:35 ` [PATCH v4 1/3] rtmutex: update rt-mutex-design Alex Shi
-- strict thread matches above, loose matches on Subject: below --
2017-05-25 5:26 [PATCH v3 " Alex Shi
2017-05-25 5:26 ` [PATCH 3/3] rtmutex: remove unnecessary adjust prio Alex Shi
2017-06-20 0:40 ` Alex Shi
2017-04-13 14:02 [RFC PATCH 0/3] rtmutex comments update and trival fix Alex Shi
2017-04-13 14:02 ` [PATCH 3/3] rtmutex: remove unnecessary adjust prio Alex Shi
2017-04-13 16:15 ` Steven Rostedt
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=ce4ed6d3-49bc-dc6f-b0c3-a3a1296b68c7@linaro.org \
--to=alex.shi@linaro.org \
--cc=bigeasy@linutronix.de \
--cc=corbet@lwn.net \
--cc=juri.lelli@arm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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®