From: David Miller <davem@davemloft.net>
To: jezz@sysmic.org
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
afleming@freescale.com
Subject: Re: [PATCH] Remove nested function
Date: Thu, 08 Oct 2009 02:10:25 -0700 (PDT) [thread overview]
Message-ID: <20091008.021025.13024270.davem@davemloft.net> (raw)
In-Reply-To: <1254990863-15271-1-git-send-email-jezz@sysmic.org>
From: J=E9r=F4me Pouiller <jezz@sysmic.org>
Date: Thu, 8 Oct 2009 10:34:23 +0200
> Some toolchains dislike nested function definition, so we define func=
tion match
> outside of of_phy_find_device.
> =
> Signed-off-by: J=E9r=F4me Pouiller <jezz@sysmic.org>
Acked-by: David S. Miller <davem@davemloft.net>
prev parent reply other threads:[~2009-10-08 9:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 15:15 Nested function in drivers/of/of_mdio.c Jérôme Pouiller
2009-10-07 16:11 ` Grant Likely
2009-10-07 16:23 ` vb
2009-10-08 8:45 ` Jérôme Pouiller
2009-10-08 11:14 ` Gabriel Paubert
2009-10-08 8:34 ` [PATCH] Remove nested function Jérôme Pouiller
2009-10-08 9:10 ` 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=20091008.021025.13024270.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=afleming@freescale.com \
--cc=jezz@sysmic.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).