From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: kernel-janitors@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [patch] f2fs: dereferencing an ERR_PTR
Date: Fri, 24 May 2013 11:32:33 +0000 [thread overview]
Message-ID: <1369395153.10521.15.camel@kjgkr> (raw)
In-Reply-To: <20130524112340.GA23932@mwanda>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
2013-05-24 (금), 14:23 +0300, Dan Carpenter:
> On Fri, May 24, 2013 at 12:46:08PM +0900, Jaegeuk Kim wrote:
> > From ded3c78fcb6dd8c39a8664471544942e51ff9faf Mon Sep 17 00:00:00 2001
> > From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
> > Date: Fri, 24 May 2013 12:41:04 +0900
> > Subject: [PATCH] f2fs: align data types between on-disk and in-memory
> > block
> > addresses
> > Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
> > linux-f2fs-devel@lists.sourceforge.net
> >
> > The on-disk block address is defined as __le32, but in-memory block
> > address,
> > block_t, does as u64.
> >
> > Let's synchronize them to 32 bits.
> >
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
>
> What you say sounds good to me. Could you give me the reported-by
> tag instead of the Signed-off-by? The Signed-off-by means it went
> through my hands and it's intended as sort of a legal thing like
> signing a document.
Ok, I see.
Thank you very much for the notification. :)
>
> regards,
> dan carpenter
--
Jaegeuk Kim
Samsung
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-05-24 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 10:02 [patch] f2fs: dereferencing an ERR_PTR Dan Carpenter
2013-05-23 10:12 ` Dan Carpenter
2013-05-24 3:46 ` Jaegeuk Kim
2013-05-24 11:23 ` Dan Carpenter
2013-05-24 11:32 ` Jaegeuk Kim [this message]
2013-05-26 15:05 ` walter harms
2013-05-26 20:41 ` Dan Carpenter
2013-05-27 7:13 ` walter harms
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=1369395153.10521.15.camel@kjgkr \
--to=jaegeuk.kim@samsung.com \
--cc=dan.carpenter@oracle.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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