public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: mtip32xx: fix crash on surprise removal of the drive
Date: Tue, 23 Jun 2015 09:00:46 +0000	[thread overview]
Message-ID: <20150623090046.GI30834@mwanda> (raw)
In-Reply-To: <20150620123829.GA24933@mwanda>

On Tue, Jun 23, 2015 at 10:11:28AM +0200, Julia Lawall wrote:
> 
> 
> On Tue, 23 Jun 2015, Dan Carpenter wrote:
> 
> > On Mon, Jun 22, 2015 at 10:24:51AM -0700, Asai Thambi SP wrote:
> > >
> > >
> > > On 6/20/2015 5:38 AM, Dan Carpenter wrote:
> > > > Hello Asai Thambi SP,
> > > >
> > > > The patch 2132a544727e: "mtip32xx: fix crash on surprise removal of
> > > > the drive" from May 11, 2015, leads to the following static checker
> > > > warning:
> > > >
> > > > 	drivers/block/mtip32xx/mtip32xx.c:4489 mtip_pci_remove()
> > > > 	warn: 'dd' was already freed.
> > > Thanks Dan.
> > > We got this report as soon as patch was merged.
> >
> > I try to avoid sending duplicates.  Who sent you the report?  I looked
> > through my kbuild zero bot emails and I don't think they sent it to you.
> 
> I probably sent it.  My emails to the mailing list are probably all still
> being rejected.
> 

Oh yes.  That's it.  The other thing is that I was swamped in vacation
email backlog so I missed the original kbuild email.

To be honest, I don't feel bad about duplicates.  If people don't like
them, then they should stop introducing bugs!  :)

regards,
dan carpenter


      parent reply	other threads:[~2015-06-23  9:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-20 12:38 mtip32xx: fix crash on surprise removal of the drive Dan Carpenter
2015-06-22 17:24 ` Asai Thambi SP
2015-06-23  7:37 ` Dan Carpenter
2015-06-23  8:11 ` Julia Lawall
2015-06-23  9:00 ` Dan Carpenter [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=20150623090046.GI30834@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.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