From: Ingo Molnar <mingo@kernel.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Baruch Siach <baruch@tkos.co.il>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [GIT PULL] liblockdep fixes for v3.19
Date: Wed, 4 Feb 2015 06:59:36 +0100 [thread overview]
Message-ID: <20150204055936.GA10578@gmail.com> (raw)
In-Reply-To: <54D0C642.2050705@oracle.com>
* Sasha Levin <sasha.levin@oracle.com> wrote:
> On 02/03/2015 06:26 AM, Ingo Molnar wrote:
> >
> > * Sasha Levin <sasha.levin@oracle.com> wrote:
> >
> >> Hi Ingo,
> >>
> >> Two fixes for liblockdep. One prevents git from trying to track the generated
> >> .so libraries, and the other avoids mixups with header files when building
> >> liblockdep inside a kernel tree that doesn't match the one being currently
> >> used in the system.
> >>
> >>
> >> The following changes since commit ec6f34e5b552fb0a52e6aae1a5afbbb1605cc6cc:
> >>
> >> Linux 3.19-rc5 (2015-01-18 18:02:20 +1200)
> >>
> >> are available in the git repository at:
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux.git
> >
> > Hm, which branch is it in?
>
> Uh, I'm not sure why git didn't fill that in. Sorry.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux.git liblockdep-fixes-3.19
Pulled, thanks Sasha!
Ingo
next prev parent reply other threads:[~2015-02-04 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 12:46 [GIT PULL] liblockdep fixes for v3.19 Sasha Levin
2015-02-03 11:26 ` Ingo Molnar
2015-02-03 12:59 ` Sasha Levin
2015-02-04 5:59 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-22 2:28 Sasha Levin
2014-12-23 9:29 ` Ingo Molnar
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=20150204055936.GA10578@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=baruch@tkos.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.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.