From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: Tree for Feb 17 (kernel/kcmp.c)
Date: Thu, 23 Feb 2012 00:29:52 +0400 [thread overview]
Message-ID: <20120222202952.GA16093@moon> (raw)
In-Reply-To: <4F454E20.2060505@xenotime.net>
On Wed, Feb 22, 2012 at 12:20:48PM -0800, Randy Dunlap wrote:
...
>
> Since this build error is still occurring in linux-next 20120222,
> I looked and found that the Ecode is misspelled.
>
> Please s/EOPNOTSUP/EOPNOTSUPP/
>
Thanks!
Cyrill
next prev parent reply other threads:[~2012-02-22 20:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 5:50 linux-next: Tree for Feb 17 Stephen Rothwell
2012-02-17 18:00 ` linux-next: Tree for Feb 17 (kernel/kcmp.c) Randy Dunlap
2012-02-17 23:14 ` Stephen Rothwell
2012-02-18 6:58 ` Cyrill Gorcunov
2012-02-22 20:20 ` Randy Dunlap
2012-02-22 20:29 ` Cyrill Gorcunov [this message]
2012-02-17 18:34 ` linux-next: Tree for Feb 17 (uml) Randy Dunlap
2012-02-17 21:32 ` Geert Uytterhoeven
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=20120222202952.GA16093@moon \
--to=gorcunov@openvz.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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.