From: Claudiu Manoil <claudiu.manoil@nxp.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>
Subject: RE: [PATCH net-next 0/2] enetc: Clean endianness warnings up
Date: Thu, 19 Nov 2020 10:18:00 +0000 [thread overview]
Message-ID: <DB8PR04MB6764480610C5FC6311BB03BF96E00@DB8PR04MB6764.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20201118095435.633a6e2e@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
>-----Original Message-----
>From: Jakub Kicinski <kuba@kernel.org>
[...]
>Subject: Re: [PATCH net-next 0/2] enetc: Clean endianness warnings up
>
>On Wed, 18 Nov 2020 09:52:58 -0800 Jakub Kicinski wrote:
>> On Tue, 17 Nov 2020 20:20:02 +0200 Claudiu Manoil wrote:
>> > Cleanup patches to address the outstanding endianness issues
>> > in the driver reported by sparse.
>>
>> Build bot says this doesn't apply to net-next, could you double check?
>
>Hm, not sure what happened there, it does seem to apply now.
>
>Could you resend regardless? Would be good to get this build tested.
Reformatted and resent patches.
next prev parent reply other threads:[~2020-11-19 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 18:20 [PATCH net-next 0/2] enetc: Clean endianness warnings up Claudiu Manoil
2020-11-17 18:20 ` [PATCH net-next 1/2] enetc: Fix endianness issues for enetc_ethtool Claudiu Manoil
2020-11-17 18:20 ` [PATCH net-next 2/2] enetc: Fix endianness issues for enetc_qos Claudiu Manoil
2020-11-18 17:52 ` [PATCH net-next 0/2] enetc: Clean endianness warnings up Jakub Kicinski
2020-11-18 17:54 ` Jakub Kicinski
2020-11-19 10:18 ` Claudiu Manoil [this message]
2020-11-25 22:55 ` 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=DB8PR04MB6764480610C5FC6311BB03BF96E00@DB8PR04MB6764.eurprd04.prod.outlook.com \
--to=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--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 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.