All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yao Yuan <yao.yuan@freescale.com>
To: Arnd Bergmann <arnd@arndb.de>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Cc: "vinod.koul@intel.com" <vinod.koul@intel.com>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stefan@agner.ch" <stefan@agner.ch>
Subject: RE: [PATCH] dmaengine: fsl-edma: add PM suspend/resume support
Date: Thu, 16 Jul 2015 08:01:38 +0000	[thread overview]
Message-ID: <BL2PR03MB3380E34F751336BA0C0C5F283990@BL2PR03MB338.namprd03.prod.outlook.com> (raw)
In-Reply-To: <2042080.Y9rzRSQLpW@wuerfel>

Hi Arnd,
Ok, I will remove the #ifdef in the next version.
Thanks.

Hi All,
Is there any others comments?

Thanks for your review.

Best Regards,
Yuan Yao

On Wednesday, July 15, 2015 10:55 PM Arnd wrote:
> On Wednesday 15 July 2015 10:29:55 Yao Yuan wrote:
> > Hi Arnd,
> >
> > Thanks for your review.
> > And can you give me more information?
> > In my opinion, The fsl_edma_pm_state will just be used when CONFIG_PM
> > support. So why not use the #ifdefs to remove the unnecessary code? Since
> the PM will not be selected in many use cases.
> 
> I would consider code readability more important than saving a few instructions,
> and the #ifdef interrupts the reading flow.
> Another aspect is that the compiler does not produce warnings for incorrect
> code in an #ifdef, so we try to use e.g. 'if (IS_ENABLED(CONFIG_FOO))'
> instead of '#ifdef CONFIG_FOO' wherever possible.
> 
> 	Arnd

WARNING: multiple messages have this Message-ID (diff)
From: yao.yuan@freescale.com (Yao Yuan)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: fsl-edma: add PM suspend/resume support
Date: Thu, 16 Jul 2015 08:01:38 +0000	[thread overview]
Message-ID: <BL2PR03MB3380E34F751336BA0C0C5F283990@BL2PR03MB338.namprd03.prod.outlook.com> (raw)
In-Reply-To: <2042080.Y9rzRSQLpW@wuerfel>

Hi Arnd,
Ok, I will remove the #ifdef in the next version.
Thanks.

Hi All,
Is there any others comments?

Thanks for your review.

Best Regards,
Yuan Yao

On Wednesday, July 15, 2015 10:55 PM Arnd wrote:
> On Wednesday 15 July 2015 10:29:55 Yao Yuan wrote:
> > Hi Arnd,
> >
> > Thanks for your review.
> > And can you give me more information?
> > In my opinion, The fsl_edma_pm_state will just be used when CONFIG_PM
> > support. So why not use the #ifdefs to remove the unnecessary code? Since
> the PM will not be selected in many use cases.
> 
> I would consider code readability more important than saving a few instructions,
> and the #ifdef interrupts the reading flow.
> Another aspect is that the compiler does not produce warnings for incorrect
> code in an #ifdef, so we try to use e.g. 'if (IS_ENABLED(CONFIG_FOO))'
> instead of '#ifdef CONFIG_FOO' wherever possible.
> 
> 	Arnd

  reply	other threads:[~2015-07-16  8:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15  9:32 Yuan Yao
2015-07-15  9:32 ` No subject Yuan Yao
2015-07-15  9:32 ` [PATCH] dmaengine: fsl-edma: add PM suspend/resume support Yuan Yao
2015-07-15  9:32   ` Yuan Yao
2015-07-15  9:56   ` Arnd Bergmann
2015-07-15  9:56     ` Arnd Bergmann
2015-07-15 10:29     ` Yao Yuan
2015-07-15 10:29       ` Yao Yuan
2015-07-15 14:54       ` Arnd Bergmann
2015-07-15 14:54         ` Arnd Bergmann
2015-07-16  8:01         ` Yao Yuan [this message]
2015-07-16  8:01           ` Yao Yuan
2015-07-16 13:24   ` Vinod Koul
2015-07-16 13:24     ` Vinod Koul
2015-07-17  5:41     ` Yao Yuan
2015-07-17  5:41       ` Yao Yuan

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=BL2PR03MB3380E34F751336BA0C0C5F283990@BL2PR03MB338.namprd03.prod.outlook.com \
    --to=yao.yuan@freescale.com \
    --cc=arnd@arndb.de \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefan@agner.ch \
    --cc=vinod.koul@intel.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.