From: Greg KH <gregkh@linuxfoundation.org>
To: James Hogan <james.hogan@mips.com>
Cc: clabbe.montjoie@gmail.com, ralf@linux-mips.org,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "MIPS: Fix typo BIG_ENDIAN to CPU_BIG_ENDIAN" has been added to the 4.15-stable tree
Date: Tue, 20 Feb 2018 16:51:19 +0100 [thread overview]
Message-ID: <20180220155119.GA28139@kroah.com> (raw)
In-Reply-To: <20180220153244.GD29460@jhogan-linux.mipstec.com>
On Tue, Feb 20, 2018 at 03:32:44PM +0000, James Hogan wrote:
> Hi Greg,
>
> On Tue, Feb 20, 2018 at 12:10:06PM +0100, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > MIPS: Fix typo BIG_ENDIAN to CPU_BIG_ENDIAN
> >
> > to the 4.15-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > mips-fix-typo-big_endian-to-cpu_big_endian.patch
> > and it can be found in the queue-4.15 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> FYI this will introduce the following harmless kconfig warnings which
> are fixed by commit ec897569ad7d ("usb: Move USB_UHCI_BIG_ENDIAN_* out
> of USB_SUPPORT"):
>
> warning: (MIPS_GENERIC) selects USB_UHCI_BIG_ENDIAN_MMIO which has unmet direct dependencies (USB_SUPPORT && USB)
> warning: (MIPS_GENERIC) selects USB_UHCI_BIG_ENDIAN_DESC which has unmet direct dependencies (USB_SUPPORT && USB)
>
> If anybody cares about such warnings, that patch could be applied also.
I'll go queue that up too, thanks.
greg k-h
prev parent reply other threads:[~2018-02-20 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 11:10 Patch "MIPS: Fix typo BIG_ENDIAN to CPU_BIG_ENDIAN" has been added to the 4.15-stable tree gregkh
2018-02-20 15:32 ` James Hogan
2018-02-20 15:51 ` Greg KH [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=20180220155119.GA28139@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=clabbe.montjoie@gmail.com \
--cc=james.hogan@mips.com \
--cc=ralf@linux-mips.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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 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.