From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: William Breathitt Gray <vilhelm.gray@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Driver core update for 4.7-rc1
Date: Fri, 20 May 2016 22:04:38 -0700 [thread overview]
Message-ID: <20160521050438.GA9445@kroah.com> (raw)
In-Reply-To: <CA+55aFxPyXS-RKx+mOBB7_U+XdqXyeXzAT8wnNuKJ3rQwoEU2g@mail.gmail.com>
On Fri, May 20, 2016 at 09:51:18PM -0700, Linus Torvalds wrote:
> On Fri, May 20, 2016 at 8:23 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > William Breathitt Gray (13):
> > base: isa: Remove X86_32 dependency
> > isa: Decouple X86_32 dependency from the ISA Kconfig option
>
> So I'm going to revert these unless I get
>
> (a) a good reason for them
>
> (b) patches to get rid of the incessant warnings these cause.
What warnings? I haven't seen any reports of warnings, what .config
causes them?
> Most of the ISA drivers are not 64-bit safe. They give compiler
> warnings, and they will definitely simply not work. So just blindly
> enabling that shit is not the answer.
>
> We've never needed this before, why do we need it now?
I'll let William answer that, it seems he has some crazy isa hardware
for x86_64 platforms...
thanks,
greg k-h
next prev parent reply other threads:[~2016-05-21 5:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 3:23 [GIT PULL] Driver core update for 4.7-rc1 Greg KH
2016-05-21 4:51 ` Linus Torvalds
2016-05-21 5:04 ` Greg KH [this message]
2016-05-21 5:20 ` Linus Torvalds
2016-05-21 5:39 ` Greg KH
2016-05-21 6:01 ` Linus Torvalds
2016-05-21 16:20 ` William Breathitt Gray
2016-05-21 16:31 ` Linus Torvalds
2016-05-21 16:59 ` Linus Torvalds
2016-05-21 17:16 ` William Breathitt Gray
2016-05-21 17:23 ` Linus Torvalds
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=20160521050438.GA9445@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vilhelm.gray@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.