From: David Miller <davem@davemloft.net>
To: alex.bluesman.smirnov@gmail.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH 1/2 net v2] 6lowpan: rework data fetching from skb
Date: Sat, 12 May 2012 23:28:21 -0400 (EDT) [thread overview]
Message-ID: <20120512.232821.1019571950434617908.davem@davemloft.net> (raw)
In-Reply-To: <1336748290-25649-1-git-send-email-alex.bluesman.smirnov@gmail.com>
This and your other patch are not appropriate this late in
the -rc series, and Linus has ratched up his standards even
higher with todays' RC release.
You'll need to resubmit these for net-next.
next prev parent reply other threads:[~2012-05-13 3:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1336656163-19382-1-git-send-email-y>
2012-05-10 13:22 ` [PATCH 1/2 net] 6lowpan: add missing pskb_may_pull() check alex.bluesman.smirnov
2012-05-10 13:30 ` Eric Dumazet
2012-05-10 14:05 ` Alexander Smirnov
2012-05-10 16:28 ` David Miller
2012-05-11 14:58 ` [PATCH 1/2 net v2] 6lowpan: rework data fetching from skb Alexander Smirnov
2012-05-13 3:28 ` David Miller [this message]
2012-05-10 13:22 ` [PATCH 2/2 net] 6lowpan: fix hop limit compression alex.bluesman.smirnov
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=20120512.232821.1019571950434617908.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=eric.dumazet@gmail.com \
--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).