From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/2] Get rid of kmem_realloc()
Date: Tue, 18 Aug 2020 08:18:01 -0700 [thread overview]
Message-ID: <20200818151801.GJ6107@magnolia> (raw)
In-Reply-To: <20200818100720.oiwqk3yi2dsvjqav@eorzea>
On Tue, Aug 18, 2020 at 12:07:20PM +0200, Carlos Maiolino wrote:
> On Mon, Aug 17, 2020 at 08:39:22AM -0700, Darrick J. Wong wrote:
> > On Mon, Aug 17, 2020 at 12:17:16PM +0200, Carlos Maiolino wrote:
> > > On Mon, Aug 17, 2020 at 07:55:33AM +0100, Christoph Hellwig wrote:
> > > > Both patches looks good:
> > > >
> > > > Reviewed-by: Christoph Hellwig <hch@lst.de>
> > > >
> > > > although personally I would have simply sent them as a single patch.
> > >
> > > Thanks Christoph. I have no preference, I just submitted the patches according
> > > to what I was doing, 'remove users, nothing broke? Remove functions', but I
> > > particularly have no preference, Darrick, if the patches need to be merged just
> > > give me a heads up.
> >
> > Yes, the two patches are simple enough that they ought to be merged.
>
> Ok, you want me to resend or it's just a heads up for the next time?
Yes please. You've got plenty of time. :)
(FWIW I'll probably put this in for-next after -rc6, though I guess it
mostly depends on whether or not anyone tries to land any huge patchsets
this cycle that would clash with this...)
--D
>
>
> --
> Carlos
>
prev parent reply other threads:[~2020-08-18 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 14:26 [PATCH 0/2] Get rid of kmem_realloc() Carlos Maiolino
2020-08-13 14:26 ` [PATCH 1/2] xfs: remove kmem_realloc() users Carlos Maiolino
2020-08-13 14:26 ` [PATCH 2/2] xfs: remove kmem_realloc() Carlos Maiolino
2020-08-17 6:55 ` [PATCH 0/2] Get rid of kmem_realloc() Christoph Hellwig
2020-08-17 10:17 ` Carlos Maiolino
2020-08-17 15:39 ` Darrick J. Wong
2020-08-18 10:07 ` Carlos Maiolino
2020-08-18 15:18 ` Darrick J. Wong [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=20200818151801.GJ6107@magnolia \
--to=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-xfs@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