From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Karicheri\, Muralidharan" <m-karicheri2@ti.com>
Cc: "linux-media\@vger.kernel.org" <linux-media@vger.kernel.org>,
"mchehab\@infradead.org" <mchehab@infradead.org>,
"hverkuil\@xs4all.nl" <hverkuil@xs4all.nl>,
"davinci-linux-open-source\@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>
Subject: Re: [PATCH - v4 1/4] V4L-vpfe_capture-remove-clock and platform code
Date: Tue, 12 Jan 2010 08:19:18 -0800 [thread overview]
Message-ID: <87tyurgut5.fsf@deeprootsystems.com> (raw)
In-Reply-To: <A69FA2915331DC488A831521EAE36FE40162DF9E7C@dlee06.ent.ti.com> (Muralidharan Karicheri's message of "Tue\, 12 Jan 2010 08\:40\:44 -0600")
"Karicheri, Muralidharan" <m-karicheri2@ti.com> writes:
[...]
>>
>>Also, this doesn't accuratly reflect the changes done in the patch.
>>
>>Here the clock configuration isn't moved, it's removed. You should
>>mention it being removed here and added to platform-specific code in
>>subsequent patches.
>>
>>Sorry to be so nit-picky about the comments, but having a well-written
>>and descriptive changelog is extremely importanty. For the benefit of
>>reading the git history later, and also for those of us less familiar
>>with the details of these drivers, we rely heavily on a good changelog.
>>
>
> [MK] I think you are being too picky on these comments :(
Part of my role is to be picky. ;)
> Besides this was gone through several reviews and I was wondering
> why you chose to ignore these comments earlier. It was now being
> sent for merge, not for review.
I did not do a detailed review in the earlier versions because I was
leaving this to be thoroughly reviewed by linux-media folks.
However, with all the clock issues, I decided to give it a more
thorough review, and I found the changelogs to not be helpful in
understanding the patches.
The linux-media maintainers are certainly free to merge the stuff with
the current confusing changelog, but I would not recommend it.
> This is really not helping the upstream merge :(
Well, it may be taking a bit longer, but it is helping the quality of
the changes that are eventually merged upstream.
> Anyways, I will make these changes and send again.
Thanks,
Kevin
next prev parent reply other threads:[~2010-01-12 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 23:36 [PATCH - v4 4/4] DaVinci-vpfe-capture-converting-ccdc-drivers-to-platform-drivers m-karicheri2
2010-01-11 23:36 ` [PATCH - v4 2/4] V4L-vpfe-capture-converting dm355 ccdc driver to a platform driver m-karicheri2
2010-01-11 23:36 ` [PATCH - v4 3/4] V4L-vpfe-capture-converting-dm644x-driver " m-karicheri2
2010-01-11 23:36 ` [PATCH - v4 1/4] V4L-vpfe_capture-remove-clock and platform code m-karicheri2
2010-01-12 0:16 ` Kevin Hilman
2010-01-12 14:40 ` Karicheri, Muralidharan
2010-01-12 16:19 ` Kevin Hilman [this message]
2010-01-12 0:22 ` [PATCH - v4 2/4] V4L-vpfe-capture-converting dm355 ccdc driver to a platform driver Kevin Hilman
2010-01-12 0:28 ` [PATCH - v4 4/4] DaVinci-vpfe-capture-converting-ccdc-drivers-to-platform-drivers Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2010-01-11 19:22 m-karicheri2
2010-01-11 19:22 ` [PATCH - v4 2/4] V4L-vpfe-capture-converting dm355 ccdc driver to a platform driver m-karicheri2
2010-01-11 19:22 ` [PATCH - v4 3/4] V4L-vpfe-capture-converting-dm644x-driver " m-karicheri2
2010-01-11 19:22 ` [PATCH - v4 1/4] V4L-vpfe_capture-remove-clock and platform code m-karicheri2
2010-01-11 19:33 ` Karicheri, Muralidharan
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=87tyurgut5.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=mchehab@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 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.