All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Wu <josh.wu@atmel.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: <linux-media@vger.kernel.org>
Subject: Re: [PATCH 0/4] atmel-isi: Remove platform data support
Date: Mon, 21 Sep 2015 09:33:10 +0800	[thread overview]
Message-ID: <55FF5E56.8010009@atmel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1509201715180.30819@axis700.grange>

Hi, Guennadi

On 9/20/2015 11:25 PM, Guennadi Liakhovetski wrote:
> Hi Laurent, Josh,
>
> It's ok not to CC me immediately if it's expected, that patches will be
> further forwarded (by Josh in this case) to me. And it helps, that Josh
> has collected all Atmel ISI patches in a git tree branch - thanks! But,
> please make sure, that all patches also appear in my mailbox at least
> once, especially if they are (even trivially) modified - like in this
> case, where patches 2 and 3 have been merged into 1.
yes, got it. I will make sure of that in future. Thanks for the remind.

Best Regards,
Josh Wu
>
> Thanks
> Guennadi
>
> On Sat, 1 Aug 2015, Laurent Pinchart wrote:
>
>> Hello,
>>
>> While reviewing patches for the atmel-isi I noticed a couple of small issues
>> with the driver. Here's a patch series to fix them, the main change being the
>> removal of platform data support now that all users have migrated to DT.
>>
>> The patches have been compile-tested only. Josh, would you be able to test
>> them on hardware ?
>>
>> Laurent Pinchart (4):
>>    v4l: atmel-isi: Simplify error handling during DT parsing
>>    v4l: atmel-isi: Remove unused variable
>>    v4l: atmel-isi: Remove support for platform data
>>    v4l: atmel-isi: Remove unused platform data fields
>>
>>   drivers/media/platform/soc_camera/atmel-isi.c |  40 ++------
>>   drivers/media/platform/soc_camera/atmel-isi.h | 126 +++++++++++++++++++++++++
>>   include/media/atmel-isi.h                     | 131 --------------------------
>>   3 files changed, 136 insertions(+), 161 deletions(-)
>>   create mode 100644 drivers/media/platform/soc_camera/atmel-isi.h
>>   delete mode 100644 include/media/atmel-isi.h
>>
>> -- 
>> Regards,
>>
>> Laurent Pinchart
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>


      reply	other threads:[~2015-09-21  1:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-01  9:22 [PATCH 0/4] atmel-isi: Remove platform data support Laurent Pinchart
2015-08-01  9:22 ` [PATCH 1/4] v4l: atmel-isi: Simplify error handling during DT parsing Laurent Pinchart
2015-08-01  9:22 ` [PATCH 2/4] v4l: atmel-isi: Remove unused variable Laurent Pinchart
2015-08-06  8:19   ` Josh Wu
2015-08-01  9:22 ` [PATCH 3/4] v4l: atmel-isi: Remove support for platform data Laurent Pinchart
2015-08-01  9:22 ` [PATCH 4/4] v4l: atmel-isi: Remove unused platform data fields Laurent Pinchart
2015-08-03  2:56 ` [PATCH 0/4] atmel-isi: Remove platform data support Josh Wu
2015-08-04 22:08   ` Laurent Pinchart
2015-08-05  3:31     ` Josh Wu
2015-09-20 15:25 ` Guennadi Liakhovetski
2015-09-21  1:33   ` Josh Wu [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=55FF5E56.8010009@atmel.com \
    --to=josh.wu@atmel.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@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 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.