From: Johannes Berg <johannes@sipsolutions.net>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: backports@vger.kernel.org
Subject: Re: [PATCH] backports: add definitions S32_MAX and S32_MIN
Date: Fri, 24 Feb 2017 13:30:43 +0100 [thread overview]
Message-ID: <1487939443.2540.19.camel@sipsolutions.net> (raw)
In-Reply-To: <c5eb014a-b922-f825-0319-af46d4864ab4@broadcom.com> (sfid-20170223_092759_188265_A4FEF280)
> I create a package nightly for our internal tree and wireless-testing
> and build for couple of target kernels to run some wifi tests on
> target systems. So I tend to hit issues pretty soon. Not covering all
> target kernels though.
Ok, that's nice. I'm torn between doing something that runs on our
existing infrastructure (easy, but internal) or building some kind of
infrastructure, likely on the build box we have from the LF... that's
harder but accessible to people other than me.
Or are there any alternatives? Perhaps if I put the scripts upstream
then it doesn't matter that I might actually be running it on our
internal infrastructure, since anyone can just take the scripts and run
them?
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2017-02-24 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 22:18 [PATCH] backports: add definitions S32_MAX and S32_MIN Arend van Spriel
2017-02-23 7:49 ` Johannes Berg
2017-02-23 8:27 ` Arend Van Spriel
2017-02-24 12:30 ` Johannes Berg [this message]
2017-03-01 9:47 ` Arend Van Spriel
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=1487939443.2540.19.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@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.