public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Sieka <tur@semihalf.com>
To: Paul Mackerras <paulus@samba.org>
Cc: torvalds@linux-foundation.org, linuxppc-dev@ozlabs.org,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: Please pull powerpc.git merge branch
Date: Fri, 28 Mar 2008 23:06:29 +0100	[thread overview]
Message-ID: <47ED6BE5.9060807@semihalf.com> (raw)
In-Reply-To: <18412.58902.189124.391104@cargo.ozlabs.ibm.com>

Paul Mackerras wrote:
> Linus,
> 
> I have added another commit to the powerpc.git merge branch, so when
> you do:
> 
> git pull \
> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git merge
> 
> you'll get a fix for a bug where the hardware data breakpoint would
> sometimes fail to trigger on powerpc, if multiple threads put a
> breakpoint on the same address.  The bug has been around for a while
> and Michael Ellerman just found the cause and posted a fix.

Hello Paul,

What about http://patchwork.ozlabs.org/linuxppc/patch?id=17525 ? I don't
see it in the merge branch of your repository, and it would be nice to
get it upstream as it fixes boot problems on some MPC5200-based boards.

Regards,
Bartlomiej

  reply	other threads:[~2008-03-28 22:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 12:35 Please pull powerpc.git merge branch Paul Mackerras
2008-03-28 22:06 ` Bartlomiej Sieka [this message]
2008-04-01 23:12   ` Paul Mackerras
2008-04-02  4:27     ` Grant Likely
  -- strict thread matches above, loose matches on Subject: below --
2008-04-03 11:33 Paul Mackerras
2008-03-27 23:08 Paul Mackerras
2008-03-25  3:32 Paul Mackerras
2008-03-24  8:05 Paul Mackerras
2008-03-20  0:43 Paul Mackerras
2008-03-12 23:51 Paul Mackerras
2008-03-03 11:41 Paul Mackerras
2008-03-03 15:44 ` Grant Likely
2008-02-20  3:46 Paul Mackerras
2008-02-21 12:15 ` Paul Mackerras
2008-02-14 22:00 Paul Mackerras

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=47ED6BE5.9060807@semihalf.com \
    --to=tur@semihalf.com \
    --cc=akpm@linux-foundation.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=torvalds@linux-foundation.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