From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Two imx-drm oops fixes
Date: Tue, 9 Sep 2014 23:13:41 +0800 [thread overview]
Message-ID: <20140909151339.GA2341@dragon> (raw)
In-Reply-To: <20140908190949.GB16374@kroah.com>
On Mon, Sep 08, 2014 at 12:09:49PM -0700, Greg Kroah-Hartman wrote:
> On Mon, Sep 08, 2014 at 12:08:59PM -0700, Greg Kroah-Hartman wrote:
> > On Mon, Sep 01, 2014 at 06:07:12PM +0100, Russell King - ARM Linux wrote:
> > > Greg,
> > >
> > > Here's two oops fixes for imx-drm, which I've had queued up for a number
> > > of months now. Shawn posted different fixes for the same oops recently
> > > as well.
> >
> > So do I take your patches, or Shawn's?
>
> Actually, yours are "smaller", so I'll defer to you and take yours...
Greg,
My patch is bigger than Russell's because I cleaned up the code a little
bit along the way of fixing the bug.
I will send you the cleanup as an incremental patch based on Russell's
fixes.
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawn.guo@freescale.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] Two imx-drm oops fixes
Date: Tue, 9 Sep 2014 23:13:41 +0800 [thread overview]
Message-ID: <20140909151339.GA2341@dragon> (raw)
In-Reply-To: <20140908190949.GB16374@kroah.com>
On Mon, Sep 08, 2014 at 12:09:49PM -0700, Greg Kroah-Hartman wrote:
> On Mon, Sep 08, 2014 at 12:08:59PM -0700, Greg Kroah-Hartman wrote:
> > On Mon, Sep 01, 2014 at 06:07:12PM +0100, Russell King - ARM Linux wrote:
> > > Greg,
> > >
> > > Here's two oops fixes for imx-drm, which I've had queued up for a number
> > > of months now. Shawn posted different fixes for the same oops recently
> > > as well.
> >
> > So do I take your patches, or Shawn's?
>
> Actually, yours are "smaller", so I'll defer to you and take yours...
Greg,
My patch is bigger than Russell's because I cleaned up the code a little
bit along the way of fixing the bug.
I will send you the cleanup as an incremental patch based on Russell's
fixes.
Shawn
next prev parent reply other threads:[~2014-09-09 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 17:07 [PATCH 0/2] Two imx-drm oops fixes Russell King - ARM Linux
2014-09-01 17:07 ` Russell King - ARM Linux
2014-09-01 17:07 ` [PATCH 1/2] imx-drm: ipuv3-plane: fix ipu_plane_dpms() Russell King
2014-09-01 17:07 ` Russell King
2014-09-01 17:07 ` [PATCH 2/2] imx-drm: imx-ldb: fix NULL pointer in imx_ldb_unbind() Russell King
2014-09-01 17:07 ` Russell King
2014-09-08 19:08 ` [PATCH 0/2] Two imx-drm oops fixes Greg Kroah-Hartman
2014-09-08 19:08 ` Greg Kroah-Hartman
2014-09-08 19:09 ` Greg Kroah-Hartman
2014-09-08 19:09 ` Greg Kroah-Hartman
2014-09-09 15:13 ` Shawn Guo [this message]
2014-09-09 15:13 ` Shawn Guo
2014-09-09 15:38 ` Greg Kroah-Hartman
2014-09-09 15:38 ` Greg Kroah-Hartman
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=20140909151339.GA2341@dragon \
--to=shawn.guo@freescale.com \
--cc=linux-arm-kernel@lists.infradead.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.