From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Minchan Kim <minchan@kernel.org>, Nitin Gupta <ngupta@vflare.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] zram: include linux/err.h
Date: Tue, 18 Mar 2014 21:35:10 +0300 [thread overview]
Message-ID: <20140318183510.GA430@swordfish> (raw)
In-Reply-To: <201403152126.02967.arnd@arndb.de>
Hello Arnd,
On (03/15/14 21:26), Arnd Bergmann wrote:
> On Saturday 15 March 2014, Sergey Senozhatsky wrote:
> > On (03/15/14 10:40), Arnd Bergmann wrote:
> > > The zram driver uses the ERR_PTR macro defined in <linux/err.h>
> > > and relies on this header to be included implicitly through
> > > other headers, which is not (always) the case on the ARM architecture.
> > >
> >
> > returned from zcomp ERR_PTR is checked and used in zram_drv.c, should
> > in this case there also be inclusion of err.h in zram_drv.h? if so, it
> > probably makes sense to move inclusion of err.h to zcomp.h, which is
> > included both in zcomp.c and zram_drv.c
> >
>
> The normal convention is to only include headers from other headers if
> that is required by the contents of the header itself.
>
> Following the common conventions, it's better to include linux/err.h
> in both zram_drv.c and zcomp.c, but not in zram_drv.h.
thanks.
may I ask you to resend the patch with linux/err.h included
in both zram_drv.c and zcomp.c?
-ss
> I didn't do that in my patch, because I only got a build error in
> one of the two files.
>
> Arnd
>
next prev parent reply other threads:[~2014-03-18 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 9:40 [PATCH] zram: include linux/err.h Arnd Bergmann
2014-03-15 14:18 ` Sergey Senozhatsky
2014-03-15 20:26 ` Arnd Bergmann
2014-03-18 18:35 ` Sergey Senozhatsky [this message]
[not found] ` <20140319013946.GF13475@bbox>
2014-03-20 20:58 ` Sergey Senozhatsky
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=20140318183510.GA430@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
/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