All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: add missing multicast.h include
Date: Wed, 6 Nov 2013 13:43:54 +0100	[thread overview]
Message-ID: <20131106124354.GG970@neomailbox.net> (raw)
In-Reply-To: <1383741387-9813-1-git-send-email-linus.luessing@web.de>

[-- Attachment #1: Type: text/plain, Size: 405 bytes --]

On Wed, Nov 06, 2013 at 01:36:27PM +0100, Linus Lüssing wrote:
> Not having it doesn't seem to break anything, but looks like it's
> recommended C practice.

Please,

report which commit id (and commit subject) introduced this problem (use the
Introduced-by clause). In this way I can easily squash the two patches together
before sending them upstream.


Cheers,


-- 
Antonio Quartulli

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-11-06 12:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 12:36 [B.A.T.M.A.N.] [PATCH] batman-adv: add missing multicast.h include Linus Lüssing
2013-11-06 12:43 ` Antonio Quartulli [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=20131106124354.GG970@neomailbox.net \
    --to=antonio@meshcoding.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.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 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.