All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Anna Schumaker <Anna.Schumaker@netapp.com>,
	Jeff Layton <jeff.layton@primarydata.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 00/10] sunrpc: fixes and cleanups for svc creation and thread handling
Date: Mon, 1 Dec 2014 15:12:33 -0500	[thread overview]
Message-ID: <20141201201233.GD30001@fieldses.org> (raw)
In-Reply-To: <CAHQdGtRaZ33kzweTMiSQhjAmUkQdHrq140obhrvmY2bZC=xcdg@mail.gmail.com>

On Mon, Dec 01, 2014 at 03:08:57PM -0500, Trond Myklebust wrote:
> On Mon, Dec 1, 2014 at 2:56 PM, J. Bruce Fields <bfields@fieldses.org> wrote:
> > On Thu, Nov 20, 2014 at 09:17:44AM -0500, Anna Schumaker wrote:
> >> On 11/19/2014 04:59 PM, Jeff Layton wrote:
> >> > On Wed, 19 Nov 2014 16:37:58 -0500
> >> > "J. Bruce Fields" <bfields@fieldses.org> wrote:
> >> >
> >> >> On Wed, Nov 19, 2014 at 07:51:12AM -0500, Jeff Layton wrote:
> >> >>> Patch #1 in this series is a bugfix, but probably isn't worth sending to
> >> >>> stable. The rest are just cleanups in preparation for some other patches
> >> >>> that I have queued up. Can you consider these for 3.19?
> >> >> Sure, I've read through them, they look fine.
> >> >>
> >> >> When I tried to apply them to my for-3.19 there were rejects due to
> >> >> tracing stuff in include/trace/events/sunrpc.h.  I haven't tried to
> >> >> investigate yet.
> >> >>
> >> >> --b.
> >> >>
> >> > Ahh yeah. These are based on top of the tracepoint patches I sent to
> >> > Trond a couple of weeks ago. I think he's planning to merge those in
> >> > 3.19 too, but I don't think he's done that yet. Anna may have though...
> >>
> >> I have them in a private tree on my laptop that I use for testing.  Want me to push them out somewhere?
> >
> > That'd help me at least test, but we need something more than a
> > temporary testing branch to get ready for the merge window.  Choices
> > include:
> >
> >         - Trond merges them all now, I pull that and apply these on top.
> >         - I merge them instead, or we divide the patches between us
> >           somehow.  Worst case, it's probably even OK if there's a patch
> >           or two that we both apply.
> >
> > In any case we need to get that sorted out now-ish as the merge window's
> > probably starting next week.
> >
> 
> All patches that I plan on merging for the next window were pushed out
> last Friday. Jeff's tracepoint and debugfs patchset should therefore
> be present in my nfs-for-next and linux-next branches on
> git.linux-nfs.org.

OK, great, I'll go take a look at that and figure out what's needed,
thanks.

--b.

      reply	other threads:[~2014-12-01 20:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 12:51 [PATCH 00/10] sunrpc: fixes and cleanups for svc creation and thread handling Jeff Layton
2014-11-19 12:51 ` [PATCH 01/10] sunrpc: release svc_pool_map reference when serv allocation fails Jeff Layton
2014-11-19 12:51 ` [PATCH 02/10] sunrpc: add a generic rq_flags field to svc_rqst and move rq_secure to it Jeff Layton
2014-11-19 12:51 ` [PATCH 03/10] sunrpc: move rq_local field to rq_flags Jeff Layton
2014-11-19 12:51 ` [PATCH 04/10] sunrpc: move rq_usedeferral flag " Jeff Layton
2014-11-19 12:51 ` [PATCH 05/10] sunrpc: move rq_dropme flag into rq_flags Jeff Layton
2014-11-19 12:51 ` [PATCH 06/10] sunrpc: move rq_splice_ok " Jeff Layton
2014-11-19 12:51 ` [PATCH 07/10] sunrpc: move rq_cachetype field to better optimize space Jeff Layton
2014-11-19 12:51 ` [PATCH 08/10] sunrpc: convert sp_task_pending flag to use atomic bitops Jeff Layton
2014-11-19 12:51 ` [PATCH 09/10] sunrpc: have svc_wake_up only deal with pool 0 Jeff Layton
2014-11-19 12:51 ` [PATCH 10/10] sunrpc: require svc_create callers to pass in meaningful shutdown routine Jeff Layton
2014-11-19 14:57 ` [PATCH 00/10] sunrpc: fixes and cleanups for svc creation and thread handling J. Bruce Fields
2014-11-19 21:37 ` J. Bruce Fields
2014-11-19 21:59   ` Jeff Layton
2014-11-20 14:17     ` Anna Schumaker
2014-12-01 19:56       ` J. Bruce Fields
2014-12-01 20:08         ` Trond Myklebust
2014-12-01 20:12           ` J. Bruce Fields [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=20141201201233.GD30001@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Anna.Schumaker@netapp.com \
    --cc=jeff.layton@primarydata.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.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.