mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Pratik Patel <pratikp@codeaurora.org>,
	peter.lachner@intel.com, norbert.schulz@intel.com,
	keven.boell@intel.com, yann.fouassier@intel.com,
	laurent.fert@intel.com, linux-api@vger.kernel.org
Subject: Re: [PATCH v0 01/11] stm class: Introduce an abstraction for System Trace Module devices
Date: Fri, 20 Mar 2015 16:53:50 +0200	[thread overview]
Message-ID: <87k2ybd8jl.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <CANLsYkwithjLgtztf8aBDRv-QL2VGOwc4XZ=1sGBSHg4LiymBg@mail.gmail.com>

Mathieu Poirier <mathieu.poirier@linaro.org> writes:

> As promised I worked on a prototype that connects the coresight-stm
> driver with the generic STM interface you have suggested.  Things work
> quite well and aside from the enhancement related to the ioctl() and
> private member as discussed above, we should move ahead with this.
>
> I will send out a new version of the coresight-stm driver as soon as I
> see your patches with those changes.

Actually, instread of a private member I'd simply pass struct stm_data
pointer to the callback (like we do with other callbacks) and the
private data would be in the structure that embeds this struct stm_data,
so that you can get to it using container_of():

struct my_stm {
       struct stm_data	data;
       void		*my_stuff;
       ...
};

...

long my_ioctl(struct stm_data *data, unsigned int cmd, unsigned long
	      arg)
{
        struct my_stm *mine = container_of(data, struct my_stm, data);

...

Would this work for you? I'm otherwise ready to send the second version
of my patchset.

Regards,
--
Alex

  reply	other threads:[~2015-03-20 14:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-07 11:35 [PATCH v0 00/11] Introduce Intel Trace Hub support Alexander Shishkin
2015-03-07 11:35 ` [PATCH v0 01/11] stm class: Introduce an abstraction for System Trace Module devices Alexander Shishkin
2015-03-07 22:26   ` Paul Bolle
2015-03-17 10:13     ` Alexander Shishkin
2015-03-09 21:29   ` Mathieu Poirier
2015-03-17 10:37     ` Alexander Shishkin
2015-03-18 15:07       ` Mathieu Poirier
2015-03-19 14:23         ` Alexander Shishkin
2015-03-19 14:39           ` Mathieu Poirier
2015-03-19 22:21       ` Mathieu Poirier
2015-03-20 14:53         ` Alexander Shishkin [this message]
2015-03-20 15:19           ` Mathieu Poirier
2015-03-07 11:35 ` [PATCH v0 02/11] MAINTAINERS: add an entry for System Trace Module device class Alexander Shishkin
2015-03-07 11:35 ` [PATCH v0 03/11] stm class: dummy_stm: Add dummy driver for testing stm class Alexander Shishkin
2015-03-07 11:35 ` [PATCH v0 04/11] stm class: stm_console: Add kernel-console-over-stm driver Alexander Shishkin
2015-03-07 11:35 ` [PATCH v0 05/11] intel_th: Add driver infrastructure for Intel Trace Hub devices Alexander Shishkin
2015-03-07 11:35 ` [PATCH v0 06/11] intel_th: Add pci glue layer for Intel Trace Hub Alexander Shishkin
2015-03-07 11:35 ` [PATCH v0 07/11] intel_th: Add Global Trace Hub driver Alexander Shishkin
2015-03-07 11:35 ` [PATCH v0 08/11] intel_th: Add Software " Alexander Shishkin
2015-03-07 11:35 ` [PATCH v0 09/11] intel_th: Add Memory Storage Unit driver Alexander Shishkin
2015-03-07 11:36 ` [PATCH v0 10/11] intel_th: Add PTI output driver Alexander Shishkin
2015-03-07 11:36 ` [PATCH v0 11/11] MAINTAINERS: add an entry for Intel(R) Trace Hub Alexander Shishkin

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=87k2ybd8jl.fsf@ashishki-desk.ger.corp.intel.com \
    --to=alexander.shishkin@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=keven.boell@intel.com \
    --cc=laurent.fert@intel.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=norbert.schulz@intel.com \
    --cc=peter.lachner@intel.com \
    --cc=pratikp@codeaurora.org \
    --cc=yann.fouassier@intel.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

all inboxes | Powered by JetHome®