From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Wolfram Sang <wsa@kernel.org>,
Evan Nimmo <Evan.Nimmo@alliedtelesis.co.nz>,
"andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"jarkko.nikula@linux.intel.com" <jarkko.nikula@linux.intel.com>,
"jdelvare@suse.de" <jdelvare@suse.de>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/1] i2c: algo-pca: Reapply i2c bus settings after reset
Date: Mon, 14 Sep 2020 11:51:04 +0300 [thread overview]
Message-ID: <CAHp75Vf-1vqHjqNixXtnziCd6squwwj0sEArZ8C1YiDwafhk7Q@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VdtE_UBsNrSxbVPprmp7=-iVCrXv9x6Tu82b4q2ODfKQg@mail.gmail.com>
On Mon, Sep 14, 2020 at 11:50 AM Andy Shevchenko
<andy.shevchenko@gmail.com> wrote:
>
> On Mon, Sep 14, 2020 at 12:27 AM Chris Packham
> <Chris.Packham@alliedtelesis.co.nz> wrote:
> > On 12/09/20 7:45 am, Wolfram Sang wrote:
>
> > I'm happy to route it to stable@ if you think it's worth it but I don't
> > think there's a specific Fixes: reference that can be used. The current
> > behavior appears to have been that way since before git (looks like we
> > noticed in 2014 but it's taken me 6 years to nag people into sending
> > their fixes upstream).
>
> JFYI: there is a history.git repository from History Group on
> kernel.org. You may dig till the very beginning of the kernel (yes,
> it's not properly formed Git history, but it will give you a hash
> commit as a reference.
Stephen, btw, does your scripts that validate Fixes, take into
consideration references to history.git?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-09-14 8:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 20:32 [PATCH v4 1/1] i2c: algo-pca: Reapply i2c bus settings after reset Evan Nimmo
2020-09-09 8:23 ` Wolfram Sang
2020-09-09 20:39 ` Chris Packham
2020-09-11 19:45 ` Wolfram Sang
2020-09-13 21:23 ` Chris Packham
2020-09-14 6:49 ` Wolfram Sang
2020-09-14 20:50 ` Chris Packham
2020-09-14 8:50 ` Andy Shevchenko
2020-09-14 8:51 ` Andy Shevchenko [this message]
2020-09-14 10:42 ` Stephen Rothwell
2020-09-14 11:01 ` Andy Shevchenko
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=CAHp75Vf-1vqHjqNixXtnziCd6squwwj0sEArZ8C1YiDwafhk7Q@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=Evan.Nimmo@alliedtelesis.co.nz \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wsa@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 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).