public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Behan Webster <behanw@converseincode.com>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Michal Marek" <mmarek@suse.cz>,
	linux-kbuild@vger.kernel.org, "Jan-Simon Möller" <dl9pf@gmx.de>
Subject: Re: linux-next
Date: Wed, 19 Feb 2014 07:07:17 +0100	[thread overview]
Message-ID: <20140219060717.GA25806@ravnborg.org> (raw)
In-Reply-To: <53041454.6090404@converseincode.com>

> >>The LLVMLinux project is working on changes to the LLVM/clang toolchain
> >>as well as to the linux kernel code in order to be able to compile the
> >>kernel with clang.
> >I have no objection to this, but would like to see more of these patches
> >reviewed by (among others) the kbuild guys (cc'd).  I also could not find
> >some of these patches published on lkml (where I would expect to see
> >them).  And the top patch has a very uninformative commit message :-(
> Of course. That is the intention. I'll review all the commit
> messages as well.

Please send the patches as least to linux-kbuild for review.
I almost never go hunting for patches in a git repo for review,
and this is the same for others.

	Sam

  reply	other threads:[~2014-02-19  6:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5303C695.4030403@converseincode.com>
2014-02-19  0:17 ` linux-next Stephen Rothwell
2014-02-19  2:17   ` linux-next Behan Webster
2014-02-19  6:07     ` Sam Ravnborg [this message]
2014-02-19  6:12       ` linux-next Behan Webster
2014-02-19  6:22         ` linux-next Stephen Rothwell
2014-02-19 18:06           ` linux-next Behan Webster
2014-02-20  0:03             ` linux-next Stephen Rothwell

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=20140219060717.GA25806@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=behanw@converseincode.com \
    --cc=dl9pf@gmx.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox