All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakob Viketoft <jakob@viketoft.se>
To: eric.y.miao@gmail.com
Cc: Daniel Mack <daniel@caiaq.de>,
	linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>,
	minimumlaw@rambler.ru
Subject: Re: [PATCH] colibri.h: Fix building for colibri 270...
Date: Wed, 05 May 2010 13:02:18 +0200	[thread overview]
Message-ID: <4BE1503A.7020702@viketoft.se> (raw)
In-Reply-To: <z2jf17812d71005050321m2520f76cv95801b0539800db5@mail.gmail.com>

Hello!

I didn't see this first as the e-mail address jakob.viketoft@bitsim.com 
is being shut down (changing jobs).

Eric Miao wrote:
> On Wed, May 5, 2010 at 5:53 PM, Daniel Mack <daniel@caiaq.de> wrote:
>> On Wed, May 05, 2010 at 05:47:14PM +0800, Eric Miao wrote:
>>> On Wed, May 5, 2010 at 5:44 PM, Daniel Mack <daniel@caiaq.de> wrote:
>>>>> And I'm not able to find
>>>>> drivers/pcmcia/pxa2xx_colibri.c as well.
>>>> Erm - how is that related to the patch in question?
>>>>
>>> The error seems to be (as in previous mail):
>>>
>>>  CC      drivers/pcmcia/pxa2xx_colibri.o
>>> In file included from drivers/pcmcia/pxa2xx_colibri.c:25:
>>> arch/arm/mach-pxa/include/mach/colibri.h:13: error: expected ')'
>>> before '*' token
>>> make[2]: *** [drivers/pcmcia/pxa2xx_colibri.o] Error 1
>>> make[1]: *** [drivers/pcmcia] Error 2
>>> make: *** [drivers] Error 2
>> Ah, sorry.

The pcmcia-patch isn't my work, but that of Alex A. Mihaylov 
(minimumlaw@rambler.ru). I was hoping that he would be pushing those 
bits upstream separately, but I think some things needs to me shifted 
around a bit to be accepted.

>>
>>> And actually, inclusion of <mach/mfp.h> is better to be placed where it's
>>> used, i.e. drivers/pcmcia/pxa2xx_colibri.c.
>> In general I agree, but in this case, mfp_t is used in this header file,
>> so every piece of code which includes colibri.h will need both
>> <mach/mfp.h> and <net/ax88796.h>. And as this is a rule for all users, I
>> think the right place for the inclusion is the header file?
>>
> 
> I see.
> 
> Acked-by: Eric Miao <eric.y.miao@gmail.com>

Thanks.

> 
> 
>> Apart from that, this fix will work for both mainline and -stable, which
>> makes things easier :)
>>
> 
> I'll take it to -pxa then.

Sounds good!

	/Jakob


  reply	other threads:[~2010-05-05 11:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-16  9:51 [PATCH] colibri.h: Fix building for colibri 270 Jakob Viketoft
2010-04-16 10:01 ` Daniel Mack
2010-04-16 11:17   ` Jakob Viketoft
2010-04-16 11:25     ` Jakob Viketoft
2010-04-16 11:28       ` Daniel Mack
2010-04-16 11:29         ` Daniel Mack
2010-05-05  7:45           ` Eric Miao
2010-05-05  8:00             ` Daniel Mack
2010-05-05  9:28               ` Eric Miao
2010-05-05  9:44                 ` Daniel Mack
2010-05-05  9:47                   ` Eric Miao
2010-05-05  9:53                     ` Daniel Mack
2010-05-05 10:21                       ` Eric Miao
2010-05-05 11:02                         ` Jakob Viketoft [this message]
2010-05-05 15:20                   ` Greg KH
2010-05-05 15:54                     ` Daniel Mack
2010-05-05 16:15                       ` Greg KH
2010-04-16 11:26     ` Daniel Mack

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=4BE1503A.7020702@viketoft.se \
    --to=jakob@viketoft.se \
    --cc=daniel@caiaq.de \
    --cc=eric.y.miao@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minimumlaw@rambler.ru \
    /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.