All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: HuKeping <hukeping@huawei.com>
Cc: linux-kernel@vger.kernel.org, matt.fleming@intel.com,
	cbouatmailru@gmail.com, ccross@android.com,
	keescook@chromium.org, tony.luck@intel.com,
	stable@vger.kernel.org, rob.herring@calxeda.com, cxie@redhat.com,
	sdu.liu@huawei.com, wangnan0@huawei.com, peifeiyue@huawei.com
Subject: Re: [PATCH v3 0/2][request for stable inclusion] several pstore related bugfixs
Date: Mon, 2 Feb 2015 19:47:51 -0800	[thread overview]
Message-ID: <20150203034751.GD15566@kroah.com> (raw)
In-Reply-To: <1422432386-15761-1-git-send-email-hukeping@huawei.com>

On Wed, Jan 28, 2015 at 04:06:24PM +0800, HuKeping wrote:
> Hi greg,
> We want to use pstore on linux 3.10. But we found several bugfixs have not
> been merged yet. Most of them are obvious and can be cherry-picked cleanly.
> Would you please apply them to stable 3.10?
> 
> v1 -> v2:
>  - remove d4bf205da618bbd0b038e404d646f14e76915718 which has already been merged
>  - adjust 0405a5cec3406f19e69da07c8111a6bf1088ac29
> 
> v2 -> v3:
>  - attach commit to pstore/ram: avoid atomic accesses for ioremapped regions
> 
> PART 1: patches that can be cleanly applied:
> 
>  bf2883339a33b7544b92ea465b90c3de55082032
>  pstore: Fail to unlink if a driver has not defined pstore_erase
>  
>  c39524e6744284452ef45480d3153bec28960c32
>  pstore: d_alloc_name() doesn't return an ERR_PTR
>  
>  57fd835385a043577457a385f28c08be693991bf
>  pstore: clarify clearing of _read_cnt in ramoops_context
>  
>  aa9a4a1edfbd3d223af01db833da2f07850bc655
>  pstore: skip zero size persistent ram buffer in traverse
>  
>  b0aa931fb84431394d995472d0af2a6c2b61064d
>  pstore: Fix NULL pointer fault if get NULL prz in ramoops_get_next_prz
>  
> PART 2: pathes that should be adjusted:
> 
>  Rob Herring (1):
>   pstore/ram: avoid atomic accesses for ioremapped regions
> 
>  fs/pstore/ram_core.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++--
>  1 file changed, 52 insertions(+), 2 deletions(-)
> 
>  Madper Xie (1):
>   efi-pstore: Make efi-pstore return a unique id
> 
>  drivers/firmware/efi/efi-pstore.c | 18 +++++++++++++-----
>  1 file changed, 13 insertions(+), 5 deletions(-)

All now applied, along with some of these for 3.14, thanks.

greg k-h

      parent reply	other threads:[~2015-02-03  3:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28  8:06 [PATCH v3 0/2][request for stable inclusion] several pstore related bugfixs HuKeping
2015-01-28  8:06 ` [PATCH v3 1/2] pstore/ram: avoid atomic accesses for ioremapped regions HuKeping
2015-01-28  8:06 ` [PATCH v3 2/2] efi-pstore: Make efi-pstore return a unique id HuKeping
2015-02-03  3:47 ` Greg KH [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=20150203034751.GD15566@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=cbouatmailru@gmail.com \
    --cc=ccross@android.com \
    --cc=cxie@redhat.com \
    --cc=hukeping@huawei.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=peifeiyue@huawei.com \
    --cc=rob.herring@calxeda.com \
    --cc=sdu.liu@huawei.com \
    --cc=stable@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=wangnan0@huawei.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.