From: James Hogan <jhogan@kernel.org>
To: Mathieu Malaterre <malat@debian.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Marcin Nowakowski <marcin.nowakowski@mips.com>,
linux-mips@linux-mips.org, "# v4 . 11" <stable@vger.kernel.org>
Subject: Re: [PATCH v3] MIPS: fix incorrect mem=X@Y handling
Date: Tue, 13 Feb 2018 14:32:40 +0000 [thread overview]
Message-ID: <20180213143239.GE4290@saruman> (raw)
In-Reply-To: <CA+7wUswyQjRvY1=4g785jNBnfAAqSUbyYSWh3qKHieJVhmbxSg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On Tue, Feb 13, 2018 at 03:03:24PM +0100, Mathieu Malaterre wrote:
> James,
>
> On Tue, Feb 13, 2018 at 2:38 PM, James Hogan <jhogan@kernel.org> wrote:
> > On Tue, Feb 13, 2018 at 01:14:29PM +0100, Mathieu Malaterre wrote:
> >> Could you please review the patch v3 ?
> >
> > Yes, looks good to me, and Ralf had applied to his test branch so I
> > presume he's happy with it too. I'll apply for 4.16.
>
> Hum, just to be sure I understand the process. Which branch are you
> talking about:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/ralf/linux.git
I was referring to upstream-sfr.git branch=mips-next-test
https://git.linux-mips.org/cgit/ralf/upstream-sfr.git/log/?h=mips-next-test
(The mips-next branch there is what Ralf puts into linux-next)
I've applied the patch to my mips-fixes branch here:
git://git.kernel.org/pub/scm/linux/kernel/git/jhogan/mips.git
Sorry it seems a bit haphazard with multiple trees in use.
Cheers
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-02-13 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 11:37 [PATCH v3] MIPS: fix incorrect mem=X@Y handling Marcin Nowakowski
2018-02-01 11:37 ` Marcin Nowakowski
2018-02-01 12:12 ` Mathieu Malaterre
2018-02-13 12:14 ` Mathieu Malaterre
2018-02-13 13:38 ` James Hogan
2018-02-13 14:03 ` Mathieu Malaterre
2018-02-13 14:32 ` James Hogan [this message]
2018-02-13 14:53 ` Mathieu Malaterre
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=20180213143239.GE4290@saruman \
--to=jhogan@kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=malat@debian.org \
--cc=marcin.nowakowski@mips.com \
--cc=ralf@linux-mips.org \
--cc=stable@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 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.