All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Martin Wetterwald <martin@wetterwald.eu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: linux-next: Tree for May 15 (net/ipv4/ipconfig.c:)
Date: Wed, 17 May 2023 21:57:05 -0600	[thread overview]
Message-ID: <72b07d00-53f1-9da3-1663-24282f192d75@kernel.org> (raw)
In-Reply-To: <81d74a8e-6bfb-5ed6-9851-faf120a6e9f8@infradead.org>

On 5/15/23 8:23 PM, Randy Dunlap wrote:
> 
> 
> On 5/14/23 21:12, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20230512:
> 
> ../net/ipv4/ipconfig.c:177:12: warning: 'ic_nameservers_fallback' defined but not used [-Wunused-variable]
>   177 | static int ic_nameservers_fallback __initdata;
>       |            ^~~~~~~~~~~~~~~~~~~~~~~
> 

Martin: please send a followup. Most likely it needs to be moved under a
config option.

  reply	other threads:[~2023-05-18  3:57 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15  4:12 linux-next: Tree for May 15 Stephen Rothwell
2023-05-16  2:18 ` linux-next: Tree for May 15 (drivers/dma/ti/k3-udma.c) Randy Dunlap
2023-05-16 17:35   ` Vinod Koul
2023-05-16  2:23 ` linux-next: Tree for May 15 (net/ipv4/ipconfig.c:) Randy Dunlap
2023-05-18  3:57   ` David Ahern [this message]
2023-05-16  2:26 ` linux-next: Tree for May 15 (drivers/macintosh/ams/ams-core.c) Randy Dunlap
2023-05-16  2:26   ` Randy Dunlap
2023-05-16  2:40 ` linux-next: Tree for May 15 (drivers/tty/serial/8250/8250_omap.c) Randy Dunlap
2023-05-17  5:51   ` Tony Lindgren
2023-05-16  2:45 ` linux-next: Tree for May 15 (several RV64 build errors) Randy Dunlap
2023-05-16  2:45   ` Randy Dunlap
2023-05-16  6:18   ` Alexandre Ghiti
2023-05-16  6:18     ` Alexandre Ghiti
2023-05-19 10:42     ` Alexandre Ghiti
2023-05-19 10:42       ` Alexandre Ghiti
2023-05-19 11:22       ` Conor Dooley
2023-05-19 11:22         ` Conor Dooley
2023-05-19 12:09         ` Alexandre Ghiti
2023-05-19 12:09           ` Alexandre Ghiti
2023-05-23  2:28       ` Randy Dunlap
2023-05-23  2:28         ` Randy Dunlap
2023-05-23 13:07         ` Alexandre Ghiti
2023-05-23 13:07           ` Alexandre Ghiti
2023-05-24  0:22           ` Randy Dunlap
2023-05-24  0:22             ` Randy Dunlap
2023-05-24  1:29             ` Palmer Dabbelt
2023-05-24  1:29               ` Palmer Dabbelt
2023-05-24  6:23               ` Arnd Bergmann
2023-05-24  6:23                 ` Arnd Bergmann
2023-05-24 22:41                 ` Randy Dunlap
2023-05-24 22:41                   ` Randy Dunlap
2023-05-24 22:49                   ` Conor Dooley
2023-05-24 22:49                     ` Conor Dooley
2023-05-24 23:11                     ` Palmer Dabbelt
2023-05-24 23:11                       ` Palmer Dabbelt
2023-05-25 12:50                       ` Conor Dooley
2023-05-25 12:50                         ` Conor Dooley
2023-05-16  2:51 ` linux-next: Tree for May 15 (config SERIAL_CPM) Randy Dunlap
2023-05-18  5:49   ` Jiri Slaby
2023-05-18  5:50     ` Jiri Slaby

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=72b07d00-53f1-9da3-1663-24282f192d75@kernel.org \
    --to=dsahern@kernel.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=martin@wetterwald.eu \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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.