From: Michael Neuling <mikey@neuling.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Please pull mpc52xx-next
Date: Tue, 10 Mar 2009 11:16:02 +1100 [thread overview]
Message-ID: <7605.1236644162@neuling.org> (raw)
In-Reply-To: <fa686aa40903091714h529a8546s982156fac349c426@mail.gmail.com>
> > Grant,
> >
> > Can you grab this guy too?
> >
> > http://patchwork.ozlabs.org/patch/24082/
>
> Oops, forgot to email you about this one. I actually wrote another
> patch the eliminates the sysfs attributes entirely which also
> eliminates the problem. It will be in my next pull request to Ben
> (any day now; just waiting for an ack on another patch).
OK, sounds good.
Mikey
next prev parent reply other threads:[~2009-03-10 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 18:08 Please pull mpc52xx-next Grant Likely
2009-03-09 23:46 ` Michael Neuling
2009-03-10 0:14 ` Grant Likely
2009-03-10 0:16 ` Michael Neuling [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-11 16:12 Grant Likely
2008-07-26 4:00 Grant Likely
2008-07-27 21:48 ` Grant Likely
2008-07-28 4:24 ` Grant Likely
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=7605.1236644162@neuling.org \
--to=mikey@neuling.org \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.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).