From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Chandrashekar Devegowda <chandrashekar.devegowda@intel.com>
Cc: linux-bluetooth@vger.kernel.org,
Ravishankar Srivatsa <ravishankar.srivatsa@intel.com>,
Chethan Tumkur Narayan <chethan.tumkur.narayan@intel.com>,
Kiran K <kiran.k@intel.com>, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: btintel_pcie: Support suspend-resume
Date: Mon, 11 Nov 2024 08:21:04 +0100 [thread overview]
Message-ID: <cb38ef85-363d-47aa-bc01-55a3fef5b0af@molgen.mpg.de> (raw)
In-Reply-To: <PH0PR11MB5952C7090EAA4F6B75145611FC582@PH0PR11MB5952.namprd11.prod.outlook.com>
Dear Chandrashekar,
Thank you for your space.
Am 11.11.24 um 07:33 schrieb Devegowda, Chandrashekar:
>> -----Original Message-----
>> Sent: Friday, November 08, 2024 2:49 PM
>> To: Devegowda, Chandrashekar <chandrashekar.devegowda@intel.com>
[…]
>> Am 08.11.24 um 15:39 schrieb ChandraShekar Devegowda:
>>
>> The space in your name is still missing.
>
> I have added my second name, my first name doesn’t have a space so
> please consider ChandraShekar as a single name.
Thank you. In your email you now do *not* use CamelCase, which is more
common in Western culture. (Of course you can write your name as you
want, and I just pointed it out.)
>>> This patch contains the changes in driver for vendor specific handshake
>>> during enter of D3 and D0 exit.
>>
>> Please document the datasheet name and revision.
>
> Datasheet is internal to Intel, sorry wouldn't be able to share at
> the moment.
Although it is not public, the name would still be good to have. Intel
employees can probably get access more easily, and non-Intel folks could
directly approach with the name, and in the future it might be even made
public.
[…]
Thank you for acknowledging the other comments.
Kind regards
Paul
next prev parent reply other threads:[~2024-11-11 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 14:39 [PATCH v2] Bluetooth: btintel_pcie: Support suspend-resume ChandraShekar Devegowda
2024-11-08 9:18 ` Paul Menzel
2024-11-11 6:33 ` Devegowda, Chandrashekar
2024-11-11 7:21 ` Paul Menzel [this message]
2025-01-24 9:06 ` Devegowda, Chandrashekar
2024-11-11 18:41 ` Bjorn Helgaas
2025-01-24 9:07 ` Devegowda, Chandrashekar
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=cb38ef85-363d-47aa-bc01-55a3fef5b0af@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=bhelgaas@google.com \
--cc=chandrashekar.devegowda@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=ravishankar.srivatsa@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