From: Jakub Kicinski <kuba@kernel.org>
To: Ajay Kaher <ajay.kaher@broadcom.com>
Cc: nick.shi@broadcom.com, alexey.makhalov@broadcom.com,
richardcochran@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
netdev@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
linux-kernel@vger.kernel.org, florian.fainelli@broadcom.com,
vamsi-krishna.brahmajosyula@broadcom.com,
tapas.kundu@broadcom.com, shubham-sg.gupta@broadcom.com,
karen.wang@broadcom.com, hari-krishna.ginka@broadcom.com
Subject: Re: [PATCH 2/2] ptp/ptp_vmw: load ptp_vmw driver by directly probing the device
Date: Mon, 25 Aug 2025 16:11:35 -0700 [thread overview]
Message-ID: <20250825161135.44e97a4d@kernel.org> (raw)
In-Reply-To: <20250821110323.974367-3-ajay.kaher@broadcom.com>
On Thu, 21 Aug 2025 11:03:23 +0000 Ajay Kaher wrote:
> static int __init ptp_vmw_init(void)
> {
> - if (x86_hyper_type != X86_HYPER_VMWARE)
> - return -1;
> - return acpi_bus_register_driver(&ptp_vmw_acpi_driver);
> +
> + int error = -ENODEV;
> +
checkpatch says:
CHECK: Blank lines aren't necessary after an open brace '{'
#110: FILE: drivers/ptp/ptp_vmw.c:168:
{
+
--
pw-bot: cr
next prev parent reply other threads:[~2025-08-25 23:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 11:03 [PATCH 0/2] ptp/ptp_vmw: enhancements to ptp_vmw Ajay Kaher
2025-08-21 11:03 ` [PATCH 1/2] ptp/ptp_vmw: Implement PTP clock adjustments ops Ajay Kaher
2025-08-21 11:03 ` [PATCH 2/2] ptp/ptp_vmw: load ptp_vmw driver by directly probing the device Ajay Kaher
2025-08-25 23:11 ` Jakub Kicinski [this message]
2025-09-02 10:08 ` [PATCH 0/2] ptp/ptp_vmw: enhancements to ptp_vmw Ajay Kaher
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=20250825161135.44e97a4d@kernel.org \
--to=kuba@kernel.org \
--cc=ajay.kaher@broadcom.com \
--cc=alexey.makhalov@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hari-krishna.ginka@broadcom.com \
--cc=karen.wang@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nick.shi@broadcom.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=shubham-sg.gupta@broadcom.com \
--cc=tapas.kundu@broadcom.com \
--cc=vamsi-krishna.brahmajosyula@broadcom.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;
as well as URLs for NNTP newsgroup(s).