From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Oleg Verych" <olecom@flower.upol.cz>
Cc: akpm@linux-foundation.org, sam@ravnborg.org,
linux-kernel@vger.kernel.org
Subject: Re: + search-a-little-harder-for-mkimage.patch added to -mm tree
Date: Thu, 8 Feb 2007 15:35:34 -0500 [thread overview]
Message-ID: <8bd0f97a0702081235v2e083301g49c1950fa61d8113@mail.gmail.com> (raw)
In-Reply-To: <20070208202535.GX22699@flower.upol.cz>
On 2/8/07, Oleg Verych <olecom@flower.upol.cz> wrote:
> On Thu, Feb 08, 2007 at 09:28:03AM -0500, Mike Frysinger wrote:
> > On 2/8/07, Oleg Verych <olecom@flower.upol.cz> wrote:
> > >proposition is to substitute:
> > > "$(CONFIG_SHELL) $(MKIMAGE)"
> > >with
> > > "mkimage"
> >
> > this isnt a one-to-one change ... let's look at the typical
> > mkimage-missing scenario ...
>
> You are interested in presents of `mkimage', but yet we discussing its
> missing, or "Error -> Don't care" behavior.
i'm interested in having the system work for the Blackfin port and
that's it. if people want to redefine the current standard of how
u-boot images are generated, then go for it and get the approval of
all the existing arches.
there's a difference between NACKing my changes because the patch
breaks things versus because you think the whole system should be
taking some other form.
so if you dont like the mkuboot.sh script, fine, have at it with
rewriting the system ... otherwise the patch i proposed should
continue on for inclusion.
-mike
next prev parent reply other threads:[~2007-02-08 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200702080607.l1867c0D006861@shell0.pdx.osdl.net>
2007-02-08 14:11 ` Oleg Verych
2007-02-08 14:28 ` Mike Frysinger
2007-02-08 20:25 ` Oleg Verych
2007-02-08 20:35 ` Mike Frysinger [this message]
2007-02-08 21:40 ` - " Oleg Verych
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=8bd0f97a0702081235v2e083301g49c1950fa61d8113@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
--cc=sam@ravnborg.org \
/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
all inboxes | Powered by JetHome®