From: Steven Rostedt <rostedt@goodmis.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Jason Wessel <jason.wessel@windriver.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
kgdb-bugreport@lists.sourceforge.net,
Brian Norris <briannorris@chromium.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 1/3] tracing: kdb: The skip_lines parameter should have been skip_entries
Date: Fri, 26 Apr 2019 21:32:16 -0400 [thread overview]
Message-ID: <20190426213216.7835d14a@oasis.local.home> (raw)
In-Reply-To: <CAD=FV=XbHa3GrgVMAAcf2e0W5t1gc--Z2t0vWa9RhSo32w12zA@mail.gmail.com>
On Fri, 26 Apr 2019 15:26:48 -0700
Doug Anderson <dianders@chromium.org> wrote:
> Hi,
>
> On Tue, Mar 19, 2019 at 10:12 AM Douglas Anderson <dianders@chromium.org> wrote:
> Steven: do you know if/when you plan to take this series? There's no
> crazy hurry and if you like I can sent a calendar alert to remember to
> ping you after 5.1 is released so you can land this in a "for 5.3"
> queue. Just let me know. :-)
I can add this in this to my queue for this coming merge window.
-- Steve
prev parent reply other threads:[~2019-04-27 1:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 17:12 Douglas Anderson
2019-03-19 17:12 ` [PATCH v6 2/3] tracing: Add trace_total_entries() / trace_total_entries_cpu() Douglas Anderson
2019-03-19 17:12 ` [PATCH v6 3/3] tracing: kdb: Allow ftdump to skip all but the last few entries Douglas Anderson
2019-03-20 10:50 ` Daniel Thompson
2019-04-26 22:26 ` [PATCH v6 1/3] tracing: kdb: The skip_lines parameter should have been skip_entries Doug Anderson
2019-04-27 1:32 ` Steven Rostedt [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=20190426213216.7835d14a@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=briannorris@chromium.org \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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®