All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	Jiri Pirko <jiri@nvidia.com>,
	jesse.brandeburg@intel.com,
	Karol Kolacinski <karol.kolacinski@intel.com>,
	anthony.l.nguyen@intel.com, Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	Saeed Mahameed <saeedm@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH v2 iwl-next 1/9] ice: use ice_pf_src_tmr_owned where available
Date: Tue, 22 Aug 2023 20:15:12 +0300	[thread overview]
Message-ID: <20230822171512.GO6029@unreal> (raw)
In-Reply-To: <20230822095301.31aeeaf2@kernel.org>

On Tue, Aug 22, 2023 at 09:53:01AM -0700, Jakub Kicinski wrote:
> On Tue, 22 Aug 2023 19:06:51 +0300 Leon Romanovsky wrote:
> > Can I suggest change in the process?
> > 1. Perform validation before posting
> > 2. Intel will post their patches to the netdev@ ML.
> > 3. Tony will collect reviewed patches from netdev@
> > 4. Tony will send clean PRs (without patches) from time to time to
> > netdev maintainers for acceptance.
> > 
> > It will allow to all of us (Intel, Nvidia e.t.c) to have same submission
> > flow without sacrificing open netdev@ review which will be done only once.
> > 
> > Jakub/Dave, is it possible?
> 
> That sounds worse than what they are doing today. And I can't help
> but think that you're targeting them because I asked you to stop posting
> directly for net-next. Vendetta is not a good guide for process changes.

Are you real? I had this idea even BEFORE you started to be netdev@
maintainer and had put it on paper BEFORE your request.

Should I add you to our internal conversation about it so you will be
able to see dates by yourself?

Thanks
_______________________________________________
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: Leon Romanovsky <leon@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Przemek Kitszel <przemyslaw.kitszel@intel.com>,
	anthony.l.nguyen@intel.com,
	"David S. Miller" <davem@davemloft.net>,
	Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, jesse.brandeburg@intel.com,
	Karol Kolacinski <karol.kolacinski@intel.com>,
	intel-wired-lan@lists.osuosl.org,
	Saeed Mahameed <saeedm@nvidia.com>, Jiri Pirko <jiri@nvidia.com>
Subject: Re: [Intel-wired-lan] [PATCH v2 iwl-next 1/9] ice: use ice_pf_src_tmr_owned where available
Date: Tue, 22 Aug 2023 20:15:12 +0300	[thread overview]
Message-ID: <20230822171512.GO6029@unreal> (raw)
In-Reply-To: <20230822095301.31aeeaf2@kernel.org>

On Tue, Aug 22, 2023 at 09:53:01AM -0700, Jakub Kicinski wrote:
> On Tue, 22 Aug 2023 19:06:51 +0300 Leon Romanovsky wrote:
> > Can I suggest change in the process?
> > 1. Perform validation before posting
> > 2. Intel will post their patches to the netdev@ ML.
> > 3. Tony will collect reviewed patches from netdev@
> > 4. Tony will send clean PRs (without patches) from time to time to
> > netdev maintainers for acceptance.
> > 
> > It will allow to all of us (Intel, Nvidia e.t.c) to have same submission
> > flow without sacrificing open netdev@ review which will be done only once.
> > 
> > Jakub/Dave, is it possible?
> 
> That sounds worse than what they are doing today. And I can't help
> but think that you're targeting them because I asked you to stop posting
> directly for net-next. Vendetta is not a good guide for process changes.

Are you real? I had this idea even BEFORE you started to be netdev@
maintainer and had put it on paper BEFORE your request.

Should I add you to our internal conversation about it so you will be
able to see dates by yourself?

Thanks

  reply	other threads:[~2023-08-22 17:15 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 14:17 [Intel-wired-lan] [PATCH v2 iwl-next 0/9] ice: fix timestamping in reset process Karol Kolacinski
2023-08-17 14:17 ` Karol Kolacinski
2023-08-17 14:17 ` [Intel-wired-lan] [PATCH v2 iwl-next 1/9] ice: use ice_pf_src_tmr_owned where available Karol Kolacinski
2023-08-17 14:17   ` Karol Kolacinski
2023-08-18 11:10   ` [Intel-wired-lan] " Przemek Kitszel
2023-08-18 11:10     ` Przemek Kitszel
2023-08-19 11:52   ` [Intel-wired-lan] " Leon Romanovsky
2023-08-19 11:52     ` Leon Romanovsky
2023-08-22  7:02     ` [Intel-wired-lan] " Simon Horman
2023-08-22  7:02       ` Simon Horman
2023-08-22 14:13       ` [Intel-wired-lan] " Leon Romanovsky
2023-08-22 14:13         ` Leon Romanovsky
2023-08-22 14:44         ` [Intel-wired-lan] " Przemek Kitszel
2023-08-22 14:44           ` Przemek Kitszel
2023-08-22 15:48           ` Leon Romanovsky
2023-08-22 15:48             ` Leon Romanovsky
2023-08-22 15:56             ` Przemek Kitszel
2023-08-22 15:56               ` Przemek Kitszel
2023-08-22 16:06               ` Leon Romanovsky
2023-08-22 16:06                 ` Leon Romanovsky
2023-08-22 16:53                 ` Jakub Kicinski
2023-08-22 16:53                   ` Jakub Kicinski
2023-08-22 17:15                   ` Leon Romanovsky [this message]
2023-08-22 17:15                     ` Leon Romanovsky
2023-08-17 14:17 ` [Intel-wired-lan] [PATCH v2 iwl-next 2/9] ice: introduce PTP state machine Karol Kolacinski
2023-08-17 14:17   ` Karol Kolacinski
2023-08-17 14:17 ` [Intel-wired-lan] [PATCH v2 iwl-next 3/9] ice: pass reset type to PTP reset functions Karol Kolacinski
2023-08-17 14:17   ` Karol Kolacinski
2023-08-17 14:17 ` [Intel-wired-lan] [PATCH v2 iwl-next 4/9] ice: rename PTP functions and fields Karol Kolacinski
2023-08-17 14:17   ` Karol Kolacinski
2023-08-17 14:17 ` [Intel-wired-lan] [PATCH v2 iwl-next 5/9] ice: factor out ice_ptp_rebuild_owner() Karol Kolacinski
2023-08-17 14:17   ` Karol Kolacinski
2023-08-17 14:17 ` [Intel-wired-lan] [PATCH v2 iwl-next 6/9] ice: remove ptp_tx ring parameter flag Karol Kolacinski
2023-08-17 14:17   ` Karol Kolacinski
2023-08-17 14:17 ` [Intel-wired-lan] [PATCH v2 iwl-next 7/9] ice: modify tstamp_config only during TS mode set Karol Kolacinski
2023-08-17 14:17   ` Karol Kolacinski
2023-08-17 14:17 ` [Intel-wired-lan] [PATCH v2 iwl-next 8/9] ice: restore timestamp configuration after reset Karol Kolacinski
2023-08-17 14:17   ` Karol Kolacinski
2023-08-17 14:17 ` [Intel-wired-lan] [PATCH v2 iwl-next 9/9] ice: stop destroying and reinitalizing Tx tracker during reset Karol Kolacinski
2023-08-17 14:17   ` Karol Kolacinski

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=20230822171512.GO6029@unreal \
    --to=leon@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=horms@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=jiri@nvidia.com \
    --cc=karol.kolacinski@intel.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=saeedm@nvidia.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.