From: "Shi, Yang" <yang.shi@linaro.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: akpm@linux-foundation.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linaro-kernel@lists.linaro.org
Subject: Re: [RFC V5] Add gup trace points support
Date: Wed, 13 Jan 2016 10:14:24 -0800 [thread overview]
Message-ID: <56969400.6020805@linaro.org> (raw)
In-Reply-To: <20160112151052.168bba85@gandalf.local.home>
On 1/12/2016 12:10 PM, Steven Rostedt wrote:
> On Tue, 12 Jan 2016 12:00:54 -0800
> "Shi, Yang" <yang.shi@linaro.org> wrote:
>
>> Hi Steven,
>>
>> Any more comments on this series? How should I proceed it?
>>
>
> The tracing part looks fine to me. Now you just need to get the arch
> maintainers to ack each of the arch patches, and I can pull them in for
> 4.6. Too late for 4.5. Probably need Andrew Morton's ack for the
> mm/gup.c patch.
Thanks Steven. Already sent email to x86, s390 and sparc maintainers.
Ralf already acked the MIPS part since v1.
Regards,
Yang
>
> -- Steve
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: "Shi, Yang" <yang.shi@linaro.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: akpm@linux-foundation.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linaro-kernel@lists.linaro.org
Subject: Re: [RFC V5] Add gup trace points support
Date: Wed, 13 Jan 2016 10:14:24 -0800 [thread overview]
Message-ID: <56969400.6020805@linaro.org> (raw)
In-Reply-To: <20160112151052.168bba85@gandalf.local.home>
On 1/12/2016 12:10 PM, Steven Rostedt wrote:
> On Tue, 12 Jan 2016 12:00:54 -0800
> "Shi, Yang" <yang.shi@linaro.org> wrote:
>
>> Hi Steven,
>>
>> Any more comments on this series? How should I proceed it?
>>
>
> The tracing part looks fine to me. Now you just need to get the arch
> maintainers to ack each of the arch patches, and I can pull them in for
> 4.6. Too late for 4.5. Probably need Andrew Morton's ack for the
> mm/gup.c patch.
Thanks Steven. Already sent email to x86, s390 and sparc maintainers.
Ralf already acked the MIPS part since v1.
Regards,
Yang
>
> -- Steve
>
next prev parent reply other threads:[~2016-01-13 18:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 21:22 [RFC V5] Add gup trace points support Yang Shi
2015-12-09 21:22 ` Yang Shi
2015-12-09 21:22 ` [PATCH v5 1/7] trace/events: Add gup trace events Yang Shi
2015-12-09 21:22 ` Yang Shi
2015-12-09 21:22 ` [PATCH v5 2/7] mm/gup: add gup trace points Yang Shi
2015-12-09 21:22 ` Yang Shi
2015-12-09 21:22 ` [PATCH v5 3/7] x86: " Yang Shi
2015-12-09 21:22 ` Yang Shi
2016-01-13 18:11 ` Shi, Yang
2016-01-13 18:11 ` Shi, Yang
2015-12-09 21:22 ` [PATCH v5 4/7] mips: " Yang Shi
2015-12-09 21:22 ` Yang Shi
2015-12-09 21:22 ` [PATCH v5 5/7] s390: " Yang Shi
2015-12-09 21:22 ` Yang Shi
2016-01-13 18:12 ` Shi, Yang
2016-01-13 18:12 ` Shi, Yang
2016-01-14 7:45 ` Heiko Carstens
2016-01-14 7:45 ` Heiko Carstens
2015-12-09 21:22 ` [PATCH v5 6/7] sh: " Yang Shi
2015-12-09 21:22 ` Yang Shi
2015-12-09 21:22 ` Yang Shi
2015-12-09 21:22 ` [PATCH v5 7/7] sparc64: " Yang Shi
2015-12-09 21:22 ` Yang Shi
2015-12-09 21:22 ` Yang Shi
2016-01-13 18:13 ` Shi, Yang
2016-01-13 18:13 ` Shi, Yang
2016-01-13 18:13 ` Shi, Yang
2016-01-13 20:21 ` David Miller
2016-01-13 20:21 ` David Miller
2016-01-13 20:21 ` David Miller
2016-01-13 20:44 ` Steven Rostedt
2016-01-13 20:44 ` Steven Rostedt
2016-01-13 20:44 ` Steven Rostedt
2016-01-12 20:00 ` [RFC V5] Add gup trace points support Shi, Yang
2016-01-12 20:00 ` Shi, Yang
2016-01-12 20:10 ` Steven Rostedt
2016-01-12 20:10 ` Steven Rostedt
2016-01-13 18:14 ` Shi, Yang [this message]
2016-01-13 18:14 ` Shi, Yang
2016-01-14 14:40 ` Steven Rostedt
2016-01-14 14:40 ` Steven Rostedt
2016-02-08 23:15 ` Shi, Yang
2016-02-08 23:15 ` Shi, Yang
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=56969400.6020805@linaro.org \
--to=yang.shi@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.