All of lore.kernel.org
 help / color / mirror / Atom feed
From: nick <yocto6@gmail.com>
To: khilman@deeprootsystems.com
Cc: linux@arm.linux.org.uk, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Legacy Code in gpmc-onenand.c
Date: Sat, 27 Sep 2014 22:37:02 -0400	[thread overview]
Message-ID: <5427744E.4040409@gmail.com> (raw)

Greetings Kevin and others,
I am wondering if the below code is legacy I can remove it as stated it the fix me.
Cheers Nick 
else {
                /*
                * FIX ME: Appears to be legacy code from initial ONENAND commit.
                * Unclear what boards this is for and if this can be removed.
                 */
                if (!cpu_is_omap34xx())
                        onenand_sync.wait_on_read = true;
        }

WARNING: multiple messages have this Message-ID (diff)
From: yocto6@gmail.com (nick)
To: linux-arm-kernel@lists.infradead.org
Subject: Legacy Code in gpmc-onenand.c
Date: Sat, 27 Sep 2014 22:37:02 -0400	[thread overview]
Message-ID: <5427744E.4040409@gmail.com> (raw)

Greetings Kevin and others,
I am wondering if the below code is legacy I can remove it as stated it the fix me.
Cheers Nick 
else {
                /*
                * FIX ME: Appears to be legacy code from initial ONENAND commit.
                * Unclear what boards this is for and if this can be removed.
                 */
                if (!cpu_is_omap34xx())
                        onenand_sync.wait_on_read = true;
        }

             reply	other threads:[~2014-09-28  2:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-28  2:37 nick [this message]
2014-09-28  2:37 ` Legacy Code in gpmc-onenand.c nick
2014-09-28  2:51 ` Al Viro
2014-09-28  2:51   ` Al Viro
2014-09-28 16:14 ` Sudip Mukherjee
2014-09-28 16:14   ` Sudip Mukherjee

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=5427744E.4040409@gmail.com \
    --to=yocto6@gmail.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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.