From: David Miller <davem@davemloft.net>
To: a.beregalov@gmail.com
Cc: marcel@holtmann.org, linux-bluetooth@vger.kernel.org,
mingo@elte.hu, linux-next@vger.kernel.org
Subject: Re: [PATCH] rfcomm/sock: fix build problem
Date: Tue, 09 Dec 2008 04:44:24 -0800 (PST) [thread overview]
Message-ID: <20081209.044424.134557406.davem@davemloft.net> (raw)
In-Reply-To: <20081209123950.GA31294@orion>
From: Alexander Beregalov <a.beregalov@gmail.com>
Date: Tue, 9 Dec 2008 15:39:50 +0300
> net/bluetooth/rfcomm/sock.c: In function 'rfcomm_sock_ioctl':
> net/bluetooth/rfcomm/sock.c:795: error: 'sk' undeclared (first use in this function)
> net/bluetooth/rfcomm/sock.c:795: error: (Each undeclared identifier is reported only once
> net/bluetooth/rfcomm/sock.c:795: error: for each function it appears in.)
>
> It is a conflict between a418b893
> (Bluetooth: Enable per-module dynamic debug messages)
> and 45555c0e
> (bluetooth: fix warning in net/bluetooth/rfcomm/sock.c)
>
> Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
Already fixed in net-next-2.6.
BTW, your patch reintroduces a warning.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org,
linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
mingo-X9Un+BFzKDI@public.gmane.org,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] rfcomm/sock: fix build problem
Date: Tue, 09 Dec 2008 04:44:24 -0800 (PST) [thread overview]
Message-ID: <20081209.044424.134557406.davem@davemloft.net> (raw)
In-Reply-To: <20081209123950.GA31294@orion>
From: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date: Tue, 9 Dec 2008 15:39:50 +0300
> net/bluetooth/rfcomm/sock.c: In function 'rfcomm_sock_ioctl':
> net/bluetooth/rfcomm/sock.c:795: error: 'sk' undeclared (first use in this function)
> net/bluetooth/rfcomm/sock.c:795: error: (Each undeclared identifier is reported only once
> net/bluetooth/rfcomm/sock.c:795: error: for each function it appears in.)
>
> It is a conflict between a418b893
> (Bluetooth: Enable per-module dynamic debug messages)
> and 45555c0e
> (bluetooth: fix warning in net/bluetooth/rfcomm/sock.c)
>
> Signed-off-by: Alexander Beregalov <a.beregalov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Already fixed in net-next-2.6.
BTW, your patch reintroduces a warning.
next prev parent reply other threads:[~2008-12-09 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 12:39 [PATCH] rfcomm/sock: fix build problem Alexander Beregalov
2008-12-09 12:39 ` Alexander Beregalov
2008-12-09 12:44 ` David Miller [this message]
2008-12-09 12:44 ` David Miller
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=20081209.044424.134557406.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.beregalov@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mingo@elte.hu \
/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.