From: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
To: "Marciniszyn,
Mike" <mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "John,
Jubin" <jubin.john-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org"
<devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
<dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"Weiny, Ira" <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v2 2/2] staging/rdma/hfi1: Eliminate WARN_ON when VL is invalid
Date: Fri, 20 Nov 2015 09:00:23 -0800 [thread overview]
Message-ID: <20151120170023.GA14450@kroah.com> (raw)
In-Reply-To: <32E1700B9017364D9B60AED9960492BC259BD977-RjuIdWtd+YbTXloPLtfHfbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Fri, Nov 20, 2015 at 04:43:56PM +0000, Marciniszyn, Mike wrote:
> > >
> > > Is the inprocess branch available?
> >
> > I do not understand what you mean here :(
>
> Does it fail to apply to staging-next or staging-testing or something else?
As both trees are now the same, it fails to apply to both at the moment
:)
thanks,
greg k-h
--
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
next prev parent reply other threads:[~2015-11-20 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 0:18 [PATCH v2 0/2] staging/rdma/hfi1: Miscellaneous Fixes Jubin John
2015-11-10 0:18 ` [PATCH v2 1/2] staging/rdma/hfi1: Workaround to prevent corruption during packet delivery Jubin John
[not found] ` <1447114701-11003-1-git-send-email-jubin.john-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-11-10 0:18 ` [PATCH v2 2/2] staging/rdma/hfi1: Eliminate WARN_ON when VL is invalid Jubin John
[not found] ` <1447114701-11003-3-git-send-email-jubin.john-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-11-20 0:58 ` Greg KH
[not found] ` <20151120005837.GA18080-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-11-20 15:23 ` Marciniszyn, Mike
[not found] ` <32E1700B9017364D9B60AED9960492BC259BD7E1-RjuIdWtd+YbTXloPLtfHfbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-11-20 16:35 ` Greg KH
[not found] ` <20151120163542.GA31501-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-11-20 16:43 ` Marciniszyn, Mike
[not found] ` <32E1700B9017364D9B60AED9960492BC259BD977-RjuIdWtd+YbTXloPLtfHfbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-11-20 17:00 ` Greg KH [this message]
[not found] ` <20151120170023.GA14450-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-11-20 23:59 ` Jubin John
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=20151120170023.GA14450@kroah.com \
--to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public.gmane.org \
--cc=devel-gWbeCf7V1WCQmaza687I9mD2FQJk+8+b@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=jubin.john-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).