From: Jim Lin <jilin@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/6] tegra: nand: Add Tegra NAND driver
Date: Mon, 16 Jan 2012 10:25:01 +0800 [thread overview]
Message-ID: <4B9C9637D5087840A465BDCB251780E9E2D1856333@HKMAIL02.nvidia.com> (raw)
In-Reply-To: <201201142312.12476.vapier@gentoo.org>
Simon,
Could you also add
Signed-off-by: Jim Lin <jilin@nvidia.com>
for me?
Thanks,
Jim
-----Original Message-----
From: Mike Frysinger [mailto:vapier at gentoo.org]
Sent: Sunday, January 15, 2012 12:12 PM
To: Simon Glass
Cc: u-boot at lists.denx.de; Jim Lin; Tom Warren; Scott Wood
Subject: Re: [U-Boot] [PATCH 5/6] tegra: nand: Add Tegra NAND driver
* PGP Signed by an unknown key
On Saturday 14 January 2012 23:08:45 Simon Glass wrote:
> On Sat, Jan 14, 2012 at 8:03 PM, Mike Frysinger wrote:
> > On Friday 13 January 2012 18:10:55 Simon Glass wrote:
> >> From: Jim Lin <jilin@nvidia.com>
> >>
> >> A device tree is used to configure the NAND, including memory
> >> timings and block/pages sizes.
> >>
> >> If this node is not present or is disabled, then NAND will not
> >> be initialized.
> >>
> >> Signed-off-by: Simon Glass <sjg@chromium.org>
> >
> > the Author needs to sign off too ...
>
> I have a lot like that. It doesn't feel right for me to just add their
> sign-off after all my changes. I was hoping that they would reply to
> the list with it. Does that work? The original commit does not have a
> sign-off.
sure, if the author replies with their s-o-b, or says they're OK with you
adding it, that's fine. but you're right that you can't just add it yourself
without them saying so first ...
-mike
* Unknown Key
* 0xE837F581
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
next prev parent reply other threads:[~2012-01-16 2:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 23:10 [U-Boot] [PATCH 0/6] tegra: Add NAND flash support Simon Glass
2012-01-13 23:10 ` [U-Boot] [PATCH 2/6] tegra: Add NAND support to funcmux Simon Glass
2012-01-19 22:27 ` Stephen Warren
2012-01-13 23:10 ` [PATCH 3/6] tegra: fdt: Add NAND controller binding and definitions Simon Glass
2012-01-13 23:10 ` [U-Boot] " Simon Glass
[not found] ` <1326496256-5559-4-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2012-01-20 1:03 ` Stephen Warren
2012-01-20 1:03 ` [U-Boot] " Stephen Warren
2012-04-13 17:44 ` Simon Glass
2012-04-13 17:44 ` [U-Boot] " Simon Glass
[not found] ` <1326496256-5559-1-git-send-email-sjg-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2012-01-13 23:10 ` [PATCH 1/6] fdt: Add debugging to fdtdec_get_int/addr() Simon Glass
2012-01-13 23:10 ` [U-Boot] " Simon Glass
2012-01-13 23:10 ` [PATCH 4/6] tegra: fdt: Add NAND definitions to fdt Simon Glass
2012-01-13 23:10 ` [U-Boot] " Simon Glass
2012-01-13 23:10 ` [U-Boot] [PATCH 5/6] tegra: nand: Add Tegra NAND driver Simon Glass
2012-01-15 4:03 ` Mike Frysinger
2012-01-15 4:08 ` Simon Glass
2012-01-15 4:12 ` Mike Frysinger
2012-01-16 2:25 ` Jim Lin [this message]
2012-01-20 17:31 ` Stephen Warren
2012-04-13 17:42 ` Simon Glass
2012-01-20 22:55 ` Scott Wood
2012-04-13 17:42 ` Simon Glass
2012-04-13 18:09 ` Scott Wood
2012-04-13 18:25 ` Simon Glass
2012-04-13 18:34 ` Scott Wood
2012-04-13 18:45 ` Simon Glass
2012-04-13 18:47 ` Scott Wood
2012-04-13 18:49 ` Simon Glass
2012-01-13 23:10 ` [U-Boot] [PATCH 6/6] tegra: Enable NAND on Seaboard Simon Glass
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=4B9C9637D5087840A465BDCB251780E9E2D1856333@HKMAIL02.nvidia.com \
--to=jilin@nvidia.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.