From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
Salah Triki <salah.triki@acm.org>,
dwmw2@infradead.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] jffs2: Remove NULL checks from jffs2_destroy_slab_caches
Date: Thu, 6 Aug 2015 23:27:51 +0900 [thread overview]
Message-ID: <20150806142751.GC4292@swordfish> (raw)
In-Reply-To: <alpine.DEB.2.10.1508060923250.2343@hadrien>
On (08/06/15 09:24), Julia Lawall wrote:
> > >
> > > Please provide the appropriate context next time. And for the moment, I will
> > > not apply this, because this does not work on the current MTD development tree.
> > > Try your patch bomb on the next release, as it's not worth my time to
> > > cross-merge a -next branch just for a "cleanup".
> > >
> >
> > Julia already has a patch set to cleanup all the existing users
> > (not published yet, though).
>
> We should probably have put our patches into a series. Because it is true
> that the cleanup patch breaks existing code. So one has to be aware of
> the dependency between them.
>
I guess we can wait until 3 patches in question will land in Linus's
tree. What do you think?
-ss
prev parent reply other threads:[~2015-08-06 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 19:46 [PATCH] jffs2: Remove NULL checks from jffs2_destroy_slab_caches Salah Triki
2015-08-04 20:02 ` Richard Weinberger
2015-08-04 20:06 ` Brian Norris
2015-08-05 13:32 ` Sergey Senozhatsky
2015-08-05 22:17 ` Salah Triki
2015-08-05 23:12 ` Salah Triki
2015-08-06 6:16 ` Julia Lawall
2015-08-06 14:17 ` Sergey Senozhatsky
2015-08-06 7:24 ` Julia Lawall
2015-08-06 14:27 ` Sergey Senozhatsky [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=20150806142751.GC4292@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=julia.lawall@lip6.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=salah.triki@acm.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).