linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miroslav Benes <mbenes@suse.cz>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: mingo@redhat.com, tom.zanussi@linux.intel.com,
	mhiramat@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ring-buffer: Remove unused function ring_buffer_page_len()
Date: Wed, 6 Feb 2019 17:24:45 +0100 (CET)	[thread overview]
Message-ID: <alpine.LSU.2.21.1902061723490.30584@pobox.suse.cz> (raw)
In-Reply-To: <20181228183313.674ef6de@gandalf.local.home>

On Fri, 28 Dec 2018, Steven Rostedt wrote:

> On Fri, 28 Dec 2018 14:38:47 +0100
> Miroslav Benes <mbenes@suse.cz> wrote:
> 
> > Commit 6b7e633fe9c2 ("tracing: Remove extra zeroing out of the ring
> > buffer page") removed the only caller of ring_buffer_page_len(). The
> > function is now unused and may be removed.
> > 
> > Signed-off-by: Miroslav Benes <mbenes@suse.cz>
> > ---
> > I am sorry if you received the patch more than once (hopefully not). For some
> > strange reasons git send-email segfaulted, I tried to send from a different
> > machine and made a mistake. Holiday mode *sigh*.
> > 
> >
> 
> No worries. I'm also in holiday mode. I marked the patch in my INBOX
> and hopefully when I'm back to work it's not buried and lost for months.
> 
> Even if it is, I periodically purge my INBOX where I find missing
> patches like these ;-)
> 
> So if it's not applied in a couple of weeks, just ping me about it.

Gentle ping...

Miroslav

  reply	other threads:[~2019-02-06 16:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-28 13:38 [PATCH] ring-buffer: Remove unused function ring_buffer_page_len() Miroslav Benes
2018-12-28 23:33 ` Steven Rostedt
2019-02-06 16:24   ` Miroslav Benes [this message]
2019-02-06 16:54     ` Steven Rostedt
2019-02-06 16:59       ` 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=alpine.LSU.2.21.1902061723490.30584@pobox.suse.cz \
    --to=mbenes@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tom.zanussi@linux.intel.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).