From: Jonathan Cameron <jic23@cam.ac.uk>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <jic23@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>
Subject: Re: IIO include folder hierarchy
Date: Tue, 15 May 2012 09:40:42 +0100 [thread overview]
Message-ID: <4FB2168A.2050206@cam.ac.uk> (raw)
In-Reply-To: <4FB21652.9070809@metafoo.de>
On 5/15/2012 9:39 AM, Lars-Peter Clausen wrote:
> Hi,
>
> I was just preparing a patch to move the DAC drivers out of staging. And I'm
> wondering if we want to use a flat hierarchy in the IIO include folder, i.e
> put all includes in toplevel folder. Or if we want individual subfolders for
> the different device classes (e.g. include/linux/iio/dac/ in this case). I'd
> opt for the later since I fear that things would get quite messy over time
> in the toplevel folder.
Subfolders sounds sensible to me.
>
> Thanks,
> - Lars
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-05-15 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 8:39 IIO include folder hierarchy Lars-Peter Clausen
2012-05-15 8:40 ` Jonathan Cameron [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=4FB2168A.2050206@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Michael.Hennerich@analog.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).