From: David Miller <davem@davemloft.net>
To: m-karicheri2@ti.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, arnd@arndb.de
Subject: Re: [PATCH v2 0/3] net: ti: netcp: restore get/set_pad_info() functionality
Date: Sun, 21 Feb 2016 22:02:50 -0500 (EST) [thread overview]
Message-ID: <20160221.220250.1363843818216677470.davem@davemloft.net> (raw)
In-Reply-To: <1455904724-17952-1-git-send-email-m-karicheri2@ti.com>
From: Murali Karicheri <m-karicheri2@ti.com>
Date: Fri, 19 Feb 2016 12:58:41 -0500
> This series fixes a regression and add some improvements for the ease
> of maintainance. Incorporated comments against v1.
>
> Changelogs:
>
> v2 : combined 2-3 into one patch as this involves a header change
> fixed a parse warning in 3/4 per comment from Arnd.
> Removed Sign-off from Arnd against 1/4
> added comments in 3/3 to alert on the usage of sw data per review
> comments
> v1 : added 2-4 to accomodate feedback received from review
> v0 : initial version to fix the regression (From Grygorii)
Series applied, thanks.
prev parent reply other threads:[~2016-02-22 3:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 17:58 [PATCH v2 0/3] net: ti: netcp: restore get/set_pad_info() functionality Murali Karicheri
2016-02-19 17:58 ` [PATCH v2 1/3] " Murali Karicheri
2016-02-19 20:56 ` Arnd Bergmann
2016-02-19 17:58 ` [PATCH v2 2/3] soc: ti: knav_dma: rename pad in struct knav_dma_desc to sw_data Murali Karicheri
2016-02-19 20:55 ` Arnd Bergmann
2016-02-19 17:58 ` [PATCH v2 3/3] net: netcp: rework the code for get/set sw_data in dma desc Murali Karicheri
2016-02-19 20:55 ` Arnd Bergmann
2016-02-19 22:21 ` Murali Karicheri
2016-02-19 22:25 ` Arnd Bergmann
2016-02-22 17:04 ` Murali Karicheri
2016-02-22 3:02 ` 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=20160221.220250.1363843818216677470.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=arnd@arndb.de \
--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).