From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: stmmac patches...
Date: Mon, 23 Nov 2009 09:57:53 +0100 [thread overview]
Message-ID: <4B0A4E91.3050509@st.com> (raw)
In-Reply-To: <20091120.094019.163421376.davem@davemloft.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi David,
David Miller wrote:
> From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
> Date: Fri, 20 Nov 2009 08:19:14 +0100
>
>>> Please fix this up and resubmit both of your patches.
>> I've just resent the second patch:
>> [PATCH (RESENT)] stmmac: do not fail when the timer cannot be used.
>> Let me know if I have to review something in my first patch as well.
>
> I explicitly asked you to resubmit both patches, so that I would have
> them in a group together to apply to my tree.
I'm sending them at once.
> When changes are requested in some patches within a group, I mark
> the entire group in patchwork with state 'changed requested' and
> that's why I ask for the whole series to be resubmitted.
>
> This means you should have resent the first patch even though I did
> not ask you to make any changes to it.
Thanks David for this. I know that it's not easy to manage an huge
amount of patches (especially when these have some defects ;-) ). My
personal goal is to sent patches clean and well done too.
Regards,
Peppe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAksKTpEACgkQ2Xo3j31MSSI3XACfVFcY9yj2fzFOplC8A1oma9lp
6QYAmgNdMKvJt+MyUAZHsIqjqDpDAwdD
=Z6CD
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2009-11-23 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 20:18 stmmac patches David Miller
2009-11-20 7:19 ` Giuseppe CAVALLARO
2009-11-20 17:40 ` David Miller
2009-11-23 8:57 ` 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=4B0A4E91.3050509@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 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.