netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] (net-2.6) stmmac update - Apr 2010
Date: Tue, 13 Apr 2010 12:00:09 +0200	[thread overview]
Message-ID: <4BC440A9.5000008@st.com> (raw)
In-Reply-To: <20100413.015352.223941252.davem@davemloft.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi David,

On 04/13/2010 10:53 AM, David Miller wrote:
> From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
> Date: Fri,  9 Apr 2010 12:24:15 +0200
> 
>> Hello,
>> this is another subset of patches to make the driver more generic.
>>
>> This patches splits the dma and core code for the mac 10/100 device
>> (as already done for the gmac) and reorganizes the descriptor
>> structures.
>> In the first version of the driver, the mac10/100 could only use
>> normal descriptors and the gmac could only use the enhanced ones.
>> This limit has been removed and this kind of information comes
>> from the platform.
> 
> Please:
> 
> 1) respin your patches against net-next-2.6

I'll do this soon.

> 2) Add numbers to your patch posting subject lines so there
>    is no confusion about what order your patches should be
>    applied.

Oops! you are right. Thanks!

> 
> 3) Make sure the driver compiles successfully at each step
>    of applying your patches, not just after all the changes
>    are applied.

Sure! I test this always.

Many thanks.

Best Regards
Giuseppe

> Thanks.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJLxECpAAoJEAm9vY9TshdvuH8H/RbUTVa+o7qJjRyXgb34h5t4
KSwdcnWwY90d2i/3zLvWlwaSn4J5zrSWc6EdXRpU/1zBI+xcQ0wAFieqF8R0QOoE
qIKliOPCJ7NrsV30J4xhe2R0q7e423vmTdUfcNB1VXqBaZOQOPZmKjApRT240c6E
CwLfTANwAQ6t8pl6rlyww/nTEPuOVx0ETvAGEfHloWa3Sr5TvgXndfD2dnDU9cs1
wgg/6YzehTRioMM3Rf7KySuVMcENbCkyy3R4zSNvwJONZqVqMkTWDZ1XIpq3BvpV
r2AAjXdXtVB2Z6lroP2UVCrYLcm3LB0WUdzTqrj0zpzW9cm1DEOb2nhjcWVLNHY=
=h25h
-----END PGP SIGNATURE-----

      reply	other threads:[~2010-04-13 10:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09 10:24 [PATCH] (net-2.6) stmmac update - Apr 2010 Giuseppe CAVALLARO
2010-04-09 10:24 ` [PATCH] stmmac: split core and dma for the mac10/100 Giuseppe CAVALLARO
2010-04-09 10:24   ` [PATCH] stmmac: rework normal and enhanced descriptors Giuseppe CAVALLARO
2010-04-09 10:24     ` [PATCH] stmmac: fix Transmit FIFO flush operation Giuseppe CAVALLARO
2010-04-09 10:24       ` [PATCH] stmmac: new descriptor field for the driver's platform Giuseppe CAVALLARO
2010-04-09 10:24         ` [PATCH] stmmac: get the descriptor structure from platform Giuseppe CAVALLARO
2010-04-09 10:24           ` [PATCH] stmmac: fix vlan support setup Giuseppe CAVALLARO
2010-04-09 10:24             ` [PATCH] stmmac: updated the drv module version Giuseppe CAVALLARO
2010-04-13  8:53 ` [PATCH] (net-2.6) stmmac update - Apr 2010 David Miller
2010-04-13 10:00   ` Giuseppe CAVALLARO [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=4BC440A9.5000008@st.com \
    --to=peppe.cavallaro@st.com \
    --cc=davem@davemloft.net \
    --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).