All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Doug Ledford <dledford@redhat.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Mike Marciniszyn <infinipath@intel.com>,
	Sean Hefty <sean.hefty@intel.com>,
	Hal Rosenstock <hal.rosenstock@gmail.com>,
	linux-rdma@vger.kernel.org, devel@driverdev.osuosl.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [patch] IB/hfi1: checking for NULL instead of IS_ERR
Date: Sat, 19 Sep 2015 03:01:53 +0000	[thread overview]
Message-ID: <20150919030153.GA30373@kroah.com> (raw)
In-Reply-To: <55FC32ED.1000404@redhat.com>

On Fri, Sep 18, 2015 at 11:51:09AM -0400, Doug Ledford wrote:
> On 09/16/2015 02:22 AM, Dan Carpenter wrote:
> > __get_txreq() returns an ERR_PTR() but this checks for NULL so it would
> > oops on failure.
> > 
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> 
> Thanks, applied.

Applied to what?  Should I just ignore these types of patches and not
take them in my tree and you will send them on later on?  I don't
remember what we agreed to do, sorry.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Doug Ledford <dledford@redhat.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Mike Marciniszyn <infinipath@intel.com>,
	Sean Hefty <sean.hefty@intel.com>,
	Hal Rosenstock <hal.rosenstock@gmail.com>,
	linux-rdma@vger.kernel.org, devel@driverdev.osuosl.org,
	kernel-janitors@vger.kernel.org
Subject: Re: [patch] IB/hfi1: checking for NULL instead of IS_ERR
Date: Fri, 18 Sep 2015 20:01:53 -0700	[thread overview]
Message-ID: <20150919030153.GA30373@kroah.com> (raw)
In-Reply-To: <55FC32ED.1000404@redhat.com>

On Fri, Sep 18, 2015 at 11:51:09AM -0400, Doug Ledford wrote:
> On 09/16/2015 02:22 AM, Dan Carpenter wrote:
> > __get_txreq() returns an ERR_PTR() but this checks for NULL so it would
> > oops on failure.
> > 
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> 
> Thanks, applied.

Applied to what?  Should I just ignore these types of patches and not
take them in my tree and you will send them on later on?  I don't
remember what we agreed to do, sorry.

thanks,

greg k-h

  reply	other threads:[~2015-09-19  3:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16  6:22 [patch] IB/hfi1: checking for NULL instead of IS_ERR Dan Carpenter
2015-09-16  6:22 ` Dan Carpenter
2015-09-18 15:51 ` Doug Ledford
2015-09-18 15:51   ` Doug Ledford
2015-09-19  3:01   ` Greg Kroah-Hartman [this message]
2015-09-19  3:01     ` Greg Kroah-Hartman
     [not found]     ` <20150919030153.GA30373-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-09-19 22:49       ` Weiny, Ira
2015-09-19 22:49         ` Weiny, Ira
     [not found]         ` <2807E5FD2F6FDA4886F6618EAC48510E1CB98D06-8k97q/ur5Z2krb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-09-20 17:26           ` Greg Kroah-Hartman
2015-09-20 17:26             ` Greg Kroah-Hartman
2015-09-21 15:42     ` Doug Ledford
2015-09-21 15:42       ` Doug Ledford
2015-09-21 16:48       ` Greg Kroah-Hartman
2015-09-21 16:48         ` Greg Kroah-Hartman
     [not found]         ` <20150921164846.GB27380-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-09-21 17:03           ` Doug Ledford
2015-09-21 17:03             ` Doug Ledford
     [not found]             ` <56003878.7080409-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-21 22:29               ` Greg Kroah-Hartman
2015-09-21 22:29                 ` Greg Kroah-Hartman
2015-09-22  5:32                 ` [PATCH] maintainers: update staging/rdma Sudip Mukherjee
2015-09-29  1:38                   ` Greg KH

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=20150919030153.GA30373@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dledford@redhat.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=infinipath@intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sean.hefty@intel.com \
    /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.