From: Dan Carpenter <dan.carpenter@oracle.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: adilger.kernel@dilger.ca,
Ding Xiang <dingxiang@cmss.chinamobile.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Subject: Re: [PATCH] ext4: change variable "count" to signed integer
Date: Mon, 20 Jun 2022 08:45:14 +0300 [thread overview]
Message-ID: <20220620054514.GF1999@kadam> (raw)
In-Reply-To: <Yq5QCJI7qC80AtxL@mit.edu>
On Sat, Jun 18, 2022 at 06:22:00PM -0400, Theodore Ts'o wrote:
> On Sat, Jun 18, 2022 at 12:33:01PM +0300, Dan Carpenter wrote:
> > On Fri, Jun 17, 2022 at 10:59:01PM -0400, Theodore Ts'o wrote:
> > > On Mon, 30 May 2022 18:00:47 +0800, Ding Xiang wrote:
> > > > Since dx_make_map() may return -EFSCORRUPTED now,
> > > > so change "count" to signed integer.
> > > >
> > > >
> > >
> > > Applied, thanks!
> > >
> > > [1/1] ext4: change variable "count" to signed integer
> > > commit: fefb759df063599ad483422eb07ef8e14c612cc2
> > >
> >
> > There was some kind of process error here...
> >
> > 1) That commit somehow never made it to linux-next.
>
> That's I only pushed it out Friday night (US/Eastern), and Stephen
> Rothwell creates new linux-next release based on snapshots taken
> Monday through Friday in the Morning (AU/Canberra time).
>
> Things have been crazy busy, so a last set of ext4 backports only
> happened Friday starting around 10pm localtime. (Yes, I have no
> life.)
Ah, sorry. I didn't look at the dates carefully. Thanks for taking
care of this.
It's so weird that kbuild and I didn't send this bug report. I can't
figure that bit out at all. It's not super common though and other
people are looking at static analysis so it worked out in the end.
regards,
dan carpenter
prev parent reply other threads:[~2022-06-20 5:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 10:00 [PATCH] ext4: change variable "count" to signed integer Ding Xiang
2022-06-18 2:59 ` Theodore Ts'o
2022-06-18 9:33 ` Dan Carpenter
2022-06-18 22:22 ` Theodore Ts'o
2022-06-20 5:45 ` Dan Carpenter [this message]
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=20220620054514.GF1999@kadam \
--to=dan.carpenter@oracle.com \
--cc=adilger.kernel@dilger.ca \
--cc=dingxiang@cmss.chinamobile.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).