All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <horms@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH RFC net 0/2] MAINTAINERS: Networking file coverage updates
Date: Fri, 4 Oct 2024 15:42:06 -0700	[thread overview]
Message-ID: <20241004154206.543718f5@kernel.org> (raw)
In-Reply-To: <20241004-maint-net-hdrs-v1-0-41fd555aacc5@kernel.org>

On Fri, 04 Oct 2024 11:03:20 +0100 Simon Horman wrote:
> 2. Excluding some files relating to Wireless from NETWORKING [GENERAL],
>    making their handling consistent with other files related to
>    Wireless.

LGTM, FWIW, on the wireless side I generally add stuff which seems like
it causing people to mis-post. But no objections to listing more files
either way.

      parent reply	other threads:[~2024-10-04 22:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 10:03 [PATCH RFC net 0/2] MAINTAINERS: Networking file coverage updates Simon Horman
2024-10-04 10:03 ` [PATCH RFC net 1/2] MAINTAINERS: consistently exclude wireless files from NETWORKING [GENERAL] Simon Horman
2024-10-04 14:32   ` Johannes Berg
2024-10-04 15:27   ` Kalle Valo
2024-10-07 14:13     ` Simon Horman
2024-10-07 17:30       ` Johannes Berg
2024-10-07 17:41       ` Kalle Valo
2024-10-07 18:03         ` Johannes Berg
2024-10-09  8:43           ` Simon Horman
2024-10-04 10:03 ` [PATCH RFC net 2/2] MAINTAINERS: Add headers and mailing list to UDP section Simon Horman
2024-10-04 15:25   ` Willem de Bruijn
2024-10-04 22:42 ` Jakub Kicinski [this message]

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=20241004154206.543718f5@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemdebruijn.kernel@gmail.com \
    /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.