From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <me@felipebalbi.com>
Cc: Grazvydas Ignotas <notasas@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] Add touchscreen support for Pandora
Date: Wed, 5 Nov 2008 17:17:38 -0800 [thread overview]
Message-ID: <20081106011738.GK21736@atomide.com> (raw)
In-Reply-To: <20081105235541.GH4010@frodo>
* Felipe Balbi <me@felipebalbi.com> [081105 15:56]:
> On Thu, Nov 06, 2008 at 01:41:46AM +0200, Grazvydas Ignotas wrote:
> > Yes, it's more like a placeholder for future patches. I plan to add a
> > function prototype and some more GPIOs. I also plan adding another
> > board file for input stuff (board-omap3pandora-input.c), as pandora
> > has lots of GPIO buttons with full qwerty keypad, and I don't want to
> > clutter the main board file with large arrays of structures.
> > If this is not acceptable I can stuff everything into board-omap3pandora.c
>
> I think tony has the final word here, but generally the other board
> files have the keypad stuff in the main board file (board-n800.c,
> board-3430sdp.c, board-2430sdp.c, etc)
>
> About the defines, it's only nice to put them in the header iff you
> need to use the same define on two (or more) different files. Otherwise,
> you can make the defines local to the file that needs them :-)
Well the header should be there only if needed for other boards.
Tony
prev parent reply other threads:[~2008-11-06 1:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 21:19 [PATCH 1/2] Add touchscreen support for Pandora Grazvydas Ignotas
2008-11-05 21:19 ` [PATCH 2/2] Enable touchscreen in pandora's defconfig Grazvydas Ignotas
2008-11-05 22:39 ` [PATCH 1/2] Add touchscreen support for Pandora Felipe Balbi
2008-11-05 23:41 ` Grazvydas Ignotas
2008-11-05 23:56 ` Felipe Balbi
2008-11-06 1:17 ` Tony Lindgren [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=20081106011738.GK21736@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=notasas@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox