From: David Miller <davem@davemloft.net>
To: johannes@sipsolutions.net
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/5] skb data accessors cleanup
Date: Fri, 16 Jun 2017 11:50:13 -0400 (EDT) [thread overview]
Message-ID: <20170616.115013.1187787408957466917.davem@davemloft.net> (raw)
In-Reply-To: <20170616070747.3332-1-johannes@sipsolutions.net>
From: Johannes Berg <johannes@sipsolutions.net>
Date: Fri, 16 Jun 2017 09:07:42 +0200
> Over night, Fengguang's bot told me that it compiled all of its many
> various configurations successfully, and I had done allyesconfig on
> x86_64 myself yesterday to iron out the things I missed.
>
> So now I think I'm happy with it.
>
> My tree was based on your
>
> commit 3715c47bcda8bb56f7e2be27276282a2d0d48c09
> Merge: 18b6e7955d8f d8fbd27469fc
> Author: David S. Miller <davem@davemloft.net>
> Date: Thu Jun 15 14:31:56 2017 -0400
>
> Merge branch 'r8152-support-new-chips'
>
> when the compilation tests happened, but I've reviewed the changes
> coming into net-next in the meantime and didn't see any new usages
> of skb data accessors having come in.
Series applied, thanks!
I tell ya, spatch appears to be the crack cocaine of Linus kernel
development. Once someone gets into some spatch scripting work,
they can't stop!
next prev parent reply other threads:[~2017-06-16 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 7:07 [PATCH 0/5] skb data accessors cleanup Johannes Berg
2017-06-16 7:07 ` [PATCH 1/5] networking: convert many more places to skb_put_zero() Johannes Berg
2017-06-16 7:07 ` [PATCH 2/5] networking: introduce and use skb_put_data() Johannes Berg
2017-06-16 7:07 ` [PATCH 3/5] networking: make skb_put & friends return void pointers Johannes Berg
2017-06-16 7:07 ` [PATCH 4/5] networking: make skb_pull " Johannes Berg
2017-06-16 7:07 ` [PATCH 5/5] networking: make skb_push & __skb_push " Johannes Berg
2017-06-16 15:50 ` David Miller [this message]
2017-06-16 19:43 ` [PATCH 0/5] skb data accessors cleanup Joe Perches
2017-06-16 19:44 ` 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=20170616.115013.1187787408957466917.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johannes@sipsolutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox