From: Al Viro <viro@ZenIV.linux.org.uk>
To: nick <yocto6@gmail.com>
Cc: khilman@deeprootsystems.com, linux@arm.linux.org.uk,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Legacy Code in gpmc-onenand.c
Date: Sun, 28 Sep 2014 03:51:14 +0100 [thread overview]
Message-ID: <20140928025114.GY7996@ZenIV.linux.org.uk> (raw)
In-Reply-To: <5427744E.4040409@gmail.com>
On Sat, Sep 27, 2014 at 10:37:02PM -0400, nick wrote:
> 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
Nick, could you take that to more appropriate forum? alt.sex.fetish.FIXME
would probably be a good starting point...
WARNING: multiple messages have this Message-ID (diff)
From: viro@ZenIV.linux.org.uk (Al Viro)
To: linux-arm-kernel@lists.infradead.org
Subject: Legacy Code in gpmc-onenand.c
Date: Sun, 28 Sep 2014 03:51:14 +0100 [thread overview]
Message-ID: <20140928025114.GY7996@ZenIV.linux.org.uk> (raw)
In-Reply-To: <5427744E.4040409@gmail.com>
On Sat, Sep 27, 2014 at 10:37:02PM -0400, nick wrote:
> 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
Nick, could you take that to more appropriate forum? alt.sex.fetish.FIXME
would probably be a good starting point...
next prev parent reply other threads:[~2014-09-28 2:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 2:37 Legacy Code in gpmc-onenand.c nick
2014-09-28 2:37 ` nick
2014-09-28 2:51 ` Al Viro [this message]
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=20140928025114.GY7996@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--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 \
--cc=yocto6@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 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.