public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH -v2] fbdev: sh_mobile_meram: Fix defined but not used compiler warnings
Date: Tue, 26 Nov 2013 15:58:20 +0100	[thread overview]
Message-ID: <1510041.WqZSiK0jXs@avalon> (raw)
In-Reply-To: <5294B3B9.3090104@ti.com>

Hi Tomi,

On Tuesday 26 November 2013 16:44:09 Tomi Valkeinen wrote:
> On 2013-11-06 13:57, Laurent Pinchart wrote:
> > On Wednesday 06 November 2013 09:57:27 Geert Uytterhoeven wrote:
> >> If both CONFIG_PM_SLEEP and CONFIG_PM_RUNTIME are not set:
> >> 
> >> drivers/video/sh_mobile_meram.c:573: warning: ?sh_mobile_meram_suspend?
> >> defined but not used drivers/video/sh_mobile_meram.c:597: warning:
> >> ?sh_mobile_meram_resume? defined but not used
> >> 
> >> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> > 
> > Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > 
> > and applied to my tree.
> 
> What does that mean? Are you collecting sh_mobile video patches?
> 
> Or to rephrase, shall I apply this to fbdev fixes tree?

I was planning to send you a pull request for that, but if you can pick it up 
that's even easier, thanks.

-- 
Regards,

Laurent Pinchart
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131126/9a4a3971/attachment.sig>

  reply	other threads:[~2013-11-26 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06  8:57 [PATCH -v2] fbdev: sh_mobile_meram: Fix defined but not used compiler warnings Geert Uytterhoeven
2013-11-06 11:57 ` Laurent Pinchart
2013-11-26 14:44   ` Tomi Valkeinen
2013-11-26 14:58     ` Laurent Pinchart [this message]
2013-11-26 15:00       ` Tomi Valkeinen

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=1510041.WqZSiK0jXs@avalon \
    --to=laurent.pinchart@ideasonboard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox