mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Ingo Molnar <mingo@kernel.org>
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: Tue, 03 Feb 2015 07:59:46 -0500	[thread overview]
Message-ID: <54D0C642.2050705@oracle.com> (raw)
In-Reply-To: <20150203112645.GD2511@gmail.com>

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


Thanks,
Sasha

  reply	other threads:[~2015-02-03 13:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 12:46 Sasha Levin
2015-02-03 11:26 ` Ingo Molnar
2015-02-03 12:59   ` Sasha Levin [this message]
2015-02-04  5:59     ` Ingo Molnar
  -- 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=54D0C642.2050705@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=baruch@tkos.co.il \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome