From: Josh Triplett <josh@kernel.org>
To: Christopher Li <sparse@chrisli.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] lib: __builtin_object_size should accept void *
Date: Wed, 23 Nov 2016 20:35:36 -0800 [thread overview]
Message-ID: <20161124043536.cw2664fjdsdg7ssy@x> (raw)
In-Reply-To: <CANeU7Q=tRrCDxo25xgQC8qAQJsA27dEUiJ8sjDTXU-HAL3_h6w@mail.gmail.com>
On Thu, Nov 24, 2016 at 12:01:21PM +0800, Christopher Li wrote:
> On Thu, Nov 24, 2016 at 11:28 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
> > Doesn't seem to be pushed yet - at least I don't see it in master
> > on git://git.kernel.org/pub/scm/devel/sparse/sparse.git
>
> That is right. I haven't push them out yet. The last few days have been a bit
> hectic for me in terms patch apply and modify. I am considering setup
> a linux-next
> like staging repository for sparse. Maybe sparse-next?
Probably doesn't need a separate integration repository; if you want to
stage changes that you don't know you want to ship yet, a "next" branch
in the main repository would be easier for people to find and use. If
you just want to give changes time to stabilize, you can probably put
them on "master" and just not release them yet.
next prev parent reply other threads:[~2016-11-24 4:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 20:24 [PATCH] lib: __builtin_object_size should accept void * Michael S. Tsirkin
2016-11-24 0:16 ` Christopher Li
2016-11-24 3:28 ` Michael S. Tsirkin
2016-11-24 4:01 ` Christopher Li
2016-11-24 4:35 ` Josh Triplett [this message]
2016-11-24 5:03 ` Christopher Li
2016-11-24 5:19 ` Josh Triplett
2016-11-24 5:49 ` Christopher Li
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=20161124043536.cw2664fjdsdg7ssy@x \
--to=josh@kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=mst@redhat.com \
--cc=sparse@chrisli.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox