All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Guan Xuetao <gxt@mprc.pku.edu.cn>,
	sfr@canb.auug.org.au, linux-next@vger.kernel.org
Subject: [Consult] About only one Signed-of-by for the patches
Date: Tue, 27 May 2014 09:23:38 +0800	[thread overview]
Message-ID: <5383E91A.4010208@gmail.com> (raw)

Hello Maintainers:

I find some of patches are only Signed-of-by me, are they OK?

e.g:

commit d7de15786d1a10fa18b80fd44026d442e7a84bd2
Author: Chen Gang <gang.chen.5i5j@gmail.com>
Date:   Tue Apr 15 09:21:30 2014 +0800

    arch:unicore32:mm: add devmem_is_allowed() to support STRICT_DEVMEM
    
    unicore32 supports STRICT_DEVMEM, so it needs devmem_is_allowed(), like
    some of other architectures have done (e.g. arm, powerpc, x86 ...).
    
    The related error with allmodconfig:
    
        CC      drivers/char/mem.o
      drivers/char/mem.c: In function â<U+0080><U+0098>range_is_allowedâ<U+0080><U+0099>:
      drivers/char/mem.c:69: error: implicit declaration of function â<U+0080><U+0098>devmem_is_allowedâ<U+0080><U+0099>
      make[2]: *** [drivers/char/mem.o] Error 1
      make[1]: *** [drivers/char] Error 2
      make: *** [drivers] Error 2
    
    Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
    Acked-by: Xuetao Guan <gxt@mprc.pku.edu.cn>


Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

             reply	other threads:[~2014-05-27  1:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27  1:23 Chen Gang [this message]
2014-05-27  1:34 ` [Consult] About only one Signed-of-by for the patches Stephen Rothwell
2014-05-27  1:50   ` Chen Gang
2014-05-27  5:07   ` 回复: " Xuetao Guan 
2014-05-27 22:43     ` Stephen Rothwell
2014-05-28  0:00       ` 回复: " Xuetao Guan 

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=5383E91A.4010208@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=gxt@mprc.pku.edu.cn \
    --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 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.