From: Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH v3 5/5] staging: lustre: libcfs.h: remove IS_PO2 and __is_po2
Date: Sat, 7 Nov 2015 12:03:41 +0200 [thread overview]
Message-ID: <20151107100341.GA2852@waves> (raw)
In-Reply-To: <20151107011109.GB7495@kroah.com>
On Fri, Nov 06, 2015 at 05:11:09PM -0800, Greg KH wrote:
> On Thu, Oct 29, 2015 at 03:00:24AM +0200, Aya Mahfouz wrote:
> > Removes IS_PO2 and __is_po2 since the uses of IS_PO2 have
> > been replaced by is_power_of_2
> >
> > Signed-off-by: Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>
> > ---
> > v2:
> > -became patch number 5 in the series
> > v3:
> > -no change
> >
> > drivers/staging/lustre/include/linux/libcfs/libcfs.h | 7 -------
> > 1 file changed, 7 deletions(-)
>
> I can't take this yet, as your patch 2/5 didn't apply :(
No, problems. I understand that it is hard for these patches to apply as
is given that they are quite old. I will recheck if there are new uses
of them and resend this patch alone or in another patchset.
Thanks,
--
Kind Regards,
Aya Saif El-yazal Mahfouz
prev parent reply other threads:[~2015-11-07 10:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 0:52 [lustre-devel] [PATCH v3 0/5] Remove uses and definition of IS_PO2 Aya Mahfouz
2015-10-29 0:54 ` [lustre-devel] [PATCH v3 1/5] staging: lustre: ldlm_extent.c: replace IS_PO2 by is_power_of_2 Aya Mahfouz
2015-10-29 0:55 ` [lustre-devel] [PATCH v3 2/5] staging: lustre: hash.c: Replace " Aya Mahfouz
2015-11-07 1:10 ` Greg KH
2015-10-29 0:57 ` [lustre-devel] [PATCH v3 3/5] staging: lustre: workitem.c: replace " Aya Mahfouz
2015-10-29 0:59 ` [lustre-devel] [PATCH v3 4/5] staging: lustre: selftest.h: " Aya Mahfouz
2015-10-29 1:00 ` [lustre-devel] [PATCH v3 5/5] staging: lustre: libcfs.h: remove IS_PO2 and __is_po2 Aya Mahfouz
2015-11-07 1:11 ` Greg KH
2015-11-07 10:03 ` Aya Mahfouz [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=20151107100341.GA2852@waves \
--to=mahfouz.saif.elyazal@gmail.com \
--cc=lustre-devel@lists.lustre.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.