From: Jiri Pirko <jiri@resnulli.us>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: Bart Van Assche <bvanassche@acm.org>,
netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
linux-arm-kernel@lists.infradead.org,
Bagas Sanjaya <bagasdotme@gmail.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-clk@vger.kernel.org, Milena Olech <milena.olech@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net-next v3 1/9] dpll: documentation on DPLL subsystem interface
Date: Thu, 10 Aug 2023 08:45:28 +0200 [thread overview]
Message-ID: <ZNSHiOUiTbOAFIIR@nanopsycho> (raw)
In-Reply-To: <20230809214027.556192-2-vadim.fedorenko@linux.dev>
Wed, Aug 09, 2023 at 11:40:19PM CEST, vadim.fedorenko@linux.dev wrote:
>Add documentation explaining common netlink interface to configure DPLL
>devices and monitoring events. Common way to implement DPLL device in
>a driver is also covered.
>
>Co-developed-by: Bagas Sanjaya <bagasdotme@gmail.com>
>Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
>Signed-off-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
>Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Signed-off-by: Jiri Pirko <jiri@nvidia.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Pirko <jiri@resnulli.us>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: Jakub Kicinski <kuba@kernel.org>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Milena Olech <milena.olech@intel.com>,
Michal Michalik <michal.michalik@intel.com>,
linux-arm-kernel@lists.infradead.org, poros@redhat.com,
mschmidt@redhat.com, netdev@vger.kernel.org,
linux-clk@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>,
intel-wired-lan@lists.osuosl.org,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH net-next v3 1/9] dpll: documentation on DPLL subsystem interface
Date: Thu, 10 Aug 2023 08:45:28 +0200 [thread overview]
Message-ID: <ZNSHiOUiTbOAFIIR@nanopsycho> (raw)
In-Reply-To: <20230809214027.556192-2-vadim.fedorenko@linux.dev>
Wed, Aug 09, 2023 at 11:40:19PM CEST, vadim.fedorenko@linux.dev wrote:
>Add documentation explaining common netlink interface to configure DPLL
>devices and monitoring events. Common way to implement DPLL device in
>a driver is also covered.
>
>Co-developed-by: Bagas Sanjaya <bagasdotme@gmail.com>
>Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
>Signed-off-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
>Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Signed-off-by: Jiri Pirko <jiri@nvidia.com>
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Pirko <jiri@resnulli.us>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: Jakub Kicinski <kuba@kernel.org>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jonathan Lemon <jonathan.lemon@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Milena Olech <milena.olech@intel.com>,
Michal Michalik <michal.michalik@intel.com>,
linux-arm-kernel@lists.infradead.org, poros@redhat.com,
mschmidt@redhat.com, netdev@vger.kernel.org,
linux-clk@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>,
intel-wired-lan@lists.osuosl.org,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH net-next v3 1/9] dpll: documentation on DPLL subsystem interface
Date: Thu, 10 Aug 2023 08:45:28 +0200 [thread overview]
Message-ID: <ZNSHiOUiTbOAFIIR@nanopsycho> (raw)
In-Reply-To: <20230809214027.556192-2-vadim.fedorenko@linux.dev>
Wed, Aug 09, 2023 at 11:40:19PM CEST, vadim.fedorenko@linux.dev wrote:
>Add documentation explaining common netlink interface to configure DPLL
>devices and monitoring events. Common way to implement DPLL device in
>a driver is also covered.
>
>Co-developed-by: Bagas Sanjaya <bagasdotme@gmail.com>
>Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
>Signed-off-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
>Signed-off-by: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Signed-off-by: Jiri Pirko <jiri@nvidia.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-10 6:45 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 21:40 [Intel-wired-lan] [PATCH net-next v3 0/9] Create common DPLL configuration API Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` [Intel-wired-lan] [PATCH net-next v3 1/9] dpll: documentation on DPLL subsystem interface Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-10 6:45 ` Jiri Pirko [this message]
2023-08-10 6:45 ` Jiri Pirko
2023-08-10 6:45 ` Jiri Pirko
2023-08-09 21:40 ` [Intel-wired-lan] [PATCH net-next v3 2/9] dpll: spec: Add Netlink spec in YAML Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` [Intel-wired-lan] [PATCH net-next v3 3/9] dpll: core: Add DPLL framework base functions Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` [Intel-wired-lan] [PATCH net-next v3 4/9] dpll: netlink: " Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` [Intel-wired-lan] [PATCH net-next v3 5/9] netdev: expose DPLL pin handle for netdevice Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` [Intel-wired-lan] [PATCH net-next v3 6/9] ice: add admin commands to access cgu configuration Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-11 2:21 ` [Intel-wired-lan] " Jakub Kicinski
2023-08-11 2:21 ` Jakub Kicinski
2023-08-11 2:21 ` Jakub Kicinski
2023-08-11 9:30 ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-11 9:30 ` Vadim Fedorenko
2023-08-11 9:30 ` Vadim Fedorenko
2023-08-11 12:16 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-08-11 12:16 ` Kubalewski, Arkadiusz
2023-08-11 12:16 ` Kubalewski, Arkadiusz
2023-08-11 13:23 ` [Intel-wired-lan] " Vadim Fedorenko
2023-08-11 13:23 ` Vadim Fedorenko
2023-08-11 13:23 ` Vadim Fedorenko
2023-08-11 12:04 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2023-08-11 12:04 ` Kubalewski, Arkadiusz
2023-08-11 12:04 ` Kubalewski, Arkadiusz
2023-08-09 21:40 ` [Intel-wired-lan] [PATCH net-next v3 7/9] ice: implement dpll interface to control cgu Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-10 6:43 ` [Intel-wired-lan] " Jiri Pirko
2023-08-10 6:43 ` Jiri Pirko
2023-08-10 6:43 ` Jiri Pirko
2023-08-09 21:40 ` [Intel-wired-lan] [PATCH net-next v3 8/9] ptp_ocp: implement DPLL ops Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` [Intel-wired-lan] [PATCH net-next v3 9/9] mlx5: Implement SyncE support using DPLL infrastructure Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
2023-08-09 21:40 ` Vadim Fedorenko
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=ZNSHiOUiTbOAFIIR@nanopsycho \
--to=jiri@resnulli.us \
--cc=bagasdotme@gmail.com \
--cc=bvanassche@acm.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=milena.olech@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vadim.fedorenko@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.