From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Richard Weinberger <richard@nod.at>,
Mike Snitzer <snitzer@redhat.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] UBI: fix rb_tree node comparison in add_map
Date: Tue, 13 May 2014 12:08:09 +0300 [thread overview]
Message-ID: <1399972089.1797.29.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20140510011913.GH28907@ld-irv-0074>
On Fri, 2014-05-09 at 18:19 -0700, Brian Norris wrote:
> Hi Artem,
>
> On Sat, Mar 22, 2014 at 12:56:59AM +0100, Richard Weinberger wrote:
> > Am 21.03.2014 20:54, schrieb Mike Snitzer:
> > > The comparisons used in add_vol() shouldn't be identical. Pretty sure
> > > the following is correct but it is completely untested.
> > >
> > > Signed-off-by: Mike Snitzer <snitzer@redhat.com>
> > > ---
> > > drivers/mtd/ubi/fastmap.c | 4 ++--
> > > 1 files changed, 2 insertions(+), 2 deletions(-)
> > >
> > > NOTE: I stumbled upon this code while implementing some rb_tree code
> > > (and looking for some existing rb_tree code as a reference).
> >
> > Thanks a lot for pointing this out!
> >
> > Acked-by: Richard Weinberger <richard@nod.at>
>
> Bump?
>
> I'm passing through my queue, and I occasionally see some obvious,
> reviewed fixes like this one. Typically, you get around to them
> eventually, but you never know. Do you prefer the "bump"?
I'll pick this now, thanks for pointing. And yes, a "bump" is helpful.
E.g., I missed this ones.
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2014-05-13 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 19:54 Mike Snitzer
2014-03-21 23:56 ` Richard Weinberger
2014-05-10 1:19 ` Brian Norris
2014-05-13 9:08 ` Artem Bityutskiy [this message]
2014-05-13 10:48 ` Artem Bityutskiy
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=1399972089.1797.29.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=snitzer@redhat.com \
/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
Powered by JetHome