All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: Olof Johansson <olof@lixom.net>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	 SoC Team <soc@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 0/5] SoC changes for 5.17
Date: Tue, 4 Jan 2022 20:40:43 -0500	[thread overview]
Message-ID: <CAK8P3a3sBADt4Cu=LGbjHQpQ32O-BtFk1aQFwhL8Ar=M_gj6Xw@mail.gmail.com> (raw)
In-Reply-To: <CAOesGMgx99GJ3gQmdgauSs3aF8xr4FgcgsELRz4HSVXmujHJnQ@mail.gmail.com>

On Tue, Jan 4, 2022 at 7:40 PM Olof Johansson <olof@lixom.net> wrote:
> On Tue, Jan 4, 2022 at 1:58 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
> > On 12/24/21 9:11 AM, Florian Fainelli wrote:
> > >
> > > Should I resend or fix something in those? Thanks!
> >
> >
> > Arnd, Olof, do I need to resend the 3 pull requests mentioned above?
> > Thanks and happy new year.
>
> I'm about to make a pass of merges, likely tomorrow -- I had to get my
> Honeycomb working again since it hosts all the trees and mailboxes for
> me.
>
> No need to resend at this time.

It's possible that I had accidentally merged them in the end but tagged
the branch without those merge commits, so have a look if it's in there.

I'm still traveling, so I have no access to my reflog. I'm sure there was
nothing wrong with the contents, so either they came after I had
tagged the branches, or I made a mistake.

        Arnd

WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@kernel.org>
To: Olof Johansson <olof@lixom.net>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	SoC Team <soc@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 0/5] SoC changes for 5.17
Date: Tue, 4 Jan 2022 20:40:43 -0500	[thread overview]
Message-ID: <CAK8P3a3sBADt4Cu=LGbjHQpQ32O-BtFk1aQFwhL8Ar=M_gj6Xw@mail.gmail.com> (raw)
In-Reply-To: <CAOesGMgx99GJ3gQmdgauSs3aF8xr4FgcgsELRz4HSVXmujHJnQ@mail.gmail.com>

On Tue, Jan 4, 2022 at 7:40 PM Olof Johansson <olof@lixom.net> wrote:
> On Tue, Jan 4, 2022 at 1:58 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
> > On 12/24/21 9:11 AM, Florian Fainelli wrote:
> > >
> > > Should I resend or fix something in those? Thanks!
> >
> >
> > Arnd, Olof, do I need to resend the 3 pull requests mentioned above?
> > Thanks and happy new year.
>
> I'm about to make a pass of merges, likely tomorrow -- I had to get my
> Honeycomb working again since it hosts all the trees and mailboxes for
> me.
>
> No need to resend at this time.

It's possible that I had accidentally merged them in the end but tagged
the branch without those merge commits, so have a look if it's in there.

I'm still traveling, so I have no access to my reflog. I'm sure there was
nothing wrong with the contents, so either they came after I had
tagged the branches, or I made a mistake.

        Arnd

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-01-05  1:40 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 21:31 [GIT PULL 0/5] SoC changes for 5.17 Arnd Bergmann
2021-12-23 21:31 ` Arnd Bergmann
2021-12-23 21:32 ` [GIT PULL 1/5] ARM: SoC updates for v5.17 Arnd Bergmann
2021-12-23 21:32   ` Arnd Bergmann
2022-01-10 18:28   ` pr-tracker-bot
2022-01-10 18:28     ` pr-tracker-bot
2021-12-23 21:33 ` [GIT PULL 2/5] ARM: defconfig updates for 5.17 Arnd Bergmann
2021-12-23 21:33   ` Arnd Bergmann
2022-01-10 18:28   ` pr-tracker-bot
2022-01-10 18:28     ` pr-tracker-bot
2021-12-23 21:34 ` [GIT PULL 3/5] ARM: SoC driver updates for v5.17 Arnd Bergmann
2021-12-23 21:34   ` Arnd Bergmann
2022-01-10 18:28   ` pr-tracker-bot
2022-01-10 18:28     ` pr-tracker-bot
2021-12-23 21:35 ` [GIT PULL 4/5] ARM: SoC devicetree changes " Arnd Bergmann
2021-12-23 21:35   ` Arnd Bergmann
2022-01-10 18:28   ` pr-tracker-bot
2022-01-10 18:28     ` pr-tracker-bot
2021-12-23 21:37 ` [GIT PULL 5/5] SoC: Add support for StarFive JH7100 RISC-V SoC Arnd Bergmann
2021-12-23 21:37   ` Arnd Bergmann
2022-01-10 18:28   ` pr-tracker-bot
2022-01-10 18:28     ` pr-tracker-bot
2021-12-24 17:11 ` [GIT PULL 0/5] SoC changes for 5.17 Florian Fainelli
2021-12-24 17:11   ` Florian Fainelli
2022-01-04 21:58   ` Florian Fainelli
2022-01-04 21:58     ` Florian Fainelli
2022-01-05  0:40     ` Olof Johansson
2022-01-05  0:40       ` Olof Johansson
2022-01-05  1:40       ` Arnd Bergmann [this message]
2022-01-05  1:40         ` Arnd Bergmann
2022-01-10 18:32         ` Olof Johansson
2022-01-10 18:32           ` Olof Johansson
2022-01-10 18:56           ` Florian Fainelli
2022-01-10 18:56             ` Florian Fainelli
2022-01-25 18:47           ` Bjorn Andersson
2022-01-25 18:47             ` Bjorn Andersson
2022-02-07 14:32 ` patchwork-bot+linux-soc
2022-10-28 21:03 Tj Nenka

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='CAK8P3a3sBADt4Cu=LGbjHQpQ32O-BtFk1aQFwhL8Ar=M_gj6Xw@mail.gmail.com' \
    --to=arnd@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=soc@kernel.org \
    --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 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.