linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"Hennerich, Michael" <Michael.Hennerich@analog.com>
Subject: IIO include folder hierarchy
Date: Tue, 15 May 2012 10:39:46 +0200	[thread overview]
Message-ID: <4FB21652.9070809@metafoo.de> (raw)

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.

Thanks,
- Lars

             reply	other threads:[~2012-05-15  8:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15  8:39 Lars-Peter Clausen [this message]
2012-05-15  8:40 ` IIO include folder hierarchy Jonathan Cameron

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=4FB21652.9070809@metafoo.de \
    --to=lars@metafoo.de \
    --cc=Michael.Hennerich@analog.com \
    --cc=jic23@kernel.org \
    --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).