From: Tony Lindgren <tony@atomide.com>
To: Arnaud Patard <arnaud.patard@rtp-net.org>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] ARM: OMAP2: Update N800 defconfig
Date: Mon, 5 Mar 2007 03:48:32 -0800 [thread overview]
Message-ID: <20070305114831.GD17801@atomide.com> (raw)
In-Reply-To: <85y7mdgpww.fsf@orfeo.duckcorp.org>
* Arnaud Patard <arnaud.patard@rtp-net.org> [070304 04:27]:
> 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.
Thanks, can you please add a Signed-off-by to this thread? I'll add
your patch to the "Add iptables IDLETIMER target" patch in omap-drivers
branch. Once it's been tested we should try to send it upstream when the
next merge window opens.
> As I said, I have a patch for it. I'm attaching it to this mail for
> reference because I'm now thinking that I won't be able to test it on my
> n770.
Binary firmware issue with compiling wlan driver I suppose? :(
Regards,
Tony
next prev parent reply other threads:[~2007-03-05 11:48 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
2007-03-05 11:48 ` Tony Lindgren [this message]
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=20070305114831.GD17801@atomide.com \
--to=tony@atomide.com \
--cc=arnaud.patard@rtp-net.org \
--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