From: "Petar Jovanovic" <petar.jovanovic@rt-rk.com>
To: "'Maciej W. Rozycki'" <macro@imgtec.com>,
"'David Daney'" <ddaney@caviumnetworks.com>
Cc: "'Petar Jovanovic'" <Petar.Jovanovic@imgtec.com>,
<linux-mips@linux-mips.org>, <ralf@linux-mips.org>,
<david.daney@cavium.com>
Subject: RE: [PATCH] MIPS: Octeon: Expose support for mips32r1, mips32r2 and mips64r1
Date: Fri, 16 Jun 2017 15:26:54 +0200 [thread overview]
Message-ID: <000a01d2e6a4$38a8fe70$a9fafb50$@rt-rk.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1705221846340.2590@tp.orcam.me.uk>
Can this change be applied now?
Thanks.
Regards,
Petar
WARNING: multiple messages have this Message-ID (diff)
From: "Petar Jovanovic" <petar.jovanovic@rt-rk.com>
To: "'Maciej W. Rozycki'" <macro@imgtec.com>,
'David Daney' <ddaney@caviumnetworks.com>
Cc: 'Petar Jovanovic' <Petar.Jovanovic@imgtec.com>,
linux-mips@linux-mips.org, ralf@linux-mips.org,
david.daney@cavium.com
Subject: RE: [PATCH] MIPS: Octeon: Expose support for mips32r1, mips32r2 and mips64r1
Date: Fri, 16 Jun 2017 15:26:54 +0200 [thread overview]
Message-ID: <000a01d2e6a4$38a8fe70$a9fafb50$@rt-rk.com> (raw)
Message-ID: <20170616132654.aMCSbJoHu0-vRSkXW_AkxaGRqqzU4EEsDg3WZ02Z-ug@z> (raw)
In-Reply-To: <alpine.DEB.2.00.1705221846340.2590@tp.orcam.me.uk>
Can this change be applied now?
Thanks.
Regards,
Petar
next prev parent reply other threads:[~2017-06-16 13:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 17:59 [PATCH] MIPS: Octeon: Expose support for mips32r1, mips32r2 and mips64r1 Petar Jovanovic
2017-04-05 16:01 ` Petar Jovanovic
2017-04-05 16:01 ` Petar Jovanovic
2017-04-25 17:24 ` Petar Jovanovic
2017-05-08 15:25 ` Petar Jovanovic
2017-05-08 15:25 ` Petar Jovanovic
2017-05-15 11:33 ` Petar Jovanovic
2017-05-21 1:37 ` Maciej W. Rozycki
2017-05-22 16:25 ` David Daney
2017-05-22 16:43 ` Petar Jovanovic
2017-05-22 16:43 ` Petar Jovanovic
2017-05-22 17:52 ` Maciej W. Rozycki
2017-06-16 13:26 ` Petar Jovanovic [this message]
2017-06-16 13:26 ` Petar Jovanovic
2017-07-06 16:17 ` Petar Jovanovic
2017-07-06 20:47 ` Maciej W. Rozycki
2017-07-07 11:37 ` Petar Jovanovic
2017-07-07 11:37 ` Petar Jovanovic
2017-07-07 15:04 ` Maciej W. Rozycki
2017-07-07 15:04 ` Maciej W. Rozycki
2017-07-07 16:19 ` David Daney
2017-08-07 16:59 ` Petar Jovanovic
2017-09-14 16:41 ` Petar Jovanovic
2017-09-14 16:41 ` Petar Jovanovic
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='000a01d2e6a4$38a8fe70$a9fafb50$@rt-rk.com' \
--to=petar.jovanovic@rt-rk.com \
--cc=Petar.Jovanovic@imgtec.com \
--cc=david.daney@cavium.com \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@imgtec.com \
--cc=ralf@linux-mips.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