From: Wolfram Sang <wsa@the-dreams.de>
To: Matthew Weber <matthew.weber@rockwellcollins.com>
Cc: linux-i2c@vger.kernel.org, soren.brinkmann@xilinx.com,
John Linn <john.linn@xilinx.com>,
Paresh Chaudhary <paresh.chaudhary@rockwellcollins.com>
Subject: Re: [PATCH 1/1] i2c: cadance: (bugfix) ctrl/addr reg write order
Date: Thu, 22 Jun 2017 15:26:11 +0200 [thread overview]
Message-ID: <20170622132610.GB3820@katana> (raw)
In-Reply-To: <CANQCQpbmhfD0jgW2bQm6hjR_CTJiPHbNE_jfU9uicH7PVd6xjg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
> Not urgent, fell free to work it in where it makes sense. We're on a
> older LTS at this point and will carry the patch.
Okay then. I'll add it to 4.13.
> For the Fixes: tag in this case, should I just prefix my last
> statement about the issue as there isn't a public bug report or
> specific commit I can note? I could add cadence ref manual section
> and a link to a public download of the doc.
The Fixes: tag is for specifying the commit ID which introduced the bug.
So, all stable kernel versions having that commit ID know they want the
patch carrying the Fixes: tag. I can look it up as well, but it makes my
life easier if I get it provided. No worries!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-06-22 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 1:45 [PATCH 1/1] i2c: cadance: (bugfix) ctrl/addr reg write order Matt Weber
2017-06-22 8:35 ` Wolfram Sang
2017-06-22 11:34 ` Matthew Weber
2017-06-22 13:26 ` Wolfram Sang [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=20170622132610.GB3820@katana \
--to=wsa@the-dreams.de \
--cc=john.linn@xilinx.com \
--cc=linux-i2c@vger.kernel.org \
--cc=matthew.weber@rockwellcollins.com \
--cc=paresh.chaudhary@rockwellcollins.com \
--cc=soren.brinkmann@xilinx.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;
as well as URLs for NNTP newsgroup(s).