From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: lakshmi.sowjanya.d@intel.com
Cc: tglx@linutronix.de, jstultz@google.com, giometti@enneenne.com,
corbet@lwn.net, linux-kernel@vger.kernel.org, x86@kernel.org,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, eddie.dong@intel.com,
christopher.s.hall@intel.com, jesse.brandeburg@intel.com,
davem@davemloft.net, alexandre.torgue@foss.st.com,
joabreu@synopsys.com, mcoquelin.stm32@gmail.com, perex@perex.cz,
linux-sound@vger.kernel.org, anthony.l.nguyen@intel.com,
pandith.n@intel.com, mallikarjunappa.sangannavar@intel.com,
thejesh.reddy.t.r@intel.com
Subject: Re: [RFC PATCH v2 04/10] igc: remove convert_art_to_tsc()
Date: Thu, 21 Dec 2023 18:19:52 +0200 [thread overview]
Message-ID: <ZYRlqAzwTapf7ZGd@smile.fi.intel.com> (raw)
In-Reply-To: <20231221093254.9599-5-lakshmi.sowjanya.d@intel.com>
On Thu, Dec 21, 2023 at 03:02:48PM +0530, lakshmi.sowjanya.d@intel.com wrote:
> From: Thomas Gleixner <tglx@linutronix.de>
>
> Remove convert_art_to_tsc() function call, Pass system clock cycles and
> clocksource ID as input to get_device_system_crosststamp().
...
> + return (struct system_counterval_t) {
> + .cs_id = CSID_X86_ART,
> + .cycles = tstamp,
> + .nsecs = true,
Either you should remove the extra spaces before '=' or replace them by TAB(s).
> + };
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-12-21 16:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 9:32 [RFC PATCH v2 00/10] Add support for Intel PPS Generator lakshmi.sowjanya.d
2023-12-21 9:32 ` [RFC PATCH v2 01/10] x86/tsc: Add base clock properties in clocksource structure lakshmi.sowjanya.d
2023-12-22 17:08 ` Vinicius Costa Gomes
2023-12-21 9:32 ` [RFC PATCH v2 02/10] timekeeping: Add function to convert realtime to base clock lakshmi.sowjanya.d
2023-12-21 9:32 ` [RFC PATCH v2 03/10] e10002: remove convert_art_to_tsc() lakshmi.sowjanya.d
2023-12-21 9:32 ` [RFC PATCH v2 04/10] igc: " lakshmi.sowjanya.d
2023-12-21 16:19 ` Andy Shevchenko [this message]
2023-12-21 9:32 ` [RFC PATCH v2 05/10] stmmac: intel: " lakshmi.sowjanya.d
2023-12-21 9:32 ` [RFC PATCH v2 06/10] ALSA: hda: " lakshmi.sowjanya.d
2023-12-21 9:32 ` [RFC PATCH v2 07/10] ice/ptp: " lakshmi.sowjanya.d
2023-12-21 9:32 ` [RFC PATCH v2 08/10] pps: generators: Add PPS Generator TIO Driver lakshmi.sowjanya.d
2023-12-21 16:26 ` Andy Shevchenko
2023-12-21 9:32 ` [RFC PATCH v2 09/10] Documentation: driver-api: pps: Add Intel Timed I/O PPS generator lakshmi.sowjanya.d
2023-12-21 9:32 ` [RFC PATCH v2 10/10] ABI: pps: Add ABI documentation for Intel TIO lakshmi.sowjanya.d
2023-12-21 16:27 ` Andy Shevchenko
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=ZYRlqAzwTapf7ZGd@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=anthony.l.nguyen@intel.com \
--cc=christopher.s.hall@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=eddie.dong@intel.com \
--cc=giometti@enneenne.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=joabreu@synopsys.com \
--cc=jstultz@google.com \
--cc=lakshmi.sowjanya.d@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pandith.n@intel.com \
--cc=perex@perex.cz \
--cc=tglx@linutronix.de \
--cc=thejesh.reddy.t.r@intel.com \
--cc=x86@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).