From: <gregkh@linuxfoundation.org> To: chenhc@lemote.com, chenhuacai@gmail.com, gregkh@linuxfoundation.org, james.hogan@mips.com, linux-mips@linux-mips.org, paul.burton@mips.com, wuzhangjin@gmail.com, zhangfx@lemote.com Cc: <stable-commits@vger.kernel.org> Subject: Patch "MIPS: io: Add barrier after register read in inX()" has been added to the 4.4-stable tree Date: Sun, 01 Jul 2018 13:39:02 +0200 [thread overview] Message-ID: <15304451421364@kroah.com> (raw) This is a note to let you know that I've just added the patch titled MIPS: io: Add barrier after register read in inX() to the 4.4-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-io-add-barrier-after-register-read-in-inx.patch and it can be found in the queue-4.4 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.
WARNING: multiple messages have this Message-ID (diff)
From: <gregkh@linuxfoundation.org> To: chenhc@lemote.com, chenhuacai@gmail.com, gregkh@linuxfoundation.org, james.hogan@mips.com, linux-mips@linux-mips.org, paul.burton@mips.com, wuzhangjin@gmail.com, zhangfx@lemote.com Cc: stable-commits@vger.kernel.org Subject: Patch "MIPS: io: Add barrier after register read in inX()" has been added to the 4.4-stable tree Date: Sun, 01 Jul 2018 13:39:02 +0200 [thread overview] Message-ID: <15304451421364@kroah.com> (raw) Message-ID: <20180701113902.5aqr4cK7G1CfcqwvLp2REo02qUxcIAcgqKiwzOactPw@z> (raw) This is a note to let you know that I've just added the patch titled MIPS: io: Add barrier after register read in inX() to the 4.4-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-io-add-barrier-after-register-read-in-inx.patch and it can be found in the queue-4.4 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.
next reply other threads:[~2018-07-01 11:40 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-07-01 11:39 gregkh [this message] 2018-07-01 11:39 ` Patch "MIPS: io: Add barrier after register read in inX()" has been added to the 4.4-stable tree gregkh
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=15304451421364@kroah.com \ --to=gregkh@linuxfoundation.org \ --cc=chenhc@lemote.com \ --cc=chenhuacai@gmail.com \ --cc=james.hogan@mips.com \ --cc=linux-mips@linux-mips.org \ --cc=paul.burton@mips.com \ --cc=stable-commits@vger.kernel.org \ --cc=wuzhangjin@gmail.com \ --cc=zhangfx@lemote.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: linkBe 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.