From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Jan-Simon Möller" <dl9pf@gmx.de>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [TRIVIAL] Remove braces to fix build for clang. No functional change otherwise.
Date: Tue, 20 Aug 2013 14:43:55 -0700 [thread overview]
Message-ID: <20130820214355.GA10949@kroah.com> (raw)
In-Reply-To: <1729833.NqCHnaFaae@aragorn.auenland.lan>
On Tue, Aug 20, 2013 at 11:26:01PM +0200, Jan-Simon Möller wrote:
> On Tuesday 20 August 2013 14:24:33 Greg Kroah-Hartman wrote:
> > On Tue, Aug 20, 2013 at 10:52:06PM +0200, dl9pf@gmx.de wrote:
> > > From: Jan-Simon Möller <dl9pf@gmx.de>
> > >
> > > Author: PaX Team <pageexec at freemail.hu>
> > > ML-Post:
> > > http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120507/1427
> > > 07.html URL: http://llvm.linuxfoundation.org
> > >
> > > Merge: Jan-Simon Möller <dl9pf at gmx.de>
> >
> > What am I supposed to do with these?
> >
> > > Description:
> > > Clang chokes on the notation "inl (%dx)" but works for "inl %dx"; GNU as
> > > accepts both forms.
> > No need for "description", that's implied by the body of the changelog
> > text. Also, you can wrap your lines :)
> >
> > I'll clean this all up by hand, but please do this next time so I don't
> > have to.
>
> Roger that - ignore it in the other 2 I just sent out. c'n'p from the
> existing commit msg.
> Do you want all 3 w/o then ?
As the other two were not sent to me (I'm not a maintainer of those
areas of the kernel), I have no idea, sorry.
greg k-h
next prev parent reply other threads:[~2013-08-20 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 20:52 [PATCH] [TRIVIAL] Remove braces to fix build for clang. No functional change otherwise dl9pf
2013-08-20 21:24 ` Greg Kroah-Hartman
2013-08-20 21:26 ` Jan-Simon Möller
2013-08-20 21:43 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-08-29 14:10 dl9pf
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=20130820214355.GA10949@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=dl9pf@gmx.de \
--cc=linux-kernel@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.