From: Johan Hedberg <johan.hedberg@intel.com>
To: "michal.hobot@silvair.com" <michal.hobot@silvair.com>
Cc: "Stotland, Inga" <inga.stotland@intel.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>
Subject: Re: meshctl cannot parse its own config file
Date: Tue, 28 Nov 2017 16:09:01 +0200 [thread overview]
Message-ID: <20171128140901.GA27685@x1c.home> (raw)
In-Reply-To: <1511808337.3924.2.camel@intel.com>
Hi Michal,
On Mon, Nov 27, 2017, Stotland, Inga wrote:
> On Fri, 2017-11-24 at 22:13 +0100, Michał Hobot wrote:
> > Btw, should I post an official patch? I'm new to this group.
>
> Yes, please go ahead and submit an official patch using git send-email.
Will you be submitting git-formatted patch for this? It's one of the
last few remaining patches I'd like to get merged before we create a new
BlueZ release.
Johan
prev parent reply other threads:[~2017-11-28 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 18:19 meshctl cannot parse its own config file Michał Hobot
2017-11-21 7:25 ` Stotland, Inga
2017-11-24 21:13 ` Michał Hobot
2017-11-27 18:45 ` Stotland, Inga
2017-11-28 14:09 ` Johan Hedberg [this message]
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=20171128140901.GA27685@x1c.home \
--to=johan.hedberg@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michal.hobot@silvair.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;
as well as URLs for NNTP newsgroup(s).