From: Johannes Berg <johannes@sipsolutions.net>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: linux-wireless@vger.kernel.org, backports@vger.kernel.org
Subject: Re: [PATCH v2] compat: backport nla_put_be{16,32,64}()
Date: Sat, 26 Jan 2013 21:20:01 +0100 [thread overview]
Message-ID: <1359231601.8699.2.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <510320C8.6010407@hauke-m.de>
On Sat, 2013-01-26 at 01:18 +0100, Hauke Mehrtens wrote:
> On 01/24/2013 11:44 AM, Johannes Berg wrote:
> > From: Johannes Berg <johannes.berg@intel.com>
> >
> > I intend to use these in nl80211.
> >
> > Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> > ---
> > include/linux/compat-3.5.h | 24 ++++++++++++++++++++++++
> > 1 file changed, 24 insertions(+)
> >
>
> Thank you for your patch.
> I added a missing #include <net/netlink.h> to it.
Oops, thanks :)
johannes
prev parent reply other threads:[~2013-01-26 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 10:44 [PATCH v2] compat: backport nla_put_be{16,32,64}() Johannes Berg
2013-01-26 0:18 ` Hauke Mehrtens
2013-01-26 20:20 ` Johannes Berg [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=1359231601.8699.2.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@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).