linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Junghak Sung <jh1009.sung@samsung.com>,
	linux-media@vger.kernel.org, mchehab@osg.samsung.com,
	laurent.pinchart@ideasonboard.com, sakari.ailus@iki.fi,
	pawel@osciak.com
Cc: inki.dae@samsung.com, sw0312.kim@samsung.com,
	nenggun.kim@samsung.com, sangbae90.lee@samsung.com,
	rany.kwon@samsung.com
Subject: Re: [RFC PATCH v2 1/5] media: videobuf2: Rename videobuf2-core to videobuf2-v4l2
Date: Mon, 10 Aug 2015 10:06:29 +0200	[thread overview]
Message-ID: <55C85B85.1050506@xs4all.nl> (raw)
In-Reply-To: <1438332277-6542-2-git-send-email-jh1009.sung@samsung.com>

Hi Junghak,

On 07/31/2015 10:44 AM, Junghak Sung wrote:
> Rename file name - from videobuf2-core.[ch] to videobuf2-v4l2.[ch]
> This renaming patch should be accompanied by the modifications for all device
> drivers that include this header file. It can be done with just running this
> shell script.
> 
> replace()
> {
> str1=$1
> str2=$2
> dir=$3
> for file in $(find $dir -name *.h -o -name *.c -o -name Makefile)
> do
>     echo $file
>     sed "s/$str1/$str2/g" $file > $file.out
>     mv $file.out $file
> done
> }
> replace "videobuf2-core" "videobuf2-v4l2" "include/media/"
> replace "videobuf2-core" "videobuf2-v4l2" "drivers/media/"
> 
> Signed-off-by: Junghak Sung <jh1009.sung@samsung.com>
> Signed-off-by: Geunyoung Kim <nenggun.kim@samsung.com>
> Acked-by: Seung-Woo Kim <sw0312.kim@samsung.com>
> Acked-by: Inki Dae <inki.dae@samsung.com>

Rather than moving videobuf2-core.c to videobuf2-v4l2.c I would recommend to just
create a videobuf2-v4l2.h header that includes videobuf2-core.h and nothing else.

So this patch will move all drivers over to include the new videobuf2-v4l2.h header,
leaving everything else unchanged.

Then in patch 3 you can move code from videobuf2-core.c/h to videobuf2-v4l2.c/h. This
will make patch 3 easier to read for me since I can clearly see in the diff what
has been moved from -core.c/h to -v4l2.c/h.

Right now patch 3 shows what moved from -v4l2.c/h to -core.c/h, which is the wrong
way around. And makes patch 3 much larger than it needs to be since (unsurprisingly)
most code from v4l2.c/h moves back to core.c/h.

Regards,

	Hans

  reply	other threads:[~2015-08-10  8:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-31  8:44 [RFC PATCH v2 0/5] Refactoring Videobuf2 for common use Junghak Sung
2015-07-31  8:44 ` [RFC PATCH v2 1/5] media: videobuf2: Rename videobuf2-core to videobuf2-v4l2 Junghak Sung
2015-08-10  8:06   ` Hans Verkuil [this message]
2015-07-31  8:44 ` [RFC PATCH v2 2/5] media: videobuf2: Restructurng struct vb2_buffer for common use Junghak Sung
2015-07-31  8:44 ` [RFC PATCH v2 3/5] media: videobuf2: Divide videobuf2-core into 2 parts Junghak Sung
2015-08-10 12:07   ` Hans Verkuil
2015-08-10 12:55     ` Mauro Carvalho Chehab
2015-08-10 13:38       ` Hans Verkuil
2015-08-11 13:51         ` Laurent Pinchart
2015-07-31  8:44 ` [RFC PATCH v2 4/5] media: videobuf2: Define vb2_buf_type and vb2_memory Junghak Sung
2015-08-10  8:22   ` Hans Verkuil
2015-08-11  2:19     ` Junghak Sung
2015-08-11  6:32       ` Hans Verkuil
2015-08-11 13:56     ` Laurent Pinchart
2015-08-11 13:59       ` Hans Verkuil
2015-08-11 14:04         ` Laurent Pinchart
2015-07-31  8:44 ` [RFC PATCH v2 5/5] media: videobuf2: Modify prefix for VB2 functions Junghak Sung
2015-08-10  8:31 ` [RFC PATCH v2 0/5] Refactoring Videobuf2 for common use Hans Verkuil
2015-08-10  9:32   ` Mauro Carvalho Chehab
2015-08-10 10:11     ` Hans Verkuil
2015-08-10 10:49       ` Mauro Carvalho Chehab
2015-08-10 11:44         ` Hans Verkuil
2015-08-11  1:37           ` Junghak Sung

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=55C85B85.1050506@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=inki.dae@samsung.com \
    --cc=jh1009.sung@samsung.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.com \
    --cc=nenggun.kim@samsung.com \
    --cc=pawel@osciak.com \
    --cc=rany.kwon@samsung.com \
    --cc=sakari.ailus@iki.fi \
    --cc=sangbae90.lee@samsung.com \
    --cc=sw0312.kim@samsung.com \
    /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).