From: Jason Gunthorpe <jgg@ziepe.ca>
To: Robin Murphy <robin.murphy@arm.com>
Cc: neescoba@cisco.com, kbuild-all@lists.01.org,
kernel test robot <lkp@intel.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, benve@cisco.com
Subject: Re: [PATCH] RDMA/usnic: Refactor usnic_uiom_alloc_pd()
Date: Wed, 6 Apr 2022 18:53:38 -0300 [thread overview]
Message-ID: <20220406215338.GU64706@ziepe.ca> (raw)
In-Reply-To: <87075d61-c51c-8d94-9263-17aa40f7d70e@arm.com>
On Wed, Apr 06, 2022 at 10:39:47PM +0100, Robin Murphy wrote:
> On 2022-04-06 20:54, kernel test robot wrote:
> > Hi Robin,
> >
> > I love your patch! Yet something to improve:
> >
> > [auto build test ERROR on rdma/for-next]
> > [also build test ERROR on v5.18-rc1 next-20220406]
> > [If your patch is applied to the wrong git tree, kindly drop us a note.
> > And when submitting patch, we suggest to use '--base' as documented in
> > https://git-scm.com/docs/git-format-patch]
>
> Oops, I failed to notice that this does actually depend on the other patch I
> sent cleaning up iommu_present()[1] - I should have sent them together as a
> series, sorry about that.
No worries, I'll take care to order it right
Jason
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Robin Murphy <robin.murphy@arm.com>
Cc: kernel test robot <lkp@intel.com>,
benve@cisco.com, neescoba@cisco.com, kbuild-all@lists.01.org,
linux-rdma@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RDMA/usnic: Refactor usnic_uiom_alloc_pd()
Date: Wed, 6 Apr 2022 18:53:38 -0300 [thread overview]
Message-ID: <20220406215338.GU64706@ziepe.ca> (raw)
In-Reply-To: <87075d61-c51c-8d94-9263-17aa40f7d70e@arm.com>
On Wed, Apr 06, 2022 at 10:39:47PM +0100, Robin Murphy wrote:
> On 2022-04-06 20:54, kernel test robot wrote:
> > Hi Robin,
> >
> > I love your patch! Yet something to improve:
> >
> > [auto build test ERROR on rdma/for-next]
> > [also build test ERROR on v5.18-rc1 next-20220406]
> > [If your patch is applied to the wrong git tree, kindly drop us a note.
> > And when submitting patch, we suggest to use '--base' as documented in
> > https://git-scm.com/docs/git-format-patch]
>
> Oops, I failed to notice that this does actually depend on the other patch I
> sent cleaning up iommu_present()[1] - I should have sent them together as a
> series, sorry about that.
No worries, I'll take care to order it right
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH] RDMA/usnic: Refactor usnic_uiom_alloc_pd()
Date: Wed, 06 Apr 2022 18:53:38 -0300 [thread overview]
Message-ID: <20220406215338.GU64706@ziepe.ca> (raw)
In-Reply-To: <87075d61-c51c-8d94-9263-17aa40f7d70e@arm.com>
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
On Wed, Apr 06, 2022 at 10:39:47PM +0100, Robin Murphy wrote:
> On 2022-04-06 20:54, kernel test robot wrote:
> > Hi Robin,
> >
> > I love your patch! Yet something to improve:
> >
> > [auto build test ERROR on rdma/for-next]
> > [also build test ERROR on v5.18-rc1 next-20220406]
> > [If your patch is applied to the wrong git tree, kindly drop us a note.
> > And when submitting patch, we suggest to use '--base' as documented in
> > https://git-scm.com/docs/git-format-patch]
>
> Oops, I failed to notice that this does actually depend on the other patch I
> sent cleaning up iommu_present()[1] - I should have sent them together as a
> series, sorry about that.
No worries, I'll take care to order it right
Jason
next prev parent reply other threads:[~2022-04-06 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 14:35 [PATCH] RDMA/usnic: Refactor usnic_uiom_alloc_pd() Robin Murphy
2022-04-05 14:35 ` Robin Murphy
2022-04-06 19:54 ` kernel test robot
2022-04-06 19:54 ` kernel test robot
2022-04-06 21:39 ` Robin Murphy
2022-04-06 21:39 ` Robin Murphy
2022-04-06 21:39 ` Robin Murphy
2022-04-06 21:53 ` Jason Gunthorpe [this message]
2022-04-06 21:53 ` Jason Gunthorpe
2022-04-06 21:53 ` Jason Gunthorpe
2022-04-08 17:23 ` Jason Gunthorpe via iommu
2022-04-08 17:23 ` Jason Gunthorpe
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=20220406215338.GU64706@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=benve@cisco.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lkp@intel.com \
--cc=neescoba@cisco.com \
--cc=robin.murphy@arm.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.