From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: David Cohen <dacohen@gmail.com>
Cc: Sergei Shtylyov <sshtylyov@mvista.com>,
tony@atomide.com, linux-omap@vger.kernel.org,
Hiroshi.DOYU@nokia.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] OMAP2+: IOMMU: change OMAP2+ error message to dev_dbg()
Date: Tue, 15 Feb 2011 15:51:55 +0000 [thread overview]
Message-ID: <20110215155155.GE11199@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTin=4z0o6=J9f-1mszvGrpaRMgCMk=Ckh5+9j6EQ@mail.gmail.com>
On Tue, Feb 15, 2011 at 04:50:29PM +0200, David Cohen wrote:
> That could be my choice.
> I'm not planing to resend this patch, but how good/bad it sounds to
> you to have dev_dbg_cont() for such situation?
That doesn't help when the message gets corrupted by another thread,
so I'd much prefer the "format line then print" approach rather than
the blah_CONT stuff.
WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] OMAP2+: IOMMU: change OMAP2+ error message to dev_dbg()
Date: Tue, 15 Feb 2011 15:51:55 +0000 [thread overview]
Message-ID: <20110215155155.GE11199@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTin=4z0o6=J9f-1mszvGrpaRMgCMk=Ckh5+9j6EQ@mail.gmail.com>
On Tue, Feb 15, 2011 at 04:50:29PM +0200, David Cohen wrote:
> That could be my choice.
> I'm not planing to resend this patch, but how good/bad it sounds to
> you to have dev_dbg_cont() for such situation?
That doesn't help when the message gets corrupted by another thread,
so I'd much prefer the "format line then print" approach rather than
the blah_CONT stuff.
next prev parent reply other threads:[~2011-02-15 15:52 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 13:20 [PATCH 0/2] IOMMU fault callback support David Cohen
2011-02-15 13:20 ` David Cohen
2011-02-15 13:20 ` [PATCH 1/2] OMAP2+: IOMMU: change OMAP2+ error message to dev_dbg() David Cohen
2011-02-15 13:20 ` David Cohen
2011-02-15 13:38 ` Sergei Shtylyov
2011-02-15 13:38 ` Sergei Shtylyov
2011-02-15 13:44 ` David Cohen
2011-02-15 13:44 ` David Cohen
2011-02-15 13:56 ` Sergei Shtylyov
2011-02-15 13:56 ` Sergei Shtylyov
2011-02-15 14:01 ` David Cohen
2011-02-15 14:01 ` David Cohen
2011-02-15 13:59 ` Jarkko Nikula
2011-02-15 13:59 ` Jarkko Nikula
2011-02-15 14:08 ` David Cohen
2011-02-15 14:08 ` David Cohen
2011-02-15 14:21 ` David Cohen
2011-02-15 14:21 ` David Cohen
2011-02-15 14:30 ` Jarkko Nikula
2011-02-15 14:30 ` Jarkko Nikula
2011-02-15 14:29 ` Russell King - ARM Linux
2011-02-15 14:29 ` Russell King - ARM Linux
2011-02-15 14:36 ` David Cohen
2011-02-15 14:36 ` David Cohen
2011-02-15 14:44 ` Russell King - ARM Linux
2011-02-15 14:44 ` Russell King - ARM Linux
2011-02-15 14:50 ` David Cohen
2011-02-15 14:50 ` David Cohen
2011-02-15 15:51 ` Russell King - ARM Linux [this message]
2011-02-15 15:51 ` Russell King - ARM Linux
2011-02-15 13:20 ` [PATCH 2/2] OMAP: IOMMU: add support to callback during fault handling David Cohen
2011-02-15 13:20 ` David Cohen
2011-02-15 13:32 ` [PATCH 0/2] IOMMU fault callback support David Cohen
2011-02-15 13:32 ` David Cohen
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=20110215155155.GE11199@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Hiroshi.DOYU@nokia.com \
--cc=dacohen@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=sshtylyov@mvista.com \
--cc=tony@atomide.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 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.