linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH v5] remove no longer use of pdflush interface
Date: Wed, 13 Jun 2012 06:18:00 +0000 (UTC)	[thread overview]
Message-ID: <jr9ban$4mi$1@dough.gmane.org> (raw)
In-Reply-To: 1339374670-2821-1-git-send-email-liwp.linux@gmail.com

On Mon, 11 Jun 2012 at 00:31 GMT, Wanpeng Li <liwp.linux@gmail.com> wrote:
> +	printk_once(KERN_WARNING "%s exported in /proc is scheduled for removal\n",
> +			table->procname);
> +

This equals to WARN_ONCE(1, ....);


  reply	other threads:[~2012-06-13  6:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11  0:31 [PATCH v5] remove no longer use of pdflush interface Wanpeng Li
2012-06-13  6:18 ` Cong Wang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-11  0:29 Wanpeng Li

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='jr9ban$4mi$1@dough.gmane.org' \
    --to=xiyou.wangcong@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 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).