All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Sandeep Patil <sspatil@google.com>,
	Matthias Kaehlcke <mka@chromium.org>,
	Nathan Chancellor <natechancellor@gmail.com>
Subject: Clang backports for 4.9 and 4.4
Date: Mon, 19 Nov 2018 10:31:35 -0800	[thread overview]
Message-ID: <CAKwvOdm4ZDa245csse093mHx_-gCunoM4Wv1_T361cQj-c3hmg@mail.gmail.com> (raw)

Greg,
I'm in the process of preparing backports for building 4.9 and 4.4
kernels with Clang.  Going off of mka's very helpful:
https://lkml.org/lkml/2017/11/22/943, I've prepared the list of SHA's
that were marked UPSTREAM (internal convention used to denote patch
applies cleanly):
https://gist.github.com/nickdesaulniers/fe995f4b7c52af8de1a283c0a53562d9.
But it seems that some of these shas no longer apply cleanly.  I was
thus curious:

1. May I send you a pull request with the patches properly backported?
I'm happy to do the work, just want a green light before backporting
all of these patches.
2. Should I denote in any way if I had to modify any patch to get it
to apply cleanly?  This helps in code review, IMO.  If so, what
convention should I use?

-- 
Thanks,
~Nick Desaulniers

             reply	other threads:[~2018-11-20  4:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 18:31 Nick Desaulniers [this message]
2018-11-19 18:52 ` Clang backports for 4.9 and 4.4 Nathan Chancellor
2018-11-19 19:17   ` Nick Desaulniers
2018-11-19 19:20     ` Nathan Chancellor
2018-11-19 23:13       ` Nick Desaulniers
2018-11-20  7:48         ` Greg KH
2018-11-20 11:26           ` Nathan Chancellor
2018-11-20 12:07             ` Greg KH
2018-11-20 16:46               ` Nathan Chancellor
2018-11-20 16:52                 ` Greg KH
2018-11-20 17:30                   ` Nick Desaulniers
2018-11-21 18:19                     ` Greg KH
2018-11-21 18:38                       ` Nick Desaulniers

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=CAKwvOdm4ZDa245csse093mHx_-gCunoM4Wv1_T361cQj-c3hmg@mail.gmail.com \
    --to=ndesaulniers@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=mka@chromium.org \
    --cc=natechancellor@gmail.com \
    --cc=sspatil@google.com \
    --cc=stable@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.