All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	NeilBrown <neilb@suse.de>,
	Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: linux-next: manual merge of the nfsd tree with the nfs tree
Date: Mon, 10 Aug 2009 12:05:37 -0400	[thread overview]
Message-ID: <20090810160537.GD3401@fieldses.org> (raw)
In-Reply-To: <20090810105851.80333493.sfr@canb.auug.org.au>

On Mon, Aug 10, 2009 at 10:58:51AM +1000, Stephen Rothwell wrote:
> Hi Bruce,
> 
> Today's linux-next merge of the nfsd tree got a conflict in
> net/sunrpc/cache.c between commit
> 173912a6add00f4715774dcecf9ee53274c5924c ("SUNRPC: Move procfs-specific
> stuff out of the generic sunrpc cache code") from the nfs tree and commit
> f866a8194f7cbabb9135b98b9ac7d26237b88367 ("sunrpc/cache: rename
> queue_loose to cache_dequeue") from the nfsd tree.

OK, thanks.

Looks like there may be some less trivial conflicts now, though.  Trond,
maybe you could rebase the cache stuff against my latest for-2.6.32?

--b.

> 
> Just context changes. I fixed it up (see below) and can carry the fix as
> necessary.
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
> 
> diff --cc net/sunrpc/cache.c
> index db7720e,d19c075..0000000
> --- a/net/sunrpc/cache.c
> +++ b/net/sunrpc/cache.c
> @@@ -884,7 -908,19 +884,7 @@@ static int cache_release(struct inode *
>   
>   
>   
> - static void queue_loose(struct cache_detail *detail, struct cache_head *ch)
>  -static const struct file_operations cache_file_operations = {
>  -	.owner		= THIS_MODULE,
>  -	.llseek		= no_llseek,
>  -	.read		= cache_read,
>  -	.write		= cache_write,
>  -	.poll		= cache_poll,
>  -	.ioctl		= cache_ioctl, /* for FIONREAD */
>  -	.open		= cache_open,
>  -	.release	= cache_release,
>  -};
>  -
>  -
> + static void cache_dequeue(struct cache_detail *detail, struct cache_head *ch)
>   {
>   	struct cache_queue *cq;
>   	spin_lock(&queue_lock);

  reply	other threads:[~2009-08-10 16:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10  0:58 linux-next: manual merge of the nfsd tree with the nfs tree Stephen Rothwell
2009-08-10 16:05 ` J. Bruce Fields [this message]
2009-08-10 18:08   ` Trond Myklebust
2009-08-10 18:17     ` J. Bruce Fields
  -- strict thread matches above, loose matches on Subject: below --
2015-02-10  0:55 Stephen Rothwell
2015-02-10 15:34 ` J. Bruce Fields
2021-10-24 23:59 Stephen Rothwell
2021-10-25  0:10 ` Stephen Rothwell
2025-03-20 22:11 Stephen Rothwell
2025-03-21 13:32 ` Chuck Lever
2025-03-21 13:37   ` Trond Myklebust
2025-03-21 13:40     ` Chuck Lever

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=20090810160537.GD3401@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=sfr@canb.auug.org.au \
    /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.