mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: steve@snewbury.org.uk
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ppp: Pass PPP Kconfig defines through to the CPP
Date: Tue, 1 Apr 2025 16:26:23 +0200	[thread overview]
Message-ID: <b5e6d8a2-df18-4e64-938e-39e73d1214f9@lunn.ch> (raw)
In-Reply-To: <20250331194918.385248-1-steve@snewbury.org.uk>

On Mon, Mar 31, 2025 at 08:49:16PM +0100, steve@snewbury.org.uk wrote:
> From: Steven Newbury <steve@snewbury.org.uk>
> 
> It seems for a very long time the conditional code in ppp_generic.c for PPP_MULTILINK
> and PPP_FILTER hasn't been compiled!  I do wonder whether anybody actually still uses
> these options!
> ---
>  drivers/net/ppp/Makefile | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/net/ppp/Makefile b/drivers/net/ppp/Makefile
> index 16c457d6b324..9d12915e4ac5 100644
> --- a/drivers/net/ppp/Makefile
> +++ b/drivers/net/ppp/Makefile
> @@ -12,3 +12,10 @@ obj-$(CONFIG_PPP_SYNC_TTY) += ppp_synctty.o
>  obj-$(CONFIG_PPPOE) += pppox.o pppoe.o
>  obj-$(CONFIG_PPPOL2TP) += pppox.o
>  obj-$(CONFIG_PPTP) += pppox.o pptp.o
> +
> +ifdef CONFIG_PPP_MULTILINK
> +ccflags-y += -DCONFIG_PPP_MULTILINK
> +endif
> +ifdef CONFIG_PPP_FILTER
> +ccflags-y += -DCONFIG_PPP_FILTER
> +endif

That looks very odd. I don't see many other instances for Makefiles
doing this. Please add a bigger explanation of why this is needed, and
why the usual Kconfig mechanism don't work.

    Andrew

---
pw-bot: cr

           reply	other threads:[~2025-04-01 14:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20250331194918.385248-1-steve@snewbury.org.uk>]

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=b5e6d8a2-df18-4e64-938e-39e73d1214f9@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=steve@snewbury.org.uk \
    /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

all inboxes | Powered by JetHome®