linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: ERAMOTO Masaya <eramoto.masaya@jp.fujitsu.com>,
	"linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH BlueZ] obexd: Fix compile error due to lack of header
Date: Fri, 27 Oct 2017 13:29:31 +0200	[thread overview]
Message-ID: <1509103771.19297.1.camel@hadess.net> (raw)
In-Reply-To: <1158c872-8eb3-b710-5013-fa04bfebd745@jp.fujitsu.com>

On Fri, 2017-10-27 at 16:55 +0900, ERAMOTO Masaya wrote:
> Hi Bastien,
> 
> On 10/26/2017 09:39 PM, Bastien Nocera wrote:
> > On Thu, 2017-10-26 at 15:05 +0900, ERAMOTO Masaya wrote:
> > > When compiling with gcc 7.2.0, gcc outputs the following
> > > messages.
> > > This patch adds the header stdlib.h to each obex-related header
> > > including
> > > functions with the type ssize_t, so the same problem does not
> > > also
> > > happen
> > > in case using there headers individually.
> > 
> > I already sent a patch for this about 2 months ago, look for
> > "obexd:
> > Fix compilation error on F27"
> 
> Sorry for I had missed this patch.
> 
> Now, it seems that you are blocking the patch set including this
> patch
> due to that Florian commented about one of the patch set.

I'm not blocking anything, it didn't get reviewed at all.

>  Is there any
> upgrades for the patch set?

The patch set is just a bunch of unrelated fixes, the patches can be
committed individually.

I think one of us needs to figure out what the change is to put the
justification in the commit message before that's going to be accepted
though.

      reply	other threads:[~2017-10-27 11:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26  6:05 [PATCH BlueZ] obexd: Fix compile error due to lack of header ERAMOTO Masaya
2017-10-26 12:05 ` Luiz Augusto von Dentz
2017-10-27  7:21   ` ERAMOTO Masaya
2017-11-02 14:13   ` Bastien Nocera
2017-10-26 12:39 ` Bastien Nocera
2017-10-27  7:55   ` ERAMOTO Masaya
2017-10-27 11:29     ` Bastien Nocera [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=1509103771.19297.1.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=eramoto.masaya@jp.fujitsu.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;
as well as URLs for NNTP newsgroup(s).