From: m-karicheri2@ti.com (Murali Karicheri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 2/3] net: Add Keystone NetCP ethernet driver
Date: Thu, 11 Dec 2014 09:14:37 -0500 [thread overview]
Message-ID: <5489A6CD.20909@ti.com> (raw)
In-Reply-To: <20141210.204110.618599360537141819.davem@davemloft.net>
On 12/10/2014 08:41 PM, David Miller wrote:
> From: Murali Karicheri<m-karicheri2@ti.com>
> Date: Wed, 10 Dec 2014 16:31:02 -0500
>
>> Are you referring to the static code analyser sparse that is invoked
>> through?
>
> You have to explicitly enable endian checking, it's not on by
> default.
Thanks David and others who responded. Let me do this and resolve any
warning before the next post.
BTW, could you provide any suggestions that would help us merge this
series to upstream? This has been sitting on this list for a while now.
Thanks and regards,
--
Murali Karicheri
Linux Kernel, Texas Instruments
next prev parent reply other threads:[~2014-12-11 14:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 21:41 [PATCH v7 0/3] net: Add Keystone NetCP ethernet driver support Murali Karicheri
2014-12-02 21:41 ` [PATCH v7 1/3] Documentation: dt: net: Add binding doc for Keystone NetCP ethernet driver Murali Karicheri
2014-12-02 21:41 ` [PATCH v7 3/3] MAINTAINER: net: Add TI NETCP Ethernet driver entry Murali Karicheri
[not found] ` <1417556503-22290-3-git-send-email-m-karicheri2@ti.com>
2014-12-09 18:10 ` [PATCH v7 2/3] net: Add Keystone NetCP ethernet driver David Miller
2014-12-10 21:31 ` Murali Karicheri
2014-12-11 1:41 ` David Miller
2014-12-11 3:04 ` default enable sparse __CHECK_ENDIAN__ (was: Re: [PATCH v7 2/3] net: Add Keystone NetCP ethernet driver) Joe Perches
2014-12-11 11:18 ` Marcel Holtmann
2014-12-11 14:14 ` Murali Karicheri [this message]
2014-12-11 17:01 ` [PATCH v7 2/3] net: Add Keystone NetCP ethernet driver David Miller
2014-12-11 17:17 ` Murali Karicheri
2014-12-11 18:34 ` Joe Perches
2014-12-11 20:21 ` Murali Karicheri
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=5489A6CD.20909@ti.com \
--to=m-karicheri2@ti.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).