public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Kitt <steve@sk2.org>
To: Wolfram Sang <wsa@kernel.org>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: remove the 2.6 "Upgrading I2C Drivers" guide
Date: Thu, 6 Aug 2020 09:09:26 +0200	[thread overview]
Message-ID: <20200806090800.08b77d4a@heffalump.sk2.org> (raw)
In-Reply-To: <20200805215351.GB2182@kunai>

[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]

Hi Wolfram,

On Wed, 5 Aug 2020 23:53:51 +0200, Wolfram Sang <wsa@kernel.org> wrote:
> On Wed, Aug 05, 2020 at 08:31:49PM +0200, Stephen Kitt wrote:
> > All the drivers have long since been upgraded, and all the important
> > information here is also included in the "Implementing I2C device
> > drivers" guide.
> > 
> > Signed-off-by: Stephen Kitt <steve@sk2.org>  
> 
> True! Thanks.
> 
> But I can't apply the patch?
> 
> > base-commit: 2324d50d051ec0f14a548e78554fb02513d6dcef  
> 
> Maybe because I don't have the commit in my tree? Can you rebase on top
> of 5.8?

Ah, yes, the commit is on top of Linus’ current master, following the merge
of docs-5.9 from Jon’s tree. In 5.8 the file is a .txt file, but Mauro
converted it to .rst for 5.9, and this patch removes the latter file (to
avoid a merge conflict later on...). If you prefer, I can submit it to the
docs tree instead!

> And please also remove the reference in Documentation/i2c/index.rst

Oops, yes, I’ll do that in v2 once we decide where it should go.

Regards,

Stephen

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-08-06 11:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 18:31 [PATCH] docs: remove the 2.6 "Upgrading I2C Drivers" guide Stephen Kitt
2020-08-05 21:53 ` Wolfram Sang
2020-08-06  7:09   ` Stephen Kitt [this message]
2020-08-06  8:33     ` Wolfram Sang
2020-08-06 16:13       ` Stephen Kitt

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=20200806090800.08b77d4a@heffalump.sk2.org \
    --to=steve@sk2.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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