From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: Todd Poynor <toddpoynor@google.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, Lingzhu Xiang <lxiang@redhat.com>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: fixup 64-bit divides in linux-3.0 stable backport of upstream fix
Date: Sat, 6 Apr 2013 01:31:29 +0200 [thread overview]
Message-ID: <1365204363@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <CAAW3YpbM7Vk_=qXv2NCgRsCkashsTpYC_6osA_udm2oDsiz5qA@mail.gmail.com>
Todd Poynor wrote...
> On Fri, Apr 5, 2013 at 4:01 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Fri, Apr 05, 2013 at 03:54:23PM -0700, Todd Poynor wrote:
> > > Replace C division operators with div64_u64 for divides introduced in:
> > > commit 503f4bdcc078e7abee273a85ce322de81b18a224
> > > ext4: use atomic64_t for the per-flexbg free_clusters count
> > >
> > > Specific to the linux-3.0 backport of the upstream patch.
> >
> > Why is this specific? Why is this working differently in 3.0 from 3.4
> > and newer?
>
> Looks like 3.1 doesn't have this patch.
Just comparing the "ext4: use atomic64_t for the per-flexbg
free_clusters count" patches for 3.0 and 3.4, your fix and git: The
build errors in 3.0.72 your patch fixes originate in find_group_flex
which was removed in v3.1-rc3-44-g4113c4c, hence only 3.0 was
affected.
Christoph
next prev parent reply other threads:[~2013-04-05 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1365202463-25872-1-git-send-email-toddpoynor@google.com>
[not found] ` <20130405230107.GA8412@kroah.com>
2013-04-05 23:18 ` [PATCH] ext4: fixup 64-bit divides in linux-3.0 stable backport of upstream fix Todd Poynor
2013-04-05 23:31 ` Christoph Biedl [this message]
2013-04-05 23:32 ` Theodore Ts'o
2013-04-05 23:50 ` Theodore Ts'o
2013-04-05 23:55 ` Greg KH
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=1365204363@msgid.manchmal.in-ulm.de \
--to=linux-kernel.bfrz@manchmal.in-ulm.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=lxiang@redhat.com \
--cc=stable@vger.kernel.org \
--cc=toddpoynor@google.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