From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] dma: sh: inherit debug options from the subsystem for sh
Date: Thu, 10 Jul 2014 12:25:58 +0000 [thread overview]
Message-ID: <9184799.0kesuWAK5g@avalon> (raw)
In-Reply-To: <1404033022-3014-1-git-send-email-wsa@the-dreams.de>
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
Hi Wolfram,
On Thursday 03 July 2014 10:48:34 Wolfram Sang wrote:
> Hi,
>
> > With dynamic debug, these flags dont make much sense unless you want
> > something to be printed *always* during boot.
>
> Yes, this was exactly what I wanted.
Why is that ? My understanding is that the purpose of the
CONFIG_DMADEVICES_DEBUG option is to enable debug messages for debugging. As
it requires recompiling the kernel, wouldn't dynamic printk be a better
alternative ?
> So, for consistency reasons I copied the existing mechanism over to sh. If
> it turns out that the desired default is something different, I'll send
> patches for that.
--
Regards,
Laurent Pinchart
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-07-10 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 9:10 [PATCH] dma: sh: inherit debug options from the subsystem for sh Wolfram Sang
2014-06-29 9:32 ` Geert Uytterhoeven
2014-06-29 19:56 ` Laurent Pinchart
2014-06-30 13:51 ` Vinod Koul
2014-07-03 8:48 ` Wolfram Sang
2014-07-03 9:14 ` Vinod Koul
2014-07-10 11:56 ` Wolfram Sang
2014-07-10 12:25 ` Laurent Pinchart [this message]
2014-07-10 12:48 ` Wolfram Sang
2014-07-10 15:21 ` Vinod Koul
2014-07-10 15:22 ` Vinod Koul
2014-07-10 15:42 ` Laurent Pinchart
2014-07-11 8:32 ` Simon Horman
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=9184799.0kesuWAK5g@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox