From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
Andrey Konovalov <andreyknvl@google.com>,
David Miller <davem@davemloft.net>,
linux-can@vger.kernel.org,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>,
Kostya Serebryany <kcc@google.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH] can: fix warning in bcm_connect/proc_register
Date: Fri, 28 Oct 2016 10:58:53 +0200 [thread overview]
Message-ID: <29de7555-9a84-0b29-3e49-a96fa26390f0@pengutronix.de> (raw)
In-Reply-To: <CAM_iQpUVB3g6gq9-RX0QAzM_ojOS0q+jq9n9objyFwyTHPAgkw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 525 bytes --]
On 10/27/2016 06:28 PM, Cong Wang wrote:
>>> Hmm, bo->bound should guarantee it, so never mind, your patch
>>> looks fine.
>>
>> Can I add your Acked-by?
>
> Of course.
>
> Acked-by: Cong Wang <xiyou.wangcong@gmail.com>
Thanks,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2016-10-28 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 19:11 [PATCH] can: fix warning in bcm_connect/proc_register Oliver Hartkopp
2016-10-24 20:10 ` Cong Wang
2016-10-24 20:17 ` Cong Wang
2016-10-25 12:12 ` Andrey Konovalov
2016-10-27 8:45 ` Marc Kleine-Budde
2016-10-27 16:28 ` Cong Wang
2016-10-28 8:58 ` Marc Kleine-Budde [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=29de7555-9a84-0b29-3e49-a96fa26390f0@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=andreyknvl@google.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=glider@google.com \
--cc=kcc@google.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=syzkaller@googlegroups.com \
--cc=xiyou.wangcong@gmail.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).