public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP2: Update N800 defconfig
Date: Sun, 04 Mar 2007 21:04:49 +0100	[thread overview]
Message-ID: <85zm6sdbby.fsf@orfeo.duckcorp.org> (raw)
In-Reply-To: <45EAF579.50404@googlemail.com> (Dirk Behme's message of "Sun, 04 Mar 2007 17:36:09 +0100")

Dirk Behme <dirk.behme@googlemail.com> writes:

> Arnaud Patard (Rtp) wrote:
>> Dirk Behme <dirk.behme@googlemail.com> writes:
>>
>>
>>>Arnaud Patard (Rtp) wrote:
>>>
>>>>>Update N800 defconfig, mainly to disable netfilter which
>>>>>doesn't compile:
>>>>
>>>> Fixing the build may be a better idea than disabling it.
>>>
>>>Yes, your are right ;) But this is something we can't do here on OMAP
>>>list.
>>
>>
>> I disagree. This driver afaik can only be found in the omap tree and
>> it's only a matter of taking few minutes to update the driver to follow
>> upstream changes. So, unless the original author of the driver fixes it
>> (which I doubt), it's up to us to fix it.
>
> Uups, we have some OMAP specifc stuff in net/ipv4/netfilter? I wasn't

yeah :(

> aware of this. Yes, then your are right that we have to fix it. I
> thought it is an upstream issue. Then, forget my N800 defconfig


I though too until I've started looking for a newer/fixed version.

> changes, thanks for the correction and the patch.
>

Arnaud

  reply	other threads:[~2007-03-04 20:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-04 10:29 [PATCH] ARM: OMAP2: Update N800 defconfig Dirk Behme
2007-03-04 10:42 ` Arnaud Patard
2007-03-04 11:52   ` Dirk Behme
2007-03-04 12:21     ` Arnaud Patard
2007-03-04 16:36       ` Dirk Behme
2007-03-04 20:04         ` Arnaud Patard [this message]
2007-03-05 11:48       ` Tony Lindgren
2007-03-05 13:10         ` Arnaud Patard
2007-03-05 13:51           ` Tony Lindgren

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=85zm6sdbby.fsf@orfeo.duckcorp.org \
    --to=arnaud.patard@rtp-net.org \
    --cc=dirk.behme@googlemail.com \
    --cc=linux-omap-open-source@linux.omap.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