From: Artem Bityutskiy <dedekind@infradead.org>
To: Vinit Agnihotri <vinit.agnihotri@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: overflows while calculating volume->used_bytes
Date: Tue, 10 Jul 2007 11:14:57 +0300 [thread overview]
Message-ID: <1184055297.3531.82.camel@sauron> (raw)
In-Reply-To: <9b52d64c0707100058m7730acdbv8fb8c3ca57eac2ac@mail.gmail.com>
On Tue, 2007-07-10 at 13:28 +0530, Vinit Agnihotri wrote:
> Heres the modified patch.
> Not special purpose as such. Its just my flash is a bit large :)
Committed the patch, thanks, although it did not apply cleanly and
I did hand work. Thy to save your mail and use git-am -i -s as I do.
P.S. It is so much easier to use git or quilt for preparing patches
then dealing with diff.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2007-07-10 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 5:37 overflows while calculating volume->used_bytes Vinit Agnihotri
2007-07-10 7:01 ` Artem Bityutskiy
[not found] ` <9b52d64c0707100047k604ca250g94a0657defc6eac3@mail.gmail.com>
2007-07-10 7:58 ` Vinit Agnihotri
2007-07-10 8:14 ` Artem Bityutskiy [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=1184055297.3531.82.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=vinit.agnihotri@gmail.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