From: Greg KH <greg@kroah.com>
To: Sanjay R Mehta <Sanju.Mehta@amd.com>
Cc: mika.westerberg@linux.intel.com, andreas.noever@gmail.com,
michael.jamet@intel.com, YehezkelShB@gmail.com,
linux-usb@vger.kernel.org, Sanath S <Sanath.S@amd.com>
Subject: Re: [PATCH Internal] thunderbolt: Remove enabling/disabling TMU based on CLx
Date: Wed, 21 Jun 2023 12:52:32 +0200 [thread overview]
Message-ID: <2023062153-barterer-condiment-c209@gregkh> (raw)
In-Reply-To: <1687343842-17881-1-git-send-email-Sanju.Mehta@amd.com>
On Wed, Jun 21, 2023 at 05:37:22AM -0500, Sanjay R Mehta wrote:
> From: Sanath S <Sanath.S@amd.com>
Why "Internal"?
next prev parent reply other threads:[~2023-06-21 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 10:37 [PATCH Internal] thunderbolt: Remove enabling/disabling TMU based on CLx Sanjay R Mehta
2023-06-21 10:52 ` Greg KH [this message]
2023-06-21 10:52 ` Greg KH
2023-06-21 10:57 ` Sanjay R Mehta
2023-06-21 11:15 ` Mika Westerberg
2023-06-21 12:18 ` Sanjay R Mehta
2023-06-21 12:54 ` Mika Westerberg
2023-06-21 16:07 ` Sanjay R Mehta
2023-06-22 4:45 ` Mika Westerberg
2023-07-06 13:48 ` Sanjay R Mehta
2023-07-31 9:41 ` Mika Westerberg
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=2023062153-barterer-condiment-c209@gregkh \
--to=greg@kroah.com \
--cc=Sanath.S@amd.com \
--cc=Sanju.Mehta@amd.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.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