From: David Miller <davem@davemloft.net>
To: claudiu.manoil@freescale.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/6] gianfar: Device configuration fixes
Date: Tue, 18 Feb 2014 15:03:26 -0500 (EST) [thread overview]
Message-ID: <20140218.150326.345866777429417518.davem@davemloft.net> (raw)
In-Reply-To: <1392634399-5456-1-git-send-email-claudiu.manoil@freescale.com>
From: Claudiu Manoil <claudiu.manoil@freescale.com>
Date: Mon, 17 Feb 2014 12:53:13 +0200
> This patchset represents the first part of an effort
> to solve some old device configuration issues in gianfar,
> especially run-time reset and re-configuration problems.
> I'm referring to "on-the-fly" configuration of registers
> against HW specification, concurrency issues during device
> reset / re-configuration operations, and implementing HW
> advisories for these operations.
>
> There's also a good deal of code cleanup and refactoring,
> and some other (minor) fixes as well.
>
> Thank you.
Series applied, thanks.
prev parent reply other threads:[~2014-02-18 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 10:53 [PATCH net-next v2 0/6] gianfar: Device configuration fixes Claudiu Manoil
2014-02-17 10:53 ` [PATCH net-next v2 1/6] gianfar: Cleanup/Fix gfar_probe and the hw init code Claudiu Manoil
2014-02-17 10:53 ` [PATCH net-next v2 2/6] gianfar: Remove sysfs stubs for FIFOCFG and stashing Claudiu Manoil
2014-02-17 10:53 ` [PATCH net-next v2 3/6] gianfar: Remove useless HAS_PADDING device flag Claudiu Manoil
2014-02-17 10:53 ` [PATCH net-next v2 4/6] gianfar: Factor out enabling/disabling of hw interrupts Claudiu Manoil
2014-02-17 10:53 ` [PATCH net-next v2 5/6] gianfar: Add missing graceful reset steps and fixes Claudiu Manoil
2014-02-17 10:53 ` [PATCH net-next v2 6/6] gianfar: Remove clean_rx_ring race from gfar_ethtool Claudiu Manoil
2014-02-18 20:03 ` 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=20140218.150326.345866777429417518.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=claudiu.manoil@freescale.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