From: Kees Cook <keescook@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Subject: Re: linux-next: manual merge of the kspp tree with the net-next tree
Date: Thu, 7 Mar 2024 11:23:07 -0800 [thread overview]
Message-ID: <202403071122.F11DAADF50@keescook> (raw)
In-Reply-To: <20240307162958.02ec485c@canb.auug.org.au>
On Thu, Mar 07, 2024 at 04:29:58PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> FIXME: Add owner of second tree to To:
> Add author(s)/SOB of conflicting commits.
>
> Today's linux-next merge of the kspp tree got conflicts in:
>
> drivers/net/ethernet/intel/ice/ice_lib.c
> drivers/net/ethernet/intel/ice/ice_xsk.c
>
> between commits:
>
> 3e5fb691faee ("ice: make ice_vsi_cfg_rxq() static")
> a292ba981324 ("ice: make ice_vsi_cfg_txq() static")
>
> from the net-next tree and commit:
>
> 014dc22af922 ("overflow: Change DEFINE_FLEX to take __counted_by member")
>
> from the kspp tree.
>
> I fixed it up (I used those files from the former and applied the
> following merge fix patch) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Thu, 7 Mar 2024 16:26:02 +1100
> Subject: [PATCH] fix up for "overflow: Change DEFINE_FLEX to take __counted_by
> member"
>
> comflcting with commits
>
> 3e5fb691faee ("ice: make ice_vsi_cfg_rxq() static")
> a292ba981324 ("ice: make ice_vsi_cfg_txq() static")
>
> from the net-nect tree.
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> drivers/net/ethernet/intel/ice/ice_base.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_base.c b/drivers/net/ethernet/intel/ice/ice_base.c
> index d2fd315556a3..a545a7917e4f 100644
> --- a/drivers/net/ethernet/intel/ice/ice_base.c
> +++ b/drivers/net/ethernet/intel/ice/ice_base.c
> @@ -956,7 +956,7 @@ ice_vsi_cfg_txq(struct ice_vsi *vsi, struct ice_tx_ring *ring,
> int ice_vsi_cfg_single_txq(struct ice_vsi *vsi, struct ice_tx_ring **tx_rings,
> u16 q_idx)
> {
> - DEFINE_FLEX(struct ice_aqc_add_tx_qgrp, qg_buf, txqs, 1);
> + DEFINE_RAW_FLEX(struct ice_aqc_add_tx_qgrp, qg_buf, txqs, 1);
>
> if (q_idx >= vsi->alloc_txq || !tx_rings || !tx_rings[q_idx])
> return -EINVAL;
> @@ -978,7 +978,7 @@ int ice_vsi_cfg_single_txq(struct ice_vsi *vsi, struct ice_tx_ring **tx_rings,
> static int
> ice_vsi_cfg_txqs(struct ice_vsi *vsi, struct ice_tx_ring **rings, u16 count)
> {
> - DEFINE_FLEX(struct ice_aqc_add_tx_qgrp, qg_buf, txqs, 1);
> + DEFINE_RAW_FLEX(struct ice_aqc_add_tx_qgrp, qg_buf, txqs, 1);
> int err = 0;
> u16 q_idx;
Thanks! This looks correct to me.
--
Kees Cook
next prev parent reply other threads:[~2024-03-07 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 5:29 linux-next: manual merge of the kspp tree with the net-next tree Stephen Rothwell
2024-03-07 19:23 ` Kees Cook [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-13 4:19 Stephen Rothwell
2025-03-26 4:54 ` Stephen Rothwell
2020-07-27 9:27 Stephen Rothwell
2020-08-05 4:05 ` Stephen Rothwell
2017-02-22 0:06 Stephen Rothwell
2017-02-22 6:35 ` Daniel Borkmann
2017-02-21 23:51 Stephen Rothwell
2017-02-22 6:37 ` Daniel Borkmann
2017-02-19 23:56 Stephen Rothwell
2017-02-20 9:01 ` Daniel Borkmann
2017-02-08 1:30 Stephen Rothwell
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=202403071122.F11DAADF50@keescook \
--to=keescook@chromium.org \
--cc=anthony.l.nguyen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=sfr@canb.auug.org.au \
/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