public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Hansjoerg Lipp <hjlipp@web.de>
Subject: Re: linux-next: Tree for March 17 (gigaset isdn)
Date: Wed, 17 Mar 2010 18:30:27 +0100	[thread overview]
Message-ID: <4BA111B3.3040108@imap.cc> (raw)
In-Reply-To: <4BA0F78F.9090804@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

Am 17.03.2010 16:38 schrieb Randy Dunlap:
> On 03/16/10 22:08, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20100316:
> 
> 
> ERROR: "gigaset_isdn_regdev" [drivers/isdn/gigaset/gigaset.ko] undefined!
> ERROR: "gigaset_isdn_regdrv" [drivers/isdn/gigaset/gigaset.ko] undefined!
> ERROR: "gigaset_isdn_unregdrv" [drivers/isdn/gigaset/gigaset.ko] undefined!
> ERROR: "gigaset_isdn_unregdev" [drivers/isdn/gigaset/gigaset.ko] undefined!
> 
> when
> # CONFIG_ISDN_I4L is not set
> # CONFIG_ISDN_CAPI is not set
> CONFIG_ISDN_DRV_GIGASET=m # or =y
> 

Rats, you're right. Sorry for the oversight. I will create a fix right away.

Thanks,
Tilman

-- 
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: 259 bytes --]

      reply	other threads:[~2010-03-17 17:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17  5:08 linux-next: Tree for March 17 Stephen Rothwell
2010-03-17 15:38 ` linux-next: Tree for March 17 (gigaset isdn) Randy Dunlap
2010-03-17 17:30   ` Tilman Schmidt [this message]

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=4BA111B3.3040108@imap.cc \
    --to=tilman@imap.cc \
    --cc=hjlipp@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sfr@canb.auug.org.au \
    /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