All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod@redhat.com>
To: lkp@lists.01.org
Subject: Tree build request
Date: Fri, 16 Sep 2016 15:05:45 -0400	[thread overview]
Message-ID: <20160916190545.GE31517@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 518 bytes --]

Hello,

I'd like to get a tree full of test patches I'm submitting to netdev built
across more arches than I have directly available, and it was suggested
that I send a request here. Work-in-progress patches are available here
(including one that fixes a problem reported by your infra w/the initial
patches I sent to netdev).

Tree location:

https://github.com/jarodwilson/linux-muck

Thanks much, please let me know if any additional information is required.

-- 
Jarod Wilson
jarod(a)redhat.com


                 reply	other threads:[~2016-09-16 19:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160916190545.GE31517@redhat.com \
    --to=jarod@redhat.com \
    --cc=lkp@lists.01.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.