From: Simon Horman <horms@kernel.org>
To: Rosen Penev <rosenp@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, linux@armlinux.org.uk,
linux-kernel@vger.kernel.org, o.rempel@pengutronix.de,
p.zabel@pengutronix.de
Subject: Re: [PATCHv2 net-next] net: ag71xx: update FIFO bits and descriptions
Date: Thu, 29 Aug 2024 21:55:22 +0100 [thread overview]
Message-ID: <20240829205522.GC1368797@kernel.org> (raw)
In-Reply-To: <CAKxU2N9F6+nZzW=me_ti76RwUFiKqG5RT0Ztgztc8yE9O3fwhQ@mail.gmail.com>
On Thu, Aug 29, 2024 at 01:21:02PM -0700, Rosen Penev wrote:
> On Thu, Aug 29, 2024 at 12:47 PM Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > On Thu, 29 Aug 2024 10:47:01 -0700 Rosen Penev wrote:
> > > > Please consider a patch to allow compilation of this driver with
> > > > COMPILE_TEST in order to increase build coverage.
> > > Is that just
> >
> > Aha, do that and run an allmodconfig build on x86 to make sure nothing
> > breaks. If it's all fine please submit
> Funny enough it did break due to a mistake (L0 vs LO).
Then I'd say this exercise is a success :)
> I guess I'll
> send a series just to keep these patches together.
In general, if you have multiple patches for the same driver,
for a single tree (net or net-next) I would either:
1) Send them as a series
2) Wait for one to be accepted before sending the next one
Option 1 seems appropriate here.
next prev parent reply other threads:[~2024-08-29 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 22:38 [PATCHv2 net-next] net: ag71xx: update FIFO bits and descriptions Rosen Penev
2024-08-29 16:52 ` Simon Horman
2024-08-29 17:47 ` Rosen Penev
2024-08-29 19:47 ` Jakub Kicinski
2024-08-29 20:21 ` Rosen Penev
2024-08-29 20:55 ` Simon Horman [this message]
2024-08-29 20:19 ` Simon Horman
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=20240829205522.GC1368797@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=rosenp@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 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).