mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Matt Turner <mattst88@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PULL] alpha.git
Date: Sun, 16 Feb 2025 22:06:11 +1100	[thread overview]
Message-ID: <20250216220611.41e33084@canb.auug.org.au> (raw)
In-Reply-To: <CAEdQ38F6ts1qXj2xb+PN=O_byGwZAp1mvF8aRdTEq2zrzLBFSA@mail.gmail.com>

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

Hi Matt,

On Fri, 14 Feb 2025 16:36:43 -0500 Matt Turner <mattst88@gmail.com> wrote:
>
> The last time I sent a pull request to Linus he noted that the commits
> weren't in linux-next. I meant to sort that out before next time, but
> well, better late than never!
> 
> Could you please add
> https://git.kernel.org/pub/scm/linux/kernel/git/mattst88/alpha.git
> alpha-next to linux-next?

Added from tomorrow.  I have put just you as a contact for problems
with the tree (conflict, build failures ...), do you want anyone else -
or a mailing list?

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

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

  parent reply	other threads:[~2025-02-16 11:06 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-14 21:34 Matt Turner
2025-02-14 21:36 ` Matt Turner
2025-02-14 21:40   ` pr-tracker-bot
2025-02-15  2:30     ` Matt Turner
2025-02-15  3:56       ` Linus Torvalds
2025-02-16 11:06   ` Stephen Rothwell [this message]
2025-02-15  4:07 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2025-11-12 20:11 Matt Turner
2025-11-13  2:25 ` pr-tracker-bot
2023-02-25 20:40 Matt Turner
2023-02-25 20:51 ` Linus Torvalds
2023-02-25 21:10 ` pr-tracker-bot
2021-07-30  3:08 Matt Turner
2021-07-30  5:13 ` pr-tracker-bot
2020-06-13  0:57 Matt Turner
2020-06-13 18:00 ` pr-tracker-bot
2019-02-11  4:46 Matt Turner
2019-02-11 18:35 ` pr-tracker-bot
2018-12-30 22:25 Matt Turner
2018-12-31 18:05 ` pr-tracker-bot
2018-05-23  4:02 Matt Turner
2018-04-08 18:44 Matt Turner
2018-04-09 16:13 ` Linus Torvalds
2018-04-09 16:46   ` Matt Turner
2018-02-02 19:52 Matt Turner
2018-01-21  2:25 Matt Turner
2018-01-23 10:23 ` Mikulas Patocka
2018-01-23 17:56   ` Matt Turner
2018-01-24  9:55     ` Mikulas Patocka
2017-09-04 20:50 Matt Turner
2017-08-29 19:35 Matt Turner
2012-05-24 18:43 Matt Turner

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=20250216220611.41e33084@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®