From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next 0/3] Clean up and improvements for 5.7
Date: Wed, 18 Mar 2020 20:28:30 -0300 [thread overview]
Message-ID: <20200318232830.GA18585@ziepe.ca> (raw)
In-Reply-To: <20200316210246.7753.40221.stgit@awfm-01.aw.intel.com>
On Mon, Mar 16, 2020 at 05:04:47PM -0400, Dennis Dalessandro wrote:
> Here are some clean up/improvement patches. Mike got rid of dead code and Kaike
> took a stab at fixing the kobj and cdev complaints. This serious should
> go before the AIP posting. I'll be posting a v2 of the AIP code soon, and I
> think I still owe a response on one issue. Coming up, but for now it's just
> these 3.
>
>
> Kaike Wan (2):
> IB/hfi1: Remove kobj from hfi1_devdata
>
> Mike Marciniszyn (1):
> IB/rdmavt: Delete unused routine
I'm going to take these two to for-next
> IB/hfi1: Use the ibdev in hfi1_devdata as the parent of cdev
This one is getting closer to the right idea but needs a lot more work
Thanks,
Jason
prev parent reply other threads:[~2020-03-18 23:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 21:04 [PATCH for-next 0/3] Clean up and improvements for 5.7 Dennis Dalessandro
2020-03-16 21:04 ` [PATCH for-next 1/3] IB/rdmavt: Delete unused routine Dennis Dalessandro
2020-03-16 21:05 ` [PATCH for-next 2/3] IB/hfi1: Remove kobj from hfi1_devdata Dennis Dalessandro
2020-03-16 21:05 ` [PATCH for-next 3/3] IB/hfi1: Use the ibdev in hfi1_devdata as the parent of cdev Dennis Dalessandro
2020-03-18 13:31 ` Jason Gunthorpe
2020-03-18 16:02 ` Wan, Kaike
2020-03-18 16:34 ` Jason Gunthorpe
2020-03-18 17:13 ` Wan, Kaike
2020-03-18 23:18 ` Jason Gunthorpe
2020-03-20 12:19 ` Wan, Kaike
2020-03-20 16:09 ` Wan, Kaike
2020-03-20 16:32 ` Jason Gunthorpe
2020-03-20 17:30 ` Wan, Kaike
2020-03-20 17:33 ` Jason Gunthorpe
2020-03-18 23:28 ` Jason Gunthorpe [this message]
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=20200318232830.GA18585@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=linux-rdma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).