ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Krzysztof Kozlowski <krzk@kernel.org>, ksummit@lists.linux.dev
Subject: Re: [MAINTAINERS SUMMIT] Hidden commits from next (aka why maintainers hoard them in backpack)
Date: Thu, 11 Sep 2025 15:36:24 +0300	[thread overview]
Message-ID: <20250911123624.GE13915@pendragon.ideasonboard.com> (raw)
In-Reply-To: <8e0590dcae46d8f8c3b8c29427b4c8ced227ea92.camel@sipsolutions.net>

On Thu, Sep 11, 2025 at 02:35:38PM +0200, Johannes Berg wrote:
> On Thu, 2025-09-11 at 15:27 +0300, Laurent Pinchart wrote:
> > 
> > > Just a friendly note, Laurent, I appreciate your work and I do not want
> > > to point that you committed it incorrectly. In the contrary - your
> > > commit is right, but your upstream maintainer stops you from including
> > > this in linux-next. My aim here is only to discuss and improve the process.
> > 
> > I would be happy to have my tree included in linux-next. I'm worried
> > that the fact that the media subsystem cherry-picks my pull requests
> > instead of merging them would cause issues though. Am I worrying
> > needlessly, or is that a real issue ?
> 
> If they end up in both trees with different commit IDs it'll get flagged
> (and you'll get an email about it), but presumably you'll drop them from
> your trees pretty much as soon as that happens, so it should be fine
> afaict.

If it happens as an accident, sure, but I don't think it's a very nice
mode of operation as a standard process.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2025-09-11 12:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11 11:04 Krzysztof Kozlowski
2025-09-11 11:44 ` Krzysztof Kozlowski
2025-09-11 12:05 ` Mark Brown
2025-09-11 18:45   ` Dan Carpenter
2025-09-11 12:06 ` Jiri Kosina
2025-09-11 12:10   ` Krzysztof Kozlowski
2025-09-11 13:18   ` James Bottomley
2025-09-11 13:49     ` Mark Brown
2025-09-11 15:32       ` James Bottomley
2025-09-11 16:02         ` Mark Brown
2025-09-11 16:11           ` James Bottomley
2025-09-11 16:50             ` Mark Brown
2025-09-11 12:27 ` Laurent Pinchart
2025-09-11 12:31   ` Bartosz Golaszewski
2025-09-11 12:33     ` Laurent Pinchart
2025-09-11 12:42       ` Krzysztof Kozlowski
2025-09-11 12:58         ` Greg KH
2025-09-12  9:03         ` Dan Carpenter
2025-09-11 12:34   ` Geert Uytterhoeven
2025-09-11 12:35   ` Johannes Berg
2025-09-11 12:36     ` Laurent Pinchart [this message]
2025-09-11 12:48       ` Mark Brown
2025-09-11 12:47   ` Krzysztof Kozlowski
2025-09-11 12:53     ` Laurent Pinchart
2025-09-11 13:40   ` Mark Brown
2025-09-11 14:25     ` Steven Rostedt
2025-09-11 19:29       ` Laurent Pinchart
2025-09-11 19:43         ` Steven Rostedt
2025-09-12  9:52       ` Vlastimil Babka
2025-09-12 17:45         ` Steven Rostedt
2025-09-11 12:49 ` Sasha Levin
2025-09-12 11:55   ` Krzysztof Kozlowski

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=20250911123624.GE13915@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=johannes@sipsolutions.net \
    --cc=krzk@kernel.org \
    --cc=ksummit@lists.linux.dev \
    /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