From: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
To: santosh prasad nayak <santoshprasadnayak@gmail.com>
Cc: marcel@holtmann.org, padovan@profusion.mobi, davem@davemloft.net,
linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: Silence static checker warning.
Date: Thu, 01 Mar 2012 07:43:56 +0000 [thread overview]
Message-ID: <20120301074354.GA25627@aemeltch-MOBL1> (raw)
In-Reply-To: <CAOD=uF5Ux0w=EPbX0V3qOy1VnZQr6Q35uUxrF9Qv1hZ4MjYJOA@mail.gmail.com>
Hi Santosh,
On Thu, Mar 01, 2012 at 11:07:14AM +0530, santosh prasad nayak wrote:
> @Dan,
> In future patches I will take care of it. Is it ok ? If
> required I can resend the patch with required changes on subject line.
>
> @Andrei
>
> In my local clone your changes are not visible.
>
> What is the schedule of linux-next ?
> Is it updated every week or bi-weekly or monthly ?
We use Johan's tree so far:
git://git.kernel.org/pub/scm/linux/kernel/git/jh/bluetooth-next.git
I think the tree we use shall be published on bluez.org website.
The change seems to be included to:
"pull request: bluetooth-next 2012-02-24"
http://www.spinics.net/lists/linux-wireless/msg85442.html
Best regards
Andrei Emeltchenko
next prev parent reply other threads:[~2012-03-01 7:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 17:18 [PATCH] Bluetooth: Silence static checker warning santosh nayak
2012-02-29 17:39 ` Marcel Holtmann
2012-02-29 17:46 ` Marcel Holtmann
2012-02-29 19:16 ` Dan Carpenter
2012-02-29 20:45 ` Andrei Emeltchenko
2012-03-01 5:49 ` santosh prasad nayak
2012-03-01 6:25 ` Dan Carpenter
2012-03-01 7:43 ` Andrei Emeltchenko [this message]
2012-03-02 9:15 ` David Laight
2012-03-02 11:04 ` Dan Carpenter
2012-03-02 17:57 ` Marcel Holtmann
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=20120301074354.GA25627@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=davem@davemloft.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=netdev@vger.kernel.org \
--cc=padovan@profusion.mobi \
--cc=santoshprasadnayak@gmail.com \
/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