alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: Sagar Arun Kamble <sagar.a.kamble@intel.com>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
	linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
	Stephen Boyd <sboyd@codeaurora.org>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	John Stultz <john.stultz@linaro.org>,
	intel-wired-lan@lists.osuosl.org,
	Thomas Gleixner <tglx@linutronix.de>,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] timecounter: Make cyclecounter struct part of timecounter struct
Date: Fri, 1 Dec 2017 07:56:05 -0800	[thread overview]
Message-ID: <20171201155605.7c7oiq5we4n7wdum@localhost> (raw)
In-Reply-To: <1512114454-26958-1-git-send-email-sagar.a.kamble@intel.com>

On Fri, Dec 01, 2017 at 01:17:34PM +0530, Sagar Arun Kamble wrote:
> There is no real need for the users of timecounters to define cyclecounter
> and timecounter variables separately. Since timecounter will always be
> based on cyclecounter, have cyclecounter struct as member of timecounter
> struct.

Could you please put the PTP maintainer onto CC?

Thanks,
Richard

  reply	other threads:[~2017-12-01 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01  7:47 [PATCH 1/1] timecounter: Make cyclecounter struct part of timecounter struct Sagar Arun Kamble
2017-12-01 15:56 ` Richard Cochran [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-12-02  4:31 Sagar Arun Kamble
2017-12-02 18:04 ` Richard Cochran
2017-12-04  5:13   ` Sagar Arun Kamble

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=20171201155605.7c7oiq5we4n7wdum@localhost \
    --to=richardcochran@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=john.stultz@linaro.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sagar.a.kamble@intel.com \
    --cc=sboyd@codeaurora.org \
    --cc=tglx@linutronix.de \
    /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).