All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Szycik <marcin.szycik@linux.intel.com>
To: Jakub Kicinski <kuba@kernel.org>,
	Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: jiri@resnulli.us, wojciech.drewek@intel.com, idosch@nvidia.com,
	jesse.brandeburg@intel.com, Eric Dumazet <edumazet@google.com>,
	netdev@vger.kernel.org, Tony Nguyen <anthony.l.nguyen@intel.com>,
	intel-wired-lan@lists.osuosl.org,
	michal.swiatkowski@linux.intel.com, pabeni@redhat.com,
	davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v4 0/7] Add PFCP filter support
Date: Mon, 18 Dec 2023 11:04:01 +0100	[thread overview]
Message-ID: <ff8cfb1e-8a03-4a82-a651-3424bf9787a6@linux.intel.com> (raw)
In-Reply-To: <20231215084924.40b47a7e@kernel.org>



On 15.12.2023 17:49, Jakub Kicinski wrote:
> On Fri, 15 Dec 2023 11:11:23 +0100 Alexander Lobakin wrote:
>> Ping? :s
>> Or should we resubmit?
> 
> Can you wait for next merge window instead?
> We're getting flooded with patches as everyone seemingly tries to get
> their own (i.e. the most important!) work merged before the end of 
> the year. The set of PRs from the bitmap tree which Linus decided
> not to pull is not empty. So we'd have to go figure out what's exactly
> is in that branch we're supposed to pull, and whether it's fine.
> It probably is, but you see, this is a problem which can be solved by
> waiting, and letting Linus pull it himself. While the 150 patches we're
> getting a day now have to be looked at.

Let's wait to the next window then.

Thanks,
Marcin
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

WARNING: multiple messages have this Message-ID (diff)
From: Marcin Szycik <marcin.szycik@linux.intel.com>
To: Jakub Kicinski <kuba@kernel.org>,
	Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: davem@davemloft.net, Eric Dumazet <edumazet@google.com>,
	pabeni@redhat.com, Tony Nguyen <anthony.l.nguyen@intel.com>,
	michal.swiatkowski@linux.intel.com, wojciech.drewek@intel.com,
	idosch@nvidia.com, jesse.brandeburg@intel.com,
	intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	jiri@resnulli.us
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v4 0/7] Add PFCP filter support
Date: Mon, 18 Dec 2023 11:04:01 +0100	[thread overview]
Message-ID: <ff8cfb1e-8a03-4a82-a651-3424bf9787a6@linux.intel.com> (raw)
In-Reply-To: <20231215084924.40b47a7e@kernel.org>



On 15.12.2023 17:49, Jakub Kicinski wrote:
> On Fri, 15 Dec 2023 11:11:23 +0100 Alexander Lobakin wrote:
>> Ping? :s
>> Or should we resubmit?
> 
> Can you wait for next merge window instead?
> We're getting flooded with patches as everyone seemingly tries to get
> their own (i.e. the most important!) work merged before the end of 
> the year. The set of PRs from the bitmap tree which Linus decided
> not to pull is not empty. So we'd have to go figure out what's exactly
> is in that branch we're supposed to pull, and whether it's fine.
> It probably is, but you see, this is a problem which can be solved by
> waiting, and letting Linus pull it himself. While the 150 patches we're
> getting a day now have to be looked at.

Let's wait to the next window then.

Thanks,
Marcin

  reply	other threads:[~2023-12-18 10:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07 16:49 [Intel-wired-lan] [PATCH iwl-next v4 0/7] Add PFCP filter support Marcin Szycik
2023-12-07 16:49 ` Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 1/7] ip_tunnel: use a separate struct to store tunnel params in the kernel Marcin Szycik
2023-12-07 16:49   ` Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 2/7] ip_tunnel: convert __be16 tunnel flags to bitmaps Marcin Szycik
2023-12-07 16:49   ` Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 3/7] lib/bitmap: add tests for IP tunnel flags conversion helpers Marcin Szycik
2023-12-07 16:49   ` Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 4/7] pfcp: add PFCP module Marcin Szycik
2023-12-07 16:49   ` Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 5/7] pfcp: always set pfcp metadata Marcin Szycik
2023-12-07 16:49   ` Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 6/7] ice: refactor ICE_TC_FLWR_FIELD_ENC_OPTS Marcin Szycik
2023-12-07 16:49   ` Marcin Szycik
2023-12-07 16:49 ` [Intel-wired-lan] [PATCH iwl-next v4 7/7] ice: Add support for PFCP hardware offload in switchdev Marcin Szycik
2023-12-07 16:49   ` Marcin Szycik
2023-12-08 21:34 ` [Intel-wired-lan] [PATCH iwl-next v4 0/7] Add PFCP filter support Tony Nguyen
2023-12-08 21:34   ` Tony Nguyen
2023-12-11 12:38   ` Alexander Lobakin
2023-12-11 12:38     ` Alexander Lobakin
2023-12-11 21:23     ` Tony Nguyen
2023-12-11 21:23       ` Tony Nguyen
2023-12-12 10:45       ` Marcin Szycik
2023-12-12 10:45         ` Marcin Szycik
2023-12-15 10:11         ` Alexander Lobakin
2023-12-15 10:11           ` Alexander Lobakin
2023-12-15 16:49           ` Jakub Kicinski
2023-12-15 16:49             ` Jakub Kicinski
2023-12-18 10:04             ` Marcin Szycik [this message]
2023-12-18 10:04               ` Marcin Szycik
2023-12-18 12:47               ` Alexander Lobakin
2023-12-18 12:47                 ` Alexander Lobakin
2023-12-18 15:57                 ` Yury Norov
2023-12-18 15:57                   ` Yury Norov
2023-12-18 16:16                   ` Alexander Potapenko
2023-12-18 16:16                     ` Alexander Potapenko
2023-12-19  9:04                     ` Alexander Lobakin
2023-12-19  9:04                       ` Alexander Lobakin

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=ff8cfb1e-8a03-4a82-a651-3424bf9787a6@linux.intel.com \
    --to=marcin.szycik@linux.intel.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=wojciech.drewek@intel.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.