From: Theodore Ts'o <tytso@mit.edu>
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: Fri, 5 Apr 2013 19:32:29 -0400 [thread overview]
Message-ID: <20130405233228.GA6597@thunk.org> (raw)
In-Reply-To: <CAAW3YpbM7Vk_=qXv2NCgRsCkashsTpYC_6osA_udm2oDsiz5qA@mail.gmail.com>
On Fri, Apr 05, 2013 at 04:18:15PM -0700, Todd Poynor wrote:
> Perhaps the better fix is to revert those additional changes and let
> the ext4 folks figure out what to do about the remaining atomic_reads.
>
> > And care to cc: the ext4 developers/maintainers when sending ext4
> > patches?
Can you send me the original patch? I'd like to fix the problem
upstream first.... I'm curious why I didn't notice this, since I run
tests (and thus build) 32-bit x86 kernels, and Eric Whitney is doing
test builds and runs regression tests an ARM Pandaboard. Can you give
me details about your compilation environment and how this causing
problems for you?
Thanks,
- Ted
next prev parent reply other threads:[~2013-04-05 23:32 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
2013-04-05 23:32 ` Theodore Ts'o [this message]
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=20130405233228.GA6597@thunk.org \
--to=tytso@mit.edu \
--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