From: Tilman Schmidt <tilman@imap.cc>
To: Adrian Bunk <bunk@stusta.de>
Cc: Kai Germaschewski <kai.germaschewski@unh.edu>,
Hansjoerg Lipp <hjlipp@web.de>,
kkeil@suse.de, isdn4linux@listserv.isdn4linux.de,
linux-kernel@vger.kernel.org
Subject: Re: Kbuild problem
Date: Tue, 20 Feb 2007 22:55:17 +0100 [thread overview]
Message-ID: <45DB6E45.5040408@imap.cc> (raw)
In-Reply-To: <20070220145943.GU13958@stusta.de>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
Am 20.02.2007 15:59 schrieb Adrian Bunk:
> I'm usually someone who likes to avoid including unneeded code in the
> kernel, but in this case I'd say KISS - and build it always into the
> gigaset module.
There seems to be a clear majority for this solution. So KISS it
will be. Thanks for all the advice. I'll do a new patch.
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]
next prev parent reply other threads:[~2007-02-20 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 21:56 [2.6 patch] drivers/isdn/gigaset/: build asyncdata.o into the gigaset module Adrian Bunk
2007-02-16 0:17 ` Tilman Schmidt
2007-02-16 8:33 ` Adrian Bunk
2007-02-17 0:04 ` Kbuild problem (was: [2.6 patch] drivers/isdn/gigaset/: build asyncdata.o into the gigaset module) Tilman Schmidt
2007-02-17 10:52 ` Adrian Bunk
2007-02-17 18:36 ` Kbuild problem Tilman Schmidt
2007-02-18 5:22 ` Kai Germaschewski
2007-02-18 10:40 ` Adrian Bunk
2007-02-20 13:56 ` Tilman Schmidt
2007-02-20 14:12 ` Joerg Dorchain
2007-02-20 14:59 ` Adrian Bunk
2007-02-20 21:55 ` Tilman Schmidt [this message]
2007-11-01 1:39 kbuild problem Randy Dunlap
2007-11-01 5:21 ` Sam Ravnborg
2007-11-01 17:11 ` Randy Dunlap
2007-11-01 17:59 ` Sam Ravnborg
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=45DB6E45.5040408@imap.cc \
--to=tilman@imap.cc \
--cc=bunk@stusta.de \
--cc=hjlipp@web.de \
--cc=isdn4linux@listserv.isdn4linux.de \
--cc=kai.germaschewski@unh.edu \
--cc=kkeil@suse.de \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome