From: Johan Hedberg <johan.hedberg@gmail.com>
To: Hemant Gupta <hemantgupta.ste@gmail.com>
Cc: Hemant Gupta <hemant.gupta@stericsson.com>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] mgmtops: Handle Start Discovery Complete in case of failure
Date: Tue, 10 Apr 2012 13:04:56 +0300 [thread overview]
Message-ID: <20120410100456.GA7832@x220> (raw)
In-Reply-To: <CACj007=DC4gon83DoNTLn-X8gG+ehojwY7E-bVP3YxMkLvhFKA@mail.gmail.com>
Hi Hemant,
On Tue, Apr 10, 2012, Hemant Gupta wrote:
> Sorry, but I thought we need to allign to the opening brace.
That's for the kernel. We haven't changed the expected coding style for
user space.
Johan
next prev parent reply other threads:[~2012-04-10 10:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 7:07 [PATCH] mgmtops: Handle Start Discovery Complete in case of failure Hemant Gupta
2012-04-10 9:13 ` Johan Hedberg
2012-04-10 9:58 ` Hemant Gupta
2012-04-10 10:04 ` Johan Hedberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-09 5:47 Hemant Gupta
2012-04-09 7:05 ` Marcel Holtmann
2012-04-09 7:08 ` Hemant Gupta
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=20120410100456.GA7832@x220 \
--to=johan.hedberg@gmail.com \
--cc=hemant.gupta@stericsson.com \
--cc=hemantgupta.ste@gmail.com \
--cc=linux-bluetooth@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox