All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Print correct function names in dbg messages
Date: Tue, 23 May 2017 12:12:21 +0200	[thread overview]
Message-ID: <4826270.pqO2KLcmBo@bentobox> (raw)
In-Reply-To: <20170519110200.29867-1-sven@narfation.org>

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

On Freitag, 19. Mai 2017 13:02:00 CEST Sven Eckelmann wrote:
> The function names in batman-adv changed slightly in the past. But some of
> the debug messages were not updated correctly and therefore some messages
> were incorrect. To avoid this in the future, these kind of messages should
> use __func__ to automatically print the correct function name.
> 
> Signed-off-by: Sven Eckelmann <sven@narfation.org>
> ---
>  net/batman-adv/bat_iv_ogm.c            |  3 +-
>  net/batman-adv/bridge_loop_avoidance.c | 72 +++++++++++++++++-----------------
>  net/batman-adv/distributed-arp-table.c |  2 +-
>  net/batman-adv/routing.c               |  4 +-
>  net/batman-adv/send.c                  |  6 +--
>  5 files changed, 45 insertions(+), 42 deletions(-)
> 

Patch applied as 4978390e544d496157c6836bbf15270e3039e1c3 [1]


Kind regards,
	Sven

[1] https://git.open-mesh.org/batman-adv.git/commit/4978390e544d496157c6836bbf15270e3039e1c3

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-05-23 10:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-19 11:02 [B.A.T.M.A.N.] [PATCH] batman-adv: Print correct function names in dbg messages Sven Eckelmann
2017-05-23 10:12 ` Sven Eckelmann [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=4826270.pqO2KLcmBo@bentobox \
    --to=sven@narfation.org \
    --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.