All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Geliang Tang <geliangtang@163.com>
Cc: devel@driverdev.osuosl.org, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Mike Marciniszyn <infinipath@intel.com>,
	Doug Ledford <dledford@redhat.com>,
	Sean Hefty <sean.hefty@intel.com>,
	Hal Rosenstock <hal.rosenstock@gmail.com>
Subject: Re: [PATCH] staging: IB/ipath: use TASK_COMM_LEN in ipath_portdata
Date: Sat, 17 Oct 2015 22:05:09 -0700	[thread overview]
Message-ID: <20151018050509.GA2703@kroah.com> (raw)
In-Reply-To: <85f5a431a363d505975b2aee477673ef12ea4f63.1444395550.git.geliangtang@163.com>

On Thu, Oct 08, 2015 at 10:04:27PM -0700, Geliang Tang wrote:
> Use comm[TASK_COMM_LEN] instead of comm[16]. Add linux/sched.h
> header in ipath_kernel.h, and remove linux/sched.h header from
> ipath_*.c which have included ipath_kernel.h.

That's a lot of different things to be doing all in one patch.  Please
break this up into different patches and resend.

Also please add the "staging:" prefix to your subject lines, like I
changed it to here, that makes it easier for me to notice and handle
your patches properly.

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Geliang Tang <geliangtang@163.com>
Cc: Mike Marciniszyn <infinipath@intel.com>,
	Doug Ledford <dledford@redhat.com>,
	Sean Hefty <sean.hefty@intel.com>,
	Hal Rosenstock <hal.rosenstock@gmail.com>,
	linux-rdma@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: IB/ipath: use TASK_COMM_LEN in ipath_portdata
Date: Sat, 17 Oct 2015 22:05:09 -0700	[thread overview]
Message-ID: <20151018050509.GA2703@kroah.com> (raw)
In-Reply-To: <85f5a431a363d505975b2aee477673ef12ea4f63.1444395550.git.geliangtang@163.com>

On Thu, Oct 08, 2015 at 10:04:27PM -0700, Geliang Tang wrote:
> Use comm[TASK_COMM_LEN] instead of comm[16]. Add linux/sched.h
> header in ipath_kernel.h, and remove linux/sched.h header from
> ipath_*.c which have included ipath_kernel.h.

That's a lot of different things to be doing all in one patch.  Please
break this up into different patches and resend.

Also please add the "staging:" prefix to your subject lines, like I
changed it to here, that makes it easier for me to notice and handle
your patches properly.

thanks,

greg k-h

  reply	other threads:[~2015-10-18  5:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09  5:04 [PATCH] IB/hfi1: use TASK_COMM_LEN in hfi1_ctxtdata Geliang Tang
2015-10-09  5:04 ` Geliang Tang
2015-10-09  5:04 ` [PATCH] IB/ipath: use TASK_COMM_LEN in ipath_portdata Geliang Tang
2015-10-18  5:05   ` Greg Kroah-Hartman [this message]
2015-10-18  5:05     ` [PATCH] staging: " Greg Kroah-Hartman
2015-10-18 13:57     ` [PATCH v2 1/2] " Geliang Tang
2015-10-18 13:57       ` Geliang Tang
2015-10-18 13:57       ` [PATCH v2 2/2] staging: IB/ipath: remove sched.h header Geliang Tang
2015-10-18 13:57         ` Geliang Tang
2015-10-25  2:05         ` Greg Kroah-Hartman
2015-10-25  2:05           ` Greg Kroah-Hartman
2015-10-25  2:06           ` Greg Kroah-Hartman
2015-10-25  2:06             ` Greg Kroah-Hartman

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=20151018050509.GA2703@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=dledford@redhat.com \
    --cc=geliangtang@163.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=infinipath@intel.com \
    --cc=linux-kernel@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.