All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
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: Fri, 17 Jul 2020 10:59:03 -0500	[thread overview]
Message-ID: <2aa2b6dd-5d78-cf7a-6a7f-bc07dc1fef43@kernel.org> (raw)
In-Reply-To: <CAK8P3a3YXWx5PhnZzsX_fYD0FC92XAn=2gr_3MA8dJ=zSpToBw@mail.gmail.com>



On 7/17/20 10:46 AM, Arnd Bergmann wrote:
> On Fri, Jul 17, 2020 at 5:36 PM Dinh Nguyen <dinguyen@kernel.org> wrote:
>> On 7/16/20 3:10 PM, Arnd Bergmann wrote:
>>> 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.
>>>
>>
>> Thank you!
> 
> I was about to send off the pull request to Linus now, but I now saw
> that the tag I pulled was not updated and still has the broken lines.
> 
> Could you make sure you upload a new tag and send the pull
> request for that so I can pull it once more?
> 

I just sent you an updated pull request for the tag
socfpga_fixes_for_v5.8_v2.

Thanks,
Dinh

WARNING: multiple messages have this Message-ID (diff)
From: Dinh Nguyen <dinguyen@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
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: Fri, 17 Jul 2020 10:59:03 -0500	[thread overview]
Message-ID: <2aa2b6dd-5d78-cf7a-6a7f-bc07dc1fef43@kernel.org> (raw)
In-Reply-To: <CAK8P3a3YXWx5PhnZzsX_fYD0FC92XAn=2gr_3MA8dJ=zSpToBw@mail.gmail.com>



On 7/17/20 10:46 AM, Arnd Bergmann wrote:
> On Fri, Jul 17, 2020 at 5:36 PM Dinh Nguyen <dinguyen@kernel.org> wrote:
>> On 7/16/20 3:10 PM, Arnd Bergmann wrote:
>>> 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.
>>>
>>
>> Thank you!
> 
> I was about to send off the pull request to Linus now, but I now saw
> that the tag I pulled was not updated and still has the broken lines.
> 
> Could you make sure you upload a new tag and send the pull
> request for that so I can pull it once more?
> 

I just sent you an updated pull request for the tag
socfpga_fixes_for_v5.8_v2.

Thanks,
Dinh

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

  reply	other threads:[~2020-07-17 15:59 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
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 [this message]
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=2aa2b6dd-5d78-cf7a-6a7f-bc07dc1fef43@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=arnd@arndb.de \
    --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.