From: David Miller <davem@davemloft.net>
To: johannes.berg@intel.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org, wey-yi.w.guy@intel.com
Subject: Re: [PATCH net-next] iwlwifi: dont pull too much payload in skb head
Date: Fri, 18 May 2012 13:31:36 -0400 (EDT) [thread overview]
Message-ID: <20120518.133136.1737334367748084291.davem@davemloft.net> (raw)
In-Reply-To: <1DC40B07CD6EC041A66726C271A73AE61955AE5D@IRSMSX102.ger.corp.intel.com>
From: "Berg, Johannes" <johannes.berg@intel.com>
Date: Fri, 18 May 2012 14:59:04 +0000
>> Since merge window is now pretty close, I would prefer David applies this
>> directly in net-next, if you dont mind, as this patch is more a core network issue
>> than an iwlwifi one.
>>
>> Thanks !
>
> Sure, good with me, I don't think we have colliding patches.
>
> Reviewed-by: Johannes Berg <johannes.berg@intel.com>
Applied.
prev parent reply other threads:[~2012-05-18 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 14:48 [PATCH net-next] iwlwifi: dont pull too much payload in skb head Eric Dumazet
2012-05-18 14:59 ` Berg, Johannes
2012-05-18 15:21 ` Eric Dumazet
2012-05-29 14:45 ` Berg, Johannes
2012-05-18 17:31 ` David Miller [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=20120518.133136.1737334367748084291.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=johannes.berg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=wey-yi.w.guy@intel.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).