From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Aleksandar Markovic <aleksandar.markovic@rt-rk.com>
Cc: linux-mips@linux-mips.org,
Aleksandar Markovic <aleksandar.markovic@imgtec.com>,
Douglas Leung <douglas.leung@imgtec.com>,
Goran Ferenc <goran.ferenc@imgtec.com>,
James Hogan <james.hogan@imgtec.com>,
Jiri Slaby <jslaby@suse.com>,
linux-kernel@vger.kernel.org,
Miodrag Dinic <miodrag.dinic@imgtec.com>,
Paul Burton <paul.burton@imgtec.com>,
Petar Jovanovic <petar.jovanovic@imgtec.com>,
Raghu Gandham <raghu.gandham@imgtec.com>
Subject: Re: [PATCH v2 0/7] MIPS: Miscellaneous fixes related to Android Mips emulator
Date: Wed, 28 Jun 2017 18:30:11 +0200 [thread overview]
Message-ID: <20170628163011.GA17042@kroah.com> (raw)
In-Reply-To: <1498665399-29007-1-git-send-email-aleksandar.markovic@rt-rk.com>
On Wed, Jun 28, 2017 at 05:56:24PM +0200, Aleksandar Markovic wrote:
> From: Aleksandar Markovic <aleksandar.markovic@imgtec.com>
>
> v1->v2:
>
> - the patch on PREF usage in memcpy dropped as not needed
> - updated recipient lists using get_maintainer.pl
> - rebased to the latest kernel code
>
> This series contains an assortment of changes necessary for proper
> operation of Android emulator for Mips. However, we think that wider
> kernel community may benefit from them too.
This is nice, thanks for these.
How well does these patches "work" with the recent goldfish
images/kernels that are out there? I know the goldfish platform has
been revamped a lot recently, and I would not like to see these changes
cause things to break there :)
Also, any chance to get some google reviewers for these changes? I
don't think you added any to the cc: list, how come?
thanks,
greg k-h
next prev parent reply other threads:[~2017-06-28 16:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 15:56 [PATCH v2 0/7] MIPS: Miscellaneous fixes related to Android Mips emulator Aleksandar Markovic
2017-06-28 15:56 ` [PATCH v2 1/7] MIPS: cmdline: Add support for 'memmap' parameter Aleksandar Markovic
2017-06-28 15:56 ` [PATCH v2 2/7] MIPS: build: Fix "-modd-spreg" switch usage when compiling for mips32r6 Aleksandar Markovic
2017-06-28 15:56 ` [PATCH v2 3/7] MIPS: unaligned: Add DSP lwx & lhx missaligned access support Aleksandar Markovic
2017-06-28 15:56 ` [PATCH v2 4/7] MIPS: math-emu: Handle zero accumulator case in MADDF and MSUBF separately Aleksandar Markovic
2017-06-28 15:56 ` [PATCH v2 5/7] input: goldfish: Fix multitouch event handling Aleksandar Markovic
2017-06-29 18:58 ` Dmitry Torokhov
2017-07-21 10:51 ` Aleksandar Markovic
2017-06-28 15:56 ` [PATCH v2 6/7] tty: goldfish: Use streaming DMA for r/w operations on Ranchu platforms Aleksandar Markovic
2017-06-28 15:56 ` [PATCH v2 7/7] tty: goldfish: Implement support for kernel 'earlycon' parameter Aleksandar Markovic
2017-06-28 16:30 ` Greg Kroah-Hartman [this message]
2017-07-06 13:06 ` [PATCH v2 0/7] MIPS: Miscellaneous fixes related to Android Mips emulator Miodrag Dinic
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=20170628163011.GA17042@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=aleksandar.markovic@imgtec.com \
--cc=aleksandar.markovic@rt-rk.com \
--cc=douglas.leung@imgtec.com \
--cc=goran.ferenc@imgtec.com \
--cc=james.hogan@imgtec.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=miodrag.dinic@imgtec.com \
--cc=paul.burton@imgtec.com \
--cc=petar.jovanovic@imgtec.com \
--cc=raghu.gandham@imgtec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox