From: David Airlie <airlied@redhat.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v2 1/2] video: fbmem: Use 'const char' in fb_get_options()
Date: Tue, 18 Jun 2013 23:00:09 +0000 [thread overview]
Message-ID: <728837318.19851077.1371596409062.JavaMail.root@redhat.com> (raw)
In-Reply-To: <1371568723-27486-1-git-send-email-fabio.estevam@freescale.com>
----- Original Message -----
> From: "Fabio Estevam" <fabio.estevam@freescale.com>
> To: plagnioj@jcrosoft.com
> Cc: linux-fbdev@vger.kernel.org, festevam@gmail.com, geert@linux-m68k.org, "Fabio Estevam"
> <fabio.estevam@freescale.com>, "Ville Syrjälä" <ville.syrjala@linux.intel.com>, "Daniel Vetter"
> <daniel.vetter@ffwll.ch>, "Dave Airlie" <airlied@redhat.com>
> Sent: Wednesday, 19 June, 2013 1:18:42 AM
> Subject: [PATCH v2 1/2] video: fbmem: Use 'const char' in fb_get_options()
>
> Commit d20d31748 (drm: Constify the pretty-print functions) causes the
> following
> build warning:
This patch should already be merged into the fbdev tree, at least the maintainer said it was, hence why I didn't merge it into
my drm-next tree.
Is the fbdev queue not in the drm-next?
Dave.
prev parent reply other threads:[~2013-06-18 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 15:18 [PATCH v2 1/2] video: fbmem: Use 'const char' in fb_get_options() Fabio Estevam
2013-06-18 15:18 ` [PATCH v2 2/2] i915: i915_gem: Print a size_t with %z Fabio Estevam
2013-06-18 23:00 ` David Airlie [this message]
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=728837318.19851077.1371596409062.JavaMail.root@redhat.com \
--to=airlied@redhat.com \
--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).