From: Marek Vasut <marex@denx.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: davem@davemloft.net, s.hauer@pengutronix.de,
shawn.guo@linaro.org, netdev@vger.kernel.org,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH 1/2] net: fec: Do a sanity check on the gpio number
Date: Sun, 17 Feb 2013 11:32:37 +0100 [thread overview]
Message-ID: <201302171132.37529.marex@denx.de> (raw)
In-Reply-To: <1361055207-22870-1-git-send-email-festevam@gmail.com>
Dear Fabio Estevam,
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Since commit 372e722ea4d (gpiolib: use descriptors internally) the
> following warning is seen on a mx28evk board:
[...]
I wonder if some dev_dbg() won't be a good idea here. Otherwise:
Acked-by: Marek Vasut <marex@denx.de>
Best regards,
Marek Vasut
prev parent reply other threads:[~2013-02-17 10:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 22:53 [PATCH 1/2] net: fec: Do a sanity check on the gpio number Fabio Estevam
2013-02-16 22:53 ` [PATCH 2/2] net: fec: Improve logging Fabio Estevam
2013-02-17 10:33 ` Marek Vasut
2013-02-17 11:55 ` Shawn Guo
2013-02-17 13:41 ` Fabio Estevam
2013-02-17 15:08 ` Shawn Guo
2013-02-17 5:32 ` [PATCH 1/2] net: fec: Do a sanity check on the gpio number Shawn Guo
2013-02-17 10:32 ` Marek Vasut [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=201302171132.37529.marex@denx.de \
--to=marex@denx.de \
--cc=davem@davemloft.net \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.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).