All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH 0/2] fix missing evaluation when using '-include <file>'
Date: Tue, 13 Feb 2018 15:49:56 -0800	[thread overview]
Message-ID: <CANeU7QkhZix7xj4_pskyPUXSsSLX1qpXU98rJTf1BBBbxvCnXg@mail.gmail.com> (raw)
In-Reply-To: <20180210200237.a4xmiyppshy5bbbk@ltop.local>

On Sat, Feb 10, 2018 at 12:02 PM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> On Tue, Jan 30, 2018 at 02:23:11PM +0100, Jason A. Donenfeld wrote:
>> Any chance of this getting merged into the real sparse tree?
>>
>> Jason
>
> Chris,
>
> Can you please take a look at this one, please?

Hi, I take a look at this series. It is this series, right?

https://patchwork.kernel.org/patch/9954727/

It looks fine to me. I do want to apply them.

Do you want to make this 2 patch series pullable from master
or I just apply them as patch?

Chris

  reply	other threads:[~2018-02-13 23:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHmME9o--jumLrBbRn63ewKOE49+uYJ9B8V5FocptdwZ5Kd9Fw@mail.gmail.com>
2017-04-04 20:12 ` sparse with 4.10? Luc Van Oostenryck
     [not found]   ` <CAHmME9qu6p344M_VnubGtRYvbM7+w4kDmHGJG_PZvLK0kaheOw@mail.gmail.com>
2017-09-16 12:25     ` Jason A. Donenfeld
2017-09-16 14:33       ` Luc Van Oostenryck
2017-09-17 10:05       ` [PATCH 0/2] fix missing evaluation when using '-include <file>' Luc Van Oostenryck
2017-09-17 10:05         ` [PATCH 1/2] fix: missing evaluate with '-include' : add testcase Luc Van Oostenryck
2017-09-17 10:05         ` [PATCH 2/2] fix: missing evaluate with '-include' Luc Van Oostenryck
2017-09-17 11:59         ` [PATCH 0/2] fix missing evaluation when using '-include <file>' Jason A. Donenfeld
2017-09-17 19:02           ` Luc Van Oostenryck
2017-11-05 16:52             ` Luc Van Oostenryck
2018-01-30 13:23               ` Jason A. Donenfeld
2018-02-10 20:02                 ` Luc Van Oostenryck
2018-02-13 23:49                   ` Christopher Li [this message]
2018-02-14  0:02                     ` Luc Van Oostenryck
2018-02-14 12:15                       ` Jason A. Donenfeld
2018-02-15  0:00                         ` Randy Dunlap

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=CANeU7QkhZix7xj4_pskyPUXSsSLX1qpXU98rJTf1BBBbxvCnXg@mail.gmail.com \
    --to=sparse@chrisli.org \
    --cc=Jason@zx2c4.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    /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.