From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: shmobile: Remove FSF address from copyright headers
Date: Mon, 27 Oct 2014 09:05:37 +0000 [thread overview]
Message-ID: <1414427220.i8IQn7EkpG@avalon> (raw)
In-Reply-To: <1414333227-15674-1-git-send-email-laurent.pinchart+renesas@ideasonboard.com>
Hi Simon,
On Monday 27 October 2014 10:04:55 Simon Horman wrote:
> On Sun, Oct 26, 2014 at 08:31:47PM +0100, Geert Uytterhoeven wrote:
> > On Sun, Oct 26, 2014 at 3:20 PM, Laurent Pinchart 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.
Sure, that's fine with me.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-10-27 9:05 UTC|newest]
Thread overview: 5+ 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
2014-10-27 9:05 ` Laurent Pinchart [this message]
-- 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
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=1414427220.i8IQn7EkpG@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox