From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM:net: an issue for k which is u32, never < 0
Date: Mon, 11 Mar 2013 16:47:41 +0000 [thread overview]
Message-ID: <20130311164741.GL4977@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130310.171238.330349067962026661.davem@davemloft.net>
On Sun, Mar 10, 2013 at 05:12:38PM -0400, David Miller wrote:
> From: Chen Gang <gang.chen@asianux.com>
> Date: Sun, 10 Mar 2013 10:15:54 +0800
>
> >
> > k is u32 which never < 0, need type cast, or cause issue.
> >
> > Signed-off-by: Chen Gang <gang.chen@asianux.com>
>
> Who will apply this, ARM folks or me?
I'm happy if you wish to take the patch:
Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>
Thanks.
next prev parent reply other threads:[~2013-03-11 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 2:15 [PATCH] ARM:net: an issue for k which is u32, never < 0 Chen Gang
2013-03-10 21:12 ` David Miller
2013-03-11 4:53 ` Chen Gang
2013-03-11 16:47 ` Russell King - ARM Linux [this message]
2013-03-12 0:01 ` Chen Gang
2013-03-12 15:33 ` David Miller
2013-03-11 16:54 ` Mircea Gherzan
2013-03-12 0:01 ` Chen Gang
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=20130311164741.GL4977@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).