mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: [PATCH 0/5] octeontx2-af: Clean-up some bitmap related usage
Date: Fri, 25 Nov 2022 13:23:41 +0100	[thread overview]
Message-ID: <cover.1669378798.git.christophe.jaillet@wanadoo.fr> (raw)

The main point is patch 4.

The other ones are just minor things spoted while looking at the way the
'id_bmap' bitmap was used.

Christophe JAILLET (5):
  octeontx2-af: Fix a potentially spurious error message
  octeontx2-af: Slightly simplify rvu_npc_exact_init()
  octeontx2-af: Use the bitmap API to allocate bitmaps
  octeontx2-af: Fix the size of memory allocated for the 'id_bmap'
    bitmap
  octeontx2-af: Simplify a size computation in rvu_npc_exact_init()

 .../marvell/octeontx2/af/rvu_npc_hash.c         | 17 ++++++++---------
 1 file changed, 8 insertions(+), 9 deletions(-)

-- 
2.34.1


             reply	other threads:[~2022-11-25 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 12:23 Christophe JAILLET [this message]
2022-11-25 12:23 ` [PATCH 1/5] octeontx2-af: Fix a potentially spurious error message Christophe JAILLET
2022-12-01  4:50   ` patchwork-bot+netdevbpf
2022-11-25 12:23 ` [PATCH 2/5] octeontx2-af: Slightly simplify rvu_npc_exact_init() Christophe JAILLET
2022-11-25 12:23 ` [PATCH 3/5] octeontx2-af: Use the bitmap API to allocate bitmaps Christophe JAILLET
2022-11-25 12:24 ` [PATCH 4/5] octeontx2-af: Fix the size of memory allocated for the 'id_bmap' bitmap Christophe JAILLET
2022-11-25 12:24 ` [PATCH 5/5] octeontx2-af: Simplify a size computation in rvu_npc_exact_init() Christophe JAILLET

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=cover.1669378798.git.christophe.jaillet@wanadoo.fr \
    --to=christophe.jaillet@wanadoo.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®