All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Boris B. Zhmurov" <bb@kernelpanic.ru>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Willy Tarreau <wtarreau@hera.kernel.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: Linux 2.6.20.17
Date: Sun, 26 Aug 2007 19:15:10 +0400	[thread overview]
Message-ID: <46D198FE.70506@kernelpanic.ru> (raw)
In-Reply-To: <20070825110148.5fd59272.randy.dunlap@oracle.com>

Hello, Randy Dunlap.

On 25.08.2007 22:01 you said the following:


> I'm getting build errors:
> 
> x86_64 allyesconfig, allmodconfig:
> 
> drivers/ata/pata_atiixp.c:286: error: 'PCI_DEVICE_ID_ATI_IXP700_IDE' undeclared here (not in a function)
> net/bluetooth/rfcomm/tty.c:275: error: 'struct rfcomm_dev' has no member named 'tty_dev'
> net/bluetooth/rfcomm/tty.c:278: error: 'struct rfcomm_dev' has no member named 'tty_dev'


After applying patch-2.6.20.17, I'm getting build errors either:

net/bluetooth/rfcomm/tty.c: In function `rfcomm_dev_add':
net/bluetooth/rfcomm/tty.c:275: error: structure has no member named 
`tty_dev'
net/bluetooth/rfcomm/tty.c:278: error: structure has no member named 
`tty_dev'
make[3]: *** [net/bluetooth/rfcomm/tty.o] Error 1
make[2]: *** [net/bluetooth/rfcomm] Error 2
make[1]: *** [net/bluetooth] Error 2
make: *** [net] Error 2



-- 
Boris B. Zhmurov
mailto: bb@kernelpanic.ru


  reply	other threads:[~2007-08-26 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-25 15:38 Linux 2.6.20.17 Willy Tarreau
2007-08-25 15:41 ` Willy Tarreau
2007-08-25 18:01 ` Randy Dunlap
2007-08-26 15:15   ` Boris B. Zhmurov [this message]
2007-08-26 15:48     ` Marcel Holtmann
2007-08-27  1:12       ` Willy Tarreau

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=46D198FE.70506@kernelpanic.ru \
    --to=bb@kernelpanic.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=stable@vger.kernel.org \
    --cc=wtarreau@hera.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 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.