public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Sebastian Reichel <sre@kernel.org>,
	Wolfram Sang <wsa@the-dreams.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Wolfram Sang <wsa@kernel.org>
Subject: Re: linux-next: manual merge of the battery tree with the i2c tree
Date: Mon, 12 Sep 2022 17:46:23 +1000	[thread overview]
Message-ID: <20220912174623.3a7f52b8@canb.auug.org.au> (raw)
In-Reply-To: <20220912073455.rlqf6q4rsgydk46h@pengutronix.de>

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

Hi Uwe,

On Mon, 12 Sep 2022 09:34:55 +0200 Uwe Kleine-König <u.kleine-koenig@pengutronix.de> wrote:
>
> On Mon, Sep 12, 2022 at 01:03:44PM +1000, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Today's linux-next merge of the battery tree got a conflict in:
> > 
> >   drivers/power/supply/cw2015_battery.c
> > 
> > between commit:
> > 
> >   ed5c2f5fd10d ("i2c: Make remove callback return void")
> > 
> > from the i2c tree and commit:
> > 
> >   ed5c2f5fd10d ("i2c: Make remove callback return void")
> > 
> > from the battery tree.  
> 
> The commit from the battery tree is
> 
> 	0cb172a4918e ("power: supply: cw2015: Use device managed API to simplify the code")

Yes, sorry, cut and paste fail :-(

> > I fixed it up (the latter removed the code modified by the former, so
> > I just did that)  
> 
> I don't see today's tag in git yet, but removing the code sounds right.

Good, and, yeah, I am still going :-)

-- 
Cheers,
Stephen Rothwell

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

      reply	other threads:[~2022-09-12  7:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12  3:03 linux-next: manual merge of the battery tree with the i2c tree Stephen Rothwell
2022-09-12  7:34 ` Uwe Kleine-König
2022-09-12  7:46   ` Stephen Rothwell [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=20220912174623.3a7f52b8@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sre@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=wsa@kernel.org \
    --cc=wsa@the-dreams.de \
    /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