Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
* linux-next: build warning after merge of the gpio tree
@ 2019-11-05  6:43 Stephen Rothwell
  2019-11-07  8:35 ` Linus Walleij
  0 siblings, 1 reply; 17+ messages in thread
From: Stephen Rothwell @ 2019-11-05  6:43 UTC (permalink / raw)
  To: Linus Walleij
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Chris Packham

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

Hi all,

After merging the gpio tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

WARNING: vmlinux.o(.data+0xbd3f4): Section mismatch in reference from the variable bcm_iproc_gpio_driver to the (unknown reference) .init.rodata:(unknown)
The variable bcm_iproc_gpio_driver references
the (unknown reference) __initconst (unknown)
If the reference is valid then annotate the
variable with __init* or __refdata (see linux/init.h) or name the variable:
*_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console

(and similar for x86_64 allmodconfig)

Introduced by commit

  6a41b6c5fc20 ("gpio: Add xgs-iproc driver")



-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: linux-next: build warning after merge of the gpio tree
  2019-11-05  6:43 linux-next: build warning after merge of the gpio tree Stephen Rothwell
@ 2019-11-07  8:35 ` Linus Walleij
  0 siblings, 0 replies; 17+ messages in thread
From: Linus Walleij @ 2019-11-07  8:35 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Chris Packham

On Tue, Nov 5, 2019 at 7:44 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> After merging the gpio tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> WARNING: vmlinux.o(.data+0xbd3f4): Section mismatch in reference from the variable bcm_iproc_gpio_driver to the (unknown reference) .init.rodata:(unknown)
> The variable bcm_iproc_gpio_driver references
> the (unknown reference) __initconst (unknown)
> If the reference is valid then annotate the
> variable with __init* or __refdata (see linux/init.h) or name the variable:
> *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console
>
> (and similar for x86_64 allmodconfig)
>
> Introduced by commit
>
>   6a41b6c5fc20 ("gpio: Add xgs-iproc driver")

Mark Brown finally hunted this down and fixed. It should be
fine in my for-next branch now.

Yours,
Linus Walleij

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: linux-next: build warning after merge of the gpio tree
  2019-06-27  8:19 Stephen Rothwell
@ 2019-06-27 14:57 ` Linus Walleij
  0 siblings, 0 replies; 17+ messages in thread
From: Linus Walleij @ 2019-06-27 14:57 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Enrico Weigelt

On Thu, Jun 27, 2019 at 9:20 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> After merging the gpio tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> drivers/gpio/gpio-amd-fch.c: In function 'amd_fch_gpio_probe':
> drivers/gpio/gpio-amd-fch.c:171:49: warning: passing argument 2 of 'devm_ioremap_resource' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
>   priv->base = devm_ioremap_resource(&pdev->dev, &amd_fch_gpio_iores);
>                                                  ^~~~~~~~~~~~~~~~~~~
> In file included from include/linux/platform_device.h:13,
>                  from drivers/gpio/gpio-amd-fch.c:15:
> include/linux/device.h:708:15: note: expected 'struct resource *' but argument is of type 'const struct resource *'
>  void __iomem *devm_ioremap_resource(struct device *dev, struct resource *res);
>                ^~~~~~~~~~~~~~~~~~~~~
>
> Introduced by commit
>
>   9bb2e0452508 ("gpio: amd: Make resource struct const")

OK I dropped this commit until Enrico get some time to figure out
what's going wrong here.

Yours,
Linus Walleij

^ permalink raw reply	[flat|nested] 17+ messages in thread

* linux-next: build warning after merge of the gpio tree
@ 2019-06-27  8:19 Stephen Rothwell
  2019-06-27 14:57 ` Linus Walleij
  0 siblings, 1 reply; 17+ messages in thread
From: Stephen Rothwell @ 2019-06-27  8:19 UTC (permalink / raw)
  To: Linus Walleij
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Enrico Weigelt

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

Hi all,

After merging the gpio tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

