From: Ralf Baechle <ralf@linux-mips.org>
To: Shane McDonald <mcdonald.shane@gmail.com>
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
Adam Kiepul <Adam_Kiepul@pmc-sierra.com>,
"Anoop P.A." <Anoop_P.A@pmc-sierra.com>
Subject: Re: Pending PMC-Sierra MSP patches
Date: Tue, 9 Jul 2013 18:29:35 +0200 [thread overview]
Message-ID: <20130709162935.GD24481@linux-mips.org> (raw)
In-Reply-To: <CACoURw6Z7_SdXUfnqqmxur9mQHoVmD8bD1ut7eGAtGafBCujUA@mail.gmail.com>
On Tue, Jul 09, 2013 at 09:57:21AM -0600, Shane McDonald wrote:
> On Thursday, June 27, 2013, Ralf Baechle wrote:
>
> > Resendig with a few people who might be interested (or know somebody
> > who might be) added to cc.
> >
> > On Thu, Jun 27, 2013 at 04:34:39PM +0200, Ralf Baechle wrote:
> > > There is still a fair number of patches for the PMC-Sierra MSP series
> > > of platforms pending. Those patches being over two years old are
> > > fairly stale by now so I wonder if somebody with interest in the
> > > platform could review, respin and test the patches?
> > >
> > > The patches in question are can be found in patchwork at
> > >
> > >
> > http://patchwork.linux-mips.org/project/linux-mips/list/?submitter=413&archive=true
> >
> > Ralf
> >
>
> I've forwarded this email on to internal contacts at PMC-Sierra, but it
> appears there is little PMC activity on this platform. Feel free to drop
> the patches; if I find a need for them, I can respin and resubmit.
Ok, I'm going to drop the patches then. The patches will remain accessible
under
http://patchwork.linux-mips.org/user/bundle/130/?state=*&archive=both
Ralf
prev parent reply other threads:[~2013-07-09 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 14:34 Pending PMC-Sierra MSP patches Ralf Baechle
2013-06-27 14:47 ` Ralf Baechle
2013-07-09 15:57 ` Shane McDonald
2013-07-09 16:29 ` Ralf Baechle [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=20130709162935.GD24481@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Adam_Kiepul@pmc-sierra.com \
--cc=Anoop_P.A@pmc-sierra.com \
--cc=linux-mips@linux-mips.org \
--cc=mcdonald.shane@gmail.com \
/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.