All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Randy Dunlap <rdunlap@infradead.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-brauner tree
Date: Thu, 4 Apr 2024 08:59:21 +0900	[thread overview]
Message-ID: <Zg3tWULD56chInTG@codewreck.org> (raw)
In-Reply-To: <20240404101038.11486a24@canb.auug.org.au>

Thanks Stephen!

[off topic, I just spent 10 minutes looking for the list of urls of the
repos merged into linux-next to check that 'vfs-brauner' tree commit as
it doesn't appear to be in next yet, and couldn't find it as there's no
"Merge branch x of ...brauner" commit in next at the moment.
I'm sure it's there somewhere and I didn't look at the right place, but
perhaps a link to such a list could be added to either of the following
(which all describe linux-next to some level):
- https://www.kernel.org/doc/man-pages/linux-next.html
- Documentation/process/howto.rst
- Documentation/process/2.Process.rst
/off topic]


Christian,

Stephen Rothwell wrote on Thu, Apr 04, 2024 at 10:10:38AM +1100:
> [...]
> 528aa74c091d ("9p: Clean up a kdoc warning.")
> 
> These are commit
> [...] 
>   7013482ff594 ("9p/trans_fd: remove Excess kernel-doc comment")
> 
> from the v9fs tree.

Thanks for picking that commit up (assuming you did recently); I've had
it in my tree for a while and should have submitted it for 6.9-rc1 but
the other 9p tree brought a few bugs in at the same time to I had held
it off for safety, but it doesn't really make sense and I should have
sent it a while ago.

I only have a handful of patches so I can send them today/tomorrow if
you drop your's, or I can drop this one here and send the rest
shortly later to avoid further confusion.

Cheers,
-- 
Dominique Martinet | Asmadeus

  reply	other threads:[~2024-04-04  0:05 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-03 23:10 linux-next: duplicate patches in the vfs-brauner tree Stephen Rothwell
2024-04-03 23:59 ` Dominique Martinet [this message]
2024-04-04  0:21   ` Randy Dunlap
2024-04-04  1:44     ` Dominique Martinet
2024-04-05 10:57       ` Christian Brauner
2024-04-05 11:30         ` Dominique Martinet
2024-04-05 13:09           ` Christian Brauner
2024-04-04  2:09 ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2025-10-19 20:29 Stephen Rothwell
2025-01-20 22:20 Stephen Rothwell
2025-01-12 21:55 Stephen Rothwell
2025-01-05 23:10 Stephen Rothwell
2025-01-07  3:14 ` Andrew Morton
2025-01-10 11:08   ` Christian Brauner
2025-01-11  0:31     ` Andrew Morton
2024-10-20 11:08 Stephen Rothwell
2024-10-21  8:22 ` Christian Brauner
2024-10-15 22:02 Stephen Rothwell
2024-07-31 23:54 Stephen Rothwell
2024-07-24 22:00 Stephen Rothwell
2023-12-21  0:00 Stephen Rothwell
2023-12-21 10:50 ` David Howells
2023-10-18 23:12 Stephen Rothwell
2023-10-19  5:36 ` Amir Goldstein
2023-10-19  9:18   ` Christian Brauner
2023-10-12 23:48 Stephen Rothwell
2023-10-13  6:32 ` Amir Goldstein

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=Zg3tWULD56chInTG@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.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 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.