From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Laura Abbott <labbott@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: Remove FSF address
Date: Thu, 21 Dec 2017 08:05:56 -0300 [thread overview]
Message-ID: <20171221110556.GO21971@kernel.org> (raw)
In-Reply-To: <20171215135919.GA21971@kernel.org>
Em Fri, Dec 15, 2017 at 10:59:19AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Dec 14, 2017 at 03:28:45PM -0800, Laura Abbott escreveu:
> > Checkpatch in the kernel now complains about having the FSF address
> > in comments. Other tools such as rpmlint are now starting to do the
> > same thing. Remove the FSF address to reduce warnings on multiple tools.
> >
> > Signed-off-by: Laura Abbott <labbott@redhat.com>
> > ---
> > For context, I'm updating the packaging for perf in Fedora which
> > requires a code/output review. This got flagged during that review.
>
> Thanks for the patch, applied.
Ingo pointed out to me that for the files we copied from the kernel we
better wait for the kernel original files to be changed, when we'll
notice via tools/perf/check-headers.sh and update the copies. The intel
pt decoder still have this check done outside check-headers.sh, we need
to do it there, conceptually its the same issue tho.
I'll separate the patch that touches things that are tools/ only and
apply next week, when I get back from vacation time.
- Arnaldo
prev parent reply other threads:[~2017-12-21 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 23:28 [PATCH] perf: Remove FSF address Laura Abbott
[not found] ` <20171215135919.GA21971@kernel.org>
2017-12-21 11:05 ` Arnaldo Carvalho de Melo [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=20171221110556.GO21971@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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.