drivers/gpio/gpio-amd-fch.c: In function 'amd_fch_gpio_probe':
drivers/gpio/gpio-amd-fch.c:171:49: warning: passing argument 2 of 'devm_ioremap_resource' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
  priv->base = devm_ioremap_resource(&pdev->dev, &amd_fch_gpio_iores);
                                                 ^~~~~~~~~~~~~~~~~~~
In file included from include/linux/platform_device.h:13,
                 from drivers/gpio/gpio-amd-fch.c:15:
include/linux/device.h:708:15: note: expected 'struct resource *' but argument is of type 'const struct resource *'
 void __iomem *devm_ioremap_resource(struct device *dev, struct resource *res);
               ^~~~~~~~~~~~~~~~~~~~~

Introduced by commit

  9bb2e0452508 ("gpio: amd: Make resource struct const")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 17+ messages in thread

* linux-next: build warning after merge of the gpio tree
@ 2019-02-25  4:52 Stephen Rothwell
  0 siblings, 0 replies; 17+ messages in thread
From: Stephen Rothwell @ 2019-02-25  4:52 UTC (permalink / raw)
  To: Linus Walleij
  Cc: Linux Next Mailing List, Linux Kernel Mailing List,
	Enrico Weigelt, metux IT consult

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

Hi Linus,

After merging the gpio tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

drivers/gpio/gpio-amd-fch.c: In function 'amd_fch_gpio_probe':
drivers/gpio/gpio-amd-fch.c:164:49: warning: passing argument 2 of 'devm_ioremap_resource' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
  priv->base = devm_ioremap_resource(&pdev->dev, &amd_fch_gpio_iores);
                                                 ^~~~~~~~~~~~~~~~~~~
In file included from include/linux/platform_device.h:14,
                 from drivers/gpio/gpio-amd-fch.c:15:
include/linux/device.h:709:15: note: expected 'struct resource *' but argument is of type 'const struct resource *'
 void __iomem *devm_ioremap_resource(struct device *dev, struct resource *res);
               ^~~~~~~~~~~~~~~~~~~~~

Introduced by commit

  e09d168f13f0 ("gpio: AMD G-Series PCH gpio driver")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 17+ messages in thread

* linux-next: build warning after merge of the gpio tree
@ 2018-12-18  5:41 Stephen Rothwell
  0 siblings, 0 replies; 17+ messages in thread
From: Stephen Rothwell @ 2018-12-18  5:41 UTC (permalink / raw)
  To: Linus Walleij; +Cc: Linux Next Mailing List, Linux Kernel Mailing List

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

Hi Linus,

After merging the gpio tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

drivers/gpio/gpiolib-acpi.c: In function 'acpi_gpio_adr_space_handler':
drivers/gpio/gpiolib-acpi.c:911:8: warning: unused variable 'err' [-Wunused-variable]
    int err;
        ^~~

Introduced by commit

  21abf103818a ("gpio: Pass a flag to gpiochip_request_own_desc()")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: linux-next: build warning after merge of the gpio tree
  2018-11-06  1:15 Stephen Rothwell
@ 2018-11-06  7:24 ` Uwe Kleine-König
  0 siblings, 0 replies; 17+ messages in thread
From: Uwe Kleine-König @ 2018-11-06  7:24 UTC (permalink / raw)
  To: Linus Walleij
  Cc: Stephen Rothwell, Linux-Next Mailing List,
	Linux Kernel Mailing List, linux-gpio, kernel

Hi Linus,

On Tue, Nov 06, 2018 at 12:15:02PM +1100, Stephen Rothwell wrote:
> After merging the gpio tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> drivers/gpio/gpiolib.c:1514:12: warning: 'devm_gpio_chip_match' defined but not used [-Wunused-function]
>  static int devm_gpio_chip_match(struct device *dev, void *res, void *data)
>             ^~~~~~~~~~~~~~~~~~~~
> 
> Caused by commit
> 
>   48207d7595d2 ("gpio: drop devm_gpiochip_remove()")

I noticed this, too, but didn't tell immediately because I thought I'd
have to resent this patch and then forgot as you applied yourself.

Sorry for that, the obvious resolution is to drop
devm_gpio_chip_match(). Feel free to squash that into 48207d7595d2. If
your branch is already stable I can provide a patch for that.

Thanks
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

^ permalink raw reply	[flat|nested] 17+ messages in thread

* linux-next: build warning after merge of the gpio tree
@ 2018-11-06  1:15 Stephen Rothwell
  2018-11-06  7:24 ` Uwe Kleine-König
  0 siblings, 1 reply; 17+ messages in thread
From: Stephen Rothwell @ 2018-11-06  1:15 UTC (permalink / raw)
  To: Linus Walleij
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List,
	Uwe Kleine-König

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

Hi Linus,

After merging the gpio tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

drivers/gpio/gpiolib.c:1514:12: warning: 'devm_gpio_chip_match' defined but not used [-Wunused-function]
 static int devm_gpio_chip_match(struct device *dev, void *res, void *data)
            ^~~~~~~~~~~~~~~~~~~~

Caused by commit

  48207d7595d2 ("gpio: drop devm_gpiochip_remove()")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: linux-next: build warning after merge of the gpio tree
  2018-01-11  4:06 Stephen Rothwell
@ 2018-01-11  9:19 ` Linus Walleij
  0 siblings, 0 replies; 17+ messages in thread
From: Linus Walleij @ 2018-01-11  9:19 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Maciej S. Szmigiero

On Thu, Jan 11, 2018 at 5:06 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Linus,
>
> After merging the gpio tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> drivers/gpio/Kconfig:13:error: recursive dependency detected!
> drivers/gpio/Kconfig:13:        symbol GPIOLIB is selected by STX104
> drivers/iio/adc/Kconfig:699:    symbol STX104 depends on ISA_BUS_API
> arch/Kconfig:821:       symbol ISA_BUS_API is selected by GPIO_WINBOND
> drivers/gpio/Kconfig:701:       symbol GPIO_WINBOND depends on GPIOLIB
> For a resolution refer to Documentation/kbuild/kconfig-language.txt
> subsection "Kconfig recursive dependency limitations"
>
> Presumably introduced by commit
>
>   a0d65009411c ("gpio: winbond: Add driver")

Thanks, Arnd already patched it up quickly!

Yours,
Linus Walleij

^ permalink raw reply	[flat|nested] 17+ messages in thread

* linux-next: build warning after merge of the gpio tree
@ 2018-01-11  4:06 Stephen Rothwell
  2018-01-11  9:19 ` Linus Walleij
  0 siblings, 1 reply; 17+ messages in thread
From: Stephen Rothwell @ 2018-01-11  4:06 UTC (permalink / raw)
  To: Linus Walleij
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Maciej S. Szmigiero

Hi Linus,

After merging the gpio tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

drivers/gpio/Kconfig:13:error: recursive dependency detected!
drivers/gpio/Kconfig:13:	symbol GPIOLIB is selected by STX104
drivers/iio/adc/Kconfig:699:	symbol STX104 depends on ISA_BUS_API
arch/Kconfig:821:	symbol ISA_BUS_API is selected by GPIO_WINBOND
drivers/gpio/Kconfig:701:	symbol GPIO_WINBOND depends on GPIOLIB
For a resolution refer to Documentation/kbuild/kconfig-language.txt
subsection "Kconfig recursive dependency limitations"

Presumably introduced by commit

  a0d65009411c ("gpio: winbond: Add driver")

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 17+ messages in thread

* linux-next: build warning after merge of the gpio tree
@ 2017-05-30  3:52 Stephen Rothwell
  0 siblings, 0 replies; 17+ messages in thread
From: Stephen Rothwell @ 2017-05-30  3:52 UTC (permalink / raw)
  To: Linus Walleij
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Andy Shevchenko

Hi Linus,

After merging the gpio tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

drivers/gpio/gpiolib.c: In function 'gpiochip_irqchip_init_valid_mask':
drivers/gpio/gpiolib.c:1474:6: warning: unused variable 'i' [-Wunused-variable]
  int i;
      ^

Introduced by commit

  923a654c186c ("gpiolib: Re-use bitmap_fill() instead of open coded loop")

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 17+ messages in thread

* linux-next: build warning after merge of the gpio tree
@ 2016-11-14  5:31 Stephen Rothwell
  0 siblings, 0 replies; 17+ messages in thread
From: Stephen Rothwell @ 2016-11-14  5:31 UTC (permalink / raw)
  To: Linus Walleij; +Cc: linux-next, linux-kernel

Hi Linus,

After merging the gpio tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

drivers/gpio/gpiolib-acpi.c: In function 'acpi_gpiochip_add':
drivers/gpio/gpiolib-acpi.c:925:9: warning: 'lflags' may be used uninitialized in this function [-Wmaybe-uninitialized]
   ret = gpiod_hog(desc, name, lflags, dflags);
         ^
drivers/gpio/gpiolib-acpi.c:912:16: note: 'lflags' was declared here
   unsigned int lflags, dflags;
                ^
drivers/gpio/gpiolib-acpi.c:925:7: warning: 'dflags' may be used uninitialized in this function [-Wmaybe-uninitialized]
   ret = gpiod_hog(desc, name, lflags, dflags);
       ^
drivers/gpio/gpiolib-acpi.c:912:24: note: 'dflags' was declared here
   unsigned int lflags, dflags;
                        ^

These presumably have appeared since -Wmaybe-uninitialized has been
reenabled in Linus Torvald's tree.

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 17+ messages in thread

* linux-next: build warning after merge of the gpio tree
@ 2016-09-13  3:18 Stephen Rothwell
  0 siblings, 0 replies; 17+ messages in thread
From: Stephen Rothwell @ 2016-09-13  3:18 UTC (permalink / raw)
  To: Linus Walleij
  Cc: linux-next, linux-kernel, Joel Stanley, Alistair Popple,
	Jeremy Kerr, Andrew Jeffery

Hi Linus,

After merging the gpio tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

WARNING: modpost: missing MODULE_LICENSE() in drivers/gpio/gpio-aspeed.o

Introduced by commit

  361b79119a4b ("gpio: Add Aspeed driver")

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: linux-next: build warning after merge of the gpio tree
  2016-06-16  4:32 Stephen Rothwell
@ 2016-06-16 10:02 ` Linus Walleij
  0 siblings, 0 replies; 17+ messages in thread
From: Linus Walleij @ 2016-06-16 10:02 UTC (permalink / raw)
  To: Stephen Rothwell, Arnd Bergmann; +Cc: linux-next, linux-kernel

On Thu, Jun 16, 2016 at 6:32 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> After merging the gpio tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from drivers/gpio/gpiolib.c:25:0:
> drivers/gpio/gpiolib.c: In function 'lineevent_irq_thread':
> include/linux/kfifo.h:403:39: warning: 'ge.id' may be used uninitialized in this function [-Wmaybe-uninitialized]
>     )[__kfifo->in & __tmp->kfifo.mask] = \
>                                        ^
> drivers/gpio/gpiolib.c:657:24: note: 'ge.id' was declared here
>   struct gpioevent_data ge;
>                         ^
>
> Introduced by commit
>
>   61f922db7221 ("gpio: userspace ABI for reading GPIO line events")
>
> This is in the kfifo_put() call.

Thanks Stephen, Arnd has already helpfully made a patch to fix it :)

Yours,
Linus Walleij

^ permalink raw reply	[flat|nested] 17+ messages in thread

* linux-next: build warning after merge of the gpio tree
@ 2016-06-16  4:32 Stephen Rothwell
  2016-06-16 10:02 ` Linus Walleij
  0 siblings, 1 reply; 17+ messages in thread
From: Stephen Rothwell @ 2016-06-16  4:32 UTC (permalink / raw)
  To: Linus Walleij; +Cc: linux-next, linux-kernel

Hi Linus,

After merging the gpio tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

