On Sat, Jul 02, 2016 at 03:48:36PM +0200, Hauke Mehrtens wrote:
> > However, I have some trouble understanding what KCONFIG does. Wireguard
> > needs a few kernel options, so I thought that KCONFIG was the place to
> > declare such dependencies:
> >
> >
> >
On 07/02/2016 03:20 PM, Baptiste Jonglez wrote:
> Hi,
>
> I am packaging a new kernel module (wireguard), the package is currently here
> [1].
>
> However, I have some trouble understanding what KCONFIG does. Wireguard
> needs a few kernel options, so I thought that KCONFIG was the place to
>
On 02/07/2016 15:20, Baptiste Jonglez wrote:
> Hi,
>
> I am packaging a new kernel module (wireguard), the package is currently here
> [1].
>
> However, I have some trouble understanding what KCONFIG does. Wireguard
> needs a few kernel options, so I thought that KCONFIG was the place to
>
On 02/07/2016 15:20, Baptiste Jonglez wrote:
> Hi,
>
> I am packaging a new kernel module (wireguard), the package is currently here
> [1].
>
> However, I have some trouble understanding what KCONFIG does. Wireguard
> needs a few kernel options, so I thought that KCONFIG was the place to
>
Hi,
I am packaging a new kernel module (wireguard), the package is currently here
[1].
However, I have some trouble understanding what KCONFIG does. Wireguard
needs a few kernel options, so I thought that KCONFIG was the place to
declare such dependencies:
