All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
	"Schumaker, Bryan" <Bryan.Schumaker@netapp.com>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [nfs:devel 46/51] fs/nfs/write.c:1592:5: error: redefinition of 'nfs_commit_inode'
Date: Tue, 31 Jul 2012 14:16:14 +0000	[thread overview]
Message-ID: <20120731141614.GA20628@localhost> (raw)
In-Reply-To: <5017E3CA.8070502@netapp.com>

On Tue, Jul 31, 2012 at 09:55:22AM -0400, Bryan Schumaker wrote:
> I've got one at:
> git://git.linux-nfs.org/projects/bjschuma/linux-nfs.git.  I don't
> always do a good job keeping it up-to-date, but I can try to get
> into the habit of putting my patches there before submitting them.

Tree added :)  By default I'll test every branch of the monitored
trees. You may ask me to permanently blacklist/whitelist some of your
branches. Or, if a topic branch is currently in heavy development and
will become testable eventually, you may temporarily carry a line

Dont-Auto-Build

in any of the branch's commits (in the changelog). Then the script
will skip that branch automatically.

Thanks,
Fengguang

> On 07/31/2012 09:51 AM, Fengguang Wu wrote:
> > Bryan,
> > 
> > Do you have a git tree that I can run tests upon? That would help
> > prevent problems from sneaking into Trond's tree, and hence mess up
> > the maintainer's tree and waste everyone's time.
> > 
> > Thanks,
> > Fengguang
> > 

WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: "Myklebust, Trond" <Trond.Myklebust@netapp.com>,
	"Schumaker, Bryan" <Bryan.Schumaker@netapp.com>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [nfs:devel 46/51] fs/nfs/write.c:1592:5: error: redefinition of 'nfs_commit_inode'
Date: Tue, 31 Jul 2012 22:16:14 +0800	[thread overview]
Message-ID: <20120731141614.GA20628@localhost> (raw)
In-Reply-To: <5017E3CA.8070502@netapp.com>

On Tue, Jul 31, 2012 at 09:55:22AM -0400, Bryan Schumaker wrote:
> I've got one at:
> git://git.linux-nfs.org/projects/bjschuma/linux-nfs.git.  I don't
> always do a good job keeping it up-to-date, but I can try to get
> into the habit of putting my patches there before submitting them.

Tree added :)  By default I'll test every branch of the monitored
trees. You may ask me to permanently blacklist/whitelist some of your
branches. Or, if a topic branch is currently in heavy development and
will become testable eventually, you may temporarily carry a line

Dont-Auto-Build

in any of the branch's commits (in the changelog). Then the script
will skip that branch automatically.

Thanks,
Fengguang

> On 07/31/2012 09:51 AM, Fengguang Wu wrote:
> > Bryan,
> > 
> > Do you have a git tree that I can run tests upon? That would help
> > prevent problems from sneaking into Trond's tree, and hence mess up
> > the maintainer's tree and waste everyone's time.
> > 
> > Thanks,
> > Fengguang
> > 

  reply	other threads:[~2012-07-31 14:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31  2:43 [nfs:devel 46/51] fs/nfs/write.c:1592:5: error: redefinition of 'nfs_commit_inode' Fengguang Wu
2012-07-31  2:43 ` Fengguang Wu
2012-07-31  3:14 ` Myklebust, Trond
2012-07-31 12:47   ` Bryan Schumaker
2012-07-31 12:47     ` Bryan Schumaker
2012-07-31 12:55     ` Myklebust, Trond
2012-07-31 12:55       ` Myklebust, Trond
2012-07-31 13:05       ` Bryan Schumaker
2012-07-31 13:05         ` Bryan Schumaker
2012-07-31 13:30         ` Bryan Schumaker
2012-07-31 13:30           ` Bryan Schumaker
2012-07-31 13:33           ` Myklebust, Trond
2012-07-31 13:33             ` Myklebust, Trond
2012-07-31 13:44             ` Bryan Schumaker
2012-07-31 13:44               ` Bryan Schumaker
2012-07-31 13:51               ` Fengguang Wu
2012-07-31 13:51                 ` Fengguang Wu
2012-07-31 13:55                 ` Bryan Schumaker
2012-07-31 13:55                   ` Bryan Schumaker
2012-07-31 14:16                   ` Fengguang Wu [this message]
2012-07-31 14:16                     ` Fengguang Wu
2012-07-31 14:18                     ` Bryan Schumaker
2012-07-31 14:18                       ` Bryan Schumaker
2012-07-31 13:58               ` Myklebust, Trond
2012-07-31 13:58                 ` Myklebust, Trond
2012-07-31 14:08                 ` Bryan Schumaker
2012-07-31 14:08                   ` Bryan Schumaker
2012-07-31 14:10                 ` Fengguang Wu
2012-07-31 14:10                   ` Fengguang Wu
2012-07-31 14:28                   ` Myklebust, Trond
2012-07-31 14:36                     ` Fengguang Wu
2012-07-31 14:36                       ` Fengguang Wu

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=20120731141614.GA20628@localhost \
    --to=fengguang.wu@intel.com \
    --cc=Bryan.Schumaker@netapp.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bjschuma@netapp.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.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.