From: Rich Felker <dalias@libc.org>
To: jacopo mondi <jacopo@jmondi.org>
Cc: Christoph Hellwig <hch@infradead.org>,
ysato@users.sourceforge.jp, thomas.petazzoni@free-electrons.com,
robin.murphy@arm.com, geert@linux-m68k.org,
sergei.shtylyov@cogentembedded.com,
linux-renesas-soc@vger.kernel.org, linux-sh@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] sh: mm: Fix unprotected access to struct device
Date: Sat, 5 May 2018 16:45:13 -0400 [thread overview]
Message-ID: <20180505204513.GF1392@brightrain.aerifal.cx> (raw)
In-Reply-To: <20180503071539.GA19612@w540>
On Thu, May 03, 2018 at 09:15:39AM +0200, jacopo mondi wrote:
> Hi Christoph,
>
> On Wed, May 02, 2018 at 05:39:09AM -0700, Christoph Hellwig wrote:
> > On Wed, May 02, 2018 at 09:46:31AM +0200, jacopo mondi wrote:
> > > Hi again Christoph,
> > >
> > > The gentle ping actually applies to this version of the patch.
> > >
> > > Sorry for the confusion.
> >
> > I'd expect this to go in through the sh tree, but if the sh maintainers
> > are fine with it I can take it through the dma-mapping tree.
>
> Oh, that's fine then. I'll let Rich comment if he plans to send a pull
> requets for v4.17 fixes or not.
OK, I'll prepare a pull request with this and another fix I just made.
Rich
prev parent reply other threads:[~2018-05-05 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 9:42 [PATCH v3] sh: mm: Fix unprotected access to struct device Jacopo Mondi
2018-05-02 7:46 ` jacopo mondi
2018-05-02 12:39 ` Christoph Hellwig
2018-05-03 7:15 ` jacopo mondi
2018-05-05 20:45 ` Rich Felker [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=20180505204513.GF1392@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=hch@infradead.org \
--cc=jacopo@jmondi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=ysato@users.sourceforge.jp \
/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).