From: Jens Scharsig <js_at_ng@scharsoft.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/8 V2] add at91 SoC access with c structures
Date: Sat, 23 Jan 2010 12:00:31 +0100 [thread overview]
Message-ID: <4B5AD6CF.6070407@scharsoft.de> (raw)
In-Reply-To: <4B53561B.9040104@windriver.com>
Hello Tom,
> By bisectable, i mean that early patches do not depend on later patches.
> It should be possible to just apply patch 1 without applying any of
> the other patch.
>
> Patch 1 looks like is contains the union of all the config file changes.
> What it should have contained was only 1 change adding CONFIG_AT91_LEGACY.
> Fixing this will mean separating this changes into their logical parts
> and rebasing the patchset to include then in the correct order.
> This is a task best done as you develop instead of after the fact. This is
> why i recommended that it may be easier to break this patchset into multiple
> pieces and submit them separately.
>
I have fully restructured the patch. I will send this as V3 within the
next hour.
The Parts are now only depended from 9 to 1, but independed from 1 to 9.
regards
Jens
prev parent reply other threads:[~2010-01-23 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-16 20:28 [U-Boot] [PATCH 1/8 V2] add at91 SoC access with c structures Jens Scharsig
2010-01-17 17:34 ` Tom
2010-01-17 17:48 ` Jens Scharsig
2010-01-17 18:25 ` Tom
2010-01-17 19:02 ` Jens Scharsig
2010-01-23 11:00 ` Jens Scharsig [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=4B5AD6CF.6070407@scharsoft.de \
--to=js_at_ng@scharsoft.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