In file included from drivers/gpio/gpiolib.c:25:0:
drivers/gpio/gpiolib.c: In function 'lineevent_irq_thread':
include/linux/kfifo.h:403:39: warning: 'ge.id' may be used uninitialized in this function [-Wmaybe-uninitialized]
    )[__kfifo->in & __tmp->kfifo.mask] = \
                                       ^
drivers/gpio/gpiolib.c:657:24: note: 'ge.id' was declared here
  struct gpioevent_data ge;
                        ^

Introduced by commit

  61f922db7221 ("gpio: userspace ABI for reading GPIO line events")

This is in the kfifo_put() call.

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 17+ messages in thread

* Re: linux-next: build warning after merge of the gpio tree
  2014-03-07  3:59 Stephen Rothwell
@ 2014-03-07  6:16 ` Linus Walleij
  0 siblings, 0 replies; 17+ messages in thread
From: Linus Walleij @ 2014-03-07  6:16 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, linux-kernel, Jamie Iles, Alan Tull

On Fri, Mar 7, 2014 at 11:59 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi Linus,
>
> After merging the gpio tree, today's (and yesterday's) linux-next build
> (x86_64 allmodconfig among others) produced this warning:
>
> kernel/irq/Kconfig:41:error: recursive dependency detected!
> kernel/irq/Kconfig:41:  symbol GENERIC_IRQ_CHIP is selected by GPIO_DWAPB
> drivers/gpio/Kconfig:131:       symbol GPIO_DWAPB depends on IRQ_DOMAIN
> kernel/irq/Kconfig:46:  symbol IRQ_DOMAIN is selected by GENERIC_IRQ_CHIP
>
> Caused by commit 7779b3455697 ("gpio: add a driver for the Synopsys
> DesignWare APB GPIO block").

Thanks Stephen, I merged a patch from Alan Tull earlier today fixing this
problem.

Yours,
Linus Walleij

^ permalink raw reply	[flat|nested] 17+ messages in thread

* linux-next: build warning after merge of the gpio tree
@ 2014-03-07  3:59 Stephen Rothwell
  2014-03-07  6:16 ` Linus Walleij
  0 siblings, 1 reply; 17+ messages in thread
From: Stephen Rothwell @ 2014-03-07  3:59 UTC (permalink / raw)
  To: Linus Walleij; +Cc: linux-next, linux-kernel, Jamie Iles, Alan Tull

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

Hi Linus,

After merging the gpio tree, today's (and yesterday's) linux-next build
(x86_64 allmodconfig among others) produced this warning:

kernel/irq/Kconfig:41:error: recursive dependency detected!
kernel/irq/Kconfig:41:	symbol GENERIC_IRQ_CHIP is selected by GPIO_DWAPB
drivers/gpio/Kconfig:131:	symbol GPIO_DWAPB depends on IRQ_DOMAIN
kernel/irq/Kconfig:46:	symbol IRQ_DOMAIN is selected by GENERIC_IRQ_CHIP

Caused by commit 7779b3455697 ("gpio: add a driver for the Synopsys
DesignWare APB GPIO block").

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

^ permalink raw reply	[flat|nested] 17+ messages in thread

end of thread, back to index

Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-05  6:43 linux-next: build warning after merge of the gpio tree Stephen Rothwell
2019-11-07  8:35 ` Linus Walleij
  -- strict thread matches above, loose matches on Subject: below --
2019-06-27  8:19 Stephen Rothwell
2019-06-27 14:57 ` Linus Walleij
2019-02-25  4:52 Stephen Rothwell
2018-12-18  5:41 Stephen Rothwell
2018-11-06  1:15 Stephen Rothwell
2018-11-06  7:24 ` Uwe Kleine-König
2018-01-11  4:06 Stephen Rothwell
2018-01-11  9:19 ` Linus Walleij
2017-05-30  3:52 Stephen Rothwell
2016-11-14  5:31 Stephen Rothwell
2016-09-13  3:18 Stephen Rothwell
2016-06-16  4:32 Stephen Rothwell
2016-06-16 10:02 ` Linus Walleij
2014-03-07  3:59 Stephen Rothwell
2014-03-07  6:16 ` Linus Walleij

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git