mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>, Greg KH <greg@kroah.com>,
	Arnd Bergmann <arnd@arndb.de>
Cc: Vinod Koul <vkoul@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Richard Fitzgerald <rf@opensource.cirrus.com>
Subject: Re: linux-next: manual merge of the soundwire tree with the sound-asoc-fixes tree
Date: Wed, 23 Jun 2021 17:56:05 +1000	[thread overview]
Message-ID: <20210623175605.20b012cc@canb.auug.org.au> (raw)
In-Reply-To: <20210622171936.1c147fbf@canb.auug.org.au>

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

Hi all,

On Tue, 22 Jun 2021 17:19:36 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the soundwire tree got a conflict in:
> 
>   include/linux/soundwire/sdw.h
> 
> between commit:
> 
>   d38ebaf2c884 ("soundwire: export sdw_update() and sdw_update_no_pm()")
> 
> from the sound-asoc-fixes tree and commit:
> 
>   031e668bc1ad ("soundwire: bus: Make sdw_nwrite() data pointer argument const")
> 
> from the soundwire tree.
> 
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
> 
> diff --cc include/linux/soundwire/sdw.h
> index de9802a24e7e,ddbeb00799e4..000000000000
> --- a/include/linux/soundwire/sdw.h
> +++ b/include/linux/soundwire/sdw.h
> @@@ -1040,10 -1039,7 +1039,10 @@@ int sdw_write(struct sdw_slave *slave, 
>   int sdw_write_no_pm(struct sdw_slave *slave, u32 addr, u8 value);
>   int sdw_read_no_pm(struct sdw_slave *slave, u32 addr);
>   int sdw_nread(struct sdw_slave *slave, u32 addr, size_t count, u8 *val);
> - int sdw_nwrite(struct sdw_slave *slave, u32 addr, size_t count, u8 *val);
> + int sdw_nwrite(struct sdw_slave *slave, u32 addr, size_t count, const u8 *val);
>  +int sdw_update(struct sdw_slave *slave, u32 addr, u8 mask, u8 val);
>  +int sdw_update_no_pm(struct sdw_slave *slave, u32 addr, u8 mask, u8 val);
>  +
>   int sdw_compare_devid(struct sdw_slave *slave, struct sdw_slave_id id);
>   void sdw_extract_slave_id(struct sdw_bus *bus, u64 addr, struct sdw_slave_id *id);
>   

This is now a conflict between the char-misc tree and the
sound-asoc-fixes tree.

-- 
Cheers,
Stephen Rothwell

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

      reply	other threads:[~2021-06-23  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22  7:19 Stephen Rothwell
2021-06-23  7:56 ` 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=20210623175605.20b012cc@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=greg@kroah.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=rf@opensource.cirrus.com \
    --cc=vkoul@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

all inboxes | Powered by JetHome®