All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@redhat.com>,
	"zhangwei(Jovi)" <jovi.zhangwei@huawei.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] tracing: kill the no longer needed PITA code
Date: Sun, 11 Aug 2013 19:49:29 +0200	[thread overview]
Message-ID: <20130811174929.GA12119@redhat.com> (raw)
In-Reply-To: <1375292913.5418.8.camel@gandalf.local.home>

On 07/31, Steven Rostedt wrote:
>
> On Wed, 2013-07-31 at 19:31 +0200, Oleg Nesterov wrote:
> > Hello.
> >
> > Simple cleanups on top of the recent (already applied)
> > id/filter/format/enable changes.
> >
> > f_op->owner == mod is no longer needed and can go away.
> >
>
> This patch set is not needed for 3.11. I'll be holding off my review
> until I have all the 3.11 patches settled.

It seems that you have no more 3.11 patches.

Should I resend this series?

Oleg.


  reply	other threads:[~2013-08-11 17:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 17:31 [PATCH 0/3] tracing: kill the no longer needed PITA code Oleg Nesterov
2013-07-31 17:31 ` [PATCH 1/3] tracing: Kill trace_create_file_ops() and friends Oleg Nesterov
2013-07-31 17:31 ` [PATCH 2/3] tracing: Don't pass file_operations array to event_create_dir() Oleg Nesterov
2013-07-31 17:31 ` [PATCH 3/3] tracing: Kill the !CONFIG_MODULES code in trace_events.c Oleg Nesterov
2013-07-31 17:48 ` [PATCH 0/3] tracing: kill the no longer needed PITA code Steven Rostedt
2013-08-11 17:49   ` Oleg Nesterov [this message]
2013-08-12  0:20     ` Steven Rostedt
2013-08-12 17:16       ` Oleg Nesterov

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=20130811174929.GA12119@redhat.com \
    --to=oleg@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=jovi.zhangwei@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --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.