From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend@broadcom.com>, backports@vger.kernel.org
Subject: Re: [PATCH v2] backports: add ktime_get_seconds()
Date: Sun, 01 Nov 2015 08:47:50 +0100 [thread overview]
Message-ID: <1446364070.3205.0.camel@sipsolutions.net> (raw)
In-Reply-To: <56353A97.9010909@broadcom.com>
On Sat, 2015-10-31 at 23:03 +0100, Arend van Spriel wrote:
> On 10/28/2015 10:17 PM, Arend van Spriel wrote:
> > On 10/23/2015 01:52 PM, Johannes Berg wrote:
> > > From: Johannes Berg <johannes.berg@intel.com>
> > >
> > > Since commit 84b00607aeb8 ("mac80211: use ktime_get_seconds")
> > > mac80211 uses ktime_get_seconds(). This patch provide a backport
> > > using ktime_get_ts() for it.
> > >
> > > [commit message and time64_t taken from Arend's patch]
> > >
> > > Signed-off-by: Arend van Spriel <arend@broadcom.com>
> >
> > Looks good. Thanks.
>
> Actually got feedback internally that ubuntu kernel 3.19.0-30-generic
>
> does not need this patch so should we extend this with
> UTS_UBUNTU_RELEASE_ABI check?
>
If they backported that, then yeah, probably something like that --
unless we can find some #define that came with the backport to check
on?
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2015-11-01 7:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 11:52 [PATCH v2] backports: add ktime_get_seconds() Johannes Berg
2015-10-28 21:17 ` Arend van Spriel
2015-10-31 22:03 ` Arend van Spriel
2015-11-01 7:47 ` Johannes Berg [this message]
2015-11-07 17:08 ` Hauke Mehrtens
2015-12-08 8:44 ` Arend van Spriel
2015-12-08 9:04 ` Johannes Berg
2015-12-08 9:14 ` Johannes Berg
2015-12-08 9:28 ` Arend van Spriel
2015-12-08 9:38 ` Johannes Berg
2015-12-09 22:52 ` Hauke Mehrtens
2015-12-09 22:56 ` Johannes Berg
2015-12-09 22:48 ` Hauke Mehrtens
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=1446364070.3205.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=backports@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.