From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: "Lucero Palau, Alejandro" <alejandro.lucero-palau@amd.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>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"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: Thu, 23 Feb 2023 16:29:16 +0100 [thread overview]
Message-ID: <9a433778-9360-6322-bb74-6e0f51614c8c@intel.com> (raw)
In-Reply-To: <DM6PR12MB4202D1FA796BF66E6AD4C6C0C1A19@DM6PR12MB4202.namprd12.prod.outlook.com>
From: Lucero Palau, Alejandro <alejandro.lucero-palau@amd.com>
Date: Fri, 17 Feb 2023 15:20:27 +0000
>
> On 2/17/23 14:47, Alexander Lobakin wrote:
>> From: Lucero Palau, Alejandro <alejandro.lucero-palau@amd.com>
>> Date: Fri, 17 Feb 2023 10:22:36 +0000
>>
>>> From: Alejandro Lucero <alejandro.lucero-palau@amd.com>
>>>
>>> Adding an embarrasing missing semicolon precluding kernel building
>> :D
>>
>> 'Embarrassing' tho, with two 's'. And I guess "embarrassingly missed",
>> since a semicolon itself can't be "embarrassing" I believe? :D
>
> This is going worse ... :D
>
> I'll change it.
>
>> + "add", not "adding"
>> + "precluding"? You mean "breaking"?
>
> Preclude: "prevent from happening; make impossible."
Now I'm embarrassed xD You can leave it as it is, it's my dictionary's
fault :D
>
> But I can use breaking instead.
>
> Thanks!
Thanks,
Olek
next prev parent reply other threads:[~2023-02-23 15:30 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
2023-02-23 15:29 ` Alexander Lobakin [this message]
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=9a433778-9360-6322-bb74-6e0f51614c8c@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=alejandro.lucero-palau@amd.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 \
--cc=pabeni@redhat.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