From: Mugunthan V N <mugunthanvnm@ti.com>
To: Daniel Mack <zonque@gmail.com>
Cc: netdev@vger.kernel.org, bcousson@baylibre.com, nsekhar@ti.com,
sergei.shtylyov@cogentembedded.com, davem@davemloft.net,
ujhelyi.m@gmail.com, vaibhav.bedia@ti.com, d-gerlach@ti.com,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v5 0/5] cpsw: support for control module register
Date: Sat, 24 Aug 2013 00:43:20 +0530 [thread overview]
Message-ID: <5217B450.6060006@ti.com> (raw)
In-Reply-To: <1377283987-20040-1-git-send-email-zonque@gmail.com>
On Saturday 24 August 2013 12:23 AM, Daniel Mack wrote:
> Note that for personal reasons, I won't be able to work on that patch
> set for two weeks, starting from a few hours from now. If there are any
> more objections or comments, I'll catch up after that period. Or if
> anyone wants to make minor changes to my patches and resubmit them,
> I'd also be fine with that :)
>
> The compatible discussion is still ongoing, but I'd rather submit what
> I got until now, and I'm also still convinced that having
> ti,am3352-cpsw is still the best we can do.
Apart from the DT compatibility discussion this patch series looks good
to me.
Acked-by: Mugunthan V N <mugunthanvnm@ti.com>
Regards
Mugunthan V N
WARNING: multiple messages have this Message-ID (diff)
From: mugunthanvnm@ti.com (Mugunthan V N)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 0/5] cpsw: support for control module register
Date: Sat, 24 Aug 2013 00:43:20 +0530 [thread overview]
Message-ID: <5217B450.6060006@ti.com> (raw)
In-Reply-To: <1377283987-20040-1-git-send-email-zonque@gmail.com>
On Saturday 24 August 2013 12:23 AM, Daniel Mack wrote:
> Note that for personal reasons, I won't be able to work on that patch
> set for two weeks, starting from a few hours from now. If there are any
> more objections or comments, I'll catch up after that period. Or if
> anyone wants to make minor changes to my patches and resubmit them,
> I'd also be fine with that :)
>
> The compatible discussion is still ongoing, but I'd rather submit what
> I got until now, and I'm also still convinced that having
> ti,am3352-cpsw is still the best we can do.
Apart from the DT compatibility discussion this patch series looks good
to me.
Acked-by: Mugunthan V N <mugunthanvnm@ti.com>
Regards
Mugunthan V N
WARNING: multiple messages have this Message-ID (diff)
From: Mugunthan V N <mugunthanvnm@ti.com>
To: Daniel Mack <zonque@gmail.com>
Cc: <netdev@vger.kernel.org>, <bcousson@baylibre.com>,
<nsekhar@ti.com>, <sergei.shtylyov@cogentembedded.com>,
<davem@davemloft.net>, <ujhelyi.m@gmail.com>,
<vaibhav.bedia@ti.com>, <d-gerlach@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-omap@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v5 0/5] cpsw: support for control module register
Date: Sat, 24 Aug 2013 00:43:20 +0530 [thread overview]
Message-ID: <5217B450.6060006@ti.com> (raw)
In-Reply-To: <1377283987-20040-1-git-send-email-zonque@gmail.com>
On Saturday 24 August 2013 12:23 AM, Daniel Mack wrote:
> Note that for personal reasons, I won't be able to work on that patch
> set for two weeks, starting from a few hours from now. If there are any
> more objections or comments, I'll catch up after that period. Or if
> anyone wants to make minor changes to my patches and resubmit them,
> I'd also be fine with that :)
>
> The compatible discussion is still ongoing, but I'd rather submit what
> I got until now, and I'm also still convinced that having
> ti,am3352-cpsw is still the best we can do.
Apart from the DT compatibility discussion this patch series looks good
to me.
Acked-by: Mugunthan V N <mugunthanvnm@ti.com>
Regards
Mugunthan V N
next prev parent reply other threads:[~2013-08-23 19:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 18:53 [PATCH v5 0/5] cpsw: support for control module register Daniel Mack
2013-08-23 18:53 ` Daniel Mack
2013-08-23 18:53 ` [PATCH v5 1/5] net: ethernet: cpsw: switch to devres allocations Daniel Mack
2013-08-23 18:53 ` Daniel Mack
2013-08-23 18:53 ` [PATCH v5 2/5] net: ethernet: cpsw: add optional third memory region for CONTROL module Daniel Mack
2013-08-23 18:53 ` Daniel Mack
2013-08-23 19:10 ` Sergei Shtylyov
2013-08-23 19:10 ` Sergei Shtylyov
2013-08-23 19:14 ` Daniel Mack
2013-08-23 19:14 ` Daniel Mack
2013-08-23 18:53 ` [PATCH v5 3/5] net: ethernet: cpsw: introduce ti,am3352-cpsw compatible string Daniel Mack
2013-08-23 18:53 ` [PATCH v5 3/5] net: ethernet: cpsw: introduce ti, am3352-cpsw " Daniel Mack
2013-08-23 18:53 ` [PATCH v5 4/5] net: ethernet: cpsw: add support for hardware interface mode config Daniel Mack
2013-08-23 18:53 ` Daniel Mack
2013-08-23 19:18 ` Sergei Shtylyov
2013-08-23 19:18 ` Sergei Shtylyov
2013-08-23 18:53 ` [PATCH v5 5/5] ARM: dts: am33xx: adopt to cpsw changes Daniel Mack
2013-08-23 18:53 ` Daniel Mack
2013-08-23 19:13 ` Mugunthan V N [this message]
2013-08-23 19:13 ` [PATCH v5 0/5] cpsw: support for control module register Mugunthan V N
2013-08-23 19:13 ` Mugunthan V N
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=5217B450.6060006@ti.com \
--to=mugunthanvnm@ti.com \
--cc=bcousson@baylibre.com \
--cc=d-gerlach@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=ujhelyi.m@gmail.com \
--cc=vaibhav.bedia@ti.com \
--cc=zonque@gmail.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 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.