From: Jakub Kicinski <kuba@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jens Axboe <axboe@kernel.dk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH] net: dsa: qca8k: move driver to qca dir
Date: Fri, 15 Jul 2022 12:47:17 -0700 [thread overview]
Message-ID: <20220715124717.5472ceb3@kernel.org> (raw)
In-Reply-To: <62d1c288.1c69fb81.45988.55fe@mx.google.com>
On Fri, 15 Jul 2022 21:16:46 +0200 Christian Marangi wrote:
> > > Or should I just propose the move and the code split in one series?
> >
> > Yup that's what I prefer.
>
> Ok no problem, if the current merged commit is a problem, np for me with
> a revert! (it was really to prevent sending a bigger series, sorry for
> the mess)
Oh, I didn't realize Dave already merged it. No worries, it's not a big
deal. Would be great to prioritize getting the split done next. If both
are merged for before 5.19 final is cut - it doesn't really matter if
they were one series or two.
next prev parent reply other threads:[~2022-07-15 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 20:53 [net-next PATCH] net: dsa: qca8k: move driver to qca dir Christian Marangi
2022-07-13 21:02 ` Florian Fainelli
2022-07-15 5:03 ` Jakub Kicinski
2022-07-15 1:57 ` Christian Marangi
2022-07-15 19:37 ` Jakub Kicinski
2022-07-15 19:16 ` Christian Marangi
2022-07-15 19:47 ` Jakub Kicinski [this message]
2022-07-15 19:25 ` Christian Marangi
2022-07-15 11:10 ` patchwork-bot+netdevbpf
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=20220715124717.5472ceb3@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@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.