public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Make preparatory patches that initially have no effect?
Date: Sat, 14 Aug 2010 11:07:05 +0200	[thread overview]
Message-ID: <4C665CB9.2040406@emk-elektronik.de> (raw)

Hello,

my current work in the AT91 SoCs will add several new drivers.

Some of them require new header files in arch-at91 or amendments
to existing header files there. Same for some at91 specific
header files in driver/*.

In existing header files it is adding adresses for
going-to-be-used devices and proper struct SoC defines for
them, the new header files will only allow struct SoC access
anyway.

If I add those discrete changes to each driver patch (where it
might actually belong), the incremental changes to some of
those files would require all those driver patches to be applied
in the right order to avoid conflicts.

Therefore I would like to put all new header files and all
changes to header files in one patch which would need to be
applied before the driver patches.

That patch would essentially cause no change to existing code.

Anyone find this idea bad?

Reinhard

             reply	other threads:[~2010-08-14  9:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-14  9:07 Reinhard Meyer [this message]
2010-08-14 14:30 ` [U-Boot] Make preparatory patches that initially have no effect? Wolfgang Denk
2010-08-14 17:05   ` Reinhard Meyer
2010-08-14 18:46     ` Wolfgang Denk
2010-08-14 19:30       ` [U-Boot] Struct SoC access (was:Make preparatory patches that initially have no effect?) Reinhard Meyer
2010-08-14 19:36         ` Mike Frysinger
2010-08-14 19:40           ` [U-Boot] Struct SoC access Reinhard Meyer
2010-08-14 20:48             ` Mike Frysinger
2010-08-14 19:41         ` [U-Boot] Struct SoC access (was:Make preparatory patches that initially have no effect?) Wolfgang Denk
2010-08-14 19:58           ` [U-Boot] Struct SoC access Reinhard Meyer
2010-08-14 20:47             ` Reinhard Meyer
2010-08-14 21:49               ` Wolfgang Denk
2010-08-14 21:47             ` Wolfgang Denk
2010-08-14 22:15               ` Reinhard Meyer
2010-08-16 20:21                 ` Scott Wood
2010-08-17  6:58                   ` Reinhard Meyer

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=4C665CB9.2040406@emk-elektronik.de \
    --to=u-boot@emk-elektronik.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