From: kgene.kim@samsung.com (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 3/3] input: samsung-keypad - Add samsung keypad driver
Date: Mon, 02 Aug 2010 15:30:57 +0900 [thread overview]
Message-ID: <003901cb320c$47daa960$d78ffc20$%kim@samsung.com> (raw)
In-Reply-To: <4C565D21.8050506@samsung.com>
Joonyoung Shim wrote:
>
> On 8/2/2010 2:12 PM, Kukjin Kim wrote:
> > Joonyoung Shim wrote:
> >> On 8/2/2010 12:38 PM, Kukjin Kim wrote:
> >>> Joonyoung Shim wrote:
> >>>> Hi, I came back from vacation.
> >>>>
> >>>>>>>> Do you have any feedback? If ok, i want to go to input tree or samsung
> >>>>>>>> tree these added sched.h including.
> >>>>>>> I applied the patch adding samsung-keypad.c and the platform data
> >>>>>>> arch/arm/plat-samsung/include/plat/keypad.h and I expect that
> >>>>>>> patches to actually enable keypad will go through appropriate
> >>>>>>> platform tree(s).
> >>>>>>>
> >>>>>> OK, the rest will go through samsung platform tree
> >>>>>>
> >>>>> Ok..will apply.
> >>>>>
> >>>> Kukjin, could you remove keypad.h on the commit "ARM: SAMSUNG: Add
> >>>> keypad device support" of the samsung platform tree. The keypad.h file
> >>>> was included on input tree.
> >>>>
> >>
> (http://git.kernel.org/?p=linux/kernel/git/dtor/input.git;a=commit;h=0fffed27f92d9d7
> >>>> a34de9fe017b7082b5958bb93)
> >>> You mean in plat-samsung/dev-keypad.c?
> >>> If remove inclusion plat/keypad.h in there, following build error happens.
> >>>
> >> No. I mean to remove arch/arm/plat-samsung/include/plat/keypad.h file on
> >> samsung platform tree, it was applied on input tree already. If needs, i
> >> can repost.
> >>
> > If it is not small change like to remove a file in a patch, I think should be re-
> submitted.
> > Will drop your previous patch in my tree.
> >
> >>> arch/arm/plat-samsung/dev-keypad.c:41: warning: 'struct
> >> samsung_keypad_platdata' declared inside parameter list
> >>> arch/arm/plat-samsung/dev-keypad.c:41: warning: its scope is only this
> definition
> >> or declaration, which is probably not what you want
> >>> arch/arm/plat-samsung/dev-keypad.c: In function
> >> 'samsung_keypad_set_platdata':
> >>> arch/arm/plat-samsung/dev-keypad.c:50: error: invalid application of 'sizeof'
> to
> >> incomplete type 'struct samsung_keypad_platdata'
> >>> arch/arm/plat-samsung/dev-keypad.c:54: error: dereferencing pointer to
> >> incomplete type
> >>> arch/arm/plat-samsung/dev-keypad.c:55: error: dereferencing pointer to
> >> incomplete type
> >>> arch/arm/plat-samsung/dev-keypad.c:55: error: 'samsung_keypad_cfg_gpio'
> >> undeclared (first use in this function)
> >>> arch/arm/plat-samsung/dev-keypad.c:55: error: (Each undeclared identifier is
> >> reported only once
> >>> arch/arm/plat-samsung/dev-keypad.c:55: error: for each function it appears in.)
> >>> make[1]: *** [arch/arm/plat-samsung/dev-keypad.o] Error 1
> >>>
> >>> As you know, released 35 today. So we have no much time for this merge
> >> window.
> >> I'm not sure about merge rule, but I think the compile problem can be
> >> solved by merge to 36 of input tree and samsung platform tree.
> >
> > Hmm...actually, already informed about that on linux-next.
> > If it's just build problem, I or Dmitry can fix it. However, this is not just that.
> > I cannot understand how your 'plat/keypad.h' was included to both of patch.
>
> Please see the prior mail history. The keypad.h file is included only at
> the 1/3 patch in the original patch set, but Dmitry applied the 3/3
> patch modified with keypad.h.
>
> The basic problem is that each patches be applied on two tree. It makes
> compile errors at the one tree lacking keypad.h file because both tree
> share keypad.h file.
>
> There are two solutions, First, all patches go to one tree. Second, we
> wait for merging to 36 of both tree then apply platform patches.
>
> > And I'm not sure, should be 'plat/keypad.h' in which tree...
> >
Hi Dmitry,
How can/should I do for it?...Which way is better to us? :-)
Joonyoung,
Let's wait for Dmitry's reply.
I will holding drop your previous patch in my tree till that time.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
next prev parent reply other threads:[~2010-08-02 6:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 11:33 [PATCH v6 1/3] ARM: SAMSUNG: Add keypad device support Joonyoung Shim
2010-06-28 11:33 ` [PATCH v6 2/3] ARM: S5PV210: Add keypad device helpers Joonyoung Shim
2010-06-28 11:33 ` [PATCH v6 3/3] input: samsung-keypad - Add samsung keypad driver Joonyoung Shim
2010-07-06 7:58 ` Joonyoung Shim
2010-07-06 23:52 ` Kukjin Kim
2010-07-07 1:28 ` Joonyoung Shim
2010-07-09 7:07 ` Kukjin Kim
2010-07-09 7:39 ` Joonyoung Shim
2010-07-21 5:42 ` Joonyoung Shim
2010-07-21 6:21 ` Kukjin Kim
2010-07-21 8:07 ` Dmitry Torokhov
2010-07-21 9:01 ` Joonyoung Shim
2010-07-21 12:39 ` Kukjin Kim
2010-08-02 3:09 ` Joonyoung Shim
2010-08-02 3:38 ` Kukjin Kim
2010-08-02 4:41 ` Joonyoung Shim
2010-08-02 5:12 ` Kukjin Kim
2010-08-02 5:52 ` Joonyoung Shim
2010-08-02 6:30 ` Kukjin Kim [this message]
2010-08-02 7:58 ` Dmitry Torokhov
2010-08-03 2:10 ` Kukjin Kim
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='003901cb320c$47daa960$d78ffc20$%kim@samsung.com' \
--to=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.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).