From: Paolo Abeni <pabeni@redhat.com>
To: "Lucero Palau, Alejandro" <alejandro.lucero-palau@amd.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-net-drivers (AMD-Xilinx)" <linux-net-drivers@amd.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"habetsm.xilinx@gmail.com" <habetsm.xilinx@gmail.com>,
"ecree.xilinx@gmail.com" <ecree.xilinx@gmail.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"corbet@lwn.net" <corbet@lwn.net>,
"jiri@nvidia.com" <jiri@nvidia.com>
Subject: Re: [PATCH] sfc: fix builds without CONFIG_RTC_LIB
Date: Fri, 17 Feb 2023 17:46:59 +0100 [thread overview]
Message-ID: <07293a5cbb4ac1680d7b737105b1c308d626a72c.camel@redhat.com> (raw)
In-Reply-To: <DM6PR12MB420241B35AB4B8846AB4F568C1A19@DM6PR12MB4202.namprd12.prod.outlook.com>
On Fri, 2023-02-17 at 15:30 +0000, Lucero Palau, Alejandro wrote:
> BTW, I did not send the net-next tag what I'm not sure if it is required
> (I would say so).
>
> Should I add it?
Indeed is required and you should add it when you will post v2.
Thanks,
Paolo
next prev parent reply other threads:[~2023-02-17 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 10:22 [PATCH] sfc: fix builds without CONFIG_RTC_LIB alejandro.lucero-palau
2023-02-17 14:47 ` Alexander Lobakin
2023-02-17 15:20 ` Lucero Palau, Alejandro
2023-02-17 15:30 ` Lucero Palau, Alejandro
2023-02-17 16:46 ` Paolo Abeni [this message]
2023-02-23 15:29 ` Alexander Lobakin
2023-02-17 15:13 ` Manank Patel
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=07293a5cbb4ac1680d7b737105b1c308d626a72c.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=alejandro.lucero-palau@amd.com \
--cc=aleksander.lobakin@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
/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