public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Miller <davem@davemloft•net>, Arnd Bergmann <arnd@arndb•de>
Cc: Networking <netdev@vger•kernel.org>,
	David Howells <dhowells@redhat•com>,
	Linus Walleij <linus.walleij@linaro•org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>,
	Paolo Abeni <pabeni@redhat•com>
Subject: Re: linux-next: manual merge of the net-next tree with the asm-generic tree
Date: Fri, 9 Jun 2023 11:43:38 +1000	[thread overview]
Message-ID: <20230609114338.72c7da7a@canb.auug.org.au> (raw)
In-Reply-To: <20230609104037.56648990@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 604 bytes --]

Hi all,

On Fri, 9 Jun 2023 10:40:37 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> Today's linux-next merge of the net-next tree got a conflict in:
> 
>   fs/netfs/iterator.c
> 
> between commit:
> 
>   ee5971613da3 ("netfs: Pass a pointer to virt_to_page()")
> 
> from the asm-generic tree and commit:
> 
>   f5f82cd18732 ("Move netfs_extract_iter_to_sg() to lib/scatterlist.c")
> 
> from the net-next tree.
> 
> I fixed it up (I used the file from the former and applied the patch
                                          ^^^^^^ latter

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-06-09  1:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  0:40 linux-next: manual merge of the net-next tree with the asm-generic tree Stephen Rothwell
2023-06-09  1:43 ` Stephen Rothwell [this message]
2023-06-09  6:31 ` Arnd Bergmann
2023-06-27 23:37   ` Stephen Rothwell

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=20230609114338.72c7da7a@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=arnd@arndb$(echo .)de \
    --cc=davem@davemloft$(echo .)net \
    --cc=dhowells@redhat$(echo .)com \
    --cc=linus.walleij@linaro$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox