From: Ralf Baechle <ralf@linux-mips.org>
To: Wu Zhangjin <wuzhangjin@gmail.com>
Cc: Manuel Lauss <manuel.lauss@googlemail.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: zboot: make the vmlinuz be fresh all the time
Date: Thu, 15 Oct 2009 09:40:24 +0200 [thread overview]
Message-ID: <20091015074024.GA12835@linux-mips.org> (raw)
In-Reply-To: <1255586019.11221.5.camel@falcon>
On Thu, Oct 15, 2009 at 01:53:39PM +0800, Wu Zhangjin wrote:
> I have updated my git repository to your master branch, and plan to push
> the basic support of fuloong2f to you and also the linux-mips mailing
> list, is it okay? any suggestion?
Sure, go ahead. It would be appreciated if you would rebase your code
to the queue branch of linux-queue.git for submission; this will
minimize merge conflicts.
Ralf
prev parent reply other threads:[~2009-10-15 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 11:11 [PATCH] MIPS: zboot: make the vmlinuz be fresh all the time Wu Zhangjin
2009-10-14 11:17 ` Manuel Lauss
2009-10-14 11:44 ` Ralf Baechle
2009-10-15 5:53 ` Wu Zhangjin
2009-10-15 7:40 ` Ralf Baechle [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=20091015074024.GA12835@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@googlemail.com \
--cc=wuzhangjin@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).