From: Greg KH <gregkh@linuxfoundation.org>
To: Liam Mark <lmark@codeaurora.org>
Cc: devel@driverdev.osuosl.org, linaro-mm-sig@lists.linaro.org,
Sumit Semwal <sumit.semwal@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: android: ion: Initialize dma_address of new sg list
Date: Fri, 16 Feb 2018 19:50:59 +0100 [thread overview]
Message-ID: <20180216185059.GC9616@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1802160956030.20374@lmark-linux.qualcomm.com>
On Fri, Feb 16, 2018 at 09:57:12AM -0800, Liam Mark wrote:
> On Fri, 16 Feb 2018, Greg KH wrote:
>
> > On Fri, Feb 09, 2018 at 10:16:56PM -0800, Liam Mark wrote:
> > > Fix the dup_sg_table function to initialize the dma_address of the new
> > > sg list entries instead of the source dma_address entries.
> > >
> > > Fixes: 17fd283f3870 ("staging: android: ion: Duplicate sg_table")
> >
> > So this should be sent to the stable trees as well, right?
> >
> > Please add that when you resend...
>
> My understanding was that I should only send this to the stable branch if
> it fixes a real bug.
>
> Both myself and Laura can't see any actual problems that result from this
> issue, the change is more to help future proof the code.
>
> My commit message wasn't clear about this and could have mislead people
> into thinking there was a bug.
> I will update the commit message to make it clear that this issue doesn't
> currently result in any problem.
>
> Do you still want me to send it to the stable trees?
If it's not a bugfix, no need to. But please clean up your changelog
text as it implies that it is a bugfix...
thanks,
greg k-h
prev parent reply other threads:[~2018-02-16 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 6:16 [PATCH] staging: android: ion: Initialize dma_address of new sg list Liam Mark
2018-02-12 6:56 ` Dan Carpenter
2018-02-12 21:25 ` Liam Mark
2018-02-15 23:31 ` Laura Abbott
2018-02-16 17:45 ` Liam Mark
2018-02-16 16:23 ` Greg KH
2018-02-16 17:57 ` Liam Mark
2018-02-16 18:50 ` Greg KH [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=20180216185059.GC9616@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=devel@driverdev.osuosl.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lmark@codeaurora.org \
--cc=sumit.semwal@linaro.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