All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@fedoraproject.org>
To: Oded Gabbay <oded.gabbay@amd.com>
Cc: Joerg Roedel <joro@8bytes.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
	iommu@lists.linux-foundation.org
Subject: Re: [git pull] IOMMU Updates for Linux v4.1
Date: Tue, 5 May 2015 14:22:02 -0400	[thread overview]
Message-ID: <CA+5PVA63kPZcbzsjd1EE=rzL_CwF8yNXTdoZf=6RvGCpvtq04Q@mail.gmail.com> (raw)
In-Reply-To: <5545BDB2.6020006@amd.com>

On Sun, May 3, 2015 at 2:18 AM, Oded Gabbay <oded.gabbay@amd.com> wrote:
>
>
> On 05/03/2015 01:14 AM, Joerg Roedel wrote:
>>
>> Hi Oded,
>>
>> On Sat, May 02, 2015 at 07:59:39PM +0300, Oded Gabbay wrote:
>>>
>>> However, Joerg is not answering my emails for some reason
>>> (vacation/sick?)
>>
>>
>> Sorry, I was travelling for the last 3 weeks and had bad internet
>> access. But I am back and will take care of this on Monday.
>>
>>
>>         Joerg
>>
> Glad to hear it was vacation and not my other guess :)
> Usually I'd be more patient, but as Fedora 22 already uses kernel 4.0, I
> wanted to get this fix asap into stable.

Is Fedora a particular concern here, or did you just happen to notice
we're shipping with 4.0?  I'm curious if there is a Fedora bug that
was reported for the issue you're concerned about that we may have
missed.

josh

  reply	other threads:[~2015-05-05 18:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20  2:34 [git pull] IOMMU Updates for Linux v4.1 Joerg Roedel
2015-04-20  6:23 ` Oded Gabbay
2015-04-20  6:23   ` Oded Gabbay
2015-05-02 16:59   ` Oded Gabbay
2015-05-02 16:59     ` Oded Gabbay
2015-05-02 22:14     ` Joerg Roedel
2015-05-03  6:18       ` Oded Gabbay
2015-05-03  6:18         ` Oded Gabbay
2015-05-05 18:22         ` Josh Boyer [this message]
2015-05-06 12:03           ` Oded Gabbay

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='CA+5PVA63kPZcbzsjd1EE=rzL_CwF8yNXTdoZf=6RvGCpvtq04Q@mail.gmail.com' \
    --to=jwboyer@fedoraproject.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oded.gabbay@amd.com \
    --cc=torvalds@linux-foundation.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.