From: lethal@linux-sh.org (Paul Mundt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] arm & sh: factorised duplicated clkdev.c
Date: Wed, 17 Nov 2010 13:11:06 +0900 [thread overview]
Message-ID: <20101117041106.GC2790@linux-sh.org> (raw)
In-Reply-To: <1289919848-23262-1-git-send-email-plagnioj@jcrosoft.com>
On Tue, Nov 16, 2010 at 04:04:08PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> factorise some generic infrastructure to assist looking up struct clks
> for the ARM & SH architecture.
>
> as the code is identical at 99%
>
> put the arch specific code for allocation as example in asm/clkdev.h
>
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> Acked-by: Paul Mundt <lethal@linux-sh.org>
I've you've finally addressed Russell's comments and nothing else has
changed, then you should just resubmit the updated version to the patch
tracker.
next prev parent reply other threads:[~2010-11-17 4:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 15:04 [PATCH v4] arm & sh: factorised duplicated clkdev.c Jean-Christophe PLAGNIOL-VILLARD
2010-11-17 4:11 ` Paul Mundt [this message]
2010-11-17 9:06 ` Jean-Christophe PLAGNIOL-VILLARD
2011-01-13 15:59 ` [PATCH] ARM mxs: clkdev related compile fixes Uwe Kleine-König
2011-01-14 8:27 ` Jean-Christophe PLAGNIOL-VILLARD
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=20101117041106.GC2790@linux-sh.org \
--to=lethal@linux-sh.org \
--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