From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arm-soc <arm@kernel.org>, SoC Team <soc@kernel.org>,
Jernej Skrabec <jernej@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Samuel Holland <samuel@sholland.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-sunxi@lists.linux.dev
Subject: Re: Re: [GIT PULL] Allwinner DT changes for 5.19
Date: Mon, 09 May 2022 17:06:25 +0200 [thread overview]
Message-ID: <2368089.jE0xQCEvom@kista> (raw)
In-Reply-To: <CAK8P3a3ePzJbh3p9edaDfZhZoYc=0-GvFCs3+2oLGjSoAhgvhw@mail.gmail.com>
Dne ponedeljek, 09. maj 2022 ob 16:21:29 CEST je Arnd Bergmann napisal(a):
> On Sun, May 8, 2022 at 10:52 PM Jernej Škrabec <jernej.skrabec@gmail.com>
wrote:
> >
> > Dne petek, 06. maj 2022 ob 19:02:17 CEST je Jernej Skrabec napisal(a):
> > > Hi!
> > >
> > > Please pull following DT changes for 5.19.
> >
> > I missed one patch, please disregard.
>
> I had already merged this one, merging the new branch on top, while editing
> the merge log to not mention the duplicate commits. You can always follow up
> with additional changes based on a branch that is already merged like this
one.
Ok, thanks! I'll follow up with new PR next time.
Best regards,
Jernej
>
> Arnd
>
WARNING: multiple messages have this Message-ID (diff)
From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arm-soc <arm@kernel.org>, SoC Team <soc@kernel.org>,
Jernej Skrabec <jernej@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Samuel Holland <samuel@sholland.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
linux-sunxi@lists.linux.dev
Subject: Re: Re: [GIT PULL] Allwinner DT changes for 5.19
Date: Mon, 09 May 2022 17:06:25 +0200 [thread overview]
Message-ID: <2368089.jE0xQCEvom@kista> (raw)
In-Reply-To: <CAK8P3a3ePzJbh3p9edaDfZhZoYc=0-GvFCs3+2oLGjSoAhgvhw@mail.gmail.com>
Dne ponedeljek, 09. maj 2022 ob 16:21:29 CEST je Arnd Bergmann napisal(a):
> On Sun, May 8, 2022 at 10:52 PM Jernej Škrabec <jernej.skrabec@gmail.com>
wrote:
> >
> > Dne petek, 06. maj 2022 ob 19:02:17 CEST je Jernej Skrabec napisal(a):
> > > Hi!
> > >
> > > Please pull following DT changes for 5.19.
> >
> > I missed one patch, please disregard.
>
> I had already merged this one, merging the new branch on top, while editing
> the merge log to not mention the duplicate commits. You can always follow up
> with additional changes based on a branch that is already merged like this
one.
Ok, thanks! I'll follow up with new PR next time.
Best regards,
Jernej
>
> Arnd
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-09 15:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 17:02 [GIT PULL] Allwinner DT changes for 5.19 Jernej Skrabec
2022-05-06 17:02 ` Jernej Skrabec
2022-05-08 20:52 ` Jernej Škrabec
2022-05-08 20:52 ` Jernej Škrabec
2022-05-09 14:21 ` Arnd Bergmann
2022-05-09 14:21 ` Arnd Bergmann
2022-05-09 15:06 ` Jernej Škrabec [this message]
2022-05-09 15:06 ` Jernej Škrabec
2022-05-13 11:43 ` Arnd Bergmann
2022-05-13 11:43 ` Arnd Bergmann
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=2368089.jE0xQCEvom@kista \
--to=jernej.skrabec@gmail.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=jernej@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=samuel@sholland.org \
--cc=soc@kernel.org \
--cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.