From: Arnd Bergmann <arnd@arndb.de>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
davem@davemloft.net
Subject: Re: [PATCH v1 2/4] soc: ti: knav_dma: rename pad in struct knav_dma_desc to sw_data
Date: Fri, 19 Feb 2016 15:33:17 +0100 [thread overview]
Message-ID: <4255231.ICxc506b9g@wuerfel> (raw)
In-Reply-To: <1455824777-15571-2-git-send-email-m-karicheri2@ti.com>
On Thursday 18 February 2016 14:46:15 Murali Karicheri wrote:
> Rename the pad to sw_data as per description of this field in the hardware
> spec(refer sprugr9 from www.ti.com). Latest version of the document is
> at http://www.ti.com/lit/ug/sprugr9h/sprugr9h.pdf and section 3.1
> Host Packet Descriptor describes this field.
>
> Also define and use a constant for the size of sw_data field similar to
> other fields in the struct for desc and document the sw_data field
> in the header. As the sw_data is not touched by hw, it's type can be
> changed to u32.
>
>
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2016-02-19 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 19:46 [PATCH v1 1/4] net: ti: netcp: restore get/set_pad_info() functionality Murali Karicheri
2016-02-18 19:46 ` [PATCH v1 2/4] soc: ti: knav_dma: rename pad in struct knav_dma_desc to sw_data Murali Karicheri
2016-02-19 14:33 ` Arnd Bergmann [this message]
2016-02-18 19:46 ` [PATCH v1 3/4] net: netcp: rename {get/set}pad_info to {get/set}_sw_data Murali Karicheri
2016-02-19 14:37 ` Arnd Bergmann
2016-02-19 16:49 ` Murali Karicheri
2016-02-19 17:22 ` Murali Karicheri
2016-02-18 19:46 ` [PATCH v1 4/4] net: netcp: rework the code for get/set sw_data in dma desc Murali Karicheri
2016-02-19 14:41 ` [PATCH v1 1/4] net: ti: netcp: restore get/set_pad_info() functionality Arnd Bergmann
2016-02-19 15:48 ` Murali Karicheri
2016-02-19 16:41 ` Arnd Bergmann
2016-02-19 16:48 ` Murali Karicheri
2016-02-19 18:01 ` Murali Karicheri
2016-02-19 20:59 ` Arnd Bergmann
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=4255231.ICxc506b9g@wuerfel \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--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 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).