netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Matthew Wilcox <willy@infradead.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH 9/9] u64_stat: Remove the obsolete fetch_irq() variants
Date: Thu, 18 Aug 2022 18:59:00 +0200	[thread overview]
Message-ID: <Yv5v1E6mfpcxjnLV@linutronix.de> (raw)
In-Reply-To: <20220818090200.4c6889f2@kernel.org>

On 2022-08-18 09:02:00 [-0700], Jakub Kicinski wrote:
> On Thu, 18 Aug 2022 17:27:06 +0200 Sebastian Andrzej Siewior wrote:
> > On 2022-08-17 11:27:45 [-0700], Jakub Kicinski wrote:
> > > What's the thinking on merging? 8 and 9 will get reposted separately 
> > > for net-next once the discussions are over?  
> > 
> > It depends on 2/9. So either it gets routed via -tip with your blessing
> > or a feature branch containing 2/9 on top of -rc1 so you can pull that
> > change and apply 8+9.
> > Just say what works best for you and I let tglx know ;)
> 
> Heh, I saw a message from Greg politely and informatively explaining 
> to someone how they have to structure their refactoring to avoid
> conflicts in linux-next. I should have saved it cause my oratorical
> skills are weak.

No need to explains, just say that you want to see the networking bits
only ;)

> No ack, I'd much rather you waited for after the next merge window 
> and queued this refactoring to net-next. Patch 9 is changing 70
> files in networking. Unless I'm missing something and this is time
> sensitive.

It started with the clean up of the mess that has been made in the merge
and then it went on a little.

Any opinion on 8/9? It could wait for the next merge window if you want
to avoid a feature branch to pull from.

Regarding 9/9. This is a clean up, which is possible after 8/9. It can
definitely be applied later.
I assume you want only see the networking bits so I would split the
other subsystem out. I guess instead the big net patch I split them on
per driver vendor basis + net/ subsys?

Sebastian

  reply	other threads:[~2022-08-18 16:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220817162703.728679-1-bigeasy@linutronix.de>
2022-08-17 16:27 ` [PATCH 8/9] u64_stats: Streamline the implementation Sebastian Andrzej Siewior
2022-08-17 16:27 ` [PATCH 9/9] u64_stat: Remove the obsolete fetch_irq() variants Sebastian Andrzej Siewior
2022-08-17 18:27   ` Jakub Kicinski
2022-08-18 15:27     ` Sebastian Andrzej Siewior
2022-08-18 16:02       ` Jakub Kicinski
2022-08-18 16:59         ` Sebastian Andrzej Siewior [this message]
2022-08-18 17:45           ` Jakub Kicinski
2022-08-22 15:17             ` Sebastian Andrzej Siewior
2022-08-22 18:05               ` Jakub Kicinski
2022-08-25 16:45                 ` Sebastian Andrzej Siewior
2022-08-25 17:30                   ` Jakub Kicinski

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=Yv5v1E6mfpcxjnLV@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).