From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney.cavm@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-mips@linux-mips.org, linux-next@vger.kernel.org
Subject: Re: [PATCH -next] MIPS: ptrace: Add missing #include <asm/syscall.h>
Date: Wed, 26 Sep 2012 23:09:43 +0200 [thread overview]
Message-ID: <20120926210943.GA4745@linux-mips.org> (raw)
In-Reply-To: <5060A52C.1050504@gmail.com>
On Mon, Sep 24, 2012 at 11:23:40AM -0700, David Daney wrote:
> >Thanks, I already had fixed that in the linux-trace tree; the latest
> >version just had not yet propagated yet to the other trees.
> >
>
> It is still not on mips-for-linux-next. Perhaps we should arrange
> for it to be there, so that the actual propagation may commence.
Seems my fix one branch, push the other strategy didn't work so well ;-)
Fixed, sorry.
Ralf
prev parent reply other threads:[~2012-09-26 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 20:20 [PATCH -next] MIPS: ptrace: Add missing #include <asm/syscall.h> Geert Uytterhoeven
2012-09-23 17:36 ` Ralf Baechle
2012-09-24 18:23 ` David Daney
2012-09-26 21:09 ` 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=20120926210943.GA4745@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney.cavm@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-next@vger.kernel.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).