From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: Remove FSF address from copyright headers
Date: Mon, 27 Oct 2014 01:04:55 +0000 [thread overview]
Message-ID: <20141027010455.GA30485@verge.net.au> (raw)
In-Reply-To: <1414333227-15674-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
On Sun, Oct 26, 2014 at 08:31:47PM +0100, Geert Uytterhoeven wrote:
> On Sun, Oct 26, 2014 at 3:20 PM, Laurent Pinchart
> <laurent.pinchart+renesas@ideasonboard.com> wrote:
> > The information is already included in the COPYING file in the kernel
> > sources root directory, we don't want to modify all source files when
> > the FSF will move to a new address, and I'm tired of seeing the related
> > checkpatch.pl warnings.
> >
> > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
>
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> > The fun part will be to merge this while minimizing the risk of conflicts :-)
>
> Simon can just ask Linus to pull all of this at once after v3.18-rc2?
I think it is easy enough to simply add it to a cleanup branch
and manage the conflicts from there. So far the only conflict
is with Laurent's DU-DT series (which removes some of the files
changed by this series). I have rebased it accordingly.
next prev parent reply other threads:[~2014-10-27 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 14:20 [PATCH] ARM: shmobile: Remove FSF address from copyright headers Laurent Pinchart
2014-10-26 19:31 ` Geert Uytterhoeven
2014-10-27 1:04 ` Simon Horman [this message]
2014-10-27 9:05 ` Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2014-10-30 1:50 [GIT PULL] Renesas ARM Based SoC Cleanup for v3.19 Simon Horman
2014-10-30 1:50 ` [PATCH] ARM: shmobile: Remove FSF address from copyright headers Simon Horman
2014-10-30 1:50 ` Simon Horman
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=20141027010455.GA30485@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-sh@vger.kernel.org \
/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.