All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Felipe Balbi <balbi@ti.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
	Magnus Damm <damm@opensource.se>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Andi Kleen <ak@linux.intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] device: add dev_WARN_ONCE
Date: Wed, 16 Mar 2011 07:39:34 -0700	[thread overview]
Message-ID: <20110316143934.GA16166@suse.de> (raw)
In-Reply-To: <1300283975-27556-1-git-send-email-balbi@ti.com>

On Wed, Mar 16, 2011 at 03:59:35PM +0200, Felipe Balbi wrote:
> it's quite useful to print the device name
> on the stack dump caused by WARN(), but
> there are other cases where we might want
> to use WARN_ONCE.
> 
> Introduce a helper similar to dev_WARN() for
> that case too.
> 
> Signed-off-by: Felipe Balbi <balbi@ti.com>

Do you have code that needs this for .39, or can it wait for .40?

thanks,

greg k-h

  reply	other threads:[~2011-03-16 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 13:59 [PATCH] device: add dev_WARN_ONCE Felipe Balbi
2011-03-16 14:39 ` Greg KH [this message]
2011-03-16 15:53   ` Felipe Balbi

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=20110316143934.GA16166@suse.de \
    --to=gregkh@suse.de \
    --cc=ak@linux.intel.com \
    --cc=balbi@ti.com \
    --cc=damm@opensource.se \
    --cc=ebiederm@xmission.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.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.