From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Simon Horman <simon.horman@corigine.com>
Cc: netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [RFC PATCH net-next] net: dsa: replace NETDEV_PRE_CHANGE_HWTSTAMP notifier with a stub
Date: Thu, 6 Apr 2023 14:45:04 +0300 [thread overview]
Message-ID: <20230406114504.5d6sgg653hw5an7f@skbuf> (raw)
In-Reply-To: <ZC5vn9lNyUgWwlaR@corigine.com>
On Thu, Apr 06, 2023 at 09:07:11AM +0200, Simon Horman wrote:
> On Wed, Apr 05, 2023 at 11:08:52PM +0300, Vladimir Oltean wrote:
> > On Wed, Apr 05, 2023 at 11:07:05PM +0300, Vladimir Oltean wrote:
> > > On Wed, Apr 05, 2023 at 10:05:15PM +0200, Simon Horman wrote:
> > > > nit: clang-16 tells me that err is uninitialised here if dsa_stubs is false.
> > > > nit: clang-16 tell me that extack is now unused in this function.
> > >
> > > Thanks, all good points. Thank clang-16 on my behalf!
> >
> > Perhaps I shouldn't have left it there. I'll start looking into setting
> > up a toolchain with that for my own builds.
>
> I did this a few weeks back using the toolchain at the link below.
> It was quite a simple process. And well worth the effort.
>
> https://mirrors.edge.kernel.org/pub/tools/llvm/
Thanks, I did set this up yesterday, using Documentation/kbuild/llvm.rst
as a guide.
next prev parent reply other threads:[~2023-04-06 11:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 16:51 [RFC PATCH net-next] net: dsa: replace NETDEV_PRE_CHANGE_HWTSTAMP notifier with a stub Vladimir Oltean
2023-04-05 16:56 ` Vladimir Oltean
2023-04-05 20:05 ` Simon Horman
2023-04-05 20:07 ` Vladimir Oltean
2023-04-05 20:08 ` Vladimir Oltean
2023-04-06 7:07 ` Simon Horman
2023-04-06 11:45 ` Vladimir Oltean [this message]
2023-04-05 20:31 ` Vladimir Oltean
2023-04-06 7:12 ` Simon Horman
2023-04-06 2:08 ` Jakub Kicinski
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=20230406114504.5d6sgg653hw5an7f@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.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