From: "Artem B. Bityutskiy" <dedekind@yandex.ru>
To: Peter Grayson <pgrayson@realmsys.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] jffs2, symlink, and 2.6.13
Date: Tue, 04 Oct 2005 15:16:48 +0400 [thread overview]
Message-ID: <434264A0.5000708@yandex.ru> (raw)
In-Reply-To: <1128125846.6926.120.camel@localhost.localdomain>
Peter Grayson wrote:
> For those on earlier kernel versions, this change will yield compiler
> warnings. I am not sure what the policy is for maintaining compatibility
> with older kernel versions, so I did not include any changes to
> compatmac.h. Do we want to reproduce the struct inode_operations
> declaration in compatmac.h just so that latest mtd does not yield
> compiler warnings on older kernels?
The patch looks OK. Not sure how to support compatimility, I would just
let gcc print warnings in older kernels. And it looks like it is
harmless. Anyone, comments?
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2005-10-04 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 0:17 [PATCH] jffs2, symlink, and 2.6.13 Peter Grayson
2005-10-04 11:16 ` Artem B. Bityutskiy [this message]
2005-10-04 13:02 ` Josh Boyer
2005-10-04 13:14 ` Artem B. Bityutskiy
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=434264A0.5000708@yandex.ru \
--to=dedekind@yandex.ru \
--cc=linux-mtd@lists.infradead.org \
--cc=pgrayson@realmsys.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.