All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH]: Fix sparc64 build...
Date: Thu, 03 Dec 2009 22:56:34 +0100	[thread overview]
Message-ID: <4B183412.60109@gmail.com> (raw)
In-Reply-To: <20091203.125900.90813059.davem@davemloft.net>

[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]

David Miller wrote:
> From: Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>
> Date: Thu, 03 Dec 2009 21:22:27 +0100
>
>   
>> For me the main reason for or against it is break probability. Merging
>> will avoid stupid breakages like ones you fixed but may introduce more
>> subtle ones
>>     
>
> You lack a cross-build environment?
>   
I have only cross-build environment for ppc and mipsel. I installed
sparc cross-toolchain from emdebian but apparently it's not enough to
build grub-sparc. I was actually thinking that grub2-sparc was uploaded 
to debian and so at least compile-tested.
> I test build the Linux kernel for about 4 or 5 platforms, all on the
> same computer.
>
> And also as we've seen, keeping the build working doesn't keep bugs
> from creeping in.  Someone just needs to actively build and install
> test the tree on the given platform if you really want to avoid
> problems.
>
> I have about half a year of potential regressions I'm about to
> discover on sparc64.  That's not an acceptable situation, long term.
>
> I might get hit by a bus or whatever, so it would be nice if someone
> other than me were at least testing the code base out on sparc64.
>
> That way problems get spotted when they get added, or soon afterwards,
> not 6 months later like some things are about to. :-)
>
>   
The problem is that nobody of us has such hardware. I would happily do a
sparc boot every 2 weeks but I just don't have a sparc


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]

  reply	other threads:[~2009-12-03 21:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 10:17 [PATCH]: Fix sparc64 build David Miller
2009-12-03 11:26 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-03 19:02   ` David Miller
2009-12-03 20:22     ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-03 20:59       ` David Miller
2009-12-03 21:56         ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2009-12-03 22:04           ` David Miller
2009-12-04 20:54         ` Robert Millan
2009-12-03 21:03       ` David Miller
2009-12-04 20:58         ` Robert Millan
2009-12-04 21:34           ` David Miller
2009-12-06  9:12             ` Felix Zielcke
2009-12-04 20:52       ` Robert Millan
2009-12-04 20:50 ` Robert Millan
  -- strict thread matches above, loose matches on Subject: below --
2009-05-04 22:55 David Miller
2009-03-26 23:44 David Miller
2009-03-27  0:16 ` Ingo Molnar

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=4B183412.60109@gmail.com \
    --to=phcoder@gmail.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.