From: Arnd Bergmann <arnd@arndb.de>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Olof Johansson <olof@lixom.net>,
ARM <linux-arm-kernel@lists.infradead.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: linux-next: Fixes tags need some work in the arm-soc-fixes tree
Date: Thu, 16 Jul 2020 22:10:16 +0200 [thread overview]
Message-ID: <CAK8P3a06bHeOqkQPG3Ap4hu4yFU-LA3L-5nwqk+7VGhSrKO_ng@mail.gmail.com> (raw)
In-Reply-To: <1381a6c0-22fe-a175-f649-ea49da3451da@kernel.org>
On Wed, Jul 15, 2020 at 9:14 PM Dinh Nguyen <dinguyen@kernel.org> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi,
>
> I apologize for this! I have an updated branch that fixes these tags.
> Let me know if I need to respin the pull request.
I've recreated the branch from scratch now (this was one of only
two pull requests I got anyway), it should be fine now.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Dinh Nguyen <dinguyen@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Olof Johansson <olof@lixom.net>,
ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: linux-next: Fixes tags need some work in the arm-soc-fixes tree
Date: Thu, 16 Jul 2020 22:10:16 +0200 [thread overview]
Message-ID: <CAK8P3a06bHeOqkQPG3Ap4hu4yFU-LA3L-5nwqk+7VGhSrKO_ng@mail.gmail.com> (raw)
In-Reply-To: <1381a6c0-22fe-a175-f649-ea49da3451da@kernel.org>
On Wed, Jul 15, 2020 at 9:14 PM Dinh Nguyen <dinguyen@kernel.org> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi,
>
> I apologize for this! I have an updated branch that fixes these tags.
> Let me know if I need to respin the pull request.
I've recreated the branch from scratch now (this was one of only
two pull requests I got anyway), it should be fine now.
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:[~2020-07-16 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 21:57 linux-next: Fixes tags need some work in the arm-soc-fixes tree Stephen Rothwell
2020-07-13 21:57 ` Stephen Rothwell
2020-07-15 19:14 ` Dinh Nguyen
2020-07-15 19:14 ` Dinh Nguyen
2020-07-16 20:10 ` Arnd Bergmann [this message]
2020-07-16 20:10 ` Arnd Bergmann
2020-07-17 15:36 ` Dinh Nguyen
2020-07-17 15:36 ` Dinh Nguyen
2020-07-17 15:46 ` Arnd Bergmann
2020-07-17 15:46 ` Arnd Bergmann
2020-07-17 15:59 ` Dinh Nguyen
2020-07-17 15:59 ` Dinh Nguyen
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=CAK8P3a06bHeOqkQPG3Ap4hu4yFU-LA3L-5nwqk+7VGhSrKO_ng@mail.gmail.com \
--to=arnd@arndb.de \
--cc=dinguyen@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=sfr@canb.auug.org.au \
/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.