linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
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-bys missing for commit in the microblaze tree
Date: Wed, 21 Mar 2018 12:50:35 +0100	[thread overview]
Message-ID: <31dbebc4-8889-85de-aa12-7dab4cc0494f@monstr.eu> (raw)
In-Reply-To: <20180321075251.49f3c1a3@canb.auug.org.au>


[-- Attachment #1.1: Type: text/plain, Size: 743 bytes --]

Hi Stephen,

On 20.3.2018 21:52, Stephen Rothwell wrote:
> Hi Michal,
> 
> Commit
> 
>   39a21eefea04 ("MICROBLAZE")
> 
> is missing any Signed-off-bys.  In fact, it is a very strange commit
> message.
> 

Thanks for reporting it. It was just my testing commit not it shouldn't
be there. I have fixed that just now. Interesting is that my local
branch showed that this commit is not there.
Anyway thank you so much for reporting.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2018-03-21 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 20:52 linux-next: Signed-off-bys missing for commit in the microblaze tree Stephen Rothwell
2018-03-21 11:50 ` Michal Simek [this message]

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=31dbebc4-8889-85de-aa12-7dab4cc0494f@monstr.eu \
    --to=monstr@monstr.eu \
    --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;
as well as URLs for NNTP newsgroup(s).