public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the arc-current tree
Date: Wed, 30 Aug 2017 09:11:54 -0700	[thread overview]
Message-ID: <de35cfab-e727-f35f-fd41-4e553e696de2@synopsys.com> (raw)
In-Reply-To: <20170830225905.4ddb08c8@canb.auug.org.au>

On 08/30/2017 05:59 AM, Stephen Rothwell wrote:
> Hi Vineet,
>
> On Mon, 28 Aug 2017 15:28:32 -0700 Vineet Gupta <Vineet.Gupta1@synopsys.com> wrote:
>> On 08/28/2017 03:23 PM, Stephen Rothwell wrote:
>>> Commit
>>>
>>>     279921e080b9 ("ARCv2: SLC: provide a line based flush routine for debugging")
>>>
>>> is missing a Signed-off-by from its author and committer.
>>>   
>> /me slaps myself. Fixed/pushed now.
> slap again :-)

:-(

> You seem to have republished the old branch. :-(

I recently switched to a workflow where I push from 2 trees hence these SNAFUs.
Sorry for the trouble.

-Vineet

  reply	other threads:[~2017-08-30 16:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-28 22:23 linux-next: Signed-off-by missing for commit in the arc-current tree Stephen Rothwell
2017-08-28 22:28 ` Vineet Gupta
2017-08-30 12:59   ` Stephen Rothwell
2017-08-30 16:11     ` Vineet Gupta [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-29  2:13 Stephen Rothwell
2018-07-30 16:47 ` Vineet Gupta
2018-08-31  3:13 Stephen Rothwell
2024-10-07 20:48 Stephen Rothwell
2024-12-13  4:56 Stephen Rothwell
2024-12-13 22:40 ` Vineet Gupta

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=de35cfab-e727-f35f-fd41-4e553e696de2@synopsys.com \
    --to=vineet.gupta1@synopsys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox