mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] MAINTAINERS: add linux-next info
Date: Tue, 4 Jul 2023 17:39:26 +1000	[thread overview]
Message-ID: <20230704173926.4e36b414@canb.auug.org.au> (raw)
In-Reply-To: <20230704054410.12527-1-rdunlap@infradead.org>

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

Hi Randy,

That has been a long time coming :-)

On Mon,  3 Jul 2023 22:44:10 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> Add linux-next info to MAINTAINERS for ease of finding this data.
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> ---
>  MAINTAINERS |    7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff -- a/MAINTAINERS b/MAINTAINERS
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -12067,6 +12067,13 @@ F:	Documentation/litmus-tests/
>  F:	Documentation/memory-barriers.txt
>  F:	tools/memory-model/
>  
> +LINUX-NEXT TREE
> +M:	Stephen Rothwell <sfr@canb.auug.org.au>
> +L:	linux-next@vger.kernel.org
> +S:	Supported
> +B:	mailto:linux-next@vger.kernel.org and the appropriate development tree
> +T:	git git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/
> +
>  LIS3LV02D ACCELEROMETER DRIVER
>  M:	Eric Piel <eric.piel@tremplin-utc.net>
>  S:	Maintained

Acked-by: Stephen Rothwell <sfr@canb.auug.org.au>

-- 
Cheers,
Stephen Rothwell

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

      reply	other threads:[~2023-07-04  7:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04  5:44 Randy Dunlap
2023-07-04  7:39 ` Stephen Rothwell [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=20230704173926.4e36b414@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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®