All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] iommu/vt-d: Move Kconfig and Makefile bits down into intel directory
Date: Tue, 30 Jun 2020 11:43:10 +0200	[thread overview]
Message-ID: <20200630094310.GF28824@8bytes.org> (raw)
In-Reply-To: <20200612231100.293734-2-jsnitsel@redhat.com>

Hi Jerry,

On Fri, Jun 12, 2020 at 04:10:59PM -0700, Jerry Snitselaar wrote:
> Move Intel Kconfig and Makefile bits down into intel directory
> with the rest of the Intel specific files.
> 
> Cc: Joerg Roedel <joro@8bytes.org>
> Cc: Lu Baolu <baolu.lu@linux.intel.com>
> Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
> ---
>  drivers/iommu/Kconfig        | 86 +-----------------------------------
>  drivers/iommu/Makefile       |  8 +---
>  drivers/iommu/intel/Kconfig  | 86 ++++++++++++++++++++++++++++++++++++
>  drivers/iommu/intel/Makefile |  7 +++

The patches do not apply to v5.8-rc3, can you please rebase them and
resend?

Thanks,

	Joerg
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [PATCH 1/2] iommu/vt-d: Move Kconfig and Makefile bits down into intel directory
Date: Tue, 30 Jun 2020 11:43:10 +0200	[thread overview]
Message-ID: <20200630094310.GF28824@8bytes.org> (raw)
In-Reply-To: <20200612231100.293734-2-jsnitsel@redhat.com>

Hi Jerry,

On Fri, Jun 12, 2020 at 04:10:59PM -0700, Jerry Snitselaar wrote:
> Move Intel Kconfig and Makefile bits down into intel directory
> with the rest of the Intel specific files.
> 
> Cc: Joerg Roedel <joro@8bytes.org>
> Cc: Lu Baolu <baolu.lu@linux.intel.com>
> Signed-off-by: Jerry Snitselaar <jsnitsel@redhat.com>
> ---
>  drivers/iommu/Kconfig        | 86 +-----------------------------------
>  drivers/iommu/Makefile       |  8 +---
>  drivers/iommu/intel/Kconfig  | 86 ++++++++++++++++++++++++++++++++++++
>  drivers/iommu/intel/Makefile |  7 +++

The patches do not apply to v5.8-rc3, can you please rebase them and
resend?

Thanks,

	Joerg

  parent reply	other threads:[~2020-06-30  9:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-12 23:10 [PATCH 0/2] iommu: Move AMD and Intel Kconfig + Makefile bits into their directories Jerry Snitselaar
2020-06-12 23:10 ` Jerry Snitselaar
2020-06-12 23:10 ` [PATCH 1/2] iommu/vt-d: Move Kconfig and Makefile bits down into intel directory Jerry Snitselaar
2020-06-12 23:10   ` Jerry Snitselaar
2020-06-13  1:50   ` Lu Baolu
2020-06-13  1:50     ` Lu Baolu
2020-06-30  9:43   ` Joerg Roedel [this message]
2020-06-30  9:43     ` Joerg Roedel
2020-06-12 23:11 ` [PATCH 2/2] iommu/amd: Move Kconfig and Makefile bits down into amd directory Jerry Snitselaar
2020-06-12 23:11   ` Jerry Snitselaar
2020-06-15 12:16   ` Suravee Suthikulpanit
2020-06-15 12:16     ` Suravee Suthikulpanit

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=20200630094310.GF28824@8bytes.org \
    --to=joro@8bytes.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jsnitsel@redhat.com \
    --cc=linux-kernel@vger.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 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.