From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
"Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: backports@vger.kernel.org
Subject: Re: [PATCH 2/2] backports: patches: update devcoredump patch
Date: Sun, 05 Jun 2016 17:00:46 +0200 [thread overview]
Message-ID: <1465138846.2304.0.camel@sipsolutions.net> (raw)
In-Reply-To: <1465119005-4161-2-git-send-email-arend.vanspriel@broadcom.com> (sfid-20160605_113018_707595_A6BA1018)
On Sun, 2016-06-05 at 11:30 +0200, Arend van Spriel wrote:
> Due to changes in include/linux/devcoredump.h the patch needs to
> be updated.
>
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> ---
> This patch is another shot at devcoredump patch. It just fixes
> applying the patch. However, the resulting file now uses the
> scatterlist function sg_pcopy_to_buffer() so that will need a
> backport for kernels before v3.11.
>
I think, in order to make the new dev_coredumpsg() [or whatever it's
called] function generally available, we have to also adjust the kernel
version where the backported one gets used.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2016-06-05 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-05 9:30 [PATCH 1/2] backports: add definition for USB_SPEED_SUPER_PLUS Arend van Spriel
2016-06-05 9:30 ` [PATCH 2/2] backports: patches: update devcoredump patch Arend van Spriel
2016-06-05 15:00 ` Johannes Berg [this message]
2016-06-06 8:58 ` Arend Van Spriel
2016-06-06 9:00 ` Johannes Berg
2016-06-06 9:10 ` Arend Van Spriel
2016-06-06 9:12 ` Johannes Berg
2016-06-06 9:35 ` Arend Van Spriel
2016-07-10 21:16 ` [PATCH 1/2] backports: add definition for USB_SPEED_SUPER_PLUS Hauke Mehrtens
2016-07-15 10:56 ` Arend Van Spriel
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=1465138846.2304.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=backports@vger.kernel.org \
--cc=mcgrof@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 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.