linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	dalias@libc.org, linux-sh@vger.kernel.org,
	ysato@users.sourceforge.jp
Subject: Re: patch "maple: make maple_bus_type static and const" added to char-misc-testing
Date: Fri, 5 Jan 2024 10:45:56 +0100	[thread overview]
Message-ID: <2024010517-mousy-unfitted-ba9b@gregkh> (raw)
In-Reply-To: <537585054b4bb68e32153822a168af677c60708e.camel@physik.fu-berlin.de>

On Fri, Jan 05, 2024 at 10:38:00AM +0100, John Paul Adrian Glaubitz wrote:
> On Fri, 2024-01-05 at 08:34 +0100, Greg KH wrote:
> > On Thu, Jan 04, 2024 at 07:44:30PM +0100, John Paul Adrian Glaubitz wrote:
> > > On Thu, 2024-01-04 at 17:01 +0100, Geert Uytterhoeven wrote:
> > > > > I don't understand the hurry.
> > > > 
> > > > You really should aim to have your for-next branch ready by rc7, so
> > > > testers can find and report most issues, and you can get them fixed,
> > > > before the merge window opens.
> > > 
> > > Do testers not go on holiday vacations? I was just on vacation for two
> > > weeks and I find it irritating that my work is now overridden because
> > > of that.
> > 
> > What is being overridden here?
> > 
> > confused,
> 
> My role as a maintainer of arch/sh to review and apply the patch to my own tree.

Maintainer roles are never "no one else can touch my portions of the
tree".  This specific cleanup patch was sent on December 19, and then
due to no response, I applied it to my tree on January 4, a little over
2 week.

For a cleanup patch, that didn't add a new feature or do anything really
"serious", 2 weeks with no response makes me assume that no one objects
to it so I'll just sweep it up with the rest of those types of patches
and add them to my tree, especially as the merge window is about to
close for new stuff like this.

Nothing special, this is how normal tree-wide changes happen all the
time, especially for "trivial" stuff like this.

thanks,

greg k-h

  reply	other threads:[~2024-01-05  9:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 13:37 patch "maple: make maple_bus_type static and const" added to char-misc-testing gregkh
2024-01-04 13:48 ` John Paul Adrian Glaubitz
2024-01-04 13:57   ` Greg KH
2024-01-04 14:02     ` John Paul Adrian Glaubitz
2024-01-04 14:16       ` Geert Uytterhoeven
2024-01-04 14:20       ` Greg KH
2024-01-04 14:41         ` John Paul Adrian Glaubitz
2024-01-04 16:01           ` Geert Uytterhoeven
2024-01-04 18:44             ` John Paul Adrian Glaubitz
2024-01-05  7:34               ` Greg KH
2024-01-05  9:38                 ` John Paul Adrian Glaubitz
2024-01-05  9:45                   ` Greg KH [this message]
2024-01-07 21:39                     ` John Paul Adrian Glaubitz
2024-01-05  9:13               ` Geert Uytterhoeven
2024-01-07 21:46                 ` John Paul Adrian Glaubitz

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=2024010517-mousy-unfitted-ba9b@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dalias@libc.org \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-sh@vger.kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /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;
as well as URLs for NNTP newsgroup(s).