mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Chris Holvenstot" <cholvenstot@comcast.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.6.23-rc2 git4 & git5
Date: Mon, 13 Aug 2007 18:28:09 +0200	[thread overview]
Message-ID: <6bffcb0e0708130928k726bd676p79c18549dc814d05@mail.gmail.com> (raw)
In-Reply-To: <1186954962.8166.19.camel@localhost>

Hi Chris,

On 12/08/07, Chris Holvenstot <cholvenstot@comcast.net> wrote:
> This morning I reported an issue which cause a failure of the
> 2.6.23-rc2-git4 kernel to boot on my system.  The contents of my post
> may be viewed here:
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0708.1/1959.html
>
> After 3 separate builds from "virgin sources" I still had the boot
> failure with the git4 level kernel.
>
> This afternoon I picked up the git5 patch and it comes up and appears to
> run without problem.

Great!

Next time, please reply to original report. It is much easier to track bugs.

>
> Same base system.  Same hardware.  Same build process.
>
> So even though I have only been building and running "pre-release"
> kernels for a short time I feel confident in saying that something was
> not kosher with the git4 patch - at least when it came to my system.
>
> (system configuration data is in the original post)
>
> I would not normally burn the valuable time of others with a rhetorical
> post but I looked at the changes out into the git5 patch and did not
> spot anything that looked like it would have resolved the issue I was
> having and I hate not being  able to correlate a cause and effect here.
>
> Any clues, or did I just get lucky with this one?
>

I guess the problem is fixed.

Regards,
Michal

-- 
LOG
http://www.stardust.webpages.pl/log/

      reply	other threads:[~2007-08-13 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-12 21:42 Chris Holvenstot
2007-08-13 16:28 ` Michal Piotrowski [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=6bffcb0e0708130928k726bd676p79c18549dc814d05@mail.gmail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --cc=cholvenstot@comcast.net \
    --cc=linux-kernel@vger.kernel.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®