From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: Markos Chandras <Markos.Chandras@imgtec.com>,
<linux-mips@linux-mips.org>, <paul.burton@imgtec.com>,
<richard@nod.at>, <linux-kernel@vger.kernel.org>,
<ralf@linux-mips.org>, <luto@amacapital.net>,
<alex.smith@imgtec.com>, <macro@codesourcery.com>,
<mpe@ellerman.id.au>
Subject: Re: [PATCH v3] MIPS64: signal: n64 kernel bugfix of MIPS32 o32 ABI sigaction syscall
Date: Tue, 20 Oct 2015 11:12:33 -0700 [thread overview]
Message-ID: <56268411.1080307@imgtec.com> (raw)
In-Reply-To: <5625FCDE.9010608@imgtec.com>
On 10/20/2015 01:35 AM, Markos Chandras wrote:
> What tree did you use for this patch? It does not seem to apply to
> mainline or Ralf's upstream-sfr.
May I ask you to elaborate more and send me a concern details?
I definitely rebased it to mips-for-linux-next of upstream-sfr from LMO.
- Leonid
WARNING: multiple messages have this Message-ID (diff)
From: Leonid Yegoshin <Leonid.Yegoshin@imgtec.com>
To: Markos Chandras <Markos.Chandras@imgtec.com>,
linux-mips@linux-mips.org, paul.burton@imgtec.com,
richard@nod.at, linux-kernel@vger.kernel.org,
ralf@linux-mips.org, luto@amacapital.net, alex.smith@imgtec.com,
macro@codesourcery.com, mpe@ellerman.id.au
Subject: Re: [PATCH v3] MIPS64: signal: n64 kernel bugfix of MIPS32 o32 ABI sigaction syscall
Date: Tue, 20 Oct 2015 11:12:33 -0700 [thread overview]
Message-ID: <56268411.1080307@imgtec.com> (raw)
Message-ID: <20151020181233.mrMkYXYIPbi9ErExawxRWGRe3Ptao0mVHDId4t2NQEI@z> (raw)
In-Reply-To: <5625FCDE.9010608@imgtec.com>
On 10/20/2015 01:35 AM, Markos Chandras wrote:
> What tree did you use for this patch? It does not seem to apply to
> mainline or Ralf's upstream-sfr.
May I ask you to elaborate more and send me a concern details?
I definitely rebased it to mips-for-linux-next of upstream-sfr from LMO.
- Leonid
next prev parent reply other threads:[~2015-10-20 18:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 18:39 [PATCH v3] MIPS64: signal: n64 kernel bugfix of MIPS32 o32 ABI sigaction syscall Leonid Yegoshin
2015-10-19 18:39 ` Leonid Yegoshin
2015-10-20 8:35 ` Markos Chandras
2015-10-20 8:35 ` Markos Chandras
2015-10-20 18:12 ` Leonid Yegoshin [this message]
2015-10-20 18:12 ` Leonid Yegoshin
2015-10-21 8:04 ` Markos Chandras
2015-10-21 8:04 ` Markos Chandras
-- strict thread matches above, loose matches on Subject: below --
2015-10-20 16:40 Leonid Yegoshin
2015-10-20 16:40 ` Leonid Yegoshin
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=56268411.1080307@imgtec.com \
--to=leonid.yegoshin@imgtec.com \
--cc=Markos.Chandras@imgtec.com \
--cc=alex.smith@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=luto@amacapital.net \
--cc=macro@codesourcery.com \
--cc=mpe@ellerman.id.au \
--cc=paul.burton@imgtec.com \
--cc=ralf@linux-mips.org \
--cc=richard@nod.at \
/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.