public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: emilgoode@gmail.com (Emil Goode)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx: introduce function imx_free_mx3_camera
Date: Sat, 24 May 2014 17:22:00 +0200	[thread overview]
Message-ID: <20140524152200.GA4666@lianli> (raw)
In-Reply-To: <20140522181024.GA20155@pengutronix.de>

Hello Uwe and Greg,

> You'd do a better deed if you picked up
> http://thread.gmane.org/gmane.linux.kernel/1613364/focus=1635995

Since there is nothing wrong with the last version of the patch in
the above thread, I feel strange about picking it up and just splitting
it into two patches. However it would be good to have it applied.

I think the reason why the author didn't resend is that the object file
and data structure layout information in the changelog depend on the
changes to both .name and .dma_mask and by splitting the patch this
information would not apply to any one of the resulting two patches.

Perhaps keeping this information in the changelog is a good reason for
applying the patch as it is?

(I have attached the patch in question)

Best regards,

Emil Goode
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-driver-core-platform-don-t-leak-memory-allocated-for.patch
Type: text/x-diff
Size: 9958 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140524/e1732228/attachment-0001.bin>

  parent reply	other threads:[~2014-05-24 15:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 17:51 [PATCH] ARM: imx: introduce function imx_free_mx3_camera Emil Goode
2014-05-22 18:10 ` Uwe Kleine-König
2014-05-22 18:58   ` Emil Goode
2014-05-23  6:50   ` Philippe Rétornaz
2014-05-24 15:22   ` Emil Goode [this message]
2014-05-24 20:05     ` Greg Kroah-Hartman
2014-05-24 21:17       ` Uwe Kleine-König
2014-05-22 20:44 ` Dan Carpenter

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=20140524152200.GA4666@lianli \
    --to=emilgoode@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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