From: Andrew Morton <akpm@linux-foundation.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH RESEND v2 2/2] drivers/video: fsl-diu-fb: fix bugs in interrupt handling
Date: Wed, 13 Feb 2013 19:55:24 +0000 [thread overview]
Message-ID: <20130213115524.15f7ec2d.akpm@linux-foundation.org> (raw)
In-Reply-To: <1360308959-3096-2-git-send-email-agust@denx.de>
On Wed, 13 Feb 2013 10:21:52 +0100
Anatolij Gustschin <agust@denx.de> wrote:
> On Tue, 12 Feb 2013 17:01:55 -0800
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > On Tue, 12 Feb 2013 16:54:58 -0800
> > Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > > Thanks, I queued both these with a plan to merge into 3.9-rc1.
> >
> > No I didn't. The patches have already found their way into linux-next
> > via some other tree.
>
> Yes, via MPC5XXX tree. Since I didn't receive response from fbdev
> maintainer I applied both patches in my powerpc MPC5XXX next branch
> so that these can be exposed in linux-next at least. MPC5121 uses the
> fsl-diu-fb driver, so these patches could go via MPC5XXX tree, but I
> can't push them via my tree without an ACK from fbdev maintainer.
The patches look OK to me - I suggest you go ahead and merge them up
for 3.9-rc1.
> > Without any -stable tags, either. You don't think we should fix the
> > "24 and 16 bpp" thing in 3.8.x and earlier?
>
> I didn't add any -stable tags since my hope was that the patches
> will go into v3.8 via fbdev tree. It would be good to fix the bpp
> issue in 3.8.x. But the issue is not critical for earlier maintained
> stable versions I think.
Please remember to add the cc:stable to the changelogs if you want
these in 3.8.x and earlier.
next prev parent reply other threads:[~2013-02-13 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 7:35 [PATCH RESEND v2 2/2] drivers/video: fsl-diu-fb: fix bugs in interrupt handling Anatolij Gustschin
2013-02-13 0:54 ` Andrew Morton
2013-02-13 1:01 ` Andrew Morton
2013-02-13 9:21 ` Anatolij Gustschin
2013-02-13 19:55 ` Andrew Morton [this message]
2013-02-13 20:13 ` Anatolij Gustschin
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=20130213115524.15f7ec2d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fbdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).