From: Greg KH <gregkh@suse.de>
To: David Miller <davem@davemloft.net>
Cc: Ian.Campbell@citrix.com, netdev@vger.kernel.org
Subject: Re: [PATCH 0/8] skb fragment API: convert network drivers (part IV)
Date: Wed, 5 Oct 2011 13:25:58 -0700 [thread overview]
Message-ID: <20111005202558.GA13436@suse.de> (raw)
In-Reply-To: <20111005.161341.840183744862645286.davem@davemloft.net>
On Wed, Oct 05, 2011 at 04:13:41PM -0400, David Miller wrote:
> From: Greg KH <gregkh@suse.de>
> Date: Wed, 5 Oct 2011 12:17:17 -0700
>
> > On Wed, Oct 05, 2011 at 11:28:30AM +0100, Ian Campbell wrote:
> >> The following series converts a forth batch of network drivers to the
> >> SKB pages fragment API introduced in 131ea6675c76.
> >>
> >> There are two drivers/staging patches in here. I'm not sure who normally
> >> takes these, I'm sure you guys know though.
> >
> > I take them. As I don't have commit 131ea6675c76 in my tree
> > (staging-next), I'd have to wait until that patch gets merged into
> > Linus's tree, which should be after 3.2-rc1, right? Mind if I hold off
> > in taking them until then?
>
> We're trying to change all the driver accesses so we can change
> the datastructures underneath this stuff.
>
> If we have to wait until after 3.2-rc1, then we won't be able to
> make the datastructure change this merge window.
Then feel free to take these changes through your tree, I have no
objection to that. I'll handle any merge issues on my side that might
happen, but given the size of these patches (i.e. almost trivial), I
doubt that would happen.
So feel free to add my:
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
to these patches and take them through the networking tree.
thanks,
greg k-h
next prev parent reply other threads:[~2011-10-05 20:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 10:28 [PATCH 0/8] skb fragment API: convert network drivers (part IV) Ian Campbell
2011-10-05 10:28 ` [PATCH 1/8] vxge: convert to SKB paged frag API Ian Campbell
2011-10-05 21:03 ` Michał Mirosław
2011-10-05 21:32 ` David Miller
2011-10-06 7:05 ` Ian Campbell
2011-10-06 16:00 ` Ian Campbell
2011-10-06 20:00 ` David Miller
2011-10-06 20:45 ` Michał Mirosław
2011-10-06 21:08 ` Ian Campbell
2011-10-06 21:16 ` David Miller
2011-10-06 21:25 ` Ian Campbell
2011-10-06 21:56 ` David Miller
2011-10-07 5:29 ` Ian Campbell
2011-10-06 21:15 ` David Miller
2011-10-06 21:19 ` Ian Campbell
2011-10-06 21:28 ` Michał Mirosław
2011-10-05 10:28 ` [PATCH 2/8] xen: netback: " Ian Campbell
2011-10-05 10:28 ` [PATCH 3/8] xen: netfront: " Ian Campbell
2011-10-05 10:28 ` [PATCH 4/8] et131x: " Ian Campbell
2011-10-05 10:28 ` [PATCH 5/8] hv: netvsc: " Ian Campbell
2011-10-05 10:28 ` [PATCH 6/8] myri10ge: " Ian Campbell
2011-10-05 10:28 ` [PATCH 7/8] cxgb3: " Ian Campbell
2011-10-05 10:28 ` [PATCH 8/8] chelsio: " Ian Campbell
2011-10-05 19:17 ` [PATCH 0/8] skb fragment API: convert network drivers (part IV) Greg KH
2011-10-05 20:13 ` David Miller
2011-10-05 20:25 ` Greg KH [this message]
2011-10-05 20:49 ` David Miller
2011-10-05 21:36 ` David Miller
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=20111005202558.GA13436@suse.de \
--to=gregkh@suse.de \
--cc=Ian.Campbell@citrix.com \
--cc=davem@davemloft.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.