public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christian Brauner <christian@brauner.io>,
	Seth Forshee <sforshee@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patches in the vfs-idmapping tree
Date: Mon, 8 May 2023 18:40:22 +0200	[thread overview]
Message-ID: <20230508-kiesbett-werben-04b4a8cc7544@brauner> (raw)
In-Reply-To: <20230508105626.4b7fbef1@canb.auug.org.au>

On Mon, May 08, 2023 at 10:56:26AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> The following commits are also in Linus Torvalds' tree as different
> commits (but the same patches):
> 
>   85ef56bc2d65 ("ocfs2: reduce ioctl stack usage")
>   ec30adeb289d ("pipe: set FMODE_NOWAIT on pipes")

Hey Stephen,

This ende up going through Jens' tree in the end. I'll drop these
patches now.

Thanks!
Christian

      reply	other threads:[~2023-05-08 16:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  0:56 linux-next: duplicate patches in the vfs-idmapping tree Stephen Rothwell
2023-05-08 16:40 ` Christian Brauner [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=20230508-kiesbett-werben-04b4a8cc7544@brauner \
    --to=brauner@kernel.org \
    --cc=christian@brauner.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sforshee@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox