public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
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.] [PATCHv3 3/3] batman-adv: use static inline functions to fake not compiled-in routines
Date: Fri, 13 Apr 2012 23:04:23 +0200	[thread overview]
Message-ID: <201204132304.23485.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1334214449-3996-4-git-send-email-ordex@autistici.org>

On Thursday, April 12, 2012 09:07:29 Antonio Quartulli wrote:
> In case of not compiled-in components, we need to fake some functions in
> order to let the rest of the code correctly build. But instead of using
> something like:
> 
> We have to use:
> 
> static inline bla_init(struct bat_priv *bat_priv)
> {
>         return 1;
> }
> 
> In this way the compiler can correctly check the type and the number of the
> arguments passed to the function, even if the related component (bla in
> this case) is not compiled.

The same needs to be done for DAT, right ?

Regards,
Marek

  parent reply	other threads:[~2012-04-13 21:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12  7:07 [B.A.T.M.A.N.] [PATCHv2 0/3] clean up patches Antonio Quartulli
2012-04-12  7:07 ` [B.A.T.M.A.N.] [PATCHv2 1/3] batman-adv: fix comments ending style Antonio Quartulli
2012-04-13 20:32   ` Marek Lindner
2012-04-12  7:07 ` [B.A.T.M.A.N.] [PATCHv2 2/3] batman-adv: use static const for STP constant address Antonio Quartulli
2012-04-13 20:33   ` Marek Lindner
2012-04-12  7:07 ` [B.A.T.M.A.N.] [PATCHv3 3/3] batman-adv: use static inline functions to fake not compiled-in routines Antonio Quartulli
2012-04-13 20:35   ` Marek Lindner
2012-04-13 21:04   ` Marek Lindner [this message]
2012-04-13 22:13     ` Antonio Quartulli

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=201204132304.23485.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox