All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: light.hsieh@mediatek.com, ulf.hansson@linaro.org
Cc: axboe@kernel.dk, kuohong.wang@mediatek.com,
	linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	linux-mediatek@lists.infradead.org, stanley.chu@mediatek.com
Subject: Re: [RESEND PATCH v1 0/3] set ro attribute of block device according to write-protection status
Date: Wed, 4 Mar 2020 15:42:46 +0100	[thread overview]
Message-ID: <ea744da4-5615-7353-9677-846d15695f48@gmail.com> (raw)
In-Reply-To: <1583291537-15053-1-git-send-email-light.hsieh@mediatek.com>

Hi Light,

You send this series 3 times and this one as a resend. Please check your mail
config, it seems there is something wrong with it.

Regards,
Matthias

On 04/03/2020 04:12, light.hsieh@mediatek.com wrote:
> From: Light Hsieh <light.hsieh@mediatek.com>
> 
>   set ro attribute of block device according to write-protection status
> 
> Light Hsieh (3):
>   mmc: record wp_grp_size and boot_wp_status
>   mmc: check write-protection status during BLKROSET ioctl
>   block: set partition read/write policy according to write-protection
>     status
> 
>  block/ioctl.c             |   2 +-
>  block/partition-generic.c |  10 +++
>  drivers/mmc/core/block.c  | 217 ++++++++++++++++++++++++++++++++++++++++++++++
>  drivers/mmc/core/mmc.c    |  16 ++++
>  include/linux/blkdev.h    |   1 +
>  include/linux/mmc/card.h  |   3 +
>  include/linux/mmc/mmc.h   |   2 +
>  7 files changed, 250 insertions(+), 1 deletion(-)
> 

WARNING: multiple messages have this Message-ID (diff)
From: Matthias Brugger <matthias.bgg@gmail.com>
To: light.hsieh@mediatek.com, ulf.hansson@linaro.org
Cc: axboe@kernel.dk, kuohong.wang@mediatek.com,
	linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
	linux-mediatek@lists.infradead.org, stanley.chu@mediatek.com
Subject: Re: [RESEND PATCH v1 0/3] set ro attribute of block device according to write-protection status
Date: Wed, 4 Mar 2020 15:42:46 +0100	[thread overview]
Message-ID: <ea744da4-5615-7353-9677-846d15695f48@gmail.com> (raw)
In-Reply-To: <1583291537-15053-1-git-send-email-light.hsieh@mediatek.com>

Hi Light,

You send this series 3 times and this one as a resend. Please check your mail
config, it seems there is something wrong with it.

Regards,
Matthias

On 04/03/2020 04:12, light.hsieh@mediatek.com wrote:
> From: Light Hsieh <light.hsieh@mediatek.com>
> 
>   set ro attribute of block device according to write-protection status
> 
> Light Hsieh (3):
>   mmc: record wp_grp_size and boot_wp_status
>   mmc: check write-protection status during BLKROSET ioctl
>   block: set partition read/write policy according to write-protection
>     status
> 
>  block/ioctl.c             |   2 +-
>  block/partition-generic.c |  10 +++
>  drivers/mmc/core/block.c  | 217 ++++++++++++++++++++++++++++++++++++++++++++++
>  drivers/mmc/core/mmc.c    |  16 ++++
>  include/linux/blkdev.h    |   1 +
>  include/linux/mmc/card.h  |   3 +
>  include/linux/mmc/mmc.h   |   2 +
>  7 files changed, 250 insertions(+), 1 deletion(-)
> 

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

  parent reply	other threads:[~2020-03-04 14:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04  3:12 [RESEND PATCH v1 0/3] set ro attribute of block device according to write-protection status light.hsieh
2020-03-04  3:12 ` light.hsieh
2020-03-04  3:12 ` [RESEND PATCH v1 1/3] mmc: record wp_grp_size and boot_wp_status light.hsieh
2020-03-04  3:12   ` light.hsieh
2020-03-04  3:12 ` [RESEND PATCH v1 2/3] mmc: check write-protection status during BLKROSET ioctl light.hsieh
2020-03-04  3:12   ` light.hsieh
2020-03-04  3:12 ` [RESEND PATCH v1 3/3] block: set partition read/write policy according to write-protection status light.hsieh
2020-03-04  3:12   ` light.hsieh
2020-03-04 14:42 ` Matthias Brugger [this message]
2020-03-04 14:42   ` [RESEND PATCH v1 0/3] set ro attribute of block device " Matthias Brugger

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=ea744da4-5615-7353-9677-846d15695f48@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=kuohong.wang@mediatek.com \
    --cc=light.hsieh@mediatek.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=stanley.chu@mediatek.com \
    --cc=ulf.hansson@linaro.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.