From: Robert Millan <rmh@aybabtu.com>
To: David Miller <davem@davemloft.net>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH 0/10]: Respin of sparc patches.
Date: Sat, 7 Mar 2009 11:37:36 +0100 [thread overview]
Message-ID: <20090307103736.GC20540@thorin> (raw)
In-Reply-To: <20090306.163847.69930483.davem@davemloft.net>
On Fri, Mar 06, 2009 at 04:38:47PM -0800, David Miller wrote:
> From: Robert Millan <rmh@aybabtu.com>
> Date: Fri, 6 Mar 2009 20:01:10 +0100
>
> > In the future, please send followup patches in the same thread. It helps
> > keeping track of things, which is quite hard for us to keep up with already..
>
> Sure no problem.
>
> What's going to happen with these patches?
Well, we need time both for the paperwork and for reviewing them. I'm not
sure how many of us are experienced with sparc (Vincent? Who else?). I at
least can comment on Ieee1275 stuff, so does Pavel, Marco, Manoel and probably
others.
We'll get there. Just be patient :-)
> I am able to boot into the GRUB kernel prompt on my test system,
> I have a lot of new code written, I'm _EXTREMELY_ motivated
> and want to get this all working fully in the next week or so.
I'm very interested to see proper sparc support completed/merged. Your effort
is much appreciated.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-03-07 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 1:32 [PATCH 0/10]: Respin of sparc patches David Miller
2009-03-06 19:01 ` Robert Millan
2009-03-07 0:38 ` David Miller
2009-03-07 10:37 ` Robert Millan [this message]
2009-03-07 14:26 ` David Miller
2009-03-09 3:12 ` David Miller
2009-03-07 19:16 ` Vincent Pelletier
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=20090307103736.GC20540@thorin \
--to=rmh@aybabtu.com \
--cc=davem@davemloft.net \
--cc=grub-devel@gnu.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 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.