From: David Miller <davem@davemloft.net>
To: f.fainelli@gmail.com
Cc: netdev@vger.kernel.org, scott.branden@broadcom.com,
andrew@lunn.ch, abhishek.shah@broadcom.com, ray.jui@broadcom.com,
linux-kernel@vger.kernel.org, jon.mason@broadcom.com,
nbd@nbd.name
Subject: Re: [PATCH net 0/2] net: bgmac: Couple of sparse warnings
Date: Mon, 02 Apr 2018 13:18:17 -0400 (EDT) [thread overview]
Message-ID: <20180402.131817.1826947706300918872.davem@davemloft.net> (raw)
In-Reply-To: <f9e08df4-f9fa-25d1-ad3e-a0d221e92b6d@gmail.com>
From: Florian Fainelli <f.fainelli@gmail.com>
Date: Mon, 2 Apr 2018 10:17:36 -0700
> On 04/01/2018 07:21 PM, David Miller wrote:
>> From: Florian Fainelli <f.fainelli@gmail.com>
>> Date: Sun, 1 Apr 2018 10:26:28 -0700
>>
>>> This patch series fixes a couple of warnings reported by sparse, should not
>>> cause any functional problems since bgmac is typically used on LE platforms
>>> anyway.
>>
>> Series applied, thanks Florian.
>
> I did not see this in net/master or included in your recent pull request
> to Linus, not a big deal, but I just want to make sure this is not lost
> somewhere ;)
All changes go into net-next as I prepare for a merge window pull request.
prev parent reply other threads:[~2018-04-02 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 17:26 [PATCH net 0/2] net: bgmac: Couple of sparse warnings Florian Fainelli
2018-04-01 17:26 ` [PATCH net 1/2] net: bgmac: Correctly annotate register space Florian Fainelli
2018-04-01 17:26 ` [PATCH net 2/2] net: bgmac: Fix endian access in bgmac_dma_tx_ring_free() Florian Fainelli
2018-04-02 2:21 ` [PATCH net 0/2] net: bgmac: Couple of sparse warnings David Miller
2018-04-02 17:17 ` Florian Fainelli
2018-04-02 17:18 ` David Miller [this message]
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=20180402.131817.1826947706300918872.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=abhishek.shah@broadcom.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=jon.mason@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=ray.jui@broadcom.com \
--cc=scott.branden@broadcom.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;
as well as URLs for NNTP newsgroup(s).