All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot and OneNAND
Date: Thu, 03 Jul 2008 20:57:58 -0400	[thread overview]
Message-ID: <486D7596.9050001@gmail.com> (raw)
In-Reply-To: <9c9fda240807022351q14443917n6345049f5c01d7e5@mail.gmail.com>

Kyungmin Park wrote:
> On Thu, Jul 3, 2008 at 1:58 PM, Kyungmin Park <kmpark@infradead.org> wrote:
>> Hi,
>>
>> On Wed, Jul 2, 2008 at 8:55 PM, Mile Davidovic <md4uboot@gmail.com> wrote:
>>> Hello
>>> If I read code correctly u-boot have OneNAND driver. But when I check JFFS2
>>> in u-boot it seems that JFFS2 can not work on OneNAND.
>> Yes, it's not yet implemented.
>>
> 
> Feel free to use this patch.
> the mtdparts and fsload is working, but I'm not suer it's working correctly.
> 
> Thank you,
> Kyungmin Park
> ---
> diff --git a/common/cmd_jffs2.c b/common/cmd_jffs2.c
> index 1b67e73..51c742c 100644
> --- a/common/cmd_jffs2.c
> +++ b/common/cmd_jffs2.c

I don't know what the rest of the list thinks, but I would like to see a 
"Signed-off-by" line (and/or a note on where the code came from - e.g. 
linux) on all patches whether they are preliminary or not.  I would hate 
to get into a "where did this code come from" quandary over a code that 
came from, was influenced by, or simply looked like a patch that was 
posted without proper traceability.

Thanks,
gvb

  reply	other threads:[~2008-07-04  0:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02 11:55 [U-Boot-Users] u-boot and OneNAND Mile Davidovic
2008-07-03  4:58 ` Kyungmin Park
2008-07-03  6:51   ` Kyungmin Park
2008-07-04  0:57     ` Jerry Van Baren [this message]
2008-07-04  3:33       ` Kyungmin Park
2008-07-04 10:14         ` Mile Davidovic

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=486D7596.9050001@gmail.com \
    --to=gvb.uboot@gmail.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.