From: Felipe Balbi <balbi@ti.com>
To: "Per Förlin" <per.forlin@stericsson.com>
Cc: "balbi@ti.com" <balbi@ti.com>,
Mian Yousaf KAUKAB <mian.yousaf.kaukab@stericsson.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linaro-dev@lists.linaro.org" <linaro-dev@lists.linaro.org>,
Per Forlin <per.forlin@linaro.org>
Subject: Re: [PATCH] usb: musb: ux500: replace missing DBG with dev_dbg
Date: Wed, 3 Aug 2011 16:30:44 +0300 [thread overview]
Message-ID: <20110803133044.GN11080@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <4E394CC0.7050208@stericsson.com>
[-- Attachment #1: Type: text/plain, Size: 854 bytes --]
On Wed, Aug 03, 2011 at 03:27:28PM +0200, Per Förlin wrote:
> On 08/03/2011 03:17 PM, Felipe Balbi wrote:
> > On Wed, Aug 03, 2011 at 02:22:17PM +0200, Per Forlin wrote:
> >> From: Per Forlin <per.forlin@linaro.org>
> >>
> >> ux500_dma.c fail to compile becase DBG has been removed from musb_debug.
> >> Use dev_dbg for all prints.
> >>
> >> Signed-off-by: Per Forlin <per.forlin@linaro.org>
> >> Acked-by: Mian Yousaf Kaukab<mian.yousaf.kaukab@stericsson.com>
> >
> > applied, thanks. Let me know if this should go to stable and I can make
> > sure of adding stable to the Cc list.
> >
> I checked v3.0, and both ux500_dma and cppi_dma use DBG. These two
> files wont build in v3.0. Please CC stable.
ok, will do.
> I am about to send patch to fix cppi_dma as well. Should I CC stable
> when I post it?
yes :-)
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2011-08-03 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 12:22 Per Forlin
2011-08-03 13:16 ` Felipe Balbi
2011-08-03 13:17 ` Felipe Balbi
2011-08-03 13:27 ` Per Förlin
2011-08-03 13:30 ` Felipe Balbi [this message]
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=20110803133044.GN11080@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=gregkh@suse.de \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mian.yousaf.kaukab@stericsson.com \
--cc=per.forlin@linaro.org \
--cc=per.forlin@stericsson.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
all inboxes | Powered by JetHome®