From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Doug Ledford' <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"'Veeresh U. Kokatnur'"
<veereshuk-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org>,
bharat-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org
Subject: RE: The linux-rdma staging branches
Date: Thu, 17 Aug 2017 17:16:40 -0500 [thread overview]
Message-ID: <000501d317a6$80030d50$800927f0$@opengridcomputing.com> (raw)
In-Reply-To: <009501d30acf$fcfbba20$f6f32e60$@opengridcomputing.com>
ping.
So are k.o/for-next and k.o/for-X.Y-rc branche the ones to watch and test in
your git.kernel.org tree? I'm trying to tie chelsio's QA into this, and any
help is greatly appreciated!
Is there some process other vendors or interested parties care to share on
trying to catch rdma regressions early? This whole recent breakage of the rdma
core that made it into 4.9 and 4.12 is painful, to say the least.
Thanks!
Steve.
>
> He Doug, I want to get chelsio's QA tied into regular regression testing of
> fixes you have staged for release-next as well as RC fixes staged for the
> current RC release. Which branches do they want to track for regression
> testing?
>
> Also, does anyone have "best practices" for how QA orgs should regression test
> linux kernels through the release process?
>
> Thanks,
>
> Steve.
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-08-17 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 14:10 The linux-rdma staging branches Steve Wise
2017-08-17 22:16 ` Steve Wise [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='000501d317a6$80030d50$800927f0$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=bharat-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=veereshuk-ut6Up61K2wZBDgjK7y7TUQ@public.gmane.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.