From: Haavard Skinnemoen <hskinnemoen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Pull request u-boot-blackfin.git
Date: Sun, 24 Feb 2008 01:35:05 +0100 [thread overview]
Message-ID: <20080224013505.390223de@siona> (raw)
In-Reply-To: <200802231907.22816.vapier@gentoo.org>
On Sat, 23 Feb 2008 19:07:22 -0500
Mike Frysinger <vapier@gentoo.org> wrote:
> > That's why we do incremental improvements so that you can separate the
> > fixes from the other stuff and submit them even if there isn't a merge
> > window open.
>
> it's already been done
Then how come you're still trying to push 400k changesets outside the
merge window?
> my understanding was that all commands go in common/. there's plenty of
> arch-specific commands in there already.
I still think it's wrong...although if there's an existing consensus
that all commands go under common/, I'm not going to argue further
against it.
> > Second, the SPI driver that broke the tree for almost four weeks was
> > optional and ppc-specific. Have you run tests on all architectures so
> > that you can be 100% sure that you're not breaking anything this late
> > in the release cycle?
>
> i make my things conditionally compiled (see the Makefile). so yes, i'm 100%
> sure i'm not breaking anyone. if you add the CONFIG_xxx to your board
> config, well that's your fault ;).
Famous last words ;)
I take it you're absolutely sure that the new CONFIG_xxx symbols aren't
already being used anywhere?
> > Your tree touches common code
>
> Blackfin-specific pieces of common code ... there's a difference
Isn't that a contradiction? If it's blackfin-specific, it can't really
be common, can it?
And are you sure that the commands cannot be reworked to be usable on
other architectures as well? That sort of thing might come out of a
review, you know...
> > you're asking for it to be merged
> > without any review at all. I don't think that's a good idea.
>
> i'm asking for the Blackfin pieces to be merged regardless of "merge window".
> i'm making no requests wrt review. Wolfgang wants it reviewed first -- i'm
> fine with that. complaining that Blackfin changes are going in that
> arent "pure fixes" i dont care about (right now).
Ok, I'm not all that concerned about the Blackfin stuff. But I think
that, at a minimum, the stuff under common/ and drivers/ should be
posted for review, and the stuff under driver/net should preferably go
in through the Networking custodian.
Haavard
next prev parent reply other threads:[~2008-02-24 0:35 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 6:17 [U-Boot-Users] Pull request u-boot-blackfin.git Mike Frysinger
2008-02-23 8:42 ` Wolfgang Denk
2008-02-23 8:59 ` Mike Frysinger
2008-02-23 19:36 ` Wolfgang Denk
2008-02-23 20:29 ` Mike Frysinger
2008-02-23 22:25 ` Haavard Skinnemoen
2008-02-23 23:17 ` Mike Frysinger
2008-02-23 23:50 ` Haavard Skinnemoen
2008-02-24 0:07 ` Mike Frysinger
2008-02-24 0:29 ` Wolfgang Denk
2008-02-24 0:39 ` Mike Frysinger
2008-02-24 1:22 ` Wolfgang Denk
2008-02-24 1:37 ` Mike Frysinger
2008-02-24 13:44 ` Wolfgang Denk
2008-02-24 0:35 ` Haavard Skinnemoen [this message]
2008-02-24 1:15 ` Mike Frysinger
2008-02-24 13:55 ` Jean-Christophe PLAGNIOL-VILLARD
2008-02-24 16:48 ` Mike Frysinger
2008-02-23 22:30 ` Wolfgang Denk
2008-02-23 23:19 ` Mike Frysinger
2008-02-23 23:42 ` Wolfgang Denk
2008-02-24 0:09 ` Mike Frysinger
2008-02-24 0:36 ` Wolfgang Denk
2008-02-24 1:18 ` Mike Frysinger
2008-02-24 1:26 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2008-06-01 2:59 Mike Frysinger
2008-06-01 19:45 ` Wolfgang Denk
2008-06-01 20:54 ` Mike Frysinger
2008-06-01 21:54 ` Wolfgang Denk
2008-06-01 22:02 ` Mike Frysinger
2008-06-01 22:15 ` Wolfgang Denk
2008-06-01 22:47 ` Mike Frysinger
2008-06-02 11:58 ` Wolfgang Denk
2008-03-30 19:54 Mike Frysinger
2008-04-07 22:09 ` Wolfgang Denk
2008-03-16 2:33 Mike Frysinger
2008-03-18 21:17 ` Wolfgang Denk
2008-02-24 1:33 Wolfgang Denk
2008-02-05 0:31 Mike Frysinger
2008-02-14 23:12 ` Wolfgang Denk
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=20080224013505.390223de@siona \
--to=hskinnemoen@atmel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.