From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
ksummit <ksummit-discuss@lists.linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Ksummit-discuss] at91 git tree in linux-next
Date: Mon, 23 Nov 2020 22:59:06 +1100 [thread overview]
Message-ID: <20201123225906.7cd6d14e@canb.auug.org.au> (raw)
In-Reply-To: <CAMuHMdUkQqJ_+8xy3q7tjCXCU4cZsnT7EOHtfTDroc4Ke0yPrw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 583 bytes --]
Hi Geert,
On Mon, 23 Nov 2020 11:44:17 +0100 Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> How is this working?
>
> From next-20201123:
>
> Merging at91/at91-next (0698efbb33ef Merge branches 'at91-soc',
> 'at91-dt' and 'at91-defconfig' into at91-next)
>
> which is indeed a recent commit, while Next/Trees has the wrong repo
> (linux-at91.git instead of linux.git):
That is what happens when you store the (supposedly) same information
in 2 places :-( I have fixed the incorrect one.
Thanks for letting me know.
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 186 bytes --]
_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
prev parent reply other threads:[~2020-11-23 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <551A9FAC.2010203@atmel.com>
2018-08-22 12:47 ` [Ksummit-discuss] at91 git tree in linux-next Nicolas Ferre
2018-08-22 23:30 ` Stephen Rothwell
2020-11-23 10:44 ` Geert Uytterhoeven
2020-11-23 11:59 ` 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=20201123225906.7cd6d14e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=geert@linux-m68k.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).