From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
backports@vger.kernel.org
Cc: Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH 4/5] backports: add bin2hex()
Date: Fri, 13 Oct 2017 10:56:11 +0200 [thread overview]
Message-ID: <1507884971.2551.34.camel@sipsolutions.net> (raw)
In-Reply-To: <8f8b0780-b14e-4795-94ff-6d55f1541c19@broadcom.com> (sfid-20171013_105521_852219_E8C86D05)
On Fri, 2017-10-13 at 10:55 +0200, Arend van Spriel wrote:
> On 12-10-17 23:00, Johannes Berg wrote:
> > From: Johannes Berg <johannes.berg@intel.com>
>
> any remark why/who needs this. The change summary hints that it is
> needed for kernels before 3.18.
Sorry. Key stuff in the next patch requires it :)
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2017-10-13 8:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 21:00 [PATCH 1/5] backports: move headers to be clearer Johannes Berg
2017-10-12 21:00 ` [PATCH 2/5] backports: add mktime64() Johannes Berg
2017-10-12 21:00 ` [PATCH 3/5] copy-list: move mpls includes Johannes Berg
2017-10-12 21:00 ` [PATCH 4/5] backports: add bin2hex() Johannes Berg
2017-10-13 8:55 ` Arend van Spriel
2017-10-13 8:56 ` Johannes Berg [this message]
2017-10-12 21:00 ` [PATCH 5/5] backports: add signature verification code Johannes Berg
2017-10-12 21:42 ` Johannes Berg
2017-10-12 22:05 ` Johannes Berg
2017-10-13 6:00 ` Johannes Berg
2017-10-13 9:02 ` Arend van Spriel
2017-10-13 9:09 ` Johannes Berg
2017-10-13 9:10 ` Johannes Berg
2017-10-13 9:36 ` Arend van Spriel
2017-10-13 9:38 ` Johannes Berg
2017-10-13 9:39 ` Johannes Berg
2017-10-13 10:22 ` Arend van Spriel
2017-10-13 10:23 ` Johannes Berg
2017-10-13 8:56 ` [PATCH 1/5] backports: move headers to be clearer Arend van Spriel
2017-10-13 8:57 ` Johannes Berg
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=1507884971.2551.34.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=johannes.berg@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