From: Breno Leitao <leitao@debian.org>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
netdev@vger.kernel.org, Roy.Pledge@nxp.com, llvm@lists.linux.dev,
open list <linux-kernel@vger.kernel.org>,
horms@kernel.org, oe-kbuild-all@lists.linux.dev, kuba@kernel.org,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] soc: fsl: qbman: FSL_DPAA depends on COMPILE_TEST
Date: Tue, 9 Jul 2024 08:15:23 -0700 [thread overview]
Message-ID: <Zo1UC/grXeIocGu5@gmail.com> (raw)
In-Reply-To: <20240709135811.c7tqh3ocfumg6ctt@skbuf>
Hello Vladimir,
On Tue, Jul 09, 2024 at 04:58:11PM +0300, Vladimir Oltean wrote:
> On Mon, Jul 08, 2024 at 12:08:05PM -0700, Breno Leitao wrote:
> > I thought about a patch like the following (compile tested only). What
> > do you think?
>
> To be honest, there are several things I don't really like about this
> patch.
>
> - I really struggled with applying it in the current format. Could you
> please post the output of git format-patch in the future?
This is the output of `git format-patch` shifted right by a tab.
> - You addressed dpaa_set_coalesce() but not also dpaa_fq_setup()
> - You misrepresented the patch content by saying you only allocate size
> for online CPUs in the commit message. But you allocate for all
> possible CPUs.
> - You only kfree(needs_revert) in the error (revert_values) case, but
> not in the normal (return 0) case.
> - The netdev coding style is to sort the lines with variable
> declarations in reverse order of line length (they call this "reverse
> Christmas tree"). Your patch broke that order.
> - You should use kcalloc() instead of kmalloc_array() + memset()
>
> I have prepared and tested the attached alternative patch on a board and
> I am preparing to submit it myself, if you don't have any objection.
Sure, not a problem. You just asked how that would be possible, and I
decided to craft patch to show what I had in mind. I am glad we have a
way moving forward.
Thanks for solving it.
next prev parent reply other threads:[~2024-07-09 15:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 16:21 [PATCH 1/4] soc: fsl: qbman: FSL_DPAA depends on COMPILE_TEST Breno Leitao
2024-06-24 16:21 ` [PATCH 2/4] crypto: caam: Depend on COMPILE_TEST also Breno Leitao
2024-06-29 11:29 ` kernel test robot
2024-06-24 16:21 ` [PATCH 3/4] crypto: caam: Unembed net_dev structure from qi Breno Leitao
2024-06-28 16:32 ` Simon Horman
2024-07-02 13:32 ` Breno Leitao
2024-06-24 16:21 ` [PATCH 4/4] crypto: caam: Unembed net_dev structure in dpaa2 Breno Leitao
2024-06-25 14:39 ` [PATCH 1/4] soc: fsl: qbman: FSL_DPAA depends on COMPILE_TEST Jakub Kicinski
2024-06-25 22:06 ` Herbert Xu
2024-06-26 12:09 ` kernel test robot
2024-06-26 14:06 ` Vladimir Oltean
2024-06-27 18:40 ` Breno Leitao
2024-07-08 13:37 ` Vladimir Oltean
2024-07-08 19:08 ` Breno Leitao
2024-07-09 13:58 ` Vladimir Oltean
2024-07-09 15:15 ` Breno Leitao [this message]
2024-07-09 15:25 ` Vladimir Oltean
2024-06-29 13:55 ` kernel test robot
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=Zo1UC/grXeIocGu5@gmail.com \
--to=leitao@debian.org \
--cc=Roy.Pledge@nxp.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=olteanv@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).