From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Rich Felker <dalias@libc.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH 5/7 v4] sh: remove sh5/sh64 last fragments
Date: Fri, 17 Mar 2023 08:51:23 +0100 [thread overview]
Message-ID: <2749830124ec9d6990c95bf2ce4ea4de56b2967a.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <CAMuHMdXaZEWxB9Opgt2wcD2xAqF9Jv4r4KY9RGaR7vVVFXs5NQ@mail.gmail.com>
Hi Geert!
On Fri, 2023-03-17 at 08:31 +0100, Geert Uytterhoeven wrote:
> Hi Adrian,
>
> On Thu, Mar 16, 2023 at 9:46 PM John Paul Adrian Glaubitz
> <glaubitz@physik.fu-berlin.de> wrote:
> > On Thu, 2023-03-16 at 13:43 -0700, Randy Dunlap wrote:
> > > > Oops, sorry. My bad. I will use the proper tree.
> > >
> > > Just let me know if you want me to resend it.
> > > Thanks.
> >
> > No, that's fine. I will rebase my for-next tree.
>
> Rebase on top of what? Commit 49deed336ef9a409 ("parisc:
> update kbuild doc. aliases for parisc64") is in the parisc tree.
> You must not base the SH tree on the parisc tree.
Oh, I wasn't aware of that.
> Don't care about the simple conflict, Stephen and Linus can
> handle that fine.
>
> FTR, if the conflict was more complex, an immutable branch to be
> merged by all parties would be appropriate. But that's overkill and
> thus not needed for simple conflicts like this.
I'll resolve the conflict manually then. Thanks.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2023-03-17 7:51 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 4:00 [PATCH 0/7 v4] sh: various doc, build, init fixes Randy Dunlap
2023-03-06 4:00 ` [PATCH 1/7 v4] sh: SH2007: drop the bad URL info Randy Dunlap
2023-03-19 19:22 ` John Paul Adrian Glaubitz
2023-03-06 4:00 ` [PATCH 2/7 v4] sh: nmi_debug: fix return value of __setup handler Randy Dunlap
2023-03-19 19:32 ` John Paul Adrian Glaubitz
2023-03-06 4:00 ` [PATCH 3/7 v4] sh: init: use OF_EARLY_FLATTREE for early init Randy Dunlap
2023-03-19 19:48 ` John Paul Adrian Glaubitz
2023-03-06 4:00 ` [PATCH 4/7 v4] sh: math-emu: fix macro redefined warning Randy Dunlap
2023-03-19 19:49 ` John Paul Adrian Glaubitz
2023-03-06 4:00 ` [PATCH 5/7 v4] sh: remove sh5/sh64 last fragments Randy Dunlap
2023-03-16 13:23 ` John Paul Adrian Glaubitz
2023-03-16 16:44 ` Randy Dunlap
2023-03-16 16:52 ` John Paul Adrian Glaubitz
2023-03-16 20:43 ` Randy Dunlap
2023-03-16 20:46 ` John Paul Adrian Glaubitz
2023-03-17 7:31 ` Geert Uytterhoeven
2023-03-17 7:51 ` John Paul Adrian Glaubitz [this message]
2023-03-19 19:50 ` John Paul Adrian Glaubitz
2023-03-06 4:00 ` [PATCH 6/7 v4] sh: fix Kconfig entry for NUMA => SMP Randy Dunlap
2023-03-19 20:20 ` John Paul Adrian Glaubitz
2023-03-20 20:13 ` John Paul Adrian Glaubitz
2023-03-20 20:17 ` Randy Dunlap
2023-03-06 4:00 ` [PATCH 7/7 v4] sh: mcount.S: fix build error when PRINTK is not enabled Randy Dunlap
2023-03-19 20:49 ` John Paul Adrian Glaubitz
2023-03-20 8:16 ` Geert Uytterhoeven
2023-03-20 9:13 ` John Paul Adrian Glaubitz
2023-03-20 12:42 ` Geert Uytterhoeven
2023-03-20 12:43 ` Geert Uytterhoeven
2023-03-20 13:32 ` John Paul Adrian Glaubitz
2023-03-20 20:10 ` John Paul Adrian Glaubitz
2023-03-20 20:09 ` John Paul Adrian Glaubitz
2023-03-07 15:18 ` [PATCH 0/7 v4] sh: various doc, build, init fixes John Paul Adrian Glaubitz
2023-03-16 13:26 ` John Paul Adrian Glaubitz
2023-03-23 9:41 ` 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=2749830124ec9d6990c95bf2ce4ea4de56b2967a.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=arnd@arndb.de \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®