From: "Maciej W. Rozycki" <macro@linux-mips•org>
To: David Miller <davem@davemloft•net>
Cc: sergei.shtylyov@cogentembedded•com, netdev@vger•kernel.org
Subject: Re: [PATCH v2] declance: Remove `incompatible pointer type' warnings
Date: Sun, 29 Sep 2013 01:09:08 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.03.1309290107450.8907@linux-mips.org> (raw)
In-Reply-To: <20130928.153316.1766304011894422920.davem@davemloft.net>
On Sat, 28 Sep 2013, David Miller wrote:
> > Thanks, by Sergei's request please use this version instead that has the
> > reference to the original commit updated (no change to the patch itself).
>
> I can't undo the original commit once it has been installed in my tree.
No worries, and good to know, thanks.
Maciej
next prev parent reply other threads:[~2013-09-29 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 23:49 [PATCH] declance: Remove `incompatible pointer type' warnings Maciej W. Rozycki
2013-09-20 18:43 ` David Miller
2013-09-22 20:19 ` [PATCH v2] " Maciej W. Rozycki
2013-09-28 22:33 ` David Miller
2013-09-29 0:09 ` Maciej W. Rozycki [this message]
2013-09-21 22:41 ` [PATCH] " Sergei Shtylyov
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=alpine.LFD.2.03.1309290107450.8907@linux-mips.org \
--to=macro@linux-mips$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sergei.shtylyov@cogentembedded$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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