All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jian Dong <dj0227@163.com>
To: Mark Brown <broonie@kernel.org>
Cc: matthias.bgg@gmail.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, huyue2@yulong.com,
	Jian Dong <dongjian@yulong.com>
Subject: Re: [PATCH] regulator: mt6360: remove redundant error print
Date: Wed, 24 Mar 2021 09:24:35 +0800	[thread overview]
Message-ID: <20210324092435.00000343@163.com> (raw)
In-Reply-To: <20210323171628.GA9323@sirena.org.uk>

On Tue, 23 Mar 2021 17:16:28 +0000
Mark Brown <broonie@kernel.org> wrote:

> On Tue, Mar 23, 2021 at 08:22:41PM +0800, Jian Dong wrote:
> > From: Jian Dong <dongjian@yulong.com>
> > 
> > fixes coccicheck warning:
> > 
> > drivers/regulator/mt6360-regulator.c:384:3-10: line 384 is
> > redundant because platform_get_irq() already prints an error  
> 
> This doesn't apply against current code, please check and resend.
> 
> Applying: regulator: mt6360: remove redundant error print
> error: sha1 information is lacking or useless
> (drivers/regulator/mt6360-regulator.c). error: could not build fake
> ancestor Patch failed at 0001 regulator: mt6360: remove redundant
> error print

Hi 

I find the problem, before this patch, I had commit a patch 
"[PATCH]regulator: Use IRQF_ONESHOT", and it hasn't be accepted now, So
the current code is different.

I will modify and resend later.  


_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Jian Dong <dj0227@163.com>
To: Mark Brown <broonie@kernel.org>
Cc: matthias.bgg@gmail.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, huyue2@yulong.com,
	Jian Dong <dongjian@yulong.com>
Subject: Re: [PATCH] regulator: mt6360: remove redundant error print
Date: Wed, 24 Mar 2021 09:24:35 +0800	[thread overview]
Message-ID: <20210324092435.00000343@163.com> (raw)
In-Reply-To: <20210323171628.GA9323@sirena.org.uk>

On Tue, 23 Mar 2021 17:16:28 +0000
Mark Brown <broonie@kernel.org> wrote:

> On Tue, Mar 23, 2021 at 08:22:41PM +0800, Jian Dong wrote:
> > From: Jian Dong <dongjian@yulong.com>
> > 
> > fixes coccicheck warning:
> > 
> > drivers/regulator/mt6360-regulator.c:384:3-10: line 384 is
> > redundant because platform_get_irq() already prints an error  
> 
> This doesn't apply against current code, please check and resend.
> 
> Applying: regulator: mt6360: remove redundant error print
> error: sha1 information is lacking or useless
> (drivers/regulator/mt6360-regulator.c). error: could not build fake
> ancestor Patch failed at 0001 regulator: mt6360: remove redundant
> error print

Hi 

I find the problem, before this patch, I had commit a patch 
"[PATCH]regulator: Use IRQF_ONESHOT", and it hasn't be accepted now, So
the current code is different.

I will modify and resend later.  


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Jian Dong <dj0227@163.com>
To: Mark Brown <broonie@kernel.org>
Cc: matthias.bgg@gmail.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, huyue2@yulong.com,
	Jian Dong <dongjian@yulong.com>
Subject: Re: [PATCH] regulator: mt6360: remove redundant error print
Date: Wed, 24 Mar 2021 09:24:35 +0800	[thread overview]
Message-ID: <20210324092435.00000343@163.com> (raw)
In-Reply-To: <20210323171628.GA9323@sirena.org.uk>

On Tue, 23 Mar 2021 17:16:28 +0000
Mark Brown <broonie@kernel.org> wrote:

> On Tue, Mar 23, 2021 at 08:22:41PM +0800, Jian Dong wrote:
> > From: Jian Dong <dongjian@yulong.com>
> > 
> > fixes coccicheck warning:
> > 
> > drivers/regulator/mt6360-regulator.c:384:3-10: line 384 is
> > redundant because platform_get_irq() already prints an error  
> 
> This doesn't apply against current code, please check and resend.
> 
> Applying: regulator: mt6360: remove redundant error print
> error: sha1 information is lacking or useless
> (drivers/regulator/mt6360-regulator.c). error: could not build fake
> ancestor Patch failed at 0001 regulator: mt6360: remove redundant
> error print

Hi 

I find the problem, before this patch, I had commit a patch 
"[PATCH]regulator: Use IRQF_ONESHOT", and it hasn't be accepted now, So
the current code is different.

I will modify and resend later.  


  reply	other threads:[~2021-03-24  1:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 12:22 [PATCH] regulator: mt6360: remove redundant error print Jian Dong
2021-03-23 12:22 ` Jian Dong
2021-03-23 12:22 ` Jian Dong
2021-03-23 17:16 ` Mark Brown
2021-03-23 17:16   ` Mark Brown
2021-03-23 17:16   ` Mark Brown
2021-03-24  1:24   ` Jian Dong [this message]
2021-03-24  1:24     ` Jian Dong
2021-03-24  1:24     ` Jian Dong
2021-03-24 23:39 ` Mark Brown
2021-03-24 23:39   ` Mark Brown
2021-03-24 23:39   ` Mark Brown

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=20210324092435.00000343@163.com \
    --to=dj0227@163.com \
    --cc=broonie@kernel.org \
    --cc=dongjian@yulong.com \
    --cc=huyue2@yulong.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.