All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@mvista.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Errata 67/77 / walnut bugs (was: Re: Erratum 51 bugfix?)
Date: Fri, 21 Sep 2001 04:04:27 -0400	[thread overview]
Message-ID: <3BAAF48B.2C734E71@mvista.com> (raw)
In-Reply-To: 20010921153359.G20058@zax


David Gibson wrote:

> ... but it's certainly improved from what it was before.

I pushed the patch.  It would be nice if you could send patches
against the latest version of the tree, like do a pull and test
it just before you post it.  There were parts of the patch that
wouldn't apply and I had to do it manually.  Check it to ensure
I got everything OK.

Thanks.


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-09-21  8:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-17  5:23 Erratum 51 bugfix? David Gibson
2001-09-17 16:32 ` Dan Malek
2001-09-18  0:29   ` Errata 67/77 / walnut bugs (was: Re: Erratum 51 bugfix?) David Gibson
2001-09-18 18:52     ` Dan Malek
2001-09-19  2:19       ` David Gibson
2001-09-19  2:23         ` Mark Hatle
2001-09-19  6:41           ` Dan Malek
2001-09-19 10:45           ` Ralph Blach
2001-09-19  6:39         ` Dan Malek
2001-09-21  4:36           ` David Gibson
2001-09-21  5:23             ` Dan Malek
2001-09-21  5:33               ` David Gibson
2001-09-21  6:24                 ` Dan Malek
2001-09-21  8:04                 ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-20  6:23 dank
2002-07-20 15:14 ` Mark Hatle
2002-07-20 15:38   ` dank
2002-07-20 16:02     ` Mark Hatle
2002-07-20 17:57       ` dank
2002-07-23 12:39   ` dank
2002-07-23 13:10     ` Mark Hatle

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=3BAAF48B.2C734E71@mvista.com \
    --to=dan@mvista.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-embedded@lists.linuxppc.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.