linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the counters tree with the ipmi tree
@ 2020-10-12  8:13 Stephen Rothwell
  2020-10-15  5:54 ` Stephen Rothwell
  0 siblings, 1 reply; 2+ messages in thread
From: Stephen Rothwell @ 2020-10-12  8:13 UTC (permalink / raw)
  To: Shuah Khan, Corey Minyard
  Cc: Linux Kernel Mailing List, Linux Next Mailing List, Xianting Tian

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

Hi all,

Today's linux-next merge of the counters tree got a conflict in:

  drivers/char/ipmi/ipmi_msghandler.c

between commit:

  f8910ffa81b0 ("ipmi:msghandler: retry to get device id on an error")

from the ipmi tree and commit:

  dc87264ac991 ("drivers/char/ipmi: convert stats to use counter_atomic32")

from the counters 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.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/char/ipmi/ipmi_msghandler.c
index 8774a3b8ff95,36c0b1be22fb..000000000000
--- a/drivers/char/ipmi/ipmi_msghandler.c
+++ b/drivers/char/ipmi/ipmi_msghandler.c
@@@ -34,7 -34,7 +34,8 @@@
  #include <linux/uuid.h>
  #include <linux/nospec.h>
  #include <linux/vmalloc.h>
 +#include <linux/delay.h>
+ #include <linux/counters.h>
  
  #define IPMI_DRIVER_VERSION "39.2"
  

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: linux-next: manual merge of the counters tree with the ipmi tree
  2020-10-12  8:13 linux-next: manual merge of the counters tree with the ipmi tree Stephen Rothwell
@ 2020-10-15  5:54 ` Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2020-10-15  5:54 UTC (permalink / raw)
  To: Corey Minyard
  Cc: Shuah Khan, Linux Kernel Mailing List, Linux Next Mailing List,
	Xianting Tian

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

Hi all,

On Mon, 12 Oct 2020 19:13:40 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Today's linux-next merge of the counters tree got a conflict in:
> 
>   drivers/char/ipmi/ipmi_msghandler.c
> 
> between commit:
> 
>   f8910ffa81b0 ("ipmi:msghandler: retry to get device id on an error")
> 
> from the ipmi tree and commit:
> 
>   dc87264ac991 ("drivers/char/ipmi: convert stats to use counter_atomic32")
> 
> from the counters 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 drivers/char/ipmi/ipmi_msghandler.c
> index 8774a3b8ff95,36c0b1be22fb..000000000000
> --- a/drivers/char/ipmi/ipmi_msghandler.c
> +++ b/drivers/char/ipmi/ipmi_msghandler.c
> @@@ -34,7 -34,7 +34,8 @@@
>   #include <linux/uuid.h>
>   #include <linux/nospec.h>
>   #include <linux/vmalloc.h>
>  +#include <linux/delay.h>
> + #include <linux/counters.h>
>   
>   #define IPMI_DRIVER_VERSION "39.2"
>   

This is now a conflict between the counters tree and Linus' tree.

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-10-15  5:54 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-12  8:13 linux-next: manual merge of the counters tree with the ipmi tree Stephen Rothwell
2020-10-15  5:54 ` Stephen Rothwell

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).