mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: dave b <db.pub.mail@gmail.com>
Cc: Jamie Lokier <jamie@shareable.org>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Mikael Pettersson <mikpe@it.uu.se>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: weirdness with compiling a 2.6.33 kernel on arm debian
Date: Thu, 1 Apr 2010 08:08:44 +0200	[thread overview]
Message-ID: <20100401060844.GB1329@ucw.cz> (raw)
In-Reply-To: <25ae2d691003260312h62b7f853s99a2fa483a6a0847@mail.gmail.com>

On Fri 2010-03-26 21:12:34, dave b wrote:
> I believe that the 2.6.32.7 kernel I compiled and was using on the
> device while compiling the 2.6.33 kernel had *issues* (although most
> likely not kernel related). In particular various issues (apt-get not
> working) including on one piece of hardware using the kernel binary as
> produced by others.

Interesting. I remember apt-get failing recently; I thought my
databases went corrupt, but then it started to work magically...

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2010-04-01  6:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-06  3:58 dave b
2010-03-06  9:03 ` Mikael Pettersson
2010-03-06 10:24   ` dave b
2010-03-06 10:41     ` Daniel Mack
2010-03-07  1:05       ` dave b
2010-03-07 11:01         ` Martin Guy
2010-03-08  9:53         ` Uwe Kleine-König
2010-03-08 10:31           ` Daniel Mack
2010-03-11 13:10             ` dave b
2010-03-11 13:33     ` Russell King - ARM Linux
2010-03-15  1:02       ` Jamie Lokier
2010-03-26 10:12         ` dave b
2010-04-01  6:08           ` Pavel Machek [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=20100401060844.GB1329@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=db.pub.mail@gmail.com \
    --cc=jamie@shareable.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mikpe@it.uu.se \
    /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

Powered by JetHome