From: Marc Lehmann <schmorp@schmorp.de>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: have ioctls changed?
Date: Tue, 17 Nov 2015 04:45:28 +0100 [thread overview]
Message-ID: <20151117034527.GA4511@schmorp.de> (raw)
In-Reply-To: <20151117013634.GA4104@schmorp.de>
On Tue, Nov 17, 2015 at 02:36:35AM +0100, Marc Lehmann <schmorp@schmorp.de> wrote:
> While trying the new f2fs snapshot (3.18 branch from yesterday), I found that
> my GC script does no longer work:
>
> ioctl(0, 0xf506, 0x1741810) = -1 ENOTTY (Inappropriate ioctl for device)
Very strange, after much experimenting I deleted my f2fs checkout again
(I did "git pull" before and git log showed the correct changes, also the
ioctls were defined in the header files) and did a fresh checkout, and
that kernel module works.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schmorp@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
------------------------------------------------------------------------------
prev parent reply other threads:[~2015-11-17 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 1:36 have ioctls changed? Marc Lehmann
2015-11-17 2:34 ` Chao Yu
2015-11-17 3:45 ` Marc Lehmann [this message]
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=20151117034527.GA4511@schmorp.de \
--to=schmorp@schmorp.de \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).