From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Kyungmin Park' <kyungmin.park@samsung.com>
Cc: 'Kamil Debski' <k.debski@samsung.com>,
linux-media@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
m.szyprowski@samsung.com, pawel@osciak.com,
jaeryul.oh@samsung.com
Subject: RE: [RFC/PATCH v4 0/4] Multi Format Codec 5.0 driver for S5PC110 SoC
Date: Fri, 10 Dec 2010 14:23:24 +0900 [thread overview]
Message-ID: <028b01cb982a$601f6630$205e3290$%kim@samsung.com> (raw)
In-Reply-To: <AANLkTikD7UUHrao9SWsNS1YT9uTM88kH2ugOdKm6yhbS@mail.gmail.com>
Kyungmin Park wrote:
>
> >> >
> >> > Hi Kamil,
> >> >
> >> > I think, should be added my e-mail in Cc...
> >>
> >> No need to cc all, only machine specific only.
> >> and I hope minimal modification at machine specific and move to media
> >> if possible.
> >>
> > Should be reviewed proper maintainer even though it is small changes.
> > Really, I don't want to argue to you about my maintaining ship...
>
> Each preference is different and you and me are different unfortunately.
>
Hmm...What's different? If you want to submit something, should be sent to
proper maintainer.
If two maintainers, you need both maintainers' agreement or at least ack to
merge it.
> >
> > And I have a wondering about your sign.
> > Did you really check this patch before Kamil's submitting?
> > Unfortunately, I don't think so...
>
> I don't care minor issues I'm more focus on the logic.
>
Maybe you didn't check/review Kamil's patch before submitting.
So your sign has a problem. Please see "Documentation/SubmittingPatches".
I don't think that something like missing GPL license is minor issue.
I mean if you want to add your sign, you had to check it before posting.
And it doesn't matter it's small or big.
> What's the matter mfc or mfc5 and so on? some time later these names
> are changed if new mfc are introduced.
> Currently we're use the mfc version 5.
>
How about fimc0 or fimc1...it is used as hardware version?
No...it means channel. Why do you use mixed rule?
As I said, if separate hardware version required, we can do it later.
> Do you have any rules on samsung soc variable, module naming? I think
> it depends on each case by case.
>
Already mentioned.
...
I'd like to stop this here, we already talked about similar issues many
times.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
prev parent reply other threads:[~2010-12-10 5:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 13:35 [RFC/PATCH v4 0/4] Multi Format Codec 5.0 driver for S5PC110 SoC Kamil Debski
2010-12-09 13:35 ` [RFC/PATCH v4 1/4] Changes in include/linux/videodev2.h for MFC 5.1 Kamil Debski
2010-12-10 3:32 ` 박정태
[not found] ` <4D01F0B6.8090800@redhat.com>
2010-12-10 10:10 ` Kamil Debski
2010-12-09 13:35 ` [RFC/PATCH v4 2/4] MFC: Add MFC 5.1 driver to plat-s5p Kamil Debski
2010-12-10 2:44 ` Kukjin Kim
2010-12-10 10:10 ` Kamil Debski
2010-12-10 3:41 ` Kukjin Kim
2010-12-09 13:35 ` [RFC/PATCH v4 3/4] MFC: Added MFC 5.1 V4L2 driver Kamil Debski
2010-12-09 13:35 ` [RFC/PATCH v4 4/4] s5pv210: Enable MFC on Goni Kamil Debski
2010-12-10 2:32 ` [RFC/PATCH v4 0/4] Multi Format Codec 5.0 driver for S5PC110 SoC Kukjin Kim
2010-12-10 2:40 ` Kyungmin Park
2010-12-10 3:40 ` Kukjin Kim
2010-12-10 4:02 ` Kyungmin Park
2010-12-10 5:23 ` Kukjin Kim [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='028b01cb982a$601f6630$205e3290$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=jaeryul.oh@samsung.com \
--cc=k.debski@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=pawel@osciak.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