From: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
To: "Sanil, Shruthi" <shruthi.sanil@intel.com>
Cc: "daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"mgross@linux.intel.com" <mgross@linux.intel.com>,
"Thokala, Srikanth" <srikanth.thokala@intel.com>,
"Raja Subramanian,
Lakshmi Bai" <lakshmi.bai.raja.subramanian@intel.com>,
"Sangannavar,
Mallikarjunappa" <mallikarjunappa.sangannavar@intel.com>
Subject: Re: [PATCH v10 0/2] Add the driver for Intel Keem Bay SoC timer block
Date: Wed, 30 Mar 2022 11:59:34 +0300 [thread overview]
Message-ID: <YkQb9jX7A+10+DNp@smile.fi.intel.com> (raw)
In-Reply-To: <BN9PR11MB55459A4EA8D0599DCB753173F11F9@BN9PR11MB5545.namprd11.prod.outlook.com>
On Wed, Mar 30, 2022 at 05:04:01AM +0000, Sanil, Shruthi wrote:
> Gentle Reminder!
It's a merge window time. Be patient!
Also, please avoid top-posting.
> > From: Sanil, Shruthi <shruthi.sanil@intel.com>
> > Sent: Tuesday, March 22, 2022 6:30 PM
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2022-03-30 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 13:00 shruthi.sanil
2022-03-22 13:00 ` [PATCH v10 1/2] dt-bindings: timer: Add bindings for Intel Keem Bay SoC Timer shruthi.sanil
2022-03-30 11:44 ` Daniel Lezcano
2022-03-30 11:55 ` Krzysztof Kozlowski
2022-04-06 8:06 ` Daniel Lezcano
2022-04-06 15:13 ` Rob Herring
2022-03-22 13:00 ` [PATCH v10 2/2] clocksource: Add Intel Keem Bay timer support shruthi.sanil
2022-03-30 5:04 ` [PATCH v10 0/2] Add the driver for Intel Keem Bay SoC timer block Sanil, Shruthi
2022-03-30 8:59 ` andriy.shevchenko [this message]
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=YkQb9jX7A+10+DNp@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=lakshmi.bai.raja.subramanian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mgross@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=shruthi.sanil@intel.com \
--cc=srikanth.thokala@intel.com \
--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
all inboxes | Powered by JetHome®