From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/2] UBI(FS): fixing IS_ENABLED() usage + backport trees
Date: Mon, 16 Jul 2012 09:34:19 +0300 [thread overview]
Message-ID: <1342420459.3213.3.camel@brekeke> (raw)
In-Reply-To: <CAN8TOE_zv1n_Ugx9YD2XYH2trnPhHuYdWOzg5g4v2jys5Eg=fw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
On Mon, 2012-07-02 at 09:13 -0700, Brian Norris wrote:
> On Wed, Jun 27, 2012 at 4:34 AM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Mon, 2012-06-18 at 16:31 -0700, Brian Norris wrote:
> >> 2) IS_ENABLED() has changed some between v3.3 and when this commit was
> >> originally integrated in mainline, so it masks a compile error in the
> >> mainline version
> >
> > Not sure what you mean. It was introduced in 3.1
> > (2a11c8ea20bf850b3a2c60db8c2e7497d28aba99), so I have to back-port it
> > older ubifs backport trees.
>
> I was referring to
> kconfig: fix IS_ENABLED to not require all options to be defined
> 69349c2dc01c489eccaa4c472542c08e370c6d7e
> which was introduced in 3.4. I think this masks some errors in your
> mainline patch, but when you backport between 3.1..3.4-rc2, you get
> compilation errors.
I think I fixed all the backport trees, thanks!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-07-16 6:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 23:31 [PATCH 0/2] UBI(FS): fixing IS_ENABLED() usage + backport trees Brian Norris
2012-06-18 23:31 ` [PATCH 1/2] UBIFS: correct usage of IS_ENABLED() Brian Norris
2012-06-18 23:31 ` [PATCH 2/2] UBI: " Brian Norris
2012-06-27 11:34 ` [PATCH 0/2] UBI(FS): fixing IS_ENABLED() usage + backport trees Artem Bityutskiy
2012-07-02 16:13 ` Brian Norris
2012-07-16 6:34 ` Artem Bityutskiy [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=1342420459.3213.3.camel@brekeke \
--to=dedekind1@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.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