From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] ARM: davinci: re-arrange definitions to have a common davinci header
Date: Mon, 12 Dec 2011 15:03:34 +0000 [thread overview]
Message-ID: <20111212150334.GA20178@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <DF0F476B391FA8409C78302C7BA518B6043FD6@DBDE01.ent.ti.com>
On Mon, Dec 12, 2011 at 11:25:11AM +0000, Nori, Sekhar wrote:
> Hi Manju,
>
> On Thu, Dec 08, 2011 at 19:25:23, Hadli, Manjunath wrote:
> > Re-arrange definitions and remove unnecessary code so that we can
> > have a common header for all davinci platforms. This will enable
> > us to share defines and enable common routines to be used without
> > polluting hardware.h.
> > This patch set forms the base for a later set of patches for having
> > a common system module base address (DAVINCI_SYSTEM_MODULE_BASE).
>
> Its easy to dismiss this series as causing "needless churn" by
> moving around definitions from header to C files and consolidating
> definitions from multiple header files to one.
>
> You need to do a better job of "selling" this series. The best way
> to do that would be to include future patches which benefit from
> this series into this series itself. This way, its clear to judge
> the relative benefit of the "churn". You gave some examples, but
> showing code helps.
>
> Also, one of the biggest gains from this series is reducing the
> pollution in include/mach as asked by Russell in his "pet peaves"
> mail. That should find reference in the cover letter and in the
> commit text of patch 5/5.
Indeed, and I hope it takes into account (at some point) the restart
changes.
next prev parent reply other threads:[~2011-12-12 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-08 13:55 [PATCH v4 0/5] ARM: davinci: re-arrange definitions to have a common davinci header Manjunath Hadli
2011-12-08 13:55 ` [PATCH v4 1/5] davinci: vpif: remove obsolete header file inclusion Manjunath Hadli
2011-12-08 13:55 ` [PATCH v4 2/5] ARM: davinci: dm644x: remove the macros from the header to move to c file Manjunath Hadli
2011-12-08 13:55 ` [PATCH v4 3/5] ARM: davinci: dm365: " Manjunath Hadli
2011-12-08 13:55 ` [PATCH v4 4/5] ARM: davinci: dm646x: " Manjunath Hadli
2011-12-08 13:55 ` [PATCH v4 5/5] ARM: davinci: create new common platform header for davinci Manjunath Hadli
2011-12-09 10:50 ` Sergei Shtylyov
2011-12-12 11:25 ` [PATCH v4 0/5] ARM: davinci: re-arrange definitions to have a common davinci header Nori, Sekhar
2011-12-12 15:03 ` Russell King - ARM Linux [this message]
2011-12-13 9:38 ` Hadli, Manjunath
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=20111212150334.GA20178@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).