From: Jochen Friedrich <jochen@scram.de>
To: Laurent Pinchart <laurentp@cse-semaphore.com>
Cc: "linuxppc-dev@ozlabs.org list" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc: Implement GPIO LIB API on CPM2 Freescale SoC.
Date: Thu, 17 Apr 2008 14:48:46 +0200 [thread overview]
Message-ID: <4807472E.9000300@scram.de> (raw)
In-Reply-To: <200804171408.46533.laurentp@cse-semaphore.com>
Hi Laurent,
> Any preference for common function names ? cpm2_gpio32* might be too
> CPM2-specific for cpm_common.c. cpm_gpio32* is a bit too generic as it
> doesn't support port E on the CPM1.
I would keep the cpm2 name. I'll just add a comment to cpm1.c that
fsl,cpm1-pario-bank32e uses cpm2 layout.
Thanks,
Jochen
prev parent reply other threads:[~2008-04-17 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 9:48 [PATCH] powerpc: Implement GPIO LIB API on CPM2 Freescale SoC Laurent Pinchart
2008-04-17 10:13 ` Jochen Friedrich
2008-04-17 11:11 ` Laurent Pinchart
2008-04-17 11:21 ` Jochen Friedrich
2008-04-17 12:08 ` Laurent Pinchart
2008-04-17 12:46 ` Jochen Friedrich
2008-04-17 12:48 ` Jochen Friedrich [this message]
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=4807472E.9000300@scram.de \
--to=jochen@scram.de \
--cc=laurentp@cse-semaphore.com \
--cc=linuxppc-dev@ozlabs.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).