linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build failure after merge of the bluetooth tree
Date: Thu, 28 Apr 2011 11:41:18 +1000	[thread overview]
Message-ID: <20110428114118.dd5a74e0.sfr@canb.auug.org.au> (raw)

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

Hi Gustavo,

After merging the bluetooth tree, today's linux-next build (x86_64
allmodconfig) failed like this:

net/bluetooth/cmtp/core.c: In function 'cmtp_add_connection':
net/bluetooth/cmtp/core.c:349: error: 'struct l2cap_pinfo' has no member named 'omtu'
net/bluetooth/cmtp/core.c:349: error: 'struct l2cap_pinfo' has no member named 'imtu'
net/bluetooth/hidp/core.c: In function 'hidp_add_connection':
net/bluetooth/hidp/core.c:982: error: 'struct l2cap_pinfo' has no member named 'omtu'
net/bluetooth/hidp/core.c:982: error: 'struct l2cap_pinfo' has no member named 'imtu'
net/bluetooth/hidp/core.c:983: error: 'struct l2cap_pinfo' has no member named 'omtu'
net/bluetooth/hidp/core.c:983: error: 'struct l2cap_pinfo' has no member named 'imtu'

Caused by commit 6657e8f0cc05 ("Bluetooth: Move more channel info to
struct l2cap_chan").

I have used the bluetooth tree from next-20110427 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

             reply	other threads:[~2011-04-28  1:41 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28  1:41 Stephen Rothwell [this message]
2011-04-28  4:12 ` linux-next: build failure after merge of the bluetooth tree Gustavo F. Padovan
  -- strict thread matches above, loose matches on Subject: below --
2024-05-01  1:19 Stephen Rothwell
2024-05-01  1:34 ` Sungwoo Kim
2023-07-20 22:21 Iwashima, Kuniyuki
     [not found] <PH0PR11MB51269B6805230AB8ED209B14D332A@PH0PR11MB5126.namprd11.prod.outlook.com>
2023-07-20  0:50 ` Stephen Rothwell
2023-07-20  1:24   ` Jakub Kicinski
2023-07-20  3:00     ` Stephen Rothwell
     [not found]       ` <PH0PR11MB5126763E5913574B8ED6BDE4D33EA@PH0PR11MB5126.namprd11.prod.outlook.com>
2023-07-20  3:24         ` Jakub Kicinski
2023-07-20  6:00           ` Alexander Mikhalitsyn
2023-07-20 15:14           ` Jakub Kicinski
2023-07-20 15:21             ` Alexander Mikhalitsyn
2023-07-20 22:19               ` Stephen Rothwell
2023-07-20 22:12             ` Stephen Rothwell
2023-07-20 23:27               ` Jakub Kicinski
2023-07-20 23:30                 ` Stephen Rothwell
     [not found] <PH0PR11MB51262F07CD4739BDCB920483D322A@PH0PR11MB5126.namprd11.prod.outlook.com>
2023-06-23  8:34 ` Alexander Mikhalitsyn
2023-06-23  9:23   ` Alexander Mikhalitsyn
2023-06-23 12:24     ` Christian Brauner
2023-06-23 12:28       ` Alexander Mikhalitsyn
2023-06-23 15:09         ` Jakub Kicinski
2023-06-26 22:09           ` Alexander Mikhalitsyn
     [not found] <PH0PR11MB5126F2B2E020774AF8D91299D35BA@PH0PR11MB5126.namprd11.prod.outlook.com>
2023-06-15 23:27 ` Stephen Rothwell
2023-06-13  3:02 Stephen Rothwell
2023-06-15 22:32 ` Stephen Rothwell
2023-07-06 23:41   ` Stephen Rothwell
2021-12-07  0:26 Stephen Rothwell
2021-12-06  0:37 Stephen Rothwell
2021-09-27  0:16 Stephen Rothwell
     [not found] <PH0PR11MB5126EFEDB65650EFC3368981D3749@PH0PR11MB5126.namprd11.prod.outlook.com>
2021-04-08  4:57 ` Stephen Rothwell
2021-04-08  3:59 Stephen Rothwell
2020-07-27  3:44 Stephen Rothwell
2020-07-27  5:22 ` Christoph Hellwig
2020-07-27 13:28   ` Alain Michaud
2019-10-18  0:13 Stephen Rothwell
2015-09-14  0:14 Stephen Rothwell
2015-09-14  0:22 ` Stephen Rothwell
2015-09-22  1:20   ` Stephen Rothwell
2015-09-22  3:42     ` David Miller
2015-08-12  8:01 Stephen Rothwell
2014-10-27  2:19 Stephen Rothwell
2014-10-28 14:49 ` Johan Hedberg
2012-09-19  1:45 Stephen Rothwell
2012-02-22  1:21 Stephen Rothwell
2012-02-22  1:29 ` David Miller
2011-12-21  2:19 Stephen Rothwell
2011-02-15  2:16 Stephen Rothwell
2011-02-15 12:48 ` Gustavo F. Padovan

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=20110428114118.dd5a74e0.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=padovan@profusion.mobi \
    /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;
as well as URLs for NNTP newsgroup(s).