From: Kumar Gala <galak@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Please pull from 'powerpc-next' branch
Date: Thu, 1 May 2008 01:02:38 -0500 [thread overview]
Message-ID: <D44986B7-16A0-4AC2-B73F-3B4B05CF6ED2@kernel.crashing.org> (raw)
In-Reply-To: <18457.22551.705318.772517@cargo.ozlabs.ibm.com>
On May 1, 2008, at 12:41 AM, Paul Mackerras wrote:
> Kumar Gala writes:
>
>> Please pull from 'powerpc-next' branch of
>>
>> master.kernel.org:/pub/scm/linux/kernel/git/galak/powerpc.git
>> powerpc-next
>>
>> to receive the following updates:
>
> I assume you want me to send these on to Linus before the merge window
> closes. But this one:
yes.
>> Kumar Gala (1):
>> [POWERPC] Set lower flag bits in regs->trap to indicate debug
>> level exception
>
> needs a bit more motivation, since it is very new, and the commit
> message doesn't say why we want to do what the commit does. What good
> thing will happen, or what bad thing will be averted, by having this
> commit in 2.6.26?
There's no harm either way with this one. It can wait for post
2.6.26, but its pretty trivial.
- k
next prev parent reply other threads:[~2008-05-01 6:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 5:04 Please pull from 'powerpc-next' branch Kumar Gala
2008-05-01 5:41 ` Paul Mackerras
2008-05-01 6:02 ` Kumar Gala [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-13 16:50 Kumar Gala
2008-10-01 21:07 Kumar Gala
2008-07-09 13:13 Kumar Gala
2008-07-09 17:13 ` Stephen Rothwell
2008-07-10 13:24 ` Kumar Gala
2008-06-26 7:49 Kumar Gala
2008-06-26 8:14 ` Kumar Gala
2008-06-27 11:27 ` Paul Mackerras
2008-06-27 13:00 ` Kumar Gala
2008-06-30 3:52 ` Michael Ellerman
2008-06-26 8:36 ` Kumar Gala
2008-06-05 3:32 Kumar Gala
2008-06-10 14:02 ` Anton Vorontsov
2008-06-10 16:16 ` Kumar Gala
2008-05-02 4:13 Kumar Gala
2008-04-23 22:50 Kumar Gala
2008-04-23 22:56 ` Kumar Gala
2008-04-17 6:41 Kumar Gala
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=D44986B7-16A0-4AC2-B73F-3B4B05CF6ED2@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).