From: Dan Carpenter <dan.carpenter@oracle.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: "open list:ANDROID DRIVERS" <devel@driverdev.osuosl.org>,
"Bharath Vedartham" <linux.bhar@gmail.com>,
harshjain32@gmail.com, "John Hubbard" <jhubbard@nvidia.com>,
"Simon Sandström" <simon@nikanor.nu>,
linux-kernel@vger.kernel.org,
"Greg KH" <gregkh@linuxfoundation.org>,
jane.pnx9@gmail.com
Subject: Re: [PATCH] staging: kpc2000: kpc_dma: Convert get_user_pages() --> pin_user_pages()
Date: Mon, 8 Jun 2020 22:55:21 +0300 [thread overview]
Message-ID: <20200608195520.GB30374@kadam> (raw)
In-Reply-To: <CAFqt6zYqnRWYSKoZ2yAdcAK7WWa311Mmmc3Y3dm8CO9r79ZtYg@mail.gmail.com>
On Tue, Jun 09, 2020 at 01:03:51AM +0530, Souptick Joarder wrote:
> On Tue, Jun 9, 2020 at 12:47 AM Dan Carpenter <dan.carpenter@oracle.com> wrote:
> >
> > On Tue, Jun 09, 2020 at 12:31:42AM +0530, Souptick Joarder wrote:
> > > > > @@ -189,10 +192,9 @@ static int kpc_dma_transfer(struct dev_private_data *priv,
> > > > > sg_free_table(&acd->sgt);
> > > > > err_dma_map_sg:
> > > > > err_alloc_sg_table:
> > > >
> > > > So now we end up with two unnecessary labels. Probably best to delete two of these
> > > > three and name the remaining one appropriately:
> > >
> > > Hmm, I thought about it. But later decided to wait for review comments
> > > on the same in v1.
> > > I will remove it now.
> >
> > These are all unrelated to pin_user_pages(). Please don't do it in the
> > same patch. Staging code is there because it's ugly... If you don't
> > want to do unrelated changes to label names then you don't have to.
>
> What I am planning is to put this changes in a series. One patch will take care
> of pin_user_pages() related changes, 2nd patch will take care of minor bug
> fix in error path + level correction and 3rd patch
> will take care of set_page_dirty() -> set_page_dirty_lock().
Always do bug fixes first. Always do the easiest least controversial
after first.
Do the error handling bug first. Change "rv" to int. That's closely
related to the error handling. Then set_page_dirty_lock(). Then the
conversion to pin_user_pages().
Then if you want you can do any unrelated clean ups and error label
renames as patch 4.
regards,
dan carpenter
prev parent reply other threads:[~2020-06-08 19:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 17:51 [PATCH] staging: kpc2000: kpc_dma: Convert get_user_pages() --> pin_user_pages() Souptick Joarder
2020-06-01 1:44 ` John Hubbard
2020-06-08 19:01 ` Souptick Joarder
2020-06-08 19:05 ` John Hubbard
2020-06-08 19:16 ` Dan Carpenter
2020-06-08 19:22 ` John Hubbard
2020-06-08 19:14 ` Dan Carpenter
2020-06-08 19:33 ` Souptick Joarder
2020-06-08 19:55 ` Dan Carpenter [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=20200608195520.GB30374@kadam \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=harshjain32@gmail.com \
--cc=jane.pnx9@gmail.com \
--cc=jhubbard@nvidia.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.bhar@gmail.com \
--cc=simon@nikanor.nu \
/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