From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 08/10] ARMV7: Restructure OMAP i2c driver to allow code sharing between OMAP3 and OMAP4
Date: Thu, 17 Jun 2010 07:15:56 +0200 [thread overview]
Message-ID: <4C19AF8C.9040208@denx.de> (raw)
In-Reply-To: <AANLkTil00oWkK5l8EG1TZUUETPt4LcKAvPaK1UCY230W@mail.gmail.com>
Hello Steve,
Steve Sakoman wrote:
> On Mon, Jun 14, 2010 at 11:47 PM, Heiko Schocher <hs@denx.de> wrote:
>
>> Instead of making here a third copy of this defines, we
>> should make a common omap i2c.h file, which collects all
>> common defines, and only add in this file here the
>> specific defines.
>>
>> This applies to a lot of defines below. Please
>> clean up, thanks!
>
> Thanks for the comments. I made the changes and I'm preparing a
> version 2 patch.
Thanks.
> A quick procedure question. Should I post individual version 2 patch
> replies for each patch in the series that has received comments, or is
> it preferred to post a complete version 2 series? I see both
> approaches used on the list so I'm a bit confused which is proper.
I have no preference, both seems Ok to me. Say you have to make
for some patches a version 2, 3, 4 and they fit together with
lower versions from other patches from your patch series, it is
okay to post only individual versions, but the complexity can grow,
mainline code changes, so it could make sense to post the complete
patch series again.
bye
Heiko
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2010-06-17 5:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 4:39 [U-Boot] [PATCH 00/10] Add support for TI OMAP4 SDP and Panda Steve Sakoman
2010-06-15 4:39 ` [U-Boot] [PATCH 01/10] ARM: Rename arch/arm/cpu/arm_cortexa8 to armv7 Steve Sakoman
2010-06-15 4:39 ` [U-Boot] [PATCH 02/10] ARMV7: Add basic support for TI OMAP4 Steve Sakoman
2010-06-15 5:48 ` Vaibhav Bedia
2010-06-17 19:36 ` Steve Sakoman
2010-06-15 4:39 ` [U-Boot] [PATCH 03/10] ARMV7: Add support for TI OMAP4430 SDP Steve Sakoman
2010-06-15 5:26 ` Vaibhav Bedia
2010-06-15 19:45 ` Steve Sakoman
2010-06-15 4:39 ` [U-Boot] [PATCH 04/10] ARMV7: Add support for TI OMAP4 Panda Steve Sakoman
2010-06-15 5:55 ` Vaibhav Bedia
2010-06-15 4:39 ` [U-Boot] [PATCH 05/10] ARMV7: Restructure OMAP mmc driver to allow code sharing between OMAP3 and OMAP4 Steve Sakoman
2010-06-15 4:39 ` [U-Boot] [PATCH 06/10] ARMV7: Enable mmc support on TI OMAP4430 SDP Steve Sakoman
2010-06-15 4:39 ` [U-Boot] [PATCH 07/10] ARMV7: Enable mmc support on TI OMAP4 Panda Steve Sakoman
2010-06-15 4:39 ` [U-Boot] [PATCH 08/10] ARMV7: Restructure OMAP i2c driver to allow code sharing between OMAP3 and OMAP4 Steve Sakoman
2010-06-15 6:47 ` Heiko Schocher
2010-06-17 4:05 ` Steve Sakoman
2010-06-17 5:15 ` Heiko Schocher [this message]
2010-06-15 4:39 ` [U-Boot] [PATCH 09/10] ARMV7: Enable i2c support on TI OMAP4 SDP Steve Sakoman
2010-06-15 6:47 ` Heiko Schocher
2010-06-15 4:39 ` [U-Boot] [PATCH 10/10] ARMV7: Enable i2c support on TI OMAP4 Panda Steve Sakoman
2010-06-15 6:47 ` Heiko Schocher
2010-06-15 14:34 ` [U-Boot] [PATCH 00/10] Add support for TI OMAP4 SDP and Panda John Rigby
2010-06-15 20:45 ` Paulraj, Sandeep
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=4C19AF8C.9040208@denx.de \
--to=hs@denx.de \
--cc=u-boot@lists.denx.de \
/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