From: Anton Vorontsov <anton@enomsg.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
devicetree@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] ab8500-charger: we print an unintended error message
Date: Tue, 27 Aug 2013 18:13:42 -0700 [thread overview]
Message-ID: <20130828011342.GB10506@lizard> (raw)
In-Reply-To: <20130827011942.GD17061@elgon.mountain>
On Tue, Aug 27, 2013 at 04:19:42AM +0300, Dan Carpenter wrote:
> There is a missing break statement here, so we print an error message
> that the USB type is invalid. The original code still works fine
> though except for the error message.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Applied, thanks a lot!
Anton
prev parent reply other threads:[~2013-08-28 1:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 1:19 [patch] ab8500-charger: we print an unintended error message Dan Carpenter
2013-08-28 1:13 ` Anton Vorontsov [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=20130828011342.GB10506@lizard \
--to=anton@enomsg.org \
--cc=dan.carpenter@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=grant.likely@linaro.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=rob.herring@calxeda.com \
/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).