public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Ramsay Jones <ramsay@ramsayjones•plus.com>
To: Patrick Steinhardt <ps@pks•im>
Cc: GIT Mailing-list <git@vger•kernel.org>
Subject: Subject: [PATCH] object-file: fix sparse 'plain integer as NULL pointer' error
Date: Thu, 19 Mar 2026 22:49:06 +0000	[thread overview]
Message-ID: <97c623fe-4e03-4fbe-a6af-9c01c101bae4@ramsayjones.plus.com> (raw)


Signed-off-by: Ramsay Jones <ramsay@ramsayjones•plus.com>
---

Hi Patrick,

When you next re-roll your 'ps/object-counting' branch, could you please squash this
into the patch equivalent to the commit 2b24db1110 ("object-file: generalize counting
objects",2026-03-12) in tonight's 'seen' branch.

Thanks,

ATB,
Ramsay Jones


 object-file.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/object-file.c b/object-file.c
index 35be7e58cb..3708b8f18d 100644
--- a/object-file.c
+++ b/object-file.c
@@ -1941,7 +1941,7 @@ int odb_source_loose_count_objects(struct odb_source *source,
 	} else {
 		*out = 0;
 		ret = odb_source_loose_for_each_object(source, NULL, count_loose_object,
-						       out, 0);
+						       out, NULL);
 	}
 
 out:
-- 
2.53.0

next             reply	other threads:[~2026-03-19 22:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19 22:49 Ramsay Jones [this message]
2026-03-20  1:35 ` Subject: [PATCH] object-file: fix sparse 'plain integer as NULL pointer' error Junio C Hamano
2026-03-20  2:04   ` Ramsay Jones
2026-03-20  3:44     ` Ramsay Jones
2026-03-20  6:14       ` Patrick Steinhardt
2026-03-20  6:05     ` Junio C Hamano

find likely ancestor, descendant, or conflicting patches for this message:
( dfblob:35be7e58c dfblob:3708b8f18 )
 OR (
bs:"Subject: [PATCH] object-file: fix sparse 'plain integer as NULL pointer' error" )
	(help)

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=97c623fe-4e03-4fbe-a6af-9c01c101bae4@ramsayjones.plus.com \
    --to=ramsay@ramsayjones$(echo .)plus.com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=ps@pks$(echo .)im \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox