All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org
Subject: Re: [GIT PULL for 4.16] CIO2 compiler warning fix
Date: Tue, 23 Jan 2018 10:40:13 -0200	[thread overview]
Message-ID: <20180123104008.25ebdef5@vela.lan> (raw)
In-Reply-To: <20180109223517.lkj4opdpm64jpf5d@valkosipuli.retiisi.org.uk>

Em Wed, 10 Jan 2018 00:35:18 +0200
Sakari Ailus <sakari.ailus@iki.fi> escreveu:

> Hi Mauro,
> 
> Here's compile warning fix for the Intel IPU3 CIO2 driver from Arnd.
> 
> Please pull.
> 
> 
> The following changes since commit e3ee691dbf24096ea51b3200946b11d68ce75361:
> 
>   media: ov5640: add support of RGB565 and YUYV formats (2018-01-05 12:54:14 -0500)
> 
> are available in the git repository at:
> 
>   ssh://linuxtv.org/git/sailus/media_tree.git ipu3
> 
> for you to fetch changes up to 0bf3352560b82c12380823f035f5fb2171683f23:
> 
>   media: intel-ipu3: cio2: mark more PM functions as __maybe_unused (2018-01-09 13:16:07 +0200)
> 
> ----------------------------------------------------------------
> Arnd Bergmann (1):
>       media: intel-ipu3: cio2: mark more PM functions as __maybe_unused
> 
>  drivers/media/pci/intel/ipu3/ipu3-cio2.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

I got more changes than mentioned above:

git pull logs
Updating e3ee691dbf24..8d677b031a4f
Fast-forward
 drivers/media/pci/intel/ipu3/ipu3-cio2.c | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

Something wrong happened here.

Regards,
Mauro



Cheers,
Mauro

  reply	other threads:[~2018-01-23 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 22:35 [GIT PULL for 4.16] CIO2 compiler warning fix Sakari Ailus
2018-01-23 12:40 ` Mauro Carvalho Chehab [this message]
2018-01-23 12:52   ` Sakari Ailus
2018-01-23 12:56   ` Sakari Ailus
2018-01-23 13:21     ` Mauro Carvalho Chehab

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=20180123104008.25ebdef5@vela.lan \
    --to=mchehab@s-opensource.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    /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.