From: "David Härdeman" <david@hardeman.nu>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-media@vger.kernel.org, jarod@redhat.com
Subject: Re: [PATCH 1/5] rc-code: merge and rename ir-core
Date: Wed, 8 Sep 2010 23:42:13 +0200 [thread overview]
Message-ID: <20100908214213.GD13938@hardeman.nu> (raw)
In-Reply-To: <4C8792B2.2010809@infradead.org>
On Wed, Sep 08, 2010 at 10:42:10AM -0300, Mauro Carvalho Chehab wrote:
> Em 07-09-2010 18:51, David Härdeman escreveu:
> > This patch merges the files which makes up ir-core and renames the
> > resulting module to rc-core. IMHO this makes it much easier to hack
> > on the core module since all code is in one file.
> >
> > This also allows some simplification of ir-core-priv.h as fewer internal
> > functions need to be exposed.
>
> I'm not sure about this patch. Big files tend to be harder to maintain,
> as it takes more time to find the right functions inside it. Also, IMO,
> it makes sense to keep the raw-event code on a separate file.
I don't find "big" files difficult (note: we're talking about 1300 lines
here). Rather the opposite, no hesitation about which files a given
function originates from and all related code in one nice file. evdev.c
and input.c are good precedents. But of course, it all boils down to a
matter of personal taste.
> Anyway, if we apply this patch right now, it will cause merge conflicts with
> the input tree, due to the get/setkeycodebig patches, and with some other
> patches that are pending merge/review. The better is to apply such patch
> just after the release of 2.6.37-rc1, after having all those conflicts
> solved.
I agree that the big scancode patches from the input tree should go
first. I keep updating my patchset as the media_tree (staging/v2.6.37
branch) changes so I have no problem sending an updated patchset at a
suitable time in the future.
--
David Härdeman
next prev parent reply other threads:[~2010-09-08 21:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 21:51 [PATCH 0/5] rc-core: ir-core to rc-core conversion (v2) David Härdeman
2010-09-07 21:51 ` [PATCH 1/5] rc-code: merge and rename ir-core David Härdeman
2010-09-08 13:42 ` Mauro Carvalho Chehab
2010-09-08 14:10 ` Jarod Wilson
2010-09-08 21:42 ` David Härdeman [this message]
2010-09-09 4:44 ` Jarod Wilson
2010-09-07 21:51 ` [PATCH 2/5] rc-core: remove remaining users of the ir-functions keyhandlers David Härdeman
2010-09-09 5:00 ` Jarod Wilson
2010-09-07 21:51 ` [PATCH 3/5] imon: split mouse events to a separate input dev David Härdeman
2010-09-07 21:51 ` [PATCH 4/5] rc-core: make struct rc_dev the primary interface for rc drivers David Härdeman
2010-09-09 4:41 ` Jarod Wilson
2010-09-07 21:52 ` [PATCH 5/5] rc-core: convert winbond-cir David Härdeman
-- strict thread matches above, loose matches on Subject: below --
2010-09-08 15:10 [PATCH 1/5] rc-code: merge and rename ir-core Andy Walls
2010-09-08 21:12 ` David Härdeman
2010-09-09 8:20 ` Maxim Levitsky
2010-09-02 20:29 [PATCH 0/5] rc-core: ir-core to rc-core conversion David Härdeman
2010-09-02 20:29 ` [PATCH 1/5] rc-code: merge and rename ir-core David Härdeman
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=20100908214213.GD13938@hardeman.nu \
--to=david@hardeman.nu \
--cc=jarod@redhat.com \
--cc=linux-media@vger.kernel.org \
--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 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).