From: Stefan Roese <ml@stefan-roese.de>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: linuxppc-dev@ozlabs.org,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-kernel@vger.kernel.org
Subject: Re: Correct location for ADC/DAC drivers
Date: Fri, 4 May 2007 08:11:42 +0200 [thread overview]
Message-ID: <200705040811.43312.ml@stefan-roese.de> (raw)
In-Reply-To: <20070502191101.GB16696@flint.arm.linux.org.uk>
On Wednesday 02 May 2007 21:11, Russell King wrote:
> > > Is there a maintainer for this "drivers/mfd" directory?
> >
> > rmk
>
> I wouldn't go that far. There's no real infrastructure there
> to maintain, so I'd actually say that the directory was
> maintainerless. However, I'll own up to the UCB/MCP drivers
> in there.
So perhaps you could answer is you feel that these ADC & DAC chrdev device
drivers would fit into this drivers/mfd directory, or are better suited for
the drivers/char directory?
Thanks.
Best regards,
Stefan
next prev parent reply other threads:[~2007-05-04 6:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 12:35 Correct location for ADC/DAC drivers Stefan Roese
2007-05-01 21:03 ` Guennadi Liakhovetski
2007-05-02 10:25 ` Stefan Roese
2007-05-02 13:35 ` Robert Schwebel
2007-05-02 19:11 ` Russell King
2007-05-04 6:11 ` Stefan Roese [this message]
2007-05-04 7:44 ` Russell King
2007-05-04 8:24 ` Robert Schwebel
2007-05-04 8:54 ` Stefan Roese
2007-05-04 18:21 ` Robin Getz
2007-05-04 20:52 ` Robert Schwebel
2007-05-04 22:16 ` Robin Getz
[not found] <8fZXU-3EI-11@gated-at.bofh.it>
[not found] ` <8haHG-6zd-19@gated-at.bofh.it>
[not found] ` <8hd2U-1Ca-39@gated-at.bofh.it>
[not found] ` <8heii-3GM-37@gated-at.bofh.it>
2007-05-06 12:19 ` Bodo Eggert
2007-05-06 13:20 ` Paul Sokolovsky
2007-05-06 16:01 ` Robert Schwebel
2007-05-06 19:33 ` Robin Getz
2007-05-06 20:20 ` Guennadi Liakhovetski
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=200705040811.43312.ml@stefan-roese.de \
--to=ml@stefan-roese.de \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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).