From: Olliver Schinagl <oliver+list@schinagl.nl>
To: Thierry Reding <thierry.reding@gmail.com>,
linux-pwm@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Olliver Schinagl <oliver@schinagl.nl>
Subject: [RFC] pwm: chip_data vs device_data
Date: Tue, 06 Oct 2015 09:20:53 +0200 [thread overview]
Message-ID: <56137655.40804@schinagl.nl> (raw)
Hey Thierry, list,
While working on something in the pwm framework, I noticed that the void
*data in the pwm_device struct is called chip_data. Why is it not called
device_data, since it is the data associated with a PWM device, rather
then the chip, and on that note, if it really is chip related data (thus
covering the whole chip, not just the single pwm device) why is there no
chip_data in pwm_chip?
Again, is this something worth my time to add a device_data and rename
chip_data?
Olliver
next reply other threads:[~2015-10-06 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 7:20 Olliver Schinagl [this message]
2015-10-06 7:38 ` [RFC] pwm: chip_data vs device_data Thierry Reding
2015-10-06 8:21 ` Olliver Schinagl
2015-10-06 9:14 ` Thierry Reding
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=56137655.40804@schinagl.nl \
--to=oliver+list@schinagl.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=oliver@schinagl.nl \
--cc=thierry.reding@gmail.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 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).