From: Kevin Hilman <khilman@deeprootsystems.com>
To: Romit Dasgupta <romit@ti.com>
Cc: "Menon, Nishanth" <nm@ti.com>,
linux omap <linux-omap@vger.kernel.org>,
"K, Ambresh" <ambresh@ti.com>
Subject: Re: [PATCH 1/2] io: remove redundant params in omap2_init_common_hw
Date: Tue, 22 Dec 2009 09:08:46 -0800 [thread overview]
Message-ID: <871vinq6ld.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4B2F1EC3.3060001@ti.com> (Romit Dasgupta's message of "Mon\, 21 Dec 2009 12\:37\:47 +0530")
Romit Dasgupta <romit@ti.com> writes:
>> - omap2_init_common_hw(NULL, NULL, NULL, NULL, NULL);
>> + omap2_init_common_hw(NULL, NULL);
>
>
> A call to a function with NULL parameters suggests that the function is doing
> more than it should.
Not necessarily. It can also suggest that this board does not want to
override any default settings.
> I think omap2_init_common_hw and omap2_sdrc_init,
> _omap2_init_reprogram_sdrc, gpmc init can be separated from
> omap2_init_common_hw.
>
> If you are refactoring the code may be this should be taken care as
> well.
In this case, Nishanth is not refactoring, he's just removing some code
added earlier in the PM branch that is no longer needed.
A patch to do what you suggest (which is a good idea) should be a
separate patch and generated against l-o master.
Kevin
next prev parent reply other threads:[~2009-12-22 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 13:10 [PATCH 0/2] omap:pm: cleanup omap3_[mpu|dsp|l3]_rate_table Nishanth Menon
2009-12-19 13:10 ` [PATCH 1/2] io: remove redundant params in omap2_init_common_hw Nishanth Menon
2009-12-19 13:10 ` [PATCH 2/2] omap3: pm: remove omap3_[mpu|dsp|l3]_rate_tables Nishanth Menon
2009-12-21 7:07 ` [PATCH 1/2] io: remove redundant params in omap2_init_common_hw Romit Dasgupta
2009-12-22 17:08 ` Kevin Hilman [this message]
2009-12-22 17:02 ` Kevin Hilman
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=871vinq6ld.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=ambresh@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=romit@ti.